Re: [Freedos-kernel] new conv mem highs.

2004-03-29 Thread Luchezar Georgiev
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% in C but uses much more conventional RAM. But 
what we talk about is *data*, not code, so language doesn't matter.

I believe that we should just _CELEBRATE_ :)
FreeDOS 7.1: 10688
 MS-DOS 7.1:  9680
 PC-DOS 7.1:  9456
Where's the Champaigne? ;-)

Lucho

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] new conv mem highs.

2004-03-27 Thread Luchezar Georgiev
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 
that the right place for the far fnodes is the HMA (I haven't checked yet 
your latest CVS changes though - you work lightning fast! ;-)

By the way, you're a good detective (but in time you'll see that I'm also 
not a bad one ;-)

Lucho

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] new conv mem highs.

2004-03-27 Thread Arkady V.Belousov
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 against of using explict extensions, but wonder what wrong in
given case?




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] new conv mem highs.

2004-03-27 Thread Arkady V.Belousov
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 command.com
also, so this is not a bug, but a feature. :(

BO Personally I would like to compile the kernel without batch files using
BO a simple make. Problem is that we're dealing with n incompatible MAKEs.

 Problem is same, as with shells - too many different and often
incompatible ones.

BO Also at the time Tom mentioned that he found batch files easier to debug.

 I agreed - MAKE execution (sometime) isn't completely transparent and
it can't replace the shell: for example, what about conditional execution?
Something like if exist file set var=path?

BO * GNU Make is not shipped with FreeDOS, and the last time I checked it the
BO   8086 version from GNUish wasn't terribly stable (could have been an FD
BO   kernel problem though)

 I wonder why, but (almost) all GNU tools executables are too big and
not always available under DOS (especially 16-bit). :(

BO * OW WMAKE also uses quite a bit of memory and can't swap.

 For BC I use MAKER -S (which I also add into config.b).




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] new conv mem highs.

2004-03-26 Thread Bart Oldeman
   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 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

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.

After booting I haven't seen the message you quote though, so please let
me know how to reproduce if it still occurs for you.

I made an intermediate kernel tarball just in case the cronjob fails.

Bart



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] new conv mem highs.

2004-03-24 Thread Erwin Veermans
  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 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

:-/

Erwin




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] new conv mem highs.

2004-03-24 Thread Erwin Veermans
  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 that's good. It means that that panic was justified to implement
 for me as a failsafe.
 
 Remember CVS is for (public) development, released kernels should
 never have this behaviour so I'll have to fix something...

Sure, not meant for end-users. 
I just figured it would be good to raise an alert about the
current kernel to back up Lucho's remark.
 
 Bart

Erwin




---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] new conv mem highs.

2004-03-24 Thread Bernd Blaauw
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 work for you, then there are 10 of those f-nodes.
maybe that's the minimum that should be kept in conventional memory?
move all i-nodes except (the first?/lowest?) 10 into HMA

don't know if this is possible. Bart is the expert here.

Bernd

---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel