Liste des Groupes | Revenir à com programmer |
On 24/08/2024 09:15, Kerr-Mudd, John wrote:On Fri, 23 Aug 2024 20:17:59 +0100
"Kerr-Mudd, John" <admin@127.0.0.1> wrote:
On Fri, 23 Aug 2024 14:44:20 +0200
wolfgang kern <nowhere@never.at> wrote:
>On 23/08/2024 09:32, JJ asked:>
>BTW, was there a tool specifically for converting DEBUG's dump to binary? Or>
converting it to a series of DEBUG's Edit command?
back then (~1984..) there were several tools available.
I wrote one 1985 as a DOS-extender,
but we had no internet so it was never published.
you may find a lot of later attempts from many sources now:
"HEX2BIN" or similar names with .ASM,.OBJ,.COM or even .EXE.
>
this task is/was that easy and short...
so whenever needed this few bytes can be written any time.
>
The 'problem' with debug output is that it has address prefixes and
display values at the end that need stripping out to get pure hex.
>
I could post code in hex, if that's more acceptable - it's just easier
for me to just CnP a debug dump.
>
I did hex2bin and v versa a while back; OK I'll revisit it to have a
prog that does both.
Just Hex2Bin for debug typists!
BAC301B93CFEB43FCD2191E3F489D689D757AC3C30720E244FD43730F375054F
8A25D510AAE2EB5A89F929D143B440CD214BEBCF
(Is OK up to 62k, I think, might have problem with larger files if size
odd, I haven't tested it- prog desn't allow for hex pair to be split over
read boundary)
e.g.
hex2bin <hex2bin.hex >newh2bin.com
I *think* one can do
debug hex2bin.com
e100 <Paste hex string>
rcx 34 (check!)
w
q
(might be an input limit in debug, if so do CnP in smaller bits)
could work, but I'm afraid there is a much smaller size limit.
Les messages affichés proviennent d'usenet.