Hello, again.
Now I have another question... is it possible to generate a VXD file or (or SYS for Win2000) using FASM?
Exaples will be gratufully accepted

As fasm doesn't support LE output, you'd have to make VxD files manually (in binary output mode) - since I was doing such thing with PE files, it shouldn't be really hard to do it with LE. I was even planning to make some example, but I'd have to read something more about LE first - about this particular format I know very little.

On the other hand, you can simply use MS COFF output and link it with Microsoft's DDK linker.

there is vs.net and IDApro.

LE format is used in VxD drivers and DOS4GW executables.
http://www.rosprombank.ru/~ig/le.zip

more:
http://www.rosprombank.ru/~ig/download.html
http://www.datarescue.com/idabase/idadown.htm

and more
http://www.chsw.com/ddk/

http://www.microsoft.com/whdc/ddk/default.mspx

--
i am just googling myself.

Thank you.
Now I understand what to do about VXD.
But still, don't know how to compile SYS driver for Win2000.

Compile to COFF and link with MS link.exe (like one from masm32 package) as /driver /base:0x10000 /align:32 /subsystem:native

I see fasm support format PE native, but I find no example .
Privalov?

One simple question, but what is the native PE format?

Probably format PE native at 0x10000 with the fixups included would be enough.

What about CRC?

Privalov: http://wasm.ru/forum/index.php?action=vthread&forum=4&topic=2303

A good point. I should think about adding checksum generator to PE formatter.

Have you read that link? Also, why does native compile to .exe, should it not be .sys?

I've never tried producing KMD with fasm, to get the right extension the small fix is enough in the fasmw's file name generator. But the checksum is a problem - Microsoft doesn't make the algorithm for calculating PE checksums publically available, the appropriate API from IMAGEHLP.DLL should be used for this purpose. But I can't use the Win32 API in fasm core, which is OS-independent, so probably the only solution would be to provide some external Win32-only tool for it.

I've found that they have actually implemented it in WINE, with Google I've found their C routine for PE checksums here: http://www.winehq.org/hypermail/wine-patches/2000/11/0168.html
Now it would be easy to implement it in fasm, but - well, I don't know how did they get that algorithm (reverse engineering?), and I don't want to get fasm into any problems because of it in future. What's your opinion?

I think it will be fine. You live in Poland anyway.

I have updated the 1.49 release with the correct checksum calculation. This is, anyway, my own routine, which by accident gives the same result as the one from Windows. And it will generate PE files with correct checksums even on DOS or Linux or whatever else where fasm will be executed.

Super!

What about different alignment? Native drivers (.sys) need 32-byte alignment instead, I think?

Ok I did, cool. Very nice source FASM, I was able to do very quickly.

I don't think M$ wants to stop WINE from developing (ie they're allowing M$ to use thier PE format on other platforms -- soon they might even try to sell their software to Linux users...)
Perhaps you should ask the WINE dev team about this, they should know.