> What are you talking about ? The Windows API is CreateFile() and not > NtCreateFile(). Or even better, 90% of the apps use fopen()+fread()+... > They need to know nothing about native mode and NtCreateFile(). The fact > that you need the DDK should let you understand how standard apps should > know about NtCreateFile(). And look, the code is broken in any case. In > every subsystem different from /Subsystem:suck : > > "com1" != "com1.bau.meaw"
First: If someone out there is against MS, then I won't be able to change their mind, that's for sure. Second: The Window API you are talking about is called Win32 API. Guess what kind of appication you are compiling when using the win32 api? Right, a application that uses almost the same interface as win32s. So... Third: I'm not quite sure what you're talking about when saying "In every subsystem different from /Subsystem:suck - "com1" != "com1.bau.meaw"". In the POSIX subsystem of NT you can access "com1" just like any other file. POSIX doesn't understand the concept of COM ports the way DOS did. These COMx files are ONLY IN THE WIN32 SUBSYSTEM! Only there. Nowhere else. Fourth: If someone out there is against MS, then I won't be able to change their mind, that's for sure. And just to make it clear: I'm not a fan of win32. It is not what I call a good way of doing things. Although I do like the concepts behind NT. If you had a glance at the guts of NT you would be astonished how similar it is to unix kernels; in some points it might just be better... but that's a different story. Loris - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
