Timeline for What exactly was the intent and implementation of Apple DOS 3.3's volume concept?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 13 at 20:25 | comment | added | Raffzahn | @bjb I remember that feeling when I finally got a 5 MiB Profile I had no idea how to fill it :)) | |
| Jan 13 at 17:23 | comment | added | bjb | I only had 4 DOS 3.3 volumes on the Sider (re: the 'little' comment) since I was focusing primarily on ProDOS at the time. I minimized the Pascal and CP/M partitions since I didn't use them, but I decided to have a little bit of DOS 3.3 on my massive 20MB of fixed storage :-) | |
| Jan 10 at 17:29 | history | edited | hippietrail | CC BY-SA 4.0 | minor english copyedit |
| Apr 12, 2023 at 0:26 | history | edited | Raffzahn | CC BY-SA 4.0 | added 893 characters in body |
| Apr 10, 2023 at 16:58 | vote | accept | bjb | ||
| Apr 9, 2023 at 19:37 | comment | added | supercat | I've had trouble managing to swap disks with different volume IDs in emulation. If a volume number is specified with OPEN when the wrong volume is installed, the system squawks, but I can't tell whether opening a file causes the system to set whatever the current volume happens to be as a volume number that must be matched for all future operations on that file. | |
| Apr 8, 2023 at 22:42 | comment | added | Raffzahn | @supercat It's the way it is. A RWTS call always checks the numbers. Reading and comparing the header is the very base of every sector operation - read and write. Check for yourself if you don't believe. | |
| Apr 8, 2023 at 21:42 | comment | added | supercat | I know the volume number could be verified with every sector read, but that doesn't say anything about whether DOS would verify that a file which was happened to be opened on volume 123 will not get written to when a different disk is inserted. | |
| Apr 8, 2023 at 20:12 | comment | added | Raffzahn | @supercat The volume check is (as shown) part of the RWTS, thus will be done with each and every sector read - the very reason why the volume number ist (a shown) part of each sector header. Next, Volume numbers are intended to organize multi volume data sets. But you're ofc free to make them random. | |
| Apr 8, 2023 at 14:30 | comment | added | supercat | Does DOS 3.3 make any effort to guard against volume swaps while a file is open, or does it re-check available space each time it writes a sector? The fact that the volume ID is repeated on every sector would allow zero-cost checking, but the effectiveness of such checks would have been greatly enhanced if volume IDs were random, rather than being set to 254 on 99.9% of disks. | |
| Apr 7, 2023 at 23:26 | history | edited | Raffzahn | CC BY-SA 4.0 | added 1506 characters in body |
| Apr 7, 2023 at 19:40 | history | edited | Raffzahn | CC BY-SA 4.0 | added 65 characters in body |
| Apr 7, 2023 at 18:50 | history | edited | Raffzahn | CC BY-SA 4.0 | added 291 characters in body |
| Apr 7, 2023 at 18:43 | history | edited | Raffzahn | CC BY-SA 4.0 | added 291 characters in body |
| Apr 7, 2023 at 18:36 | history | edited | Raffzahn | CC BY-SA 4.0 | added 291 characters in body |
| Apr 7, 2023 at 18:25 | history | answered | Raffzahn | CC BY-SA 4.0 |