
		   VtoolsD for Windows 95
			Version 2.01

			 README.TXT

VtoolsD now includes a copy of selected Microsoft DDK help
files.  In order to conserve space, the DDK help files are
not included in the BBS/FTP versions of VtoolsD.  You will
get an error message from the installer if you select the
option to install the MS DDK help files.

Note on use of Vendor Specific Entry Points:

  Vendor specific entry points were implemeneted to overcome the problem
  of requiring a unique device ID in order to provide services
  to 16-bit applications. Since Windows 95 allows name based calling
  of VxDs from 16-bit applications (see manual), vendor specific
  entry points, while still supported, are no longer a recommended 
  approach. It is preferable to use the standard conventions. 

  Vendor specific entry points are explicitly discouraged for dynamically
  loaded VxDs, because of the problem of other VxDs or applications
  hooking into the INT 2Fh chain, and thereby making removal impossible.

Note for Borland C++ developers:

  It has come to our attention that the use of in-line
  constructors can lead to unpredictable placement of the
  VTAB. More specifically, if a class has an in-line constructor,
  then the linker will locate the VTAB in one of the segments
  in which the in-line constructor is invoked, which may be
  the INIT segment. Thus, the class is unusable after initialization
  because it's VTAB is flushed. To avoid this problem, do not
  use in-line constructors, or make sure that all invocations
  of in-line segments occur in the locked segment.
