I reinstalled Friday when I went into "hardware safe mode". I thought with all the hard drive messages it was possible that data written to the drive might have been corrupted. What's really weird about it is I did multiple reboots Friday night to see if the "unable to work hard drive" message would come up. No changes at all, just multiple reboots and everything worked fine. I booted Saturday morning to a hung WPS.
I'm currently using the version of SDD that came with ECS. I'm doing the updates on an extended schedule(one every few days) to see if problems show up after I install something. I ran a fresh install Friday and Saturday. Today I used the ECS Maint Tool to install device driver pack 3(and whatever else EMT auto-installed after it).
I haven't been able to get joysticks working so this afternoon I tried the "enhanced joystick driver" that Vesa wrote. I had problems right away and removed them. I suspect IBM's joystick driver might have been causing problems too - they never recognized the joysticks. The motherboard has a built in joystick port, but I suspect the i/o is being mapped somewhere other than the traditional location.
Before I changed it, startup.cmd had only EXIT in it. I also tried renaming startup.cmd to prevent it from running, that didn't help either. If I can't figure it out, I'll try having startup.cmd run the eCS Clock(and remove the clock from the startup folder). At least then I won't have to close E everytime I boot.
On a side note - I just tried changing the bus speeds back and got an unable to work hard drive message right away. So I suspect the SCSI card is being overclocked(or affected by something else timing related) when the CPU bus is set to 133 instead of 100.