Hi, > I thought to remember that the reason was that the disk needs to be accessed > in > order to find it out and I didn't want to do that. But I've just looked and > saw that > for the dio_query_sectsize it needs to be accessed, too. So this couldn't be > the reason. In my opinion it's absolutely legitimate for dio_query_sectcount() to access the disk. Just think of a High-Density drive backward compatible with Single-Density disks. From that perspective the sector count is a disk property, not a drive property. I'd even say that it is correct for dio_open() to access the disk (if necessary). If I write a program using DIO that asks the user to insert a disk into a drive I do so before calling dio_open()... > But the good news is, that after two years, where I lived in a very small > place > with most of my computers put away in storage, my Ataris and friends are now > at home again > and will be set up in the next weeks. I only need some more tables to put > them on... :-) Cool :-) In case you implement dio_query_sectcount() you may want to check out my diodemo.c in the samples directory. It's a sector-by-sector disk copy program (that uses dio_query_sectcount() ). In the samples/README I already claim that diodemo runs on the Atari. Maybe you can have this statement become actually true ;-) Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Tue Oct 16 11:26:52 2012
This archive was generated by hypermail 2.1.8 : 2012-10-16 11:26:55 CEST