[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Programming the Apple IIe via the cassette in
- Subject: Re: Programming the Apple IIe via the cassette in
- From: "Michael Pender" <mpender@hotmail.com>
- Date: Sun, 06 Jul 2003 06:46:50 GMT
- Newsgroups: comp.sys.apple2, comp.sys.apple2.comm, comp.sys.apple2.programmer
- References: <bbst2p$1ll0$1@arachne.labyrinth.net.au> <QetMa.9236$JY1.7045@nwrddc01.gnilink.net> <bdusvl$1pi$1@server05.icaen.uiowa.edu>
- Xref: archiver1.google.com comp.sys.apple2:32561 comp.sys.apple2.comm:423 comp.sys.apple2.programmer:2171
ground.ecn AppleII Librarian <apple2pd@ground.ecn.uiowa.edu> wrote in
message news:bdusvl$1pi$1@server05.icaen.uiowa.edu...
> In article <QetMa.9236$JY1.7045@nwrddc01.gnilink.net>,
> Michael Pender <mpender@hotmail.com> wrote:
> >The cassette interface uses the 'LOAD' and 'SAVE' commands (without an
> >argument) to load and save programs from cassette.
> >
> >The DOS 3.3 and ProDOS operating systems both 'replace' the LOAD and SAVE
> >commands to access the disk device. You'll need to chose one or the
other;
> >you can have either cassette access or disk access, but not both.
> >
>
> I disagree. I think both work. print chr$(4);"load xxx" invokes the disk
> access. load (without the print chr$(4)) invokes the monitor cassette
> access. If I remember correctly (and it gets harder everyday, but I meet
> lots of new people :-)) one can do both disk and cassette load/save in one
> pgm (basic or assem). load/save doesn't get replaced, the calling
> sequence determines which is used.
>
> $0.02
It sounds like the trick in 'immediate' mode is to avoid the DOS 3.3
intercept routine by making it into an AppleSoft command, i.e.:
] LOAD Doesn't work
versus
] :LOAD Works
In 'run' mode:
100 print chr$(4)"LOAD" Doesn't work
versus
100 LOAD Works
Nifty.
- Mike