[Coco] DriveWire with filesizes not divisible by 256

[CoCoList for Color Computer Enthusiasts]

Aaron, I really don't think it would work without rewriting both DECB and the OS9 drivers. RSDOS and OS9 fill out the remaining portion (after EOF) of the last sector(s) differently. RSDOS reservers/writes in "granule" size chunks (as it's smallest possible file), the minimum of 9 sectors (1 gran=9 sectors). OS9 relies on the setting in the device descriptor for it's minimum.
 
What would be the advantages of doing this if it could be done?
 

Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 
 
-----Original Message-----
From: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Sun, May 11, 2014 3:45 pm
Subject: [Coco] DriveWire with filesizes not divisible by 256


A couple survey responses have indicted a desire to use files of arbitrary
size in DriveWire.

Since we only read/write 256 byte sized sectors, what is the correct way to
do that?  Just fill the last sector with 0?  There isn't a way for the
server to tell the coco what's part of the file and what's not in the last
sector, and vice versa the file would become padded to 256 byte boundary if
the last sector is written, since coco can't tell server the same.  Does
that matter?  It feels a bit dangerous.

-aaron

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco