On Mar 03 04:26 96, Paul Person of 1:343/179 wrote:

  First of all, thanks for your excellent reply!

PP> You may not like this at all: it works for me. Great news, eh? 

  I figured that's what someone would say. :)  I'm hoping 10.6 will work
when it comes out.  I can't think of anything else that would do it.  I'm
also considering doing a fairly minimal install off the Warp CD into
another partition, and see if Watcom C/C++ will run on that.  (It could
always be a conflict with some of the drivers that I'm using, or something)

PP> 1) I am assuming that you are using the graphics-mode OS/2 PM debugger for 
PP> OS/2 and the character-mode debugger for DOS programs, both of which 
PP> (WD.EXE and WDW.EXE in WATCOM\BINP) state that they are "16-bit OS/2 
PP> executable"s when invoked from a DOS session. There are files with the 
PP> same names in WATCOM\BINW: WD.EXE appears to be a DOS program (since it 
PP> runs) and WDW.EXE states that it is a "16-bit Windows
executable" when 
PP> invoked from a DOS session. You might want to check which versions you are
PP> running, just in case. 

  I only installed the OS/2 and DOS modules, but I did double-check, and
yes, I'm running the correct one.  I've been all over those directories
with a fine-toothed comb...

PP> probably means OS/2 can't find STD32.DLL to load it. Although I have to 
PP> say that "Access Violation in STD32.DLL" isn't exactly the
error message I
PP> would expect to see if this were the case. 

  No, STD32.DLL is definitely in my LIBPATH.  (I even tried copying it into
OS2\DLL, which is almost first in my LIBPATH, just to be sure).  Didn't
work, so I deleted that copy.

PP> 3) Does the program run (in some sense) on its own or is it possible that 
PP> it is doing this all by itself on startup? 

  The debugger will NOT run in any sort of 32-bit OS/2 mode.  It will debug
DOS, Windows, and 16-bit OS/2 apps properly, but it won't even load in a
32-bit mode...  Just gives me the same old Access Viol. error every time. 
I'm debugging a 32-bit 'Hello World!' program as a test.

PP> 4) I have applied FP10; I have not applied FP17. I'm sure you're really 

  I've tried Fp5 through Fp17, and none of them seem to make any
difference.  I was going to try OS/2 2.1, and see if I had any luck with
it, but OS/2 2.1 won't run on my Pentium machine.  (TRAP errors on boot up
under that version of OS/2)

PP> 5) I just checked APPLYA.BAT (which applies the C_A patch), and STD32.DLL 
PP> is NOT listed. This means it is not changed by the patch. 

  I noticed that as well.

PP> 6) The "Infobase" CD-ROM has a large set of tech support
topics. Have you 
PP> tried scanning through all of them to see if any apply?

  Yup.  And checked over Watcom's web site as well.  Nothing.  I'm almost
positive that it's a conflict with one of the drivers on my system, but I
can't figure out which, and don't really have the space to re-install OS/2.
 It's happening on both my Pentium and 486, so it's got to be something
that's common between the two, but I have no idea what it could be.

Ciao for now,
- Richard
@EOT:

---