Japheth schreef:
> Generally, since the emulators apparently aren't fully reliable, it might be 
> a 
> good idea to first boot FD without Himem/Emm386 and then advance step by step.
>   
In case of troubleshooting, it's smart to start in Safe Mode (F5) or 
SingleStepping (F8) modes and see which line of code is the culprit.
if pressing F5, please set the path to your FreeDOS directory manually, 
and then use EDIT to comment out the trouble causing line of code.

As for boot process hanging after showing the "buffers in HMA" line, 
DOS=HIGH or SHELLHIGH might be the trouble as I've seen this problem 
earlier in
VMware.

A sample debugging script would be (upon F5):
SET PATH=C:\FREEDOS\BIN
EDIT C:\FDCONFIG.SYS (or EDIT C:\CONFIG.SYS)
EDIT C:\AUTOEXEC.BAT (or EDIT C:\FREEDOS\FDAUTO.BAT)

By default the FreeDOS 1.0 installs a lot of drivers, and apparently 
they not all work out of the box on every single machine.


My own use of FreeDOS is quite simple these days by mounting an ISO once 
kernel and shell have been loaded:
DEVICE=HIMEM.EXE
DOS=HIGH

SHSURD /F:FDBOOTCD.ISO
SHSUCDX /D:SHSU-CDH,X
SET PATH=C:\;C:;X:\FREEDOS\SETUP\BIN


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to