DLL's not installed by Windows but used or installed by programs should be migrated 
into the repair install along with programs and data.  Windows usually will replace 
it's own DLL's, or will ask if you want to keep a newer version of a file or replace 
it with an older one.  If you repair install on the old system, doing so on the new 
system probably won't help at all if Win 9x can't run on the new hardware.

Win 9X, unlike the NT systems, can start, run and update itself when moved from system 
to system, if it has drivers in it's database and cache of drivers to switch to. 
 If it doesn't, it can fail outright, to just disabling the device that it doesn't 
have a driver for.  If that happens, you will have to add the driver from the motherboard 
or device vendor, if they have one.  That's why I recommend not doing it on the original 
drive, but imaging the old drive to a new one, attempt the repair install in the 
old system, then installing the new drive in the new system and trying to start it. 
 Chances are that most new boards now will not work, or work very well, but only 
one way to find out as support is fast dissappearing due to the hardware no longer 
supporting the old legacy operating systems.  (at least according to the hardware 
manufacturers)  Intel and Intel chipsets for instance have not supported Win 9X for 
several years now.  So you will be forced to go with whatever VIA or SIS has to offer 
which isn't much now from my observation.

• Reply or follow-up to this message

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum