HEADS UP: Pitfall when upgrading from Win98 to Win2k or XP & latest NERO is installed
Posted: Thu May 09, 2002 1:07 pm
I've never done a Win98 to 2K or XP upgrade, so for kicks (after Ghosting the boot partition) I upgraded my newly built LAN party rig to Win2K.
If you upgrade from Win98 to either Win2K or WinXP, you need to uninstall Nero first (you can also uninstall it AFTER the upgrade) then re-install it when you're done. This MAY only apply to Nero installs using a virtual CD-R - not sure though (when you don't have a real CD-R, Nero installs a virtual CD-R which allows you to make ISO images).
The rig I tried this on does not presently have a CD-R installed in it.
Nero installs a background DLL and it apparently installs on of two different DLLs depending on whether it's a Win9x or NT based system. The 9x DLL is incompatible with Win2K/XP and it'll crash Explorer whenever you try to look at a drive's properties or bring up it's shares.
Uninstalling Nero before or after the upgrade solves the problem, then you can re-install Nero afterwards.
It was a LONG troubleshoot to figure this out, though.
I upgraded to Win2K & spent HOURS trying to figure out why Explorer was crashing when I brought up a drive's properties. I thought it was a bad COM+ Windows Update (it didn't update smoothly - locking up part way through). Reinstall of the update didn't help.
So I restored the Win98 Ghost image and upgraded to Win2K again - same problem.
Restored the Win98 Ghost image yet AGAIN and this time upgraded to WinXP. SAME PROBLEM!
I KNEW my 98 install was clean - I only just installed it the other day with only the bare minimum apps installed, so assumed it was some background app or an app that uses explorer extensions like Winzip that was causing the problem.
I never would have guessed it was Nero, though. I caught on whenl I went through the XP error logs and found a reference to a DLL that had the word "Nero" in the filename.
Interesting thing is that I have broadband so I allowed both Win2K and XP to download the latest compatibility data before upgrading, but neither reported a compatibility issue with Nero.
If you upgrade from Win98 to either Win2K or WinXP, you need to uninstall Nero first (you can also uninstall it AFTER the upgrade) then re-install it when you're done. This MAY only apply to Nero installs using a virtual CD-R - not sure though (when you don't have a real CD-R, Nero installs a virtual CD-R which allows you to make ISO images).
The rig I tried this on does not presently have a CD-R installed in it.
Nero installs a background DLL and it apparently installs on of two different DLLs depending on whether it's a Win9x or NT based system. The 9x DLL is incompatible with Win2K/XP and it'll crash Explorer whenever you try to look at a drive's properties or bring up it's shares.
Uninstalling Nero before or after the upgrade solves the problem, then you can re-install Nero afterwards.
It was a LONG troubleshoot to figure this out, though.
I upgraded to Win2K & spent HOURS trying to figure out why Explorer was crashing when I brought up a drive's properties. I thought it was a bad COM+ Windows Update (it didn't update smoothly - locking up part way through). Reinstall of the update didn't help.
So I restored the Win98 Ghost image and upgraded to Win2K again - same problem.
Restored the Win98 Ghost image yet AGAIN and this time upgraded to WinXP. SAME PROBLEM!
I KNEW my 98 install was clean - I only just installed it the other day with only the bare minimum apps installed, so assumed it was some background app or an app that uses explorer extensions like Winzip that was causing the problem.
I never would have guessed it was Nero, though. I caught on whenl I went through the XP error logs and found a reference to a DLL that had the word "Nero" in the filename.
Interesting thing is that I have broadband so I allowed both Win2K and XP to download the latest compatibility data before upgrading, but neither reported a compatibility issue with Nero.