Hello Mike,

25.05.96 18:01, you wrote a message to Vitus Jensen:

 MB>> Other than doing odd things such as overrunning the parser 
 MB>> stack,  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. 

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

My drivers are compiled small modell and I tried to avoid far pointers even
more.  So pointers to regions inside an IORB (workspace, status block) are
declared _based.
In the debugging version all string constants are declared based in _TEXT.

...
 VJ>> WLINK isn't bad, you know... 
 MB> The problem is that WLINK does not know how to write a map file 
 MB> that can be parsed by MAPSYM or TRCUST.  So, if you use the 
 MB> kernel debugger, you really do not want to run WLINK.
 
You're right.  I forgot this.

Bye,
	Vitus 

PIN: 10:1000/100.20
Fido: 2:2474/100.20

---