Debug ?

[mtb]

How can i write the content of the chip ram to a file or save a *tracker module?

Experimenting a bit:

Press shift+f12 under winuae or the debug button under uae you can see the
content of the memory, and even look for *tracker clones.

Example:


>M
Found possible ProTracker (31 samples) module at 0x5b988.
Name "swiv-title", Length 0x20ffe bytes.
>

Then ( from help ):
S <file> <addr> <n>: Save a block of Amiga memory - but what is n?


[ how can i write the module to a file? ]

And also how can i write the content of the chip ram to a file?

[ an example would be welcome with 512 - 2048 kb ]

Thanx in advance.

i think n must be the number of bytes to write, so you could write 'S <swiv-title.mod> 0x5b988 0x20ffe' .

I did not try this out but i think this is the way to do it.

[mtb]

Already tried, the result is a 0k file.

Maybe you must convert the HEX-values to DEC, for your Example again:
S swiv-title.mod 375176 135166

(sorry, i forgot to remove the <> in my last reply.. but that should not be your problem.!?)

Unfortunately i cannot try this out because the debug window on my computer does not respond to any key... :-(

ok, just found a way to get input into my debug-window..

forget what i said before. you dont have to convert the values to DEC..just remove the '0x' before the adresses.
like this:> S swiv-title.mod 5b988 20ffe

[mtb]

Thank you, i'll try

Now i discovered another problem with saving files from debug window. it seems that there is a kind of text-conversion on saving parts of the amiga memory.. when i load a saved tracker file with a hex-editor and compare it to the original file always before a value of 0x0a i find an inserted 0x0d. that is not good when you want to save mod-files.

[Toni Wilen]

Just use save state files or Action Replay!

Debugger s-command will be fixed in next release...

[mtb]

Thank you Toni.

Yes, save state - I forgot this feature!