DLL with Win95 and NT

[a_fischetti]

Do Windows NT and Windows 95 treat dll functions in the same way?
Thanks in advance.
Antonio.

_______

[balak yap]

Shall be almost the same, but NT is unicode

Hello World!!!

[a_fischetti]

What's the meaning of "unicode"?
Bye.
Antonio.

_______

[William Walseth]

For the most part, '95 and NT treat DLLs in a similar way. Typically there is not a problem sharing a DLL between NT and '95, but as with everything else there are couple things to watch out for:

1) 16-bit DLLs are very different from 32-bit DLLs. In particular, you can share data between 16-bit processes in a 16-bit DLL. This is no longer possible in 32-bit.

2) NT and '95 differ in how they load DLLs. For more details, I'd recommend "Advanced Windows", 3rd Edition, by Jeffrey Richter (Microsoft Press).

3) NT DLLs may collide when a program starts. As a result you may see a message like this appear in the Visual C++ output window
"LDR: Dll MFCN42D.DLL base 5f600000 relocated due to collision with C:\WINNT\System32\WINSPOOL.DRV". While this sounds serious it will not cause application problems other than slow start-up speed. If you have slow start-up problems look at specifying a new base address for the DLL.

4) UNICODE is a character representation. In a non-UNICODE program, characters are represented as 1 byte values, allowing for a character to specify 256 unique values. In a UNICODE program, characters are represented by 2 byte values, allowing upto 65,000 values. This all comes in handy when you're program needs to be translated into Chinese, Japanese, Korean, etc. '95 Does NOT support UNICODE. See Richter for the complete low-down on UNICODE.

[a_fischetti]

Thank you very much for your explanations.
Ciao.
Antonio.

_______