Skip to content
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

Is it necessary to manually rename the assembled file or can cadius obtain the info from _FileInformation.txt? #41

Open
Sunspark-007 opened this issue May 1, 2024 · 0 comments

Comments

@Sunspark-007
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant