ABOUT THE DEBUG VERSION
=======================
When you have a crash, you can try to peform
the same test using the debug version of
the vext2d.vxd. Lots of info will be logged then.


INSTALLATION
============
* To install the debug version, install the
non-debug first, then chdir to the debug
directory and copy the .vxd to the <win95>\system
directory. 
* If vext2d is already loaded, reboot the machine.
(Vext2d is already loaded if you have run mount.exe 
at least one time after logging on)


USING THE DEBUG VERSION
===================
* the debug version will create a logfile
(c:\\fsdext2.log) which you will not be able to
put somewhere else. Also, when a file
system is mounted, do not try to delete the
log file if it is becoming too large. The
.vxd always positions the file pointer at the
last offset written. Deleting the file when 
the .vxd is running will only cause the beginning
of the file to contain garbage.
* Try to minimise the file access (and hence the size
of the log file) when repeating a crash test!!


OPTIONS TO MOUNT.EXE
====================
Mount allows you to control the dynamically change
the number of debug information. This helps in
both speed and the size of the log file. This is
only available of the debug version of vext2d.vxd
* You can use the /d option to see the current debug
level. The '*' in the first colomn means that the
specific level is enables.
* Use /d=value to set a new level. "Value" is the sum
of the individual debug levels you see in the /d output.
Value may be:
	- a decimal number (10 or 3245 etc), 
	- a hex value (0x12 or 0xff etc), 
	- the string "def" for a default setting,
	- the string "all" for all settings
Use "all" if win95 crashes, use "def" if you wonder why a
certain application does not work the way you expected.


