Vitus Jensen wrote in a message to Mike Bilow:

 MB> Other than doing odd things such as overrunning the parser stack, 
 MB> I have never had MS C 6 spit out an "internal error."

 VJ> I got those when using _base constructs intensively. 
 VJ> However, I also did MS-DOG drivers and BIOSses (even NetWare
 VJ> 2.x, huh), so that might be related to those sources.  I
 VJ> can't remember a single internal error with MS-C 7, though. 

I can't remember ever using a _based construct in an OS/2 device driver. 
Exactly what were you trying to do?

 VJ>> There are differences between MASM 5.1 and 6, but the change
 VJ>> is no real problem. 

 MB> I like Watcom a heck of a lot better.  My preferred 
 MB> configuration for OS/2 device drivers is the Watcom compiler 
 MB> with the Microsoft/IBM linker.

 VJ> WLINK isn't bad, you know... 

The problem is that WLINK does not know how to write a map file that can be
parsed by MAPSYM or TRCUST.  So, if you use the kernel debugger, you really
do not want to run WLINK.
 
-- Mike


---