[Coco] Flash updated Dragon DOS into SDC... help!

[Tormod Volden]

On Sat, Mar 12, 2016 at 8:09 PM, Rogelio Perea wrote:
> Went back to the DSK installer image created with CoCoDskUtil and taking a
> look at the Hex Editor built in I checked on the updater BIN file. It
> indeed had the characters D and K at the first two bytes but in their
> lowercase representation, after that there were like &100 bytes or so of
> apparent gibberish until offset &H0107 the codes for uppercase D and K were
> seen, more proper code seemed to follow from that point forward. Edited the
> BIN file to trim everything off from start to the noted offset and while
> doing that also checked on the "tail" of the BIN file, a lengthy series of
> zeroes followed the end of what I took as valid ROM code... trimmed the end
> as well.
>
> With the slightly shortened updater BIN file I updated the DSK image and
> set that to run with my ML transfer routine, issued the WRITE command for
> that memory block into the SDC flash, reset the SDC for Dragon use, into
> the Dragon port and I got the banner for the 2503 release of your DOS code.
>
> Been playing with the Dragon setup all morning, no problems found on any of
> the VDK images loaded. Now any updates should be a cinch to do using the
> Dragon - heard 2504 is out... later.
>
> I am not sure how the BIN updater file in the 2503 distribution VDK got
> such padding at its start and end... MS Windows?

That's what a VDK is, its header starts with 'd' and 'k':

http://archive.worldofdragon.org/index.php?title=Tape\Disk_Preservation#VDK_File_Format

Tormod