S1590 upgrade help please

Greetings,
I'm in the middle of trying to upgrade a family member's machine from
old-time movie hardware to something not quite so old. The machine
originally had Win98SE running on an Abit IT5H with a K6 233, 128 MB ram,
and an ATI Rage II+. The machine ran fine although it was a little slow.

I'm now trying to install a Tyan s1590 with a K62-500 and 128 MB of PC66.
To begin the upgrade, I first removed all devices from device manager and
then removed the remaining ones from the HKey_Local Machine/Enum branch of
the registry that device manager would not let me remove, i.e., the hard
drive controllers. The Win98 directory from the install CD was copied to
the hard drive so that it could be accessed without worrying about the CD
not being initially detected. I then swapped the hardware over (it tested
fine with a bootable SuSE Linux CD that I have).

Win98SE will boot fine in safe mode. However, booting in normal mode takes
a long time even after all the hardware was detected (there are no obvious
conflicts in device manager). The normal mode boot time is about 20
minutes. I performed a logged boot and examined the bootlog.txt file with
Bootlog Analyzer. However, this program indicates that the processes
recorded in the bootlog.txt file completed in about 3 minutes. Clearly,
there's something else going on with the machine.

Other components in the system are:
US Robotics 33.6 ISA modem jumpered for com2, irq3
SoundBlaster 16 ISA PNP
The PC66 is actually composed of one 64MB module of PC100 and two 32MB
modules of PC66 running at the AGP 66MHz jumper setting.

I also have a VooDoo 3 3000D to install in it once I get the rest of the
hardware working (I thought that the motherboard upgrade might go more
smoothly if I left the old video card installed).

I would greatly appreciate any comments or suggestions on getting this
system to work correctly.

Thanks, Eric

Eric wrote:
 >
 > Greetings,
 > I'm in the middle of trying to upgrade a family member's machine from
 > old-time movie hardware to something not quite so old. The machine
 > originally had Win98SE running on an Abit IT5H with a K6 233, 128 MB ram,
 > and an ATI Rage II+. The machine ran fine although it was a little slow.
 >
 > I'm now trying to install a Tyan s1590 with a K62-500 and 128 MB of PC66.
 > To begin the upgrade, I first removed all devices from device manager and
 > then removed the remaining ones from the HKey_Local Machine/Enum branch of
 > the registry that device manager would not let me remove, i.e., the hard
 > drive controllers. The Win98 directory from the install CD was copied to
 > the hard drive so that it could be accessed without worrying about the CD
 > not being initially detected. I then swapped the hardware over (it tested
 > fine with a bootable SuSE Linux CD that I have).
 >
 > Win98SE will boot fine in safe mode. However, booting in normal mode
 > takes a long time even after all the hardware was detected (there are no
 > obvious conflicts in device manager). The normal mode boot time is about
 > 20 minutes. I performed a logged boot and examined the bootlog.txt file
 > with Bootlog Analyzer. However, this program indicates that the processes
 > recorded in the bootlog.txt file completed in about 3 minutes. Clearly,
 > there's something else going on with the machine.
 >
 > Other components in the system are:
 > US Robotics 33.6 ISA modem jumpered for com2, irq3
 > SoundBlaster 16 ISA PNP
 > The PC66 is actually composed of one 64MB module of PC100 and two 32MB
 > modules of PC66 running at the AGP 66MHz jumper setting.
 >
 > I also have a VooDoo 3 3000D to install in it once I get the rest of the
 > hardware working (I thought that the motherboard upgrade might go more
 > smoothly if I left the old video card installed).
 >
 > I would greatly appreciate any comments or suggestions on getting this
 > system to work correctly.
 >

I've recently discovered that there are multiple screens worth of "alias"
hardware listed in Device Manager when viewing the I/O addresses in use
under Computer Properties, View Resources. I don't know if this might be a
cause or a symptom of the 20 minute boot problem or if it's even related.
Though, as I noted above, there are no conflicting devices in Device Manager
and the system seems to work reasonably well once it boots. It just takes
20 minutes.

Eric<!-- ~MESSAGE_AFTER~ -->