Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!pasteur!agate!wheatena!archie
From: archie@wheatena.berkeley.edu (Archie Cobbs)
Newsgroups: comp.sys.apple2
Subject: ProDos from machine language
Summary: control-d don't work
Keywords: help, me, please
Message-ID: <1990Mar20.053133.16783@agate.berkeley.edu>
Date: 20 Mar 90 05:31:33 GMT
Sender: archie@brahms.berkeley.edu (Archie Cobbs)
Reply-To: archie@brahms.berkeley.edu (Archie Cobbs)
Followup-To: comp.sys.apple2
Distribution: usa
Organization: UC Berkeley (does that count?)
Lines: 25

Hi everyone. I have a question regarding ProDos. I don't use it much so
this is probably pretty easy to answer. You know how in Applesoft you
can say:

	10  D$ = CHR$(4)
	20  PRINT D$;"CATALOG"

or whatever. Under DOS 3.3 you can do the exact same thing in assembly
language (by sending the appropriate sequence of characters to $FDED)
and DOS 3.3 will respond. However, under ProDos it seems that while the
above Applesoft program works, the machine language equivalent doesn't
get the attention of ProDos, and your command just appears unanswerd
on the screen.

My question is not "how do you interface with ProDos from machine
language?", which I know there is some way to do similar to
DOS 3.3's file manager, but "how can I get ProDos to read a command
string?" For example, I have a program where the user can issue any disk
command, and the program just sends whatever the user asks for to $FDED
with a control-d prepended, but this doesn't work in ProDos.

Any solutions / explanations would be appreciated.

-Archie
Archie Cobbs					  archie@brahms.berkeley.edu