Michael J. Mahon wrote:
schmidtd wrote:mmphosis wrote:schmidtd wrote:Does anyone know how to trap the I/O errors that happen when using this interface? Right now, it dumps me back into BASIC.Yes. Look at what "jmp error" is doing in the code.Oh, right - I get that for the File Manager code. That's what I get for changing subjects without changing the subject line. My problem now is: When I do the Ctrl-D BSAVE, if an error occurs - it blows all the way back to BASIC, never giving control back to my assembly.That's a real functional deficit... I wonder how many "error exits" there are...it would be handy if all of them went through a single piece of code.
A glance at the DOS listing looks like good news! It looks like all DOS errors go to $A6D2, with the error number in the A register. Patching a JMP in there should do the job, or maybe an SEC; RTS, depending on how the normal return works. (BTW, at least one version of Beneath Apple DOS has the ERROR entry point listed erroneously as $A6D5.) -michael NadaNet networking for Apple II computers! Home page: http://members.aol.com/MJMahon/ "The wastebasket is our most important design tool--and it's seriously underused."