Michael, Eric, Dave
I just altered my EMail setup to better track this thread. I have missed
some messages.
On Fri, Aug 17, 2012 at 9:30 AM, Michael B. Brutman
mbbrut...@brutman.comwrote:
John,
Just to make sure I understand ...
You are running a batch file that is doing net use to setup
it is my sincere belief that everyone possible
should file a feature request/bug report with
the virtualbox people so UIDE works without the
two-minute analogy delay upon v.m. boot,
including those who know why and how UIDE is
delayed.
if we do this sincerely then they probably will
be
...@wolterworks.com
To: Michael B. Brutman mbbrut...@brutman.com
Cc: Discussion and general questions about FreeDOS.
freedos-user@lists.sourceforge.net
Sent: Thu, Aug 16, 2012 9:05 pm
Subject: Re: [Freedos-user] FreeDos in VirtualBox not a sure thing
Mike,
Good to make your acquaintance. Let me
John,
Just to make sure I understand ...
You are running a batch file that is doing net use to setup printer
shares, a file share, and loads nansi.sys. And the output to the screen
during that time is around 8.5 chars per second?
Just as a comparison, running the FreeDOS Beta of 1.1 under
Hi! Two thoughts about NANSI being slow in VirtualBox
while network drives and printers are used and FDAPM
is active: In DOSEMU, you can configure how agressive
screen updates should be. So it can try to keep up
with screen updates, or it can just occasionally do
a window update. DOSEMU also runs
Op 16-8-2012 0:46, john s wolter schreef:
I spent four days getting FreeDOS to work as a guest OS inside a
VirtualBox machine. The path to success was a rocky and time consuming
trial and error process. Once the particular console program was
running it was not very fast. The customer
Hi Cordata,
So is the problem simply eating up processor time?
Note that this is probably not VM specific and would
also happen on real hardware. Why not run DOS on your
real 64 bit CPU? At boot, it is in 16 bit addr space
anyway, allowing the usual DOS 16/32 bit calculations.
You would waste
Hi Eric,
Note that this is probably not VM specific and wouldalso happen on real
hardware.
If I'm running DOS in a production environment on real hardware I (personally)
would make sure the hardware could handle it and not overheat. There are
plenty of industrial solutions out there that
I spent four days getting FreeDOS to work as a guest OS inside a VirtualBox
machine. The path to success was a rocky and time consuming trial and
error process. Once the particular console program was running it was not
very fast. The customer deemed it to be usable.
Later in the day the
);
void delay_a_tick()
{
long ticks = *bios_clk_ptr;
while(*bios_clk_ptr == ticks)
_asm hlt;
}
-Original Message-
From: john s wolter johnswol...@wolterworks.com
To: freedos-user freedos-user@lists.sourceforge.net
Sent: Wed, Aug 15, 2012 5:47 pm
Subject: [Freedos-user] FreeDos in VirtualBox
Subject: [Freedos-user] FreeDos in VirtualBox not a sure thing
I spent four days getting FreeDOS to work as a guest OS inside a
VirtualBox machine. The path to success was a rocky and time consuming
trial and error process. Once the particular console program was running
it was not very fast
John,
Maybe you could help us by being very specific with what worked and what
went wrong? The only thing I could gather from your message was that it
was difficult to do, and it was slow.
One thing that is essential for good performance is to ensure that your
host machine is new enough to
12 matches
Mail list logo
