The drivers that you see on Gateway’s, Dell’s, HP’s, et al, are only the drivers that the OEM took the time to test and approve.  Frequently, they never get around to testing/approving drivers that the hardware manufacturer publishes for their products.   That’s why, when you run into issues, you may need to go directly to the hardware maker for more current drivers.

As I said in my original review of DriverMax, I’ve run into problems with Adobe’s software that were only resolved with driver updates that Dell hadn’t “approved” yet.  Since DriverMax seems to have the most current drivers, it will be the utility that I’m using for now. 

The drivers that DriverMax recommends don’t work 100% of the time – sometimes you have to revert to the previous driver.  One huge advantage that RadarSync has is that it prompts you to create a system restore point before installing the driver update.  I wish DriverMax did that because I frequently forget to do that.  So far I’ve been lucky and haven’t needed it, but there’s going to be a day that I’ll regret not having that restore point.

With all that said, I only install the computer OEM drivers unless there are issues (usually video) that need to be resolved.  Although I’m using DriverMax on any computer with CS4 installed on it.

I finally had time to try out RadarSync this morning and there are pluses and minuses:

+ It finds updates to software as well as hardware.  Drivermax only does hardware.

+ It doesn’t appear to require registration for the free version.

+/- It downloads the driver updates to separate folders that you need to open and run the update manually.  An advantage to this method is that you can copy the folder to a central location so you can update multiple machines with the same hardware/software.

The major minus that I found was that while RadarSync found an update for the video and sound card, DriverMax found an additional, more current, update for the video card, and it also found major updates to the chipset and SATA system as well as a minor update to the NIC.

In the final analysis, I have to go with DriverMax.  I’m not too concerned with most software updates – I’m much more concerned with getting the hardware drivers current.  The concern with DriverMax is the registration requirement.  If that bothers you, then use a knock-off email address to register and you should be ok. 

It’s been about three weeks, and as far as I can tell, I haven’t been inundated with spam from the DriverMax publisher, Innovative Solutions.  I do receive a newsletter from them, I believe weekly, but there’s an opt-out option that I haven’t taken advantage of yet.

I’ve been trying out the “free” DriverMax program to update hardware drivers and so far it’s been outstanding!

http://www.innovative-sol.com/drivermax/

The reason I tried it is that I had some serious issues with Adobe’s CS4 and Acrobat programs with some Dell computers at a client’s office.  After trying the normal updates and reinstalls to no avail, I updated all the hardware drivers with DriverMax and the Adobe issues disappeared!

If you try it and like it, let me know – likewise if you find an issue with DriverMax, I’d like to know that as well.

Just try and find this anywhere on Google!!!  What a mess.

Anyway, I’ve found the correct download.  btw, dotnet35.exe is NOT the correct download.  You can install it, but then when you do a Windows Update, yet another .Net 3.5 SP 1 update will be there, just as big.

The correct full install can be found in the “Microsoft Update Catalog“.   Do a search for 951847 and all the 3.5 SP1 downloads will show up.  It’s a bit confusing because there appear to be two identical XP x86 installs.  I think they’re the same.

When you download it, you get a folder with the following files:

The largest is the full install.  The others are merely updates if you already have 2.0 or 3.5 installed.  More confusion here with the filename including “IA64_AMD64″ which makes it look like a 64-bit install.  But the file names begin with “X86″ so they’re not for x64.

Here’s a direct link to the catalog page:
http://catalog.update.microsoft.com/v7/site/search.aspx?q=951847

Update: This update doesn’t seem to work either. I still get the .net 3.5 SP1 220+MB patch required w/Windows Update after installing this one. I have no idea how to properly install this patch without going through WU.

What if your Vista computer can’t get an IP address from a non-Microsoft DHCP server?

At my client’s sites, I’ve run into an issue twice now with Comcast’s “Business Gateway” cable modem from SMC Networks.  Vista refuses to acquire an IP address from the modem’s DHCP server.

It turns out to be a modification in the operating system’s DHCP Broadcast flag setting.  It changed from XP to Vista, from being disabled to being required.

The fix is pretty simple, once you find it:

In the registry,

http://support.microsoft.com/kb/928233

I was looking up DAT tapes on the OfficeMax site for a client and this is what I was offered as related:

Funny!

The final reason for keeping my old 32-bit WinXP machine around has been eliminated!  Neatco has finally released the 64-bit version of their software.

http://www.neatco.com/customer-support.aspx

If you’re not familiar with NeatReceipts, check it out.  It’s the best way of organizing and storing receipts and documents.  Great for submitting expense reports!

I installed the Win7 Beta (Build 7000, cute eh?) on my little HP Mini
and it couldn’t have been easier. Every single driver was installed
automatically including the wi-fi network card.

I timed the boot from the end of the post to opening Windows Explorer (including entering my password) at 50 seconds! It’s just as snappy on this Atom netbook as WinXP was.  I did upgrade the Mini from the default 1GB RAM to a 2GB chip for $25.  That may have helped.

The shutdown buttons are much better! They got rid of the lock button and shutdown button actually says what it’s going to do when you click it. Shutting down took about 15 seconds.

My Verizon broadband USB device works great with it, although I had to use compatibility mode to make the install think it was being installed in Vista.

It’s just one PC, but it’s looking like we have a winner! Tomorrow,
hopefully I’ll have time to install it on an old Dell PC.

One that I’m definitely going to be including on my clients’ desktops from now on is the Office Tips and Tricks gadget!

On Sunday I was doing some updates on a workstation remotely.  When it rebooted, I wasn’t able to contact it again.  It wasn’t responding to anything, including pings.  I figured that when the employees arrived Monday morning, I’d call them, have them reboot the system again and all would be well.  Of course that would have been too easy.

As it turned out, the system would boot past the Vista blippy bar thing but not quite reach the orb thing.  So something was screwy.  I was still remote, so I instructed the employee to insert the Vista install DVD, boot to the repair console and do a system restore to the day prior to the updates.  No go, same response.  So I set up the employee on a spare computer and made plans to go onsite to do more troubleshooting.

When I arrived, I found the system with a black screen and a movable mouse cursor.  Ctrl-Esc and Ctrl-Alt-Del did nothing and a reboot into safe mode reached the same conclusion.  Next I booted to the Vista DVD again and tried Startup Repair which found nothing and tried restoring to an even earlier date which still failed.

Time to turn to the master resource, Google, where I found lots of folks in the same predicament, but few fixes and none that worked on this case.  Most had something to do with MagicISO and Roxio.  Now I was really getting ticked and started digging out the disks to prepare for a reinstall.  Since I had nothing to lose, I decided on a hail Mary and did a system restore to the earliest date in the list.  It worked!

The system booted up to the logon prompt finally!  Of course the computer’s password didn’t match the server, (see previous post), but with a local admin account, that was easily fixed by removing the computer from the domain and then adding it again.

Curiously, after I removed the computer from the domain and deleted the account on the server, I noticed that the system time on the computer was off by two hours!  Checking the event log, I found a bunch of security errors with the failure of the PC’s credentials.  But they didn’t start until the time I got to the logon prompt, so I don’t think the time difference had a bearing on the failure to boot.

Checking the application logs for the PC, I found that the only recent changes were a bunch of LogMeIn updates made by Zenith Infotech on Oct.24th.  (I had restored the system to Oct. 19)  Checking the logs, the system had not been rebooted until I did the system updates Nov 9th.  So it looks like LMI was the culprit.  Now I need to reboot all the systems to make sure they don’t get stuck as well while I still have a system restore window.