FreeDriverSiteBlog - Windows XP

Windows 7 Upgrade Path chart

FreeDriverSiteAdmin — Tue, 27 Apr 2010 04:34:32 GMT

Here is a great chart I found that clearly lays out which versions will support in-place upgrades on 7. All OS's including Vista and XP included.

Cannot connect to Windows XP Remote Desktop Host - no error messages - just starts to connect and then shutsdown.

FreeDriverSiteAdmin — Fri, 09 Apr 2010 23:12:27 GMT

I had a problem with a Windows XP PRO Remote Desktop host. No one could connect to the machine either locally or remotely. There was no error on the client - it would try to connect and then just go back to blank or return to the connect screen.

On the host, I found an error that RDPDD.dll failed to load in the event logs.

The problem seems to be with the video driver.

This registry key that increases the size of the session image space solved the problem for me:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"SessionImageSize"=dword:00000020

Further research says that replacing/updating removing/reinstalling the video driver may help too.

Setup.rul 380 error while installing Intel Wireless Driver on an Dell Latitude or Dell Vostro notebook

FreeDriverSiteAdmin — Wed, 07 Apr 2010 05:26:06 GMT

You may receive the message in a Window titled "Setup Error" that says Error "Setup.rul 380" has occurred and Setup cannot continue.

The error “Setup.rul “380″” Is caused by not having .NET 2.0 or higher installed. This is because the Software that controls the card is trying to be installed with the driver also. Installing only the driver will work as well.

In order to fix this issue without installing .NET 2.0 or higher please follow these directions. Also remember what the folder name is associated with the Wireless driver you downloaded. It will be RXXXXX. In the case of a Vostro 1520 with Dell Wireless card 1397, the directory is R219313.

This is easily fixed by installing just the driver. Right click “My Computer” then click on “Manage” Then click on “Device Manager” Then right click on your wireless network card. You will then need to click on “Update Driver”. A box will pop up. Click on “No, not this time”. Now click “Next”. Now click on “Install from a list or specific location (Advanced)”. Now click on “Don’t search. I will choose the driver to install.” In the list select “Network Adapter” and click next. Now click on “Have Disk”. Now click on “Browse”. On the left side click on “My Computer”. Now go to “C:\Dell\Drivers\RXXXXX\”
NOTE: You may see that it has a lot of folders. Select the folder that’s best for your install of Windows. Then when you do this you will be left with one file to select. Select that file and click ok.

The system will then only install that driver. You won’t get the Dell Wireless software installed with it, so you should use the Microsoft interface to configure your wireless networks. To enable the Dell Wireless software, install .NET 2.0 or higher and re-run the driver setup.

Microsoft Office Picture Manager not opening or very slow to open - hangs on open

FreeDriverSiteAdmin — Wed, 24 Feb 2010 21:04:04 GMT

I recently had a user clean up a lot of pictures on their computer by moving and deleting them. The next time the user went into Office Picture Manager, the splash screen would appear but it would never bring up the program (never meaning within 5 minutes - I have read reports that it will eventually open it just takes time).

The problem seems to be the catalog file that OIS.exe (the Picture Manager executable) uses. Follow these directions to reset the picture manager catalog:

Browse to %userprofile%\Local Settings\Application Data\Microsoft\OIS. Locate the file named OIScatalog.cag, and double-click on it. When asked what you want to open the file with choose Notepad from the list. When it opens you will see a file that looks like the following. Remove any lines that start with mru path. Make sure to remove the entire line including the opening/closing tags. You can also just delete the OIScatalog.cag file, and it will be re-created the next time you open a picture.

How to determine service pack level XP non-booting

FreeDriverSiteAdmin — Mon, 22 Feb 2010 18:44:41 GMT

I had a situation where I had a non-booting Windows XP but did not know what service pack it was to know which CD to use to repair it.

Using MiniPE and a remote registry tool, navigate to this key:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion

The sub-keys and values under this location will help determine OS and Service Pack versions.

Adobe Elements 6 - Error when opening organizer - The procedure entry point _CFBundleCopyFileTypeForFileData could not be located in the dynamic link library CoreFoundation.dll.

FreeDriverSiteAdmin — Tue, 09 Feb 2010 18:04:13 GMT

It seems like this problem is related to an iTunes or Firefox update. If you search the system drive for CoreFoundation.dll and simply rename the copy in the Adobe directory to something else (old-corefoundation.dll for example), it seems to fix the problem.

Mine was in C:\Program Files\Adobe\Photoshop Elements 6.0\

IRPStackSize error or other errors when trying to access shares on machines in Hyper-V

FreeDriverSiteAdmin — Thu, 04 Feb 2010 17:17:14 GMT

I had an issue with virtual machines not talking to each other. I took a production SBS 2003 server and a production XP client workstation to that same domain and used Disk2VHD to create virtuals out of them so I could test a migration to SBS 2008 on a Hyper-V server.

From research, it seems like the problem has to do with Symantec Corporate Antivirus.

I removed Symantec AV from the server and the workstation and the SRV error messages in the Event logs went away and the machines started communicating.

On the server or local machine you might get this following message in the event viewer.
"The server's configuration parameter "irpstacksize" is too small for the server to use a local device. Please increase the value of this parameter".

One fix that did not seem to fix in my case was:

You'll have to add then following to the local pc's registry.
- Go to HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameter
- There edit the IRPStackSize value to 18 Decimal or 12 Hex.
- If the value is missing insert a new DWORD Value and name is IRPStackSize as it is spelled here with upper and lower case.
- After this you restart the computer and login. You should now be able to access shares accross the network

Ghost drive cloning "29004 Read sector failure..." or "Bad blocks encountered" while restoring an image

FreeDriverSiteAdmin — Sat, 07 Nov 2009 16:58:25 GMT

I had a drive that was going out. Kept getting error 29004 when trying to create a Ghost image of the drive. The resulting image was useless because when trying to restore it, it said unexpected end of file. Also when cloning, the drive backed up 120-125% instead of 100 which was strange.

After researching, I found these options:

This problem appears to be due to the way Ghost is accessing the drive. To resolve the problem, recreate the image using the -FNI switch to start Ghost:

Ghost -FNI

If that does not work, recreate with the -FFX switch also:

Ghost -FFX -FNI

These switches force Ghost to use a different method for accessing the drive.

Alternate cause and solution
If this error occurs regardless of your Ghost version, it is probably due to bad sectors on the destination drive if restoring an image, or due to bad sectors on the source drive if creating an image. Run Scandisk, CheckDisk, or Norton Disk Doctor with a thorough surface test.

If the problem persists, run Ghost with the -BFC switch. This will allow Ghost to ignore up to 500 bad blocks on the destination drive.

To clone a disk that has numerous bad sectors, run Ghost with the -FRO switch. This instructs Ghost to continue cloning regardless of the number of bad sectors.

If the problem continues, contact the hard drive manufacturer and obtain the diagnostic program for your specific hard drive. Run the diagnostic program on the hard drive and see if this resolves the problem.

In Ghost PE on MiniPE I was able to use the -FRO switch by choosing options and force cloning and saving the options.