-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support ProDOS 2.5 extended file dates #169
Comments
Specifically per @JohnMBrooks - "Basic displays extended dates (10-bit year 1940 to 2964) by appending the 3 top bits from the hour byte to the 7-bit year" So old GET/SET_FILE_INFO, mod/create_date/time and File Entry creation/last_mod fields:
For files created with 2.5, this becomes:
Where the Proposed algorithm:
|
Also improve install script output This is done with an eye towards issue #169
For posterity: ProDOS 8 2.4.2 SET_FILE_INFO calls seemingly fail to set the modified date if the upper byte is clear, i.e. if the year is 1900 (or 2000, if you follow Tech Note #28) and the month is < 8. |
The ProDOS 2.5 extended date and time format seems to have changed. Please see https://prodos8.com/releases/prodos-25/. |
That page is talking about the global page format. This is issue is talking about the file metadata format. Unfortunately in 2.5 they differ from each other. |
You were right, it has changed. The code will need updating. At least the global page/file stamp formats are the same now. |
The ProDOS 2.5 date format changed at alpha 4 - handle the new format: https://prodos8.com/releases/prodos-25/ Also, unify date/time parsing between file strings and the clock. NOTE: DOW for the clock is only valid for years 1900-2155. NOTE2: The new date handling is not extensively tested yet. I need to create a corpus of files with various dates in the new format. Resolves #169
Should be fixed by 92c0414 |
ProDOS 2.5 smuggles in a few extra year bits
Add support in the date decode routine, hereabouts: https://github.com/a2stuff/a2d/blob/master/desktop/desktop_main.s#L8223
There may be other places...
The text was updated successfully, but these errors were encountered: