Re: New draft version of o65 file format

From: Spiro Trikaliotis (ml-cbmhackers_at_trikaliotis.net)
Date: 2005-03-31 20:15:28

Hello,

* On Wed, Mar 30, 2005 at 02:16:11PM +0200 I wrote:

some updates:


> opencbm floppy modules:
> The opencbm API (cbm4win, cbm4linux) will(*) use the o65 file format for
> modules to load into floppy. The API itself loads o65 files to account
> for the differences between the various floppy drives (1540/1541,
> 1570/1571, 1581), and to present the API user transfer protocols for its
> use. The API user loads additional modules into the floppy drives which
> then use late binding to connect to the various support routines of the
> floppy ROM, or of the transfer protocols. Name encoding is ASCII, name
> length are restricted to 1024 characters currently (will be removed most
> probably in the near future).

This restriction has been removed.

> Currently, the simple file format is not required (but there is no
> definitive decision about this yet).

> Currently, o65 files for the opencbm API are restricted to a total of
> 64KB (65536 byte) in length.

This restriction to a total of 64KB has been removed, too.


Thus, the new text is:

> opencbm floppy modules:
> The opencbm API (cbm4win, cbm4linux) will(*) use the o65 file format
> for modules to load into floppy. The API itself loads o65 files to
> account for the differences between the various floppy drives
> (1540/1541, 1570/1571, 1581), and to present the API user transfer
> protocols for its use. The API user loads additional modules into the
> floppy drives which then use late binding to connect to the various
> support routines of the floppy ROM, or of the transfer protocols. Name
> encoding is ASCII.  Currently, the simple file format is not required
> (but there is no definitive decision about this yet).

Regards,
   Spiro.

-- 
Spiro R. Trikaliotis
http://www.trikaliotis.net/

       Message was sent through the cbm-hackers mailing list

Archive generated by hypermail pre-2.1.8.