We use Cisco VPN Software to access the office from home, Starbucks, etc.
There are several threads on the subject on the net (I used this one). There are a couple of workarounds which are mentioned including backing up the ndis.sys file and putting it back after the install but before the reboot. (This didn’t work for me, my laptop still blue screened.)
Another fix was to run the installer in Administration mode (I opened a command prompt using the “Run As Administrator” from the right click) then ran the installer. (This did work for me.)
One annoying thing was when I imported our PCF file the group password wasn’t imported. I had to use a Cisco VPN Client Password Decoder website to get the password from the PCF file to put into the address book. Everything worked fine after that (at least so far).
Hopefully someone else finds this useful.
Today was my first day using Windows 7 as my primary OS. I took the time this afternoon to install Windows 7 and start getting everything set back up. Continued »
Apparently Twitter has officially gone mainstream.
Why do I say officially when they are been around for years and have over a Billion tweets? Because phishers are now going after Twitter accounts.
So far they appear to be only getting your twitter account info and sending more messages to other people. I would imaging in a short amount of time these attacks will become more nafarous.
I’ve reached a milestone of sorts in the development process which I’d like to share. Continued »
Wordle.net creates word maps of all the words on a website. So I fed it my blog and came up with this.
I thought it was kind of cool, so I posted it up here. Try out our site and see what it does.
In the true spirit of twitter I’ll pick on a couple of people to generate there own and post them (as soon as twitter comes back up, it’s DOA at the moment).
Those of us with MSDN or TechNet accounts got access to the new Windows 7 build last night. So I had my work PC spend the night downloading it, and spent this afternoon installing it today under VMware ESX. I’ve recorded the install for posterity. I paused the recording during the borring parts like waiting for the files to expand. Continued »
One company I worked at the newer SQL Servers started taking forever to reboot the OS. The older servers didn’t take all that long. It finely dawned on us one day what it was.
If you are running Windows XP I highly recommend that you read this before installing SQL 2005 SP3 or SQL 2008 on your machine.
Apparently the IT guy who liked to tell people how smart he was decided to rely on RAID as a backup for the database, but had automated backups of the web servers. He was apparently caught steeling from the company and wiped out the SQL database on his way out the door.
Apparently my suspicions were correct and it wasn’t a system problem, but a person who deleted the data.
Andrew Hart posted a note on how some of the users are able to get there data back using the Google cache. I tried using the Internet Wayback Machine but apparently JournalSpace.com was set to not allow it to be archived.
I would recommend to the owner of the site that the contact the local police department and file a report. While company employees can’t be held liable for stupidity, intentionally destroying the company we can be held liable for.
Denis Gobo posted an update as well, as I’m sure others did as well.
UPDATE: I forgot to include that I’m following the JournalSpace.com user on twitter so that I can keep abreast of new updates.
SECOND UPDATE: My horrible spelling was pointed out to me, so I’ve corrected this. Apparently Firefox didn’t pickup the spelling problems the first time around.
In case you live under a rock and haven’t heard about Journalspace.com‘s little mistake, they have gone out of business due to a database problem. Here’s a screenshot in case the site is down when you look at it.
In a nutshell it appears that they were relying on a RAID1 array as the database backup. While we see this all the time in small database shops as noted on /. this site has been up since 2002 and had an Alexa page rank of 106,881 with 14k monthly visitors (according to Quantcast). For a site so large to be making such a simple mistake is just unacceptable. Continued »