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
Hi, I am a beginner so the answer to this question is not immediately obvious to me.
I was having trouble importing the file with cadius into a ProDOS 8 volume. The documentation and command switch list wasn't clear on the format it should take. I eventually figured out that if I want a binary file that runs from memory address $0800 then I need to name the file something like "test#060800" for cadius to properly import it into the ProDOS 8 volume.
When Merlin32 assembles a file, it generates _FileInformation.txt. If I have set ORG and TYP in the source file, shouldn't that be sufficient information to be populated and then cadius could pull out the #060800 part on its own? Thus avoiding having to name the source files names like test#060800 to avoid having to manually rename them every time?
Is it supposed to look at _FileInformation.txt?
The text was updated successfully, but these errors were encountered:
Hi, I am a beginner so the answer to this question is not immediately obvious to me.
I was having trouble importing the file with cadius into a ProDOS 8 volume. The documentation and command switch list wasn't clear on the format it should take. I eventually figured out that if I want a binary file that runs from memory address $0800 then I need to name the file something like "test#060800" for cadius to properly import it into the ProDOS 8 volume.
When Merlin32 assembles a file, it generates _FileInformation.txt. If I have set ORG and TYP in the source file, shouldn't that be sufficient information to be populated and then cadius could pull out the #060800 part on its own? Thus avoiding having to name the source files names like test#060800 to avoid having to manually rename them every time?
Is it supposed to look at _FileInformation.txt?
The text was updated successfully, but these errors were encountered: