I am very pleased with ongoing Command.com development and improvements made, but I encountered a problem related with or revealed by Bart's MEM.EXE. When booting with latest kernel (2035 or Arkady's) plus Himem.exe plus Emm386 and using xmsswap-command.com 0.82pl3e or higher, MEM.EXE fails and reports: UMB Corruption. I do not know if UMB is really corrupted by command.com or that this is cosmetic, but either way it affects me because I use the output of MEM.EXE to signal if certain TSRs or drivers are loaded. Obviously this does not work anymore with 0.82pl3e or higher. The official 0.82pl3 is working fine so it should arise from first changes implied on 0.82pl3.
Erwin ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
