Arkady V.Belousov escreveu:
Hi!
16-Июл-2004 22:15 [EMAIL PROTECTED] (Alain) wrote to [EMAIL PROTECTED]:
A> - if after the error, if I use the "a" option for abort, there is an A> "out of memory error" before returning to command prompt. "Before returning to command prompt" from which program? Note: kernel doesn't contains string "Out of memory".
A> Copy (internal of FreeCOM)
Looks like bug in FreeCOM. Steffen already fixes some bugs and, I hope, at some time makes fixed edition available to download (without recompilation).
A> - made this same test with MS-DOS 7.10 for comparisons And?
A> Results are what I explained below, plus that I got no unexpected error
Do you use MS-command.com or FreeCOM? As I understand, "no unexpected error" mean MS-command.com in given test?
1) I tested FreeDOS kernel with FreeCOM 2) I tested M$-DOS kernel and commad.com from M$
I will make some mixed tests, the idea is good ;-)
A> - If the motor has stopped, it waits a reasonable amout of time before A> showing the error, if the motor is still running (faster retry) it is A> faster. Delays are comparable between FD and M$.>> So, trouble not with FD? Another reason, that your hardware (drive, chipset, cable) is broken.
A> Not HARDWARE: I was forcing erros by _removing_ the disks. Same A> procedure with both OSs, to be able to get a comparison.
Then I don't understand: you remove diskette while there is copying something, and wish to _not_ get critical errors?! (Of course, "Out of memory" error is bug of FreeCOM, which should be fixed and, probably, already fixed).
No what I did was 3 diffenrent things:
1) FreeDOS: I got an error while copying files with normal program install, not so many errors with copy issued by hand (not in batch)
2) Test for comparison
2a) New boot, try to copy a file but removed floppy, note results
2b) New boot with M$-DOS, try to copy a file but removed floppy, note results, compared with 2a)
=> tested 2a and 2b many times with floppy and without floppy to see what happens in different situations and compare.
The out of memory error is coherent with axplained bug in FreeCOM of improper error message. If I abort a copy, _some_ message should get printed, it can just be the wrong text.
To be precise, as pointed by tom, in 2035 present bug, which related to critical errors (and it not completely fixed in 2035a), but this bug will look as hungup with message "more than two near fnodes requested at the same time!".
Not this one :)
A> Can someone send me a debug enabled KERNEL.SYS please? I believe I can I already do this. Isn't you receive k-debug.sys? Just rename it to kernel.sys.
A> I didn't receive any kernel shipped to me.
Later (after I recompile again) I try to send you (privately) compiled kernels again (and send separate letter with notification about this). But if you not receive this archive again, then I can't help you, because have no other ways beside mail.
Please yes, but sent it packed (zip or rar), it could get blocked by some overzealous antivirus. And yes, a separate letter will help to find it. You and also send it cc: to <am (AT) cosmodata.com.br>, which is on a diffrent server.
I checked all my Spam and Garbadge an found nothing with attachement...
thanks, Alain
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
