Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!bionet!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!hp4nl!kunivv1!wn2!janhen
From: janhen@wn2.sci.kun.nl (Jan Hendrikx)
Newsgroups: comp.sys.cbm
Subject: Re: CBM IEEE-488 Support Info Needed
Message-ID: <328@wn2.sci.kun.nl>
Date: 2 Feb 89 17:36:45 GMT
References: <444@madnix.UUCP>
Organization: University of Nijmegen, The Netherlands.
Lines: 48

In article <444@madnix.UUCP>, perry@madnix.UUCP (Perry Kivolowitz) writes:
> ASDG manufactures IEEE-488 (GPIB/HPIB) hardware for the CBM Amiga.
> 
> If anyone can send us copied manual pages describing IEEE-488 support
> from the BASIC language on the PET or 64 we'd be very appreciative.
> The result would be a way of migrating your 488 applications to the
> Amiga.

That is very simple.. It is described perfectly in the standard book
Programming the PET/CBM by Raeto West. Published maybe by Addison-
Wesley, or something like that (I am not sure... Someone still
owes me that book).

In short:
OPEN 7,8,9,"filename"
opens a file on device #8, secundary address 9, with name "filename"
(Procedure LISTEN DEVICE, OPEN SEC.ADR 9, filename)
PRINT#7,blah puts blah on the file (LISTEN DEVICE 8, SEC ADR 9, data,
UNLISTEN)
INPUT#7,blah reads from the file (TALK DEVICE 8, SEC ADR 9, wait for
proper data to arrive, UNTALK)
CLOSE7 closes the file (LISTEN DEVICE 8, CLOSE SEC ADR 9, UNLISTEN)
SAVE "filename",DEV,SECADR
does something like OPEN, output data, CLOSE.
LOAD "filename",DEV,SECADR. 
does something like OPEN, read data, CLOSE, except that it sends
secundary address 0 to the disk and uses the given value locally
(for a C64) or ignores it (for a PET).

You also must know that Commodore used the secundary addresses for
something non-standard, and that setting some bits in the secadrs
means special things (open/close this secadr).
The non-standard thing varies with the particular device. The disk
keeps several open files apart by different secunary addresses,
while various printers allow many print things to be set by data
sent to different secadrs. Unfortunately, they never could decide
on a standard among their own printers....

Gosh, that I still know all that after all those years.

If you really want a photocopy of a ROM disassembly of the PET,
just yell :-) :-) :-)

> Thanks
> -- 
> Perry Kivolowitz, ASDG Inc.

-Olaf Seibert (using Jan's account)