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:FDCD00
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 di
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 m
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 UD
Hi,
Gerry Hickman escribió:
What is the correct procedure for getting a "working boot
program" into the "valid Master Boot Record", and who supplies this
program? Is it Microsoft, Intel??
Hard drives usually have a default MBR, just as pre-formatted floppies
have default FAT the information
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.c
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 an
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
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 wi
Hi Johnson,
I switch to FDISK 1.2.1 (old one) and everything works, even the
logical drive size problem gone.
With old FDISK the XEON server boot normally
Thank you very much for your test procedure!
1) FDISK 1.2.1 UI have bugs, command line OK
2) FDISK 1.2.1-K not working
OK, I think
Michael Devore schreef:
At 08:07 PM 8/1/2005 +0200, Bernd Blaauw wrote:
either this is to scare non-technical people away (invalid URL) or
you're spending too much time in DOS :)
ftp.devoresoftware.com/downloads/emm386
Both styles work in IE and Firefox. Logs show browsers are how 90% of
At 08:07 PM 8/1/2005 +0200, Bernd Blaauw wrote:
either this is to scare non-technical people away (invalid URL) or you're
spending too much time in DOS :)
ftp.devoresoftware.com/downloads/emm386
Both styles work in IE and Firefox. Logs show browsers are how 90% of
people get the files. Wh
Eric Twose schreef:
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).
you could try how your project behaves on a ramdrive.
* MS RAMDR
Michael Devore schreef:
Specifically, with
device=a:\himem.exe
device=a:\emm386.exe x=test memcheck vds
Alright, one more time. I rewrote the VDS routines such that any
reserved function which was unused (0, 1, 0dh-0ffh) no longer returns an
error code, but simply sets carry flag and chains
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,
d
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
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 :-)
>
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 no
On Sat, 30 Jul 2005 15:58:04 +0100, you wrote:
Hi Gerry,
Finally did all the test ...
I found that Jeremy removed the "test" version of FDISK 1.3.0 beta
from his website. My copy is downloaded last week, the version still
shows "1.2.1-k".
Following you list, it fail in:
>>1. Boot FreeDOS on a
19 matches
Mail list logo
