At 02:29 PM 3/12/2004 +0300, Arkady V.Belousov wrote: >MD> Additional technical details follow: >[...] >MD> The above change brings up an interesting conflict with NOEMS: programs >MD> such as Turbo Debugger 2.5 will fail with a 'fatal EMS error' if the NOEMS >[...] >MD> machine, I'd recommend using a value of EMM=1 rather than NOEMS. That makes >MD> both of them happy. > > I think, this definitely should be included into some text file in the >package. For exampel, QA.TXT: "Q: Why NIOS doesn't load?", "Q: Why Turbo >Debugger fails?".
I have enough on my plate for now writing and debugging the code and keeping up with messages here, plus maintaining a semblance of a real life. At least the external info is saved in the archives, for whenever a full user documentation effort across all FreeDOS utils and apps is underway. > BTW, I should mention, that this is far not last bug from Borland. :( >For example, I was forced to make weaker arguments check in mouse driver >because peculiarity of TP IDE. I don't mind the fact that TD only looks at the INT 67h vector to try EMS, it's common and heck, I think I used to do it once in a while. What I mind is that after Turbo Debugger uses the EMS vector and gets an EMS failure for the check status and other calls instead of going "Gee, EMS isn't available, I guess I should only use conventional memory as I am fully capable of doing", heck no, it instead decides to pout and goes "Braackkk! EMS isn't available even though the vector is present, I'll show those snooty EMS-hoarding Scrooges, I'll shut down completely and refuse to run". An anonymous Borland programmer didn't have their proper caffeine dosage the morning they coded that part of TD. Hey, maybe it was Philippe. ------------------------------------------------------- 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=1470&alloc_id=3638&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
