Trap 000d when booting

[Giorgos S]

Hello everyone,

So I have an EDM machine that requires os/2 to run its software for cutting. When I boot to os/2 I get trap000d error. I tested the RTC module, RAM modules and SCSI hard drive and everythink seems fine to me.

Is it maybe the drivers fault?

Thank you

[Tomas Slavotinek]

Hi,

I'm not an OS/2 expert, but according to the documentation TRAP 000D
*usually* indicates a software problem. So, yes, it could be caused by a
driver or some other piece of software.

One of the recommended steps is to run "chkdsk -d" to check for
corrupted files.

But (as always) it may be hardware-related too - failing memory, hard
drive, or pretty much any other device. You mention you have already
tested some of these devices, but you should try running full
diagnostics on the machine if such a thing is available.

It would also help to know a little bit more about the setup you are
running:

1) What OS/2 version are you using?
2) What's the make and model/type of the computer controlling the EDM?
3) What peripherals are connected to it (and what adapters if you know)?
4) When exactly does the error appear? Always at the same point of the
boot process? Do you have a photo of the TRAP screen?
5) Did the problem appear out of nowhere or was the machine
reconfigured, moved, or manipulated in any way recently?

[Giorgos S]

First of all thank you for your answer.

Now to answer your questions:
1) I am using os/2 warp 4
2) This is an Agie Classic 3 Machine
3) It has adaptec aic 7850 controller, sbcp 5090 motherboard and as i can tell it is a multibus 2 pc.
4) The first error image appears when it tries to boot always at the same point of booting. The trap error appears when inserting os/2 installation diskette 2.
5)The machine was transported with a truck recently but it has been not working since 2005 maybe because it was not used.

I hope I gave you some helpful info.

Thank you!

[Giorgos S]

The 2 photos are below

https://ibb.co/k6dZgPq
https://ibb.co/GJwrsdN

[Louis Ohland]

The name is Clarke, Timothy N. Clarke...

Dear Lord, someone with a TRAP code... Don't see that much...

From DIMM memories, what level [if any] of fixes have you applied?

[Giorgos S]

The thing is I cannot enter os/2 terminal because it requires diskette 2 and also I dont know any other way to access some terminal from floppy in order to run chkdsk and other utilities.

[Giorgos S]

I applied no fixes to dimm memory, just took them out one by one and checked if the system recognizes them.

Sorry for bad debugging guys, I have no experience in old hardware and software

[Tomas Slavotinek]

Thanks for the info.

Since the machine was sitting for a long time and was then moved, I'd
probably focus on checking the hardware side of things first.

Try running memtest86 (v4) from a bootable floppy or CD to check if the
RAM and related systems are ok (note that the tests will take a while to
finish as they are very thorough). You could also try booting to some
other OS (NT, old nix distro, or what have you) to see how far that gets.

As Louis mentioned, Tim Clarke is much more experienced when it comes to
OS/2 and related topics. If he doesn't reply here, it may be worth it to
ping him directly.

[Giorgos S]

Thank you very much!

[Giorgos S]

I will do all that you said and I will post any updates here!

[Giorgos S]

Sorry but can't find the way to send him personal message.. How do i do this or something similar?

[Tomas Slavotinek]

I'll forward your question to him.

[Giorgos S]

Thanks mate!

Quick update:
I checked the disk using scandisk and chkdsk and everything seems fine.

I am running memtest as I am writing this.

Lets see what happens.

[Giorgos S]

Also a quick question.

How do i edit config.sys file for os/2 if i cant access the os/2 terminal through installation floppies to configure it etc?

Maybe through dos utils floppy? But then can I access the SCSI without its controller? I am not sure how SCSI works..

[Giorgos S]

RAM testing finished and no errors reported.

Now when I try to install os/2 again from floppies it shows this message.

https://ibb.co/S3Vsmgp

So is this RTC module fault or bad floppy drive?

[Tomas Slavotinek]

The garbled screen could be caused by a defective disk, a hardware
issue, or something else.

What you see there - starting with the "MZ" characters and including the
"clock$" and "timer$" strings are actually contents of some OS/2
executable. I have no clue how this information ended up on the screen,
but it's definitely not normal. I really don't think any of this is
related to the RTC module (unless the POST defaults to some problematic
values, but that seems unlikely and it would cause problems during the
memtest run too).

It's strange that you are getting different results now. You may be
right about the defective floppy...

You wanna edit the configuration files on the hard drive, right? If it's
installed on an HPFS partition, you won't be able to access the files
from DOS. You could try pressing ALT+F1 when the [OS/2] text appears in
the top left corner - that should drop you to the recovery menu. From
there you should be able to switch to a different config or drop to the
command prompt. (also, ALT+F2 should show what modules are being loaded,
but the TRAP handler will probably clear the screen immediately...).

[Giorgos S]

Hmm..

I did what you describe in the last paragraph about editing config file and the exact thing you describe happened.
It immediately returns me to the screen that I have to choose options from (terminal, vga reset, edit config file etc).

After that I run fdisk and deleted all partitions in the SCSI hard drive and hoped that I can install OS/2 again, but I had no luck.

