On Mon, 29 Mar 2004 19:00:54 -0300, Alain wrote:
INHO and considering that FreeDOS is in C versus all other DOSes being
in ASM
ROM-DOS, our greatest living competitor (not speaking of the venerable
DR-DOS that is still in coma and PC-DOS that must have finally died in
2002) is also written 90%
On Fri, 26 Mar 2004 22:22:20 + (GMT), Bart Oldeman wrote:
Can you check again? I think I solved at least Lucho's problem during the
init phase -- when fnodes could overlap disk buffers! Weird things could
happen indeed.
Congratulations, Bart! Bug fixed indeed - just tried. But I keep thinking
Hi!
27--2004 12:18 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
LG Bad news: the new build batch files don't do anything in 4DOS, probably
BO it's picky about
BO call config
BO instead of
BO call config.bat
And? [BTW, just check under freecom - also all works.]
PS: I not
Hi!
27--2004 21:10 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
Becuase I show in skipped part you, that this doesn't (always) works.
BO that (not accepting call default.bat) is a bug in 4dos 6.02 then that
call cls.com calls internal command both in NDOS and
The patched kernel behaves very strangely! :-( It outputs an error
for DEVICE=C:\DOS\HIRAM.EXE line and doesn't load it and repeates
this with many other lines (but not all). For my simpler floppy
configuration, it doesn't load HIMEM64.EXE without even showing an
error!
The
The patched kernel behaves very strangely! :-( It outputs an error
for DEVICE=C:\DOS\HIRAM.EXE line and doesn't load it and repeates
this with many other lines (but not all). For my simpler floppy
configuration, it doesn't load HIMEM64.EXE without even showing an
error!
The current
The current nightly-kernel may have reached a new landmark in the
quest for smaller conventinal-memory footprint but it lost ground in
usability and compatibility. My test-machines halt on various
arbitrary points telling me: more than two near fnodes requested at
the same time
ok
The current nightly-kernel may have reached a new landmark in the
quest for smaller conventinal-memory footprint but it lost ground in
usability and compatibility. My test-machines halt on various
arbitrary points telling me: more than two near fnodes requested at
the same time
if files=10 would
