[Oberon] debug output from OFSFATVolumes.AssignDirectoryEntry

Peter Easthope peter_easthope at gulfnet.sd64.bc.ca
Mon Sep 15 16:57:19 CEST 2003

The only way I can investigate the problem with ET.StoreAscii 
applied to a FAT file is by debug output.  

OFSFATVolumes.AssignDirectoryEntry already contains many 
Writes to the Kernel.Log.  The flags Trace and Detail are already
set TRUE in OFSFATVolumes.  Yet the debug output does not 
appear in the Kernel.Log.   Why is this?  How can I make this 
extensive output visible?

Thanks,        Peter E. 


More information about the Oberon mailing list