I suspected the bad floppy drive because I couldn't edit CD1.sys file on the floppy disk (it showed reading error crc).
Also this "timer$" and "clock$" might be from RESOURCE.SYS file. It might loads it to memory and dumps it there dunno why,
maybe some masking is happening between data.

Now I am about to change floppy drive and see what happens..

Thanks mate for your very useful info you stated above. I am starting to understand how things worked back in the days.

After I change the floppy drive I will post any updates here.

Kind regards.

[Giorgos S]

Also I will change RTC module (m48t86pc1 with ds12887+ cuz m48t86pc1 sadly is not longer manufactured) and let's see what happens with that.

[Tomas Slavotinek]

Yea, try changing the floppy drive and make sure the floppies are good
too. Hopefully, that will do the trick.

I assume you have a copy of the EDM control software somewhere... you
know, since you wiped the original hard drive.

You are doing a good job diagnosing the system. Things weren't really
all that different back then. :)

[Giorgos S]

Ah man it is really tiring but I am learning a lot for sure.. The thing is that you have to live the technology to learn it as time goes by, cuz it's difficult to learn it backwards in time..
Too many software/hardware versions etc you have to choose the right one to make it work..

Yes I got the copy of the software that controls the EDM.. Let's hope it all works out good!

[Giorgos S]

So great success installing OS/2 after replacing floppy drive!! Huge thanks for that!!

Now the problem is that when I install the software that operates the machine in top of the OS it gets me that error "locked file driver loaded" and then gets to error screen.

Any ideas?

https://ibb.co/R2KPHtN
https://ibb.co/rHj34xb
https://ibb.co/H77w20Z

[Louis Ohland]

Help! Locked File Device Driver problem
http://www.verycomputer.com/3_f0b60fa70af92df9_1.htm

Should be something close to this.

Pity it isn't running on a PS/2.

On 5/12/2022 04:10, Giorgos S wrote:
> "locked file driver loaded"

[Giorgos S]

The thing is that it has a Sentinel Super Pro parallel port key so I am wondering if the key is damaged in any way or it needs RTC module to work properly.

[Giorgos S]

Btw thank you for your answer

[Louis Ohland]

Um, never dealt with a dongle, but my SWAG is the "locked file" is
system related, not EDM. OS/2 should load once the "locked file" issue
is sordid out, the dongle should / could have it's own device statement
in configuration.ini or whatever OS/2 uses.

Fix the booting problem first, then re-assess.

[Giorgos S]

I aggree with what you said but vanilla OS/2 boots with no problem. The problem starts when I install Agiecut software, where it places itself to autostart as soon as OS/2 boots. I tried to remove some lines from the config.sys but it starts the software with shutdown sequence (I suppose for "protection").. That's why I suspected the dongle.

I will try the solution posted in "verycomputer.com" and will come back with updates.

Thank you!

[Tomas Slavotinek]

Any luck with this?

I'd expect the driver to terminate more gracefully in case the DRM check
fails... but you never know, DRM is always a suspect.

This kind of software often comes with a standalone DRM/dongle test
utility, so check the installation media if there is anything like that.

Also, does the software require any specific OS/2 fixes? If so, are they
all installed?

[Giorgos S]

Hello Tomas,
Thanks for the interest.

No, this fix from verycomputer didn't work. My config.sys has already the c:blabla/ipfs statement on the first line of it.

What else I tried is this:
-Connecting the dongle in another computer and dumping it's data to see if it is still alive or if it has been reset after all these years of unuse. This didn't work.
-Next I tried reinstalling the whole thing again with some LAN drivers that came in the Installation CD (so it can detect and work with the dongle flawlessly but this didn't work also).

I didn't find any of dongle test utility software or driver inside the installation CD. I just found a LAN driver I am mentioning above that I am suspecting it is working with the dongle.
That suspection comes from the fact that the dongle is connected through a parallel port, parallel port is being used in printers and when I am installing the LAN driver it initiates some OS/2 printer settings.

The final thing I am suspecting is that maybe the hard disk was replaced because the original manual of the machine says that its hard drive has to be >9gb and ours is just 2gb.

To answer your last question also, the fixpack is automatically installed through the CD.

Now I am just waiting the UPS battery (I saw some cables connecting the PC bus with the Power Management bus that maybe has to do something with initiating the machine etc..)
and RTC battery to see if that will change anything.

I don't have any other ideas of what it might goes wrong..

[Giorgos S]

Hello everyone,

Finally I have found the problem. It was a BIOS setting regarding IRQ and peripherals.

Thanks everyone for your time!!

[Tomas Slavotinek]

Sorry for the late reply.

Glad to hear you were able to solve the problem!

So it was an IRQ conflict? Or some other IRQ-related issue?

[Vulcanalia2010]

Hello Gsapou,

I see your are fixing your Classic 3.
Currently i am in a similar state, i bought a broken 2F Excellence from 1999.

Can you send me an email?
Maybe it is usefull for both to have a reference on some issues.

Best regards,
Paul
pap...@hotmail.com