Ferenc Wagner wrote:
Eric Pouech [EMAIL PROTECTED] writes:
_lcreat16 (and al.) is in fact a 16 bit function, implemented in
krnl386. so, normally it wouldn't be accessible from 32 bit DLLs (we
can do it in some cases, but the least we do, the better it is).
So, if the same behavior (as
Ferenc Wagner wrote:
Pouech Eric DMI AEI CAEN [EMAIL PROTECTED] writes:
please stop using krnl386.exe export when possible
(especially for dos emulation which is going out of
kernel32/krnl386.exe combo). So, if CreateFile can do,
please use it (ditto for any other krnl386 file related
functions)
Eric Pouech [EMAIL PROTECTED] writes:
_lcreat16 (and al.) is in fact a 16 bit function, implemented in
krnl386. so, normally it wouldn't be accessible from 32 bit DLLs (we
can do it in some cases, but the least we do, the better it is).
So, if the same behavior (as _lcreat16) can be obtained
Pouech Eric DMI AEI CAEN [EMAIL PROTECTED] writes:
please stop using krnl386.exe export when possible
(especially for dos emulation which is going out of
kernel32/krnl386.exe combo). So, if CreateFile can do,
please use it (ditto for any other krnl386 file related
functions) this is needed
Andreas Mohr [EMAIL PROTECTED] writes:
On Mon, May 26, 2003 at 01:04:49PM +0200, Ferenc Wagner wrote:
Volume label creation should fail, not create a regular file.
Similarly for file names ending in a slash.
Hmm, and is there a reason to not do it in _lcreat16() instead?
Or is _lcreat16()
On Mon, May 26, 2003 at 01:04:49PM +0200, Ferenc Wagner wrote:
Volume label creation should fail, not create a regular file.
Similarly for file names ending in a slash (this is actually
needed for PKSFX Version 2.04g to unpack directory trees).
please stop using krnl386.exe export when possible (especially for dos emulation which
is going out of kernel32/krnl386.exe combo). So, if CreateFile can do, please use it
(ditto for any other krnl386 file related functions)
this is needed for proper DLL separation
Hmm, and is there a reason to
