Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ames!think!snorkelwacker!bu.edu!m2c!wpi!ggray From: ggray@wpi.wpi.edu (Gary P Gray) Newsgroups: comp.sys.apple2 Subject: Re: ProDos from machine language Message-ID: <9946@wpi.wpi.edu> Date: 21 Mar 90 02:09:33 GMT References: <1990Mar20.053133.16783@agate.berkeley.edu> <1990Mar20.224015.25922@agate.berkeley.edu> Reply-To: ggray@wpi.wpi.edu (Gary P Gray) Distribution: usa Organization: Worcester Polytechnic Institute, Worcester ,MA Lines: 27 In article <1990Mar20.224015.25922@agate.berkeley.edu> archie@brahms.berkeley.edu writes: {really the best way to do this deleted } I think I know what you want. From March 1988 Nibble magazine (not direct quotes) By S. Scott Zimmerman "Nibbling at Assembly Langauge Part XV" Place the string containing the command into the input buffer starting at $200. The string can be up to 255 chars long and must end with a return. All of the characters must have the high bit set, and all letters must be upper case. They must be immediate mode operations, not stuff like READ or Write. Issue a jsr $BE03. Errors will be indicated with the carry bit set, and an error number in the accumulator. You can print out the standard error message using the prodos routine at $BE0C. Disclaimer: A) I did not ask the author to print this info B) I have never tried this. If you have problems I can check the article again, but I have no practical experience. -- -- WARNING!!! The above opinions may be HAZARDOUS or FATAL if swallowed!!! -- This has only been a test. Had these | Gary Gray -- ggray@wpi.wpi.edu been real opinions you would have been | GEnie: GGRAY6 told who to sue by your local lawyers. |