Hi, tocayo,  ;-)

On Tue, Oct 18, 2011 at 4:00 PM, Anton Vernigor <smm...@gmail.com> wrote:
> I’m trying to install FreeDOS (fdbasecd.iso) on a real (not virtual) machine
> for the first time, and I’ve met some problems. At first I couldn’t install
> FreeDOS at all, despite it was installed on VirtualBox flawlessly.
> Installation went well, no errors or warnings, and after the final reboot I
> got blank black screen with no reaction to any input, only power button
> could help.

Must be MBR or boot sector issue. (Perhaps an FDISK bug??)

> It seems it was fixed with another options used while partitioning the disc,
> but I’m not sure what certain option did the job.

"fdisk /mbr" perhaps??

> But after all I still see some strange behavior in just installed system. If
> I choose default second option in startup menu (Load freeDOS with EMM386+EMS
> and SHARE), the screen gets filled with error message, and I still see no
> reaction on keyboard or trackpad. Screen looks like this.

If you're using FreeDOS 1.0 (2006), you may want to upgrade your EMM386 to JEMM.



I suggest "JEMM386 X=TEST I=TEST" or similar (see its README.TXT).

> The other strange thing is that first (Load FreeDOS with EMM386, no EMS
> (most UMBs), max RAM free) or third (Load FreeDOS including HIMEM XMS-memory
> driver) option in startup menu works normally, as I see (not investigated
> seriously, but at least it looks so).

Sounds like an EMM386 bug. I know I don't speak for everybody, but
I'll try anyways:  nobody uses "old" EMM386, use "new" JEMM386.    ;-)

> Fourth option can’t be chosen at all.

You can edit it by hand (if savvy enough).

> So as I’m new to this kind of OS I ask where can I read about this problem
> with second menu option and how can I try to fix it, if it’s possible?


N.B. to others, the news item has long ago scrolled off the main page,
so we need to not forget to proofread this (FDhelp) one of these

> Just for now I’ve edited fdconfig.sys to hide menu and use the third option
> by default, but it doesn’t look like a good solution.
> What kind of hardware info may be helpful for solving this problem?

Just upgrade to JEMM386 first, then we'll see.

Though I would also suggest getting kernel 2040, but I don't think
that specifically will fix anything here.


All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
Freedos-user mailing list

Reply via email to