[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: apple2pd@ground.ecn.uiowa.edu (ground.ecn AppleII Librarian)
- Date: 2 Jul 2003 15:16:05 GMT
- Newsgroups: comp.sys.apple2, comp.sys.apple2.comm, comp.sys.apple2.programmer
- Organization: Iowa Computer Aided Engineering Network, University of Iowa
- References: <bbst2p$1ll0$1@arachne.labyrinth.net.au> <QetMa.9236$JY1.7045@nwrddc01.gnilink.net>
- Xref: archiver1.google.com comp.sys.apple2:32466 comp.sys.apple2.comm:415 comp.sys.apple2.programmer:2140
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
--Steve
--
--Steve (apple2pd@ground.ecn.uiowa.edu)