IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New SDD
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.
Darrell Spice, Jr.                      [link|http://www.spiceware.org/cgi-bin/spa.pl?album=./Artistic%20Overpass|Artistic Overpass]\n[link|http://www.spiceware.org/|SpiceWare] - We don't do Windows, it's too much of a chore
New Hardware
Hmmm... it's been said before that OS/2 is the best way to detect flaky hardware.

Try taking everything out of startup, and cleaning the autostart line to read only FOLDERS, TASKLIST. See if you can get it to reliably boot after that.
--\n-------------------------------------------------------------------\n* Jack Troughton                            jake at consultron.ca *\n* [link|http://consultron.ca|http://consultron.ca]                   [link|irc://irc.ecomstation.ca|irc://irc.ecomstation.ca] *\n* Kingston Ontario Canada               [link|news://news.consultron.ca|news://news.consultron.ca] *\n-------------------------------------------------------------------
     WPS/PM doesn't initialize - (SpiceWare) - (9)
         Re: WPS/PM doesn't initialize - (jake123) - (7)
             SDD - (SpiceWare) - (1)
                 Hardware - (jake123)
             should have mentioned - Matrox G400 - (SpiceWare) - (4)
                 Have you gone to the eCS website and - (jake123) - (2)
                     no change - (SpiceWare)
                     New eCS site looks nice - but - (SpiceWare)
                 FWIW, Warp 4 & G400 with SNAP for OS/2 2.0 works fine here. - (n3jja)
         found something about AGP aperture & WPS hanging - (SpiceWare)

Camptown ladies never sang all the doo dah day. No, no, no.
58 ms