But of course it is always good to remember that we have to
remind ourselves to write good code in open source. Because
we are not paid for FreeDOS, there is no quality control
dept either. On the other hand, there could be one - working
with volunteers, just like our software devel dept :-).
Hello list!
I created with BootIt NG a primary partion 512 MB, FAT16, set active, swap
drive 0 (is this needed for FreeDOS or does only Windows boot from HD0?).
Than I created the full FreeDOS CD and booted and installed form CD nearly
everything.
When I try to bot from this HD or BootIt boot
On 6/6/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hello list!
I created with BootIt NG a primary partion 512 MB, FAT16, set active, swap
drive 0 (is this needed for FreeDOS or does only Windows boot from HD0?).
Than I created the full FreeDOS CD and booted and installed form CD nearly
I'm able to boot now, but with errors:
1. EMM386
selected page frame e000 not availible
searching, no suitible frame found
EMS functions limited
2. Bad or missing Command interpreter: C:\FDOS\bin\command.com C:\FDOS\bin
/E:1/P=C:\auotexec.bat
Enter full st. commandline:
C is now with FDOS
Hi Wolfgang,
I'm able to boot now, but with errors:
What did you change?
1. EMM386
selected page frame e000 not availible
searching, no suitible frame found
EMS functions limited
Your hardware has too many data exchange areas and BIOSes
in the area between 640k and 1 MB, so DOS cannot
I tried to install FreeDOS 1.0 folling the HOWTO and it appears
to have failed rather miserably:
1) The HOWTO says it will create a boot menu that will allow
me to dual-boot. It didn't. I can no-longer boot WinMe.
2) No editors. emacs can't find it's .ed files, and none of
the vi
2. Bad or missing Command interpreter: C:\FDOS\bin\command.com C:\FDOS\bin
/E:1/P=C:\auotexec.bat
That should mean exactly that. The command.com file is not
found, maybe because the install did not fully complete.
it could also be that you boot from CD boot area, which becomes A: so
you
