Trap 000D???

Trap 000D???

Post by Bori » Sat, 20 Dec 2003 05:01:43

Call it nostalgia, but I have been trying to reload WArp 4 after some
years. I already posted some problems with SCSI, but then tried to go the
IDE route (an IBM HDD in fact and only 6 gb).

I get into the start of the installation, but at the time it says it is
starting to copy files, it all stops with a Trap D, it's been so long, what
does this mean please?


Trap 000D???

Post by Will Hone » Sat, 20 Dec 2003 18:09:07

Trap D is frequently a hardware problem, especially with memory
errors. It might be worth doing a thorough memory test before you
spend a lot of time chasing ghosts, especially if it's an older piece
of hardware that has been sitting a while. I see this kind of error
fairly often working with surplus boxes people donate to a local
charity and a lot of times all I have to do is simply pull all the
cards and memory then re-insert them to get better contacts (in fact,
I just went through that drill last night).

Will Honea < XXXX@XXXXX.COM >


Trap 000D???

Post by Mike Luthe » Sun, 21 Dec 2003 00:05:06

And while you are taking Will's suggestion below ..

If the card you have in your hands has any of the plug-in LSI's and
other chips where the pins go into sockets on the boards ...

Take your fingers and push on the devices to disturb the pins where
they go into the sockets!

Many times you will hear little noises and feel little crinkling as
these devices settle into the sockets in a different position.
Corrosion settles into the pin to socket contact surfaces. Simply
disturbing these dirty little devils has fixed more odd problems than
I'll ever be able to remember in the thirty years I've been doing this too!


--> Sleep well; OS2's still awake! ;)

Mike Luther

Trap 000D???

Post by Lars Erdma » Sun, 21 Dec 2003 05:48:12


for Warp4, the problem that shows up most frequently is that the disk driver
IBM1S506.ADD is way to outdated to handle today's large disks.
Normally, you need to update the driver by either a recent version or by
DANIS506.ADD on the install disks (in the latter case you have to either
rename the driver or update config.x/config.sys).


"Will Honea" < XXXX@XXXXX.COM > schrieb im Newsbeitrag


Trap 000D???

Post by Bori » Sun, 21 Dec 2003 18:00:57

Boris < XXXX@XXXXX.COM > wrote in

thanks for the help - idedasd is new from the update site (and the hard
disk was only 6gb anyway).

seems like a pain, but I'll just have to clean all those old contacts and
have another go.

why does warp do this but Windows and Linux don't?


Trap 000D???

Post by William L. » Sun, 21 Dec 2003 19:42:27


Tight coding in Assember, which makes it fast. Downside, it is
sentative to hardware problems like this.
Thanks a Million!

Trap 000D???

Post by Alex Taylo » Mon, 22 Dec 2003 07:55:40

OS/2 is less forgiving of flaky hardware than most other OSes. Part
of the reason is that it tends to drive the hardware harder. Another
reason is that, when encountering an error like this, OS/2's reaction
is "Something serious has gone wrong; I'd better stop everything and
halt the system so that I don't inadvertently do serious damage to
data". OTOH, the Windows reaction is to try and suppress the error
and continue as long as possible, which tends to lead to system
instability and weird behaviour.

You probably _will_ see the symptoms of hardware failure in Linux
eventually (probably when doing something heavy like recompiling the
kernel). And some day, in Windows as well.

Alex Taylor ~alex