Re: [Nasm-users] winsock problem & strange errors

[Frank K. <fbk...@co...>]

Yeoh HS wrote:

> I checked the definition of WSAdata in win32n.inc

I've got three win32n.inc's here...

this is something from "The_Owl"
WIN32N   INC       139,841  04-01-00  2:02p win32n.inc

this is "Tomcat"s - I assume it's the one we want
WIN32N   INC       290,400  05-11-99  3:34p WIN32N.INC

and this from "Gaz"s win32nasm package(?)
WIN32N   INC     1,029,613  07-07-03  2:52p win32n.inc

I don't know if it's got anything to do with the case of WSAdata, but 
there's a potential problem looming here. I've got 13 "windows.inc"s, 
too, but mostly not for Nasm (one in Gaz's package). Only one 
"nagoa.inc" (well, another one in projects\toolbar - 3k), but it's a 
fairly old one - I'll bet if I downloaded the latest version, it would 
be different. And that's not including Sheroc's package...

Maybe one of the things we could discuss on this list is which .inc is 
which, and which is best to use for what purpose.

Gaz's package interests me, because it uses Nasm's "-f win32" format, 
rather than "-f obj". (and I liked some of his macros better than 
Tomcat's - which I think is what nagoa.inc is based on?) Needs a 
different linker to handle the MS COFF. I think the linker with LCC is 
supposed to work, and I've had some success with the ld from Cygwin, in 
addition to the MS product (which is included with the package). The 
website phoenix.gb.net seems to have died. You can get the "base pack" 
from Tomcat's site, but there's a larger package (looking at it... I 
guess the "base pack" has everything you need...).

Anyway, I see potential problems if we try to assemble something that 
includes "some.inc" and we've got a file by the same name, but perhaps a 
"pre-bugfix" version... Is there a de facto standard for what you guys use?

Best,
Frank