> The JAM.SYS driver now passes the OEM number check, but it always hung
> my VMware session. Maybe you have better luck.

There's probably more to it. JAM doesn't know about FAT32, and if I recall  
the documentation correctly, it apparently accesses low-level DOS  
structures (DPBs) and devices directly. This will definitively not work if  
the host drive is FAT32, but might even cause problems only because the  
DOS version supports FAT32 at all. A FAT16-only FreeDOS kernel binary  
might fix the problem.


Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
Freedos-user mailing list

Reply via email to