Hi!
As you mention JemmEx is loaded and command.com is at the
expected locations:
It is possible that loading JemmEx broke your disk access,
because there is a conflict between BIOS, disk controller
and JemmEx regarding UMB areas. This could be triggered by
manually telling JemmEx to take more risks in UMB choices.
Please try booting without JemmEx / EMM386 or similar.
Regards, Eric
PS: It is possible, but unlikely, that drive letters differ.
Eric Auer via Freedos-user wrote:
you should also copy command.com to the target drive and
preferably write a config.sys and autoexec.bat there using
a text editor of your choice...
At least twice I have said that COMMAND.COM is in both root and
freedos\bin. Both copies are 87772 size, but the root file is dated
4/02/25 and the BIN file is dated 2/21/25.
The root also contains FDAUTO.BAT and FDCONFIG.SYS.
Two files are attached. The lower case are from the USB stick which does
boot. The upper case files are from the HDD which hangs on the last or
next last line in FDCONFIG.SYS.
12?SHELLHIGH=C:\FreeDOS\BIN\COMMAND.COM C:\FreeDOS\BIN /E:1024
/P=C:\FDAUTO.BAT
345?SHELL=C:\FreeDOS\BIN\COMMAND.COM C:\FreeDOS\BIN /E:1024
/P=C:\FDAUTO.BAT
On the last boot screen, the top line is
"HELL=C:\FreeDOS\BIN\COMMAND.COM......" Note "SHELL" not SHELLHIGH,
then, "JemmEx loaded".
Then, "Bad or missing,,,,,C:\FredDOS,,,,". No Shell.
I have not needed to build these files in so long that now I cannot even
red them.
I now have a file manager on the USB stick so am able to write text files.
Can I cause FDCONFIG.SYS to display as it loads? A search for DOS
config.sys echo got me nothing.
Ray
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
