OS/2 Warp 4

[SwedaGuy]

I hate to start an off-topic, but I'm kind of at wits end...

I have installed Warp 4, with fixpack 15 on an IBM Thinkpad X20. The correct network and video drivers are in place. The installation actually went very smoothly, compared to most Warp installs. Unfortunately, when I try to open a DOS window, I receive an Unhandled Exception error, SYS3170. I can open a full-screen DOS session without incident, just the DOS window crashes.

Some, but not all, DOS applications crash as well, with the same SYS3170 error reported. I installed Clipper, a disk label utility, and several Clipper add-on libraries, all of which seem to be running normally. WordPerfect 5.1, on the other hand will not run. The installation program worked, but when I try to launch the application, it hangs up, and eventually errors out to the same SYS message. The DrawPerfect & PlanPerfect installations wouldn't even finish before they crashed. And, it isn't just WordPerfect products that have the problem, Multi-Edit and Evolve didn't load, either.

I've tried creating my own shortcuts, as well as letting the system migrate the DOS applications in, neither seem to work.

I'm quite familiar with Hobbes, as well as a couple of other OS/2 BBSs, and I've spent the bulk of the weekend online searching for information on this problem. I have very nearly this same configuration (working flawlessly) on a desktop 486DX120, but it's Warp 3 instead of Warp 4. I need my work environment moved to this laptop before I leave town on Thursday, so I'm feeling a bit of a crunch.

Any advice, suggestions, hints, etc., would be appreciated.

[SwedaGuy]

A bit of further information:

I've gotten all the DOS applications in question to work properly. We found out the other night that this particular model has a Boot ROM, that installs in memory when active. Unfortunately, the program to disable this ROM is only a Windows application, so I can't just turn it off. However, we can exclude the memory the Boot ROM is using through setting properties for the DOS session.

This has had the effect of making the previously problematic DOS programs run without problems in a DOS Full Screen Session. However, the DOS Window Session still will not start. As soon as the windows pops up, the SYS3170 error is generated.

So it seems there was more than one reason why the SYS message was being generated. We've fixed one problem, does anyone have any idea what the other problem is?

Thanks!