Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.apple2.programmer > #1983
| Newsgroups | comp.sys.apple2.programmer |
|---|---|
| Date | 2015-11-26 11:17 -0800 |
| References | <ea18cb22-dd31-4ef1-a592-751221e7a5e9@googlegroups.com> <a84fef6a-43fd-423e-945f-784c2d8404c7@googlegroups.com> <1351ce30-836b-4b8e-8fa4-1a31bf75f126@googlegroups.com> |
| Message-ID | <ec4f5483-093c-4dcc-bca6-5b7337355773@googlegroups.com> (permalink) |
| Subject | Re: RWTS return codes |
| From | gids.rs@sasktel.net |
On Thursday, November 26, 2015 at 10:15:37 AM UTC-6, Mark Lemmert wrote: > On Thursday, November 26, 2015 at 9:36:27 AM UTC-6, gid...@sasktel.net wrote: > > On Tuesday, November 24, 2015 at 11:59:37 AM UTC-6, Mark Lemmert wrote: > > > Is anyone familiar with RWTS return codes? Any suggestions that anyone may have on the issue described below are much appreciated. > > > > > > > > > I am working on developing a routine for writing and reading data to/from floppy disk via an interface to RWTS. > > > > > > So far the routine works great. The only issue is I am noticing that I often get return codes in IOB table byte $0D that I do not recognize: for example, > > > > > > $01.....I often get this code when using a write command code > > > $09.....I often get this code when reading track 0, sector 0. > > > $D3..I got this code when trying to read a copy II plus disk. > > > > > > In all these cases the read/write appears to have been successful. > > > > > > > > > > > > So far the only information I have found on RWTS return codes is in the book Beneath DOS (section 6-5), which lists the following > > > > > > $00 = no erros > > > $08 = error during init > > > $10 = write protect error > > > $20 = volume mismatch error > > > $40 = drive error > > > $80 = read error (obsolete) > > > > > > > > > My theory is that the above are no the only return codes, they are just the return codes that indicate a serious error. > > > > > > I am tempted to design my error handling routine to break if the return code is on the above list, but otherwise ignore the return code and continue. > > > > > > Does anyone know if it is "safe" to ignore return codes other than the above list? If not, I am wondering that the other return codes are for? > > > > > > Beagle Bros has a list of errors for Dos3.3 and Prodos. They may coincide with the return code of RWTS. > > > > 1-Language not available(1) > > 2 or 3-Range error(1) > > 3-No Device Connected > > 4-Write Protected > > 5-End of Data > > 6-File(1) or Path(2) Not Found > > 7-Volume Mismatch(1) > > 8-I/0 Error > > 9-Disk Full > > $A-File Locked > > $B-Syntax Error(1) or Invalid Option(2) > > $C-No Buffers Available > > $D-File Type Mismatch > > $E-Program Too Large > > $F-Not Direct Command > > $11-Directory Full(2) > > $12-File Not Open(2) > > $13-Duplicate File Name(2) > > $14-File Busy(2) > > $15-Files Still Open(2) > > > > (1)-Dos 3.3 only > > (2)-Prodos only > > Thanks for the information! > > For the benefit of any future readers of this thread, here are my observations: > > From what I've seen, it looks to me like the RWTS return codes are not the same as DOS 3.3 Codes. > > For example, I've seen $01 returned many times just by simply writing to a blank (formatted) disk and the write was successful (verified by a corresponding read). I've also seen $09 returned when writing to Track 0, Sector 0 on a blank (formatted) disk, and the write was successful, which clearly would not be the case if the disk was full. > > I suspect that the DOS 3.3 codes refer to codes returned form the DOS file manager, which is one layer of abstraction above RWTS and can be access via assembly language. Yes, but Dos 3.3 needs to handle the disk errors that come from RWTS and convert it to a Dos 3.3 error. There should be a map of RWTS errors in Dos 3.3 that get converted to the Dos 3.3 errors. It is the same with Prodos and Basic.system. MLI errors returned by Prodos are converted to Basic.system errors of which there is a map of errors in Basic.system. Knowing the Dos 3.3 errors might help in identifying the RWTS errors.
Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar
RWTS return codes Mark Lemmert <mark.lemmert@gmail.com> - 2015-11-24 09:59 -0800
Re: RWTS return codes qkumba <peter.ferrie@gmail.com> - 2015-11-24 14:41 -0800
Re: RWTS return codes Mark Lemmert <mark.lemmert@gmail.com> - 2015-11-26 08:08 -0800
Re: RWTS return codes gids.rs@sasktel.net - 2015-11-26 07:36 -0800
Re: RWTS return codes Mark Lemmert <mark.lemmert@gmail.com> - 2015-11-26 08:15 -0800
Re: RWTS return codes qkumba <peter.ferrie@gmail.com> - 2015-11-26 08:53 -0800
Re: RWTS return codes gids.rs@sasktel.net - 2015-11-26 11:17 -0800
Re: RWTS return codes Antoine Vignau <antoine.vignau@laposte.net> - 2015-11-26 12:50 -0800
Re: RWTS return codes Mark Lemmert <mark.lemmert@gmail.com> - 2015-11-29 07:34 -0800
Re: RWTS return codes qkumba <peter.ferrie@gmail.com> - 2015-11-29 08:37 -0800
Re: RWTS return codes qkumba <peter.ferrie@gmail.com> - 2015-11-29 08:41 -0800
Re: RWTS return codes Mark Lemmert <mark.lemmert@gmail.com> - 2015-12-02 14:15 -0800
Re: RWTS return codes Mark Lemmert <mark.lemmert@gmail.com> - 2015-11-29 07:20 -0800
csiph-web