Yes, Using your R8.01 in a cmd window would be ideal.
I keep a 32b XP box handy to handle the stuff that wont run on the later 64b platforms.
The only part that's kind of a hassle is to find where the codeplug data is in RAM.
HxD 1.7.7.0 has an "Open RAM" option under the Extras tab. This opens a dropdown of the apps running/using RAM.
When I launch R8.01 in XP, the app name in the dropdown is ntvdvm.exe.
The space allocated for the RSS is not always in the same place so you have to do a search for a string of hex values.
Pick a set of bytes you know are in the codeplug (I use E5 04 00 it is in every mode before it is modified) Searches over 3 bytes long seem to take a long time. When a re-occuring pattern is found, back up about 265 bytes or so from the 1st occurance of that pattern and you should see the beginning of the codeplug....00 0F FF? for a 2k? or 00 1F FF for an 8k codeplug.
After that, the rest is pretty straight forward. Edit the hex data and save, then go look at the RSS for the changes or edit a arameter in RSS the go look in the RAM display for the changes.
Both will need an action to force it's respective program to refresh the changed data. The RSS does not calc/store to RAM? the checksum until you select the output menu page.
I open a new "dummy tab" in the editor so I can toggle back and forth to make HxD refresh it's display of the RAM contents after each change.
Give it a try. It starts out a bit bumpy, but can be a time/aggrevation saver in the long run.
It works with DOSBox too, but same deal.
The effort is in searching the? RAM for where the program is storing the codeplug.
?
