New tool for DragonDOS disk images!

[robcfg]

I deleted the original release and pushed a new one that corrects a silly mistake when storing the load and exec addresses.

https://github.com/robcfg/retrotools/re ... DOS_v1.0.1

Cheers,
Rob

[robcfg]

Sooooo... I realized that I made a silly mistake when storing the file size in the file header for binary files, making the computer trying to load them go haywire

So, here's a fixed release, enjoy!

https://github.com/robcfg/retrotools/re ... DOS_v1.0.2

[pser1]

Sooooo... I realized that I made a silly mistake when storing the file size in the file header for binary files, making the computer trying to load them go haywire
So, here's a fixed release, enjoy!
https://github.com/robcfg/retrotools/re ... DOS_v1.0.2

I have just downloaded it. Going to give it a try!
Thx a lot for sharing this nice tool!!
cheers!

[pser1]

Hi Roberto,
just clicked twice on the UI for WIndows64 and a big window has open.
After selecting a 720Kb disk with a lot of games, I have selected some and then clicked on "Extract Selected Files"
All of the files have been put in the folder I have chosen, but then opening these files to see their content, I see that
none of them has the Dragon header, I mean the 9 typicall bytes
- $55, $02, load, length, exec, $AA for binary files
So, in case I wanted to use it on XRoar, I suspect that I would be forced to add a header, a Dragon one or a CoCo one
but I think that a binary without header only could be usefull if it is a ROM dump ...
cheers!

[pser1]

Back again ...
extracting a BAS file has resulted in an ASCII file, so I can use it on XRoar with Ctrl+L and issuing CLOAD.
I asume that, in case I woud like to add a BAS file to a disc, it must be in ASCII format, not with tokenized words, right?
cheers!

[pser1]

And finally I saw the trick.
After extracting three binary files and deleting them from the disc, as soon as I have wanted to insert them in the disc,
the program asked for the Load address and then for the Exec address.
So the files I get when I use my compilation chain for the AGD converted games, will be a problem because I am
creating the binary files with header (for Dragon and for CoCo)
Probably I could change the compile bat file to change params to prevent the ASM6809 creating the headers
cheers!

[robcfg]

Hi Pere,

Thanks for giving it a try!

I thought of the files as the data itself, that's why I remove the 9 byte header. Also because if you need to assign a different load/exec address you can do it on the UI rather than editing the files.

That said, if extracting/adding them without removing the header, should easy enough to implement, so let me know.

And yes, BASIC files are automatically tokenized/detokenized on import/export so you just work with an ASCII text file.

Cheers,
Rob

[pser1]

Hi Pere,
Thanks for giving it a try!
I thought of the files as the data itself, that's why I remove the 9 byte header. Also because if you need to assign a different load/exec address you can do it on the UI rather than editing the files.
That said, if extracting/adding them without removing the header, should easy enough to implement, so let me know.
And yes, BASIC files are automatically tokenized/detokenized on import/export so you just work with an ASCII text file.
Cheers,
Rob

Hello Robert,
I am using the old DragonDos by Rolf Michelsen that can be called from a .bat file and works perfectly with binary files that come with the header.
So don't worry about that unless there are more users that ask for a different behaviour, maybe adding a check to choose header/not header ...
cheers!

[robcfg]

It should be fairly easy to detect if the file already contains the header, so I can work out how to automatically handle that.

When it comes to extracting the files, maybe a checkbox to extract or not the header could be a good solution.

[robcfg]

Hello, beautiful people!

I've implemented the detection of the DragonDOS header in binary files, so now you can add them to your disk images without having to type the load and exec addresses, and with the correct data. You'll notice that there's a new checkbox that controls whether the header shall be part of the extracted file or not. It's on by default.

Also, the command line utility has the same ability, and a new optional flag for the extract command:

Code: Select all

-strip_binary_header

that will remove the header when extracting binary files. The default behaviour is to export it, to match the UI utility.

As usual, please give it a ride and report any errors you may find.

https://github.com/robcfg/retrotools/re ... DOS_v1.0.3

Cheers,
Rob