Hi!
9-Июн-2004 03:27 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
EA> The bug submitter for "clear high parts of 32 bit registers on exec"
EA> claims to have experienced actual problems because of one program leaving
EA> values in registers and another program assuming those parts to be 0.
Some drivers (say, himem) on machine, where was written those
garbage-dependent program, clear high parts of registers. How this relates
to DOS?
EA> However, he does not tell anything about which program is affected.
We have proverb (fairy tale, to be precise): "go don't know where, get
don't know what". Same here: we don't know, which program affected, don't
know what it expected (and why!), how these expectations was reached (DOS?
drivers?) - and we should achive these expectations?!
EA> If it would be DOS4GW then we would be really motivated :-).
...to built DOS4GW into kernel? You joke.
>> How DOS should deal with third and fourth drives - I don't know, but I
>> suggest, this is possible only through driver.sys (there you point physical
>> drive number 0..127, and it traps next logical drive letter).
EA> You just said that BIOS would handle it and that equipment list can handle
EA> up to four drives as well. So why would we need a driver sys for it? And I
Because MS-DOS need it. From first versions there was reserved only two
letters for floppy drivers, and we can/should not change this. Especially,
programs with two controllers very rare and there are not hard to use
additional driver (and/or config.sys statement) for supporting those
additional hardware.
EA> do indeed suggest to make driver sys a kernel builtin if we need it at all.
This is not bug report, but wish. Also, this wish about _additional
feature_, not about change for behavior. (Changing order of drive letters
assignment _is_ feature with changed behavior).
>> Ie. you offer to integrate help, tutor and training subsystem into
>> kernel? Currently DOS ignores DOS=UMB statement, if there are no UMBs
>> available. I think, extra messages like "NO UPPER MEMORY AVAILABLE FOR YOUR
>> DOS=UMB STATEMENT" makes only uncomfortable noise.
EA> This is partially true.
This is completely true. Me always annoys messages from NDOS' LH
command about missing UMB. Note: there may be common configs for different
environments, where one environment contains UMBs, other - not.
EA> Better error messages are sometimes good but a whole
EA> tutor system would mean noise. By the way, does the kernel suppress showing
EA> more than one UMB-warning if you have more than one DEVICEHIGH/INSTALLHIGH
EA> now?
Don't know yet, config.c is not processed by me yet.
EA> Bernd filed a bug report / feature request to suppress the extra noise.
>> Manifest from QEMM
EA> This reminds me that some QEMM versions spoil APMDOS / ADV:... mode of
EA> FDAPM (i.e. it saves no energy if QEMM loaded). If you have QEMM yourself,
EA> feel free to test whether your version is affected in combination with your
EA> CPU and BIOS.
My (old) computer have no APM support.
EA> Manifest was a cool piece of software at the time.
Yes, nice.
EA> About bug 1789, kernel confused by PKZIP-builtin format command: I think
EA> the LBA-... error message happened at the beginning and the end of the
EA> process. But please do read the whole bugzilla entry and contact the bug
EA> reporter to learn more, I do not use PKZIP (I use Info-ZIP ZIP / UNZIP).
Which URL?
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
