DOS ain't dead - This May NOT Be A Problem With XMGR!!

This May NOT Be A Problem With XMGR!! (Users)

posted by Paul, 03.05.2010, 20:57

> The message about kernel diskbuffers is displayed by the FreeDOS kernel,
> NOT by XMGR! Obviously the system was "still alive" when XMGR was done
> loading, and it in fact died sometime AFTER the kernel-buffers message.
>
> With your PC-DOS system, try loading one more driver, in fact ANY driver
> whether or not it gets used, after XMGR. If that "extra" driver loads,
> and THEN your PC-DOS system appears to "hang", I am LOATHE to expect any
> problem exists in XMGR! My guess would be that the error in the latest
> Unetbootin software happens when the DOS system switches from CONFIG.SYS
> to AUTOEXEC.BAT and/or user-program handling, i.e. the error occurs when
> DOS "goes active" after all CONFIG.SYS driver-loading and other tasks.

Yes, upon further investigation, it appears that you're off the hook! It looks like MEMDISK no longer plays nice with FreeDOS in general... kind of a problem since FreeDOS is largely used in virtualized environments (not physical floppy disks). I tried your suggestions to try to work around the problem, but no luck. I was really hoping that /T0, /T1, or /T2 might do it.

I'm going to hop over to the FreeDOS mailing list to try to rally some people there. Thanks for the help!

Post reply

Complete thread:

XMGR not working with Unetbootin - Paul, 06.04.2010, 17:25 (Users)
- XMGR not working with Unetbootin - Rugxulo, 06.04.2010, 18:45
- XMGR not working with Unetbootin - Jack, 15.04.2010, 17:42
  - This May NOT Be A Problem With XMGR!! - Jack, 16.04.2010, 04:25
    - This May NOT Be A Problem With XMGR!! - Paul, 03.05.2010, 20:57