-
Notifications
You must be signed in to change notification settings - Fork 85
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
Reconstruct OARCDV source code #666
Conversation
I'm doing this. Almost done. |
Oops, forgot to add to build script. Coming up. This new ARCDEV 66 builds to an identical binary, except the metadata parts. |
Very nice! What are some examples of old-format archives that we have? |
6c7af30
to
51704b5
Compare
These: |
Note that ARCDEV 23 calls the signature word 777777777777 the new format. So presumably there could be four formats:
|
I better save this somewhere. The old OARDV BIN has no information which source it was built from. But there's this:
|
I have now compared ARCDEV 66 against OARCDV BIN. They are not the same! So the information in the email from 1984 is not correct. |
SYSEN2; DMARCD 30 is in fact identical to my reconstructed ARCDEV! |
Hmm, maybe I was too hasty. It could well be that the OLD ARCDEV in the email was assembled from ARCDEV 66. But that's not the "old arc device" we need as OARCDV BIN. |
About the archive file formats. DMARCD 30 indicates 777777777777 and ARC!!! is the same format. ARCDEV 21 and 22 has an assembly time switch for ARC or DSK directory type, so DSK is the oldest format. DEVICE; JOBDEV LIB was used to handle the DSK format.
|
The source code for the old-format DEVICE; OARCDV BIN seems lost. Rumor has it it was built from ARCDEV 66. Version 68 is for the new format, and is very different.
We found ARCDEV 23, though. It looks very similar to OARCDV. It should be possible to disassemble OARCDV and fill the gaps in version 23 to bring it up to 66 equivalent.