Hi Mike,

17.05.96 15:03, you wrote a message to Vitus Jensen:

 VJ>> {at}KEY-WORDS: internet hasch drogen porno Israel Kohl IRA RAF
 MB> Trying to attract the attention of international intelligence 
 MB> agencies?

Replace international with national.

 VJ>> For your information: I moved to MS-C 7.0 in 1993 for ADDs. 
 VJ>> I got sick of recoding drivers to prevent MS-C 6.00A to spit
 VJ>> out "internal error". I would like to move to WatCom
 VJ>> (because it is supported), but to write a new dhcalls.lib
 VJ>> plus changes in driver code is not an option.

 MB> I use the stock DHCALLS.LIB from the DDK with Watcom.

I see: it's all APIENTRY, so no problems.  My fault.

 MB> You need to write a custom ASM stub at the head of your project 
 MB> to account for the differences in segment alignment, and you can 
 MB> choose to rebuild DHCALLS.LIB from the DDK source using the 
 MB> Watcom compiler. 

Rebuild DHCALLS.LIB with WASM?

[...bollo freeware lib...]

 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."

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

 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 configuration 
 MB> for OS/2 device drivers is the Watcom compiler with the 
 MB> Microsoft/IBM linker.

WLINK isn't bad, you know... 

...

Bye,
	Vitus 

---