Hi!
9-Июн-2004 20:19 [EMAIL PROTECTED] (Eric Auer) wrote to
[EMAIL PROTECTED]:
>> (Clear high parts of 32bit regs...)
>> How this relates to DOS?
EA> MS DOS basically had no 386 stuff at all (except EMM386). In FreeDOS,
EA> however, people run 386 aware programs more often. Those leave non-zero
EA> values in 32 bit registers when they exit, and the next program which you
EA> start...
EA> Whatever. You are right. Very bad programming practice to expect the high
EA> parts of the 32 bit registers to have some value.
Expecting _any_ undocumented value is very bad practice, and changing
FD only because some "super-demo doesn't run properly", I think, not very
good. Unfortunately, in case of undocumented 16-bit registers, some other
useful programs also may expected specific values.
EA> I close that "bug report" then.
Fine.
>> EA> If it would be DOS4GW then we would be really motivated :-).
>> ...to built DOS4GW into kernel? You joke.
EA> I meant "if DOS4GW had problems with FreeDOS because FreeDOS does not
EA> clear high parts of 32 bit registers on exec then we should probably
EA> clear high parts of 32 bit registers on exec"... But now that only an
EA> old GRDB is affected, I simply marked the bug as RESOLVED WONTFIX.
Right. This is coding bug in consequent application, OS shouldn't try
to "fix" all possible errors in any possible application.
>> 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...
EA> I see no convincing technical reason why FreeDOS should not auto-detect the
EA> "more than 2 floppy drives exist"
...and? What next? Assign C: and D: for those additional drives? All
other (non-adjacent to A: and B:) drive letters will mislead users.
EA> working computer has one. Do we need to change the FreeDOS Manifesto in
EA> order to drop DRIVPARM / DRIVER.SYS plans?
No. DRIVPARM not _add_ drive letters, it _changes_ properties of
already registered. For example, on one broken computer with help of
DRIVPARM I say to DOS that change line doesn't working (properly).
>> My (old) computer have no APM support.
EA> FDAPM does not need APM. If you have it, FDAPM can use it. If not, no
EA> problem. All x86 CPUs have the HLT instruction...
EA> Things which you can do without APM with FDAPM: turn VGA on/off, spin IDE
EA> harddisks down (SPINDOWN command), save energy with help of HLT instruction,
EA> using APMDOS command, show statistics about that energy saving TSR mode,
EA> reboot through "out 64,fe" / through "jmp ffff:0" / through "int 19".
Ok. How I may/should test the FDAPM? Where it (URL)?
>> EA> About bug 1789, kernel confused by PKZIP-builtin format command
>> Which URL?
EA> http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=1789
I look at this.
EA> the ret / ret 8 issue in fl_lba_ReadWrite (when did that bug get INTRODUCED?
When Bart changes fl_* function from ASMC to ASMPASCAL calling
convention.
EA> Maybe I better downgrade to some older kernel / upgrade to a CVS kernel???).
Better to fix the bug(s). :)
-------------------------------------------------------
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
