You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changing a file (say, writing a Basic program), the file's data sectors appear to be written and flushed immediately after the SAVE command. However if the file size increases and and extra data sector is written, the Sector Count change is written to the catalog but it is not flushed.
Similarly, if I create a (very small) new program in AppleWin and save it, the catalog is written (and flushed) with a sector count = 1, then the sector count is increased to 2 but the change is not flushed to the disk. Presumably the catalog sector is flushed after the T/S sector is added, but not after the data sector is added.
Note that this doesn't have any effect within AppleWin, you will only notice it if you are using a Disk Browser to view the files at the same time as you make the changes to the disk image. But it makes my DiskBrowser program appear to be broken.
I would also guess that if AppleWin crashes for some reason, you will be leaving a corrupted disk image behind.
The text was updated successfully, but these errors were encountered:
BerliOS Bug #17456
Date: 2010-August-23 01:35
Submitted By: dmolony
Category: 1.17.2
Bug Group: Future request
Assigned To: none
Priority: 5
When changing a file (say, writing a Basic program), the file's data sectors appear to be written and flushed immediately after the SAVE command. However if the file size increases and and extra data sector is written, the Sector Count change is written to the catalog but it is not flushed.
Similarly, if I create a (very small) new program in AppleWin and save it, the catalog is written (and flushed) with a sector count = 1, then the sector count is increased to 2 but the change is not flushed to the disk. Presumably the catalog sector is flushed after the T/S sector is added, but not after the data sector is added.
Note that this doesn't have any effect within AppleWin, you will only notice it if you are using a Disk Browser to view the files at the same time as you make the changes to the disk image. But it makes my DiskBrowser program appear to be broken.
I would also guess that if AppleWin crashes for some reason, you will be leaving a corrupted disk image behind.
The text was updated successfully, but these errors were encountered: