dillon@CORY.BERKELEY.EDU (Matt Dillon) (02/25/86)
I think I know why my serial.device routines failed, but I'm not sure. The Hardware manuals have absolutely no examples or description of how error's are returned, or what happens to your BeginIO. After suspecting that read-error's were causing my poor modem program to flop over and die, I put in a small diagnostic to print what BeginIO() returned (when I begin the read-request). For some reason, It came back with: 2058 (dec) = 00001000-00001010 However, this doesn't seem to be an error #, as specified by the serial docs. Could someone explain to me what it means? If anybody has any examples of serial.device routines that handle read-errors and such without freezing up, I would appreciate it. Aside: Can somebody tell me what the 'memory overlay' bit is on one of the I/O ports. It has something to do with the WCS, I think. Also, I could not find any documentation on the format of the KickStart diskette, does anybody have any information on that?? Thanks A lot, -Matt
tomp@amiga.UUCP (Tom Pohorsky) (02/26/86)
<8602251656.AA22138@cory> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes: > I think I know why my serial.device routines failed, but I'm not >sure. The Hardware manuals have absolutely no examples or description of >how error's are returned, or what happens to your BeginIO. Look in the new ROM Kernel Manual for this info. > After suspecting that read-error's were causing my poor modem program >to flop over and die, I put in a small diagnostic to print what BeginIO() >returned (when I begin the read-request). For some reason, It came back with: > > 2058 (dec) = 00001000-00001010 > Perhaps I misunderstand what you're saying here, but bear in mind: - BeginIO (or SendIO) doesn't return a value. The ensuing WaitIO returns the error/completion code. - It's "recommended" to use SendIO rather than BeginIO. BeginIO is a tiny bit quicker, but requires the requestor to manipulate the IO_QUICK bit on his/her own. If you don't know what that bit does, use SendIO like you're "supposed" to. >any examples of serial.device routines that handle read-errors and such >without freezing up, I would appreciate it. > The Rom Kernel manual has a trite example program I wrote up back when. It handles and reports read errors. Happy hackin', tomp.