Re: Windows NT vs Win95 EXE's

["Matt Kettler" <Mkettler@Evi-Inc.Com>]

NT doesn't allow any form of direct I/O to the filesystem, or any 
of the hardware ports by user processes. I'm not exactly certain what 
he means by "using file i/o" because iostream is also "file I/O" as 
is any other means of reading a file. My guess is that he is doing 
direct file I/O, which is forbidden in NT due to the security model. 
Use Iostream, VCL, or Win32 API calls (createfile, readfile, etc). I 
would recommend Iostream for cross-platform (ie: non-wintel)  
compatablity,or  win32 API for the best cross-windows compatibility. 
C-style fopen, fseek, fread, etc should also work on NT, but perhaps 
BCB implements these in a non-NT compatible way..

In general NT has more API calls than 95 does (security services, 
etc), but also is more restrictive about direct I/O than 95 is in 
order to maintain system security. Also since NT has NTFS and FAT, 
trying to do direct file I/O may be disastrous if the volume isn't 
the filesystem you expect. (NTFS doesn't have much resemblance to FAT 
systems)