Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!lenoil
From: lenoil@mit-eddie.UUCP (Robert Scott Lenoil)
Newsgroups: net.micro.cbm
Subject: Re: [wrong] Answer: I/O to 1541 and BASIC tokens
Message-ID: <3310@mit-eddie.UUCP>
Date: Sat, 15-Dec-84 06:47:51 EST
Article-I.D.: mit-eddi.3310
Posted: Sat Dec 15 06:47:51 1984
Date-Received: Sun, 16-Dec-84 05:46:19 EST
References: <202@cmu-cs-speech2.ARPA>
Organization: MIT, Cambridge, MA
Lines: 21

> 3. Disk drive channels 0 and 1 are used by kernel when load or save
>    operations are called for. There is no real reason not to use them in your
>    programs unless your program calls for one of those operations (except
>    that it is usually advisable to respect your OS and not use something that
>    it reserves for itself - especially if you can just as easily avoid doing
>    so). This is mostly useful in machine language applications wher calls to
>    kernel's LOADRAM and SAVERAM might be common.
> 
>                                              - Jeff Rosenfeld,
>                                                jdr@cmu-cs-speech2.ARPA.

This is NOT true.  There IS a significance to secondary addresses 0 and 1.
I have seen it when writing a routine to read the directory off the disk by
opening 1,8,0,"$0".  This does act differently if I use a different secondary
address.  Perhaps someone with a copy of "Inside Commodore DOS" could look
this up and provide a (correct) answer as to the specific differences when
using secondary addresses 0 and 1.

Robert Lenoil
USENET: {ihnp4,decvax!genrad,godot,harvard}!mit-eddie!lenoil
ARPANET: lenoil@mit-xx.arpa