From: Christopher Phillips (shrydar_at_jaruth.com)
Date: 2005-04-26 03:31:10
On 25 Apr 2005, at 16:52, Spiro Trikaliotis wrote: > Hello Christopher, > > * On Mon, Apr 25, 2005 at 01:22:08PM +0800 Christopher Phillips wrote: > >> Does anyone know how you would retry a job that never even reports an >> error? > > This never occurred to me. Curious. Of course, now that I have posted about some code I wrote some weeks ago, I pull it out to try something MagerValp suggested and cannot get it to fail... > It might help if you include a assembleable (!) version of your > sources, > and/or a binary on a web-server. ;-) If it breaks again I will put together enough of the code to get to the failure point and post it - although the code I posted earlier includes all the relevant drive code aside from the port equates. > > Until now, I cannot see anything unusual that would give you headaches > in your code. Thanks. I did notice that Lasse Öörni leaves interrupts enabled for a little while at the start of his loader, with a comment about "allowing the motor to stop" Marko also starts his drive code with a cli with a comment about "; interrupts enabled until first sector read". Can anyone share any light on either of the above, or should I be asking Lasse? :) > > Of course, you could set a timeout, but I think this is over-doing. If I were to set a timeout, I don't know what I could do after it ran out other than cancel the entire load and resend the drive code, as I don't think the job code had been removed. Of course, I am only checking it's sign, not it's value, so I could be wrong on that count. Cheers, Christopher. Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.