Building Watt32 2.2.dev.rel11 with Open Watcom 1.9 on Windows, and failures.

[myrkraverk]

Dear Watt32,

I've just built the release from the website on Windows, using Open Watcom 1.9. I ran into some problems with winadinf.[hc], and "hacked" them to to compile by adding several #ifdef __WATCOMC__ guards.

I've already seen similar guards in those files, and can provide a diff, or even a pull request. It is however, completely untested at the time of this writing.

Is such a patch welcome? Since I'm not sure what any of the code in the files is supposed to do, I thought to ask first.

For the record, I just followed the directions and did

cd src

configur.bat watcom

wmake -f watcom_w.mak

as the build process.

[myrkraverk]

As an additional comment, my sock_init() fails to find a driver. I had previously installed npcap, and nmap works on my Windows 10; I think that confirms npcap is working, but I'm willing to be educated on that front.

How would I go about debugging why the npcap in watt32 driver fails to initialize?

[gvanem]

Is such a patch welcome?

Sure, Post / attach a diff -u3 output of your stuff here. But use git master as a reference since 2.2.dev.rel11 is rather old.

How would I go about debugging why the npcap in watt32 driver fails to initialize?

Try e.g. setting these in wattcp.cfg:

winpkt.trace    = 1
winpkt.dumpfile = c:\nmap_dump.txt

Rrun %WATT_ROOT%\bin\ping.exe -sd www.google.com. And look in c:\nmap_dump.txt for issues.