Re: [Freedos-kernel] Floppy disk read error

2004-07-21 Thread Arkady V.Belousov
Hi!

17--2004 00:38 [EMAIL PROTECTED] (Alain) wrote to
[EMAIL PROTECTED]:

  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.
A Please yes, but sent it packed (zip or rar), it could get blocked by
A some overzealous antivirus.

 Of course, I send in RAR archive.

A And yes, a separate letter will help to find it. You and also send it cc:
A to am (AT) cosmodata.com.br, which is on a diffrent server.

 I sent to both addresses.

A I checked all my Spam and Garbadge an found nothing with attachement...

 Then I don't know, how to send attachments to you. :(




---
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_idG21alloc_id040op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] Floppy disk read error

2004-07-16 Thread Alain

Arkady V.Belousov escreveu:
A I belive that what Nathan describes below is very close to what is
A happening!
 No. FD already have retry logic. See dsk.c:LBA_Transfer(): there access
repeater up to 5 times (N_RETRY defined in device.h as 5), with fl_reset()
between tryings.
Ok :(
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.
Copy (internal of FreeCOM)
A - made this same test with MS-DOS 7.10 for comparisons
 And?
Results are what I explained below, plus that I got no unexpected error
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.
Not HARDWARE: I was forcing erros by _removing_ the disks. Same 
procedure with both OSs, to be able to get a comparison.

A - before the error FD makes a little more noise (head movements) than
A M$, probably a longer head movement or twice the same movement.
 Probably, because more retries (5 instead 3).
Ok, that is compatible with what I got
A Can someone send me a debug enabled KERNEL.SYS please? I believe I can
A dig out some information with it.
 I already do this. Isn't you receive k-debug.sys? Just rename it to
kernel.sys.
I didn't receive any kernel shipped to me. I got kernel 2035a from 
Lucho's site, a link was posted here. Please send me a link if sending a 
file is difficult. BTW I believe that this is not affected by new 
patches, sot it could be 2035 too.

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=4721alloc_id=10040op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] Floppy disk read error

2004-07-16 Thread Alain

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=4721alloc_id=10040op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] Floppy disk read error

2004-07-15 Thread Arkady V.Belousov
Hi!

15--2004 20:44 [EMAIL PROTECTED] (Alain) wrote to
[EMAIL PROTECTED]:

A Nathan Crawford escreveu:
 To fix it, I changed the driver so that the disk operation was checked
 for success, and if it failed, it first reset the drive with int 13
 ax=, and then retried the read.  It would do this three times, or
 until the operation succeeded.
A I belive that what Nathan describes below is very close to what is
A happening!

 No. FD already have retry logic. See dsk.c:LBA_Transfer(): there access
repeater up to 5 times (N_RETRY defined in device.h as 5), with fl_reset()
between tryings.

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 - made this same test with MS-DOS 7.10 for comparisons

 And?

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 - before the error FD makes a little more noise (head movements) than
A M$, probably a longer head movement or twice the same movement.

 Probably, because more retries (5 instead 3).

A Can someone send me a debug enabled KERNEL.SYS please? I believe I can
A dig out some information with it.

 I already do this. Isn't you receive k-debug.sys? Just rename it to
kernel.sys.




---
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_idG21alloc_id040op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] Floppy disk read error

2004-07-14 Thread Alain
A I am experiencing a strange problem with FreeDOS, please help me because
A   I am not sure how it is happening:
1. Do you test 2035a?
No, please send me the link to it. I just cannot find it.
2. Do you test FD with same conditions, as other OSes (for example, if you
   boot from diskette for FD, do you boot from diskette for MS-DOS7)?
Yes.
A When I boot from C:, sometimes (very frequently) when I access floppy
A disk A: I get a message device not ready. I seems to be worse when I
A read 2 floppies sequentianly using a BATCH file that asks for the user
A two swap disks and pauses. Second floppy says not ready, after a few
A retries it starts working, but stops again but accepts retry. Every time
A the floppy drive led does light, I checked. If I copy the same files
A manualy (with copy a:*) it works.
 This looks like hardware (floppy drive) problem (something like trouble
with head moving).
It certainly looks like, so I did all the checks including using a brand 
new driver.

It certainly is FreeDOS related. It was _much_ worse with 3034. This 
does not meen that there is not something wrong somewhere too, but other 
OS's work, maybe with an automatic retry or whatever. It is probably 
something wrong + something in FreeDOS that behaves erroniously.

A I really did not understand what happens. My gess is that the floppy
A swap was not detected, but this is not 100% coherent...
 Do you mean, that drive, probably, not senses diskette change? No, I
don't think so - with broken change line there are other simptoms.
Ok that is an old hw bug. That is not it, behaviour would be different.
The problem is that there is no debug option that could help me detect 
what is really happening. If I could understand it better, I could make 
a better test. I do have some experience, but I am lost here :(

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=4721alloc_id=10040op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel


Re: [Freedos-kernel] Floppy disk read error

2004-07-14 Thread Arkady V.Belousov
Hi!

14--2004 22:41 [EMAIL PROTECTED] (Alain) wrote to
[EMAIL PROTECTED]:

 1. Do you test 2035a?
A No, please send me the link to it. I just cannot find it.

 Sources you may find at freedos.sf.net/kernel.UNSTABLE.tgz, compiled
image available at Lucho site. Also, Kenneth promise to place image on his
site www.fdos.org. If you wish, I send you may compiled edition.

  This looks like hardware (floppy drive) problem (something like trouble
 with head moving).
A It certainly looks like, so I did all the checks including using a brand
A new driver.
A It certainly is FreeDOS related. It was _much_ worse with 3034. This

 I test FreeDOS on diskette and found no issues.

A does not meen that there is not something wrong somewhere too, but other
A OS's work, maybe with an automatic retry or whatever. It is probably
A something wrong + something in FreeDOS that behaves erroniously.

 Then I can't (yet) suggest anything other here. :( FreeDOS, as other
OSes, completely BIOS-depended when accessing floppies.

A The problem is that there is no debug option that could help me detect
A what is really happening.

 You may recompile with turned DEBUGing and you get a lot of tracing
messages on screen. There are no permanently built-in debugging, which may
be turned on the fly, especially because this noticeably increases kernel.

A If I could understand it better, I could make
A a better test. I do have some experience, but I am lost here :(




---
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_idG21alloc_id040op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel