Another thing when running FreeDOS in a VM is the CPU usage of the host
machine. It will be go to 100% and the CPU fan will start. I use always
the FDAPM with the parameter APMDOS so the HLT command is used (I think
it's the instruction). With this, the host CPU is about 4% usage on my
1GHz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arkady V.Belousov wrote:
AB Most emulators / virtualizer are now close to 1 (as of QEMU and VMware).
AB There is no real / perfect solution to have a precise clock in a VM.
AB This is because it would have a big performance penalty.
Let me
Hi!
21-Июл-2006 18:43 [EMAIL PROTECTED] (Andreas Bollhalder) wrote to
freedos-devel@lists.sourceforge.net:
AB There is no real / perfect solution to have a precise clock in a VM.
AB This is because it would have a big performance penalty.
Let me doubt in this - for example, for DOS
Hi!
19-Июл-2006 17:49 [EMAIL PROTECTED] (Andreas Bollhalder) wrote to
freedos-devel@lists.sourceforge.net:
AB for two days and I had to read about 70 mail... I personally use QEMU
AB and VMware Server for testing purposes and timers often run too fast. I
AB remember that I saw this effect in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As I can tell from my experince, the factor depends a lot from the host
speed and emulation / virtualisation software. I saw speed differences
from about a bit faster ( 1.0) up to 10 times.
Most emulators / virtualizer are now close to 1 (as of QEMU
Hi!
20-Июл-2006 18:43 [EMAIL PROTECTED] (Andreas Bollhalder) wrote to
freedos-devel@lists.sourceforge.net:
Does this mean, that when you run some program, which shows clock (for
example, Norton and Volcov Commander may show clock), then this clock is too
fast? And how it fast - 1.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, first sorry about the unneeded info. I couldn't check my emails
for two days and I had to read about 70 mail... I personally use QEMU
and VMware Server for testing purposes and timers often run too fast. I
remember that I saw this effect in Bochs
I feel very strongly that we must not have timeouts on the options when
you first boot. Eric gives a good example - it happened to me. I was
at work when I was testing the new CDROM (on Parallels on my iMac) and
happened to get a phone call. When I looked back at my session, I had
gotten an
At 12:41 PM 7/17/2006 -0700, Blair Campbell wrote:
The only two timeouts are the first timeout which defaults to boot
from the hard drive rather than the CD-ROM (nothing wrong with that
IMHO), and the second just boots defaultly into installation mode,
which is what most people will be after.
I,
Hi!
17-Июл-2006 19:01 [EMAIL PROTECTED] (Blair Campbell) wrote to
freedos-devel@lists.sourceforge.net:
The only two timeouts are the first timeout which defaults to boot
from the hard drive rather than the CD-ROM (nothing wrong with that
IMHO), and the second just boots defaultly into
Hi!
18-Июл-2006 23:09 [EMAIL PROTECTED] (Andreas Bollhalder) wrote to
freedos-devel@lists.sourceforge.net:
One thing I would recommend is that we not have a timer on the options
when you boot the install CD. If I were a new user to FreeDOS, I'd
probably feel a bit rushed and would prefer to
We agree (Eric, Arkady ans me(Alain)) without any discussion! This must
be something to comemorate...
Alain
Arkady V.Belousov escreveu:
Win9x setup gives timeout before reboot, _after_ setup finished (some
steps). And I disagree, that installer should be timeouted in any part,
Arkady V.Belousov escreveu:
AB Especially when testing in a VM, the timer runs often too fast.
This is very strange, because shouldn't happen - config.c for timeouts
uses BIOS timer variable (see GetBiosTime() usage in GetBiosKey()). And,
with current code in GetBiosKey(), worser case
Soon available at
www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0-Testing
will be the files:
fdfullws.iso - FreeDOS with all disksets and corrosponding sources
fdfullcd.iso - FreeDOS with all disksets without sources
fdbasews.iso - FreeDOS BASE diskset with corrosponding sources
I'm experimenting with fdfullws.iso at the moment. It looks good so
far, but I'm not done with the install yet. There is some menu cleanup
that we could do before 1.0 ... I'll do some more experimenting and see
if I can suggest something.
One thing I would recommend is that we not have a
Jim Hall wrote:
I'm experimenting with fdfullws.iso at the moment. It looks good so
far, but I'm not done with the install yet. There is some menu cleanup
that we could do before 1.0 ... I'll do some more experimenting and see
if I can suggest something.
One thing I would recommend is
They have 15 seconds the first time (Win98 only gives 10 FYI), and the
second timeout gives 30 seconds. More than enough IMHO.
On 7/17/06, Eric Auer [EMAIL PROTECTED] wrote:
The only two timeouts are the first timeout which defaults to boot
from the hard drive rather than the CD-ROM
17 matches
Mail list logo
