/* This is an automated message sent out on the 1st
of each month. It is automagically downloaded from
http://www.freedos.org/freedos/lists/remind.txt */
MONTHLY REMINDER FOR THE FREEDOS MAILING LIST
Hi! If you are a new reader of freedos-devel (or the other FreeDOS
lists) then, welcome! If you
At 01:08 AM 7/31/2005 +0100, Gerry Hickman wrote:
Oh good grief. EMM386 doesn't have the code or capability to mess with
disk partitions. Period.
But if drive geometry is being misreported or misunderstood under EMM386
with VDS (which appears to be the case), then my guess is that it would
At 03:38 AM 7/30/2005 +, Mark Bailey wrote:
I see no difference at all with that version, either with the
development kernel/command.com or the stable kernel/
command.com.
Specifically, with
device=a:\himem.exe
device=a:\emm386.exe x=test memcheck vds
vol c: hangs. Remove vds, it works
On Sun, 31 Jul 2005 17:40:56 +0100, you wrote:
Hi Gerry,
GUI (the current version should be UI)
Sorry, UI
Never mind.
Yes, I'm not against the UI, I'm just saying I've never needed it and
(in my opinion) it's actually less confusing to use commands only.
Because you're not novice :-)
2)
On Sun, 31 Jul 2005 21:40:40 +0100, you wrote:
Hi,
I'm currently writing a project in C using djgpp that runs in DOS and
hopefully soon in FreeDOS. I notice that hard disk access is poor (noisy and
frantic, as it is when booting into Windows safe mode).
FreeDOS is DOS compatible, of course
Johnson Lam wrote:
FreeDOS is DOS compatible, of course not 100% but most of the
program works.
Dear Johnson,
Many thanks for your help. The good news is, yes, my program now runs
successfully under FreeDOS.
[noisy, frantic hard drive] is because the UltraDMA mode disabled in BIOS,
Eric T wrote:
hard disk access is poor (noisy and frantic, as it is when booting into
Windows safe mode).
Bernd wrote:
you could try how your project behaves on a ramdrive.
:) Maybe selectively. Most of the output at the moment is going to a debug
log file. But the project itself will
Hi Michael,
My main point was that the FDISK bug may have been _triggered_ by EMM386
with VDS, and that if he hadn't been running EMM386 his FDISK tests
would not have caused a bad partition table. You were saying this:
Oh good grief. EMM386 doesn't have the code or capability to mess
with
Hi,
I tested EMM386 horse with VDS option, and on this system it's still
total meltdown. All hard drive info misreported. Too scared to continue
in case can't boot anymore.
Asus A7V333 latest BIOS
Adaptec 29160N SCSI host adapter with 2 x 36Gb drives
FreeDOS Beta9sr1 except HIMEM64 3.10a and
Hi Michael:
No change with this version...system hangs on vol c: with VDS
option, works without.
Mark Bailey
At 03:38 AM 7/30/2005 +, Mark Bailey wrote:
I see no difference at all with that version, either with the
development kernel/command.com or the stable kernel/
command.com.
Hi Eric,
please do not use HTML mail. Use plain text instead. Thanks...
I'm currently writing a project in C using djgpp that runs in DOS...
hard disk access is poor (noisy and frantic, as... Windows safe mode).
Then you should indeed try the UDMA2 driver (only for PCI/newer systems,
and
On Mon, 1 Aug 2005 18:54:24 +0100, you wrote:
Hi Eric T.,
Many thanks for your help. The good news is, yes, my program now runs
successfully under FreeDOS.
Good news, hope you enjoy the feeling.
Alas, the old (pre-1997) machine I've set up with FreeDOS reports that my
c:\ drive (in LBA
On Mon, 01 Aug 2005 20:01:00 +0100, you wrote:
Hi Gerry,
OK, I think this is where we are going wrong on this list with the
testing (me included). People are posting results without locking down
versioning. I mean we are all running totoally different versions and
then wonder why we get
On Mon, 01 Aug 2005 23:02:59 +0100, you wrote:
Hi,
My painfully research result, may help you to optimize the CONFIG.SYS:
rem Why do some people run non-SCSI drives?
;DEVICE=DRIVER\UDMA2.SYS
Because SCSI means expensive!!
rem This is not open source!
DEVICEhigh=OTHER\VIDE-CDD.SYS /D:FDCD
14 matches
Mail list logo
