MADS bug with OPT F+?

[Heaven/TQA]

does anybody discovered corrupted file data structur with OPT F+ in MADS?

 

I run into issue that files are corrupted (WUDSN hex editor, Altirra and exomizer say corrupted file (neverless Altirra starts it correctly). it has several ORGs inside...

 

I am using MADS 2.0.0

 

any advice?

[flashjazzcat]

Careful using .DS in single block files. It may throw off the location counter and produce unexpected file geometry. F+ is probably intended primarily for writing ROMs, in which case you would also omit the segment headers.

[Heaven/TQA]

it definitly bugs... many ORGs... even ascending order... but OPT F+ produces corrupt file structure... so I did a workaround... dumped memory in Altirra... loaded into superpacker and put header there + run adress and saved that exe file for exomizer...

 

is there any windows/dos command to add bytes to a file so my batch file could add the headers?

[pirx]

is there any windows/dos command to add bytes to a file so my batch file could add the headers?

 

copy /B myfile1.bin+myfile2.bin

[+JAC!]

OPT F Works fine here. Beware of the order between ORG/OPT depending on what you want to achieve (re-base vs. fill).

opt h-

org $1000

opt f+

:255 lda #>*

org $3000

:255 lda #>*

opt f-

org $4000

opt f+

:255 lda #>*

org $6000

:255 lda #>*

opt f-