Base85 for DOS

[Kerr-Mudd, John]

Usual '-d' parm to decode.


Last minute fix as it didn't encode short string of binary zeros at eof
correctly: (+6)

-> d 100 lD1
1639:0100 B4 3F B9 F8-70 BA D1 01-CD 21 91 E3-74 89 D6 BF .?..p....!..t...
1639:0110 C9 72 57 B3-55 80 3E 83-00 64 74 66-83 E9 04 77 .rW.U.>..dtf...w
1639:0120 0D 74 0A B7-80 B0 00 BD-04 00 E8 46-00 55 AD 86 .t.........F.U..
1639:0130 E0 95 AD 86-E0 89 C2 D0-E7 14 00 09-E8 75 05 B0 .............u..
1639:0140 7A AA EB 1C-51 B9 04 00-52 31 D2 95-F7 F3 95 58 z...Q...R1.....X
1639:0150 F7 F3 92 50-E2 F2 52 B1-05 58 04 21-AA E2 FA 59 ...P..R..X.!...Y
1639:0160 09 C9 75 B8-59 5A B3 01-01 F9 29 D1-B4 40 CD 21 ..u.YZ....)***@.!
1639:0170 4B EB 8D 57-89 F7 01 CF-01 EF 89 CD-F7 D9 F3 AA K..W............
1639:0180 5F C3 80 3C-7A 75 09 31-C0 AB AB 46-E2 F4 E3 D5 _..<zu.1...F....
1639:0190 83 E9 05 77-0B 74 08 B0-75 BD 05 00-E8 D4 FF 55 ...w.t..u......U
1639:01A0 51 31 C0 99-31 ED B9 05-00 AC 2C 21-72 12 98 50 Q1..1.....,!r..P
1639:01B0 52 95 F7 E3-95 58 F7 E3-01 D5 5A 01-C2 83 D5 00 R....X....Z.....
1639:01C0 E2 E7 95 86-E0 AB 92 86-E0 AB 59 09-C9 75 B3 EB ..........Y..u..
1639:01D0 93 .
-> q

[Kerr-Mudd, John]

On Tue, 20 Aug 2024 08:28:46 +0100

Post by Kerr-Mudd, John
Usual '-d' parm to decode.
Last minute fix as it didn't encode short string of binary zeros at eof
correctly: (+6)
-> d 100 lD1

Smaller fix:

-> d 100 lCD
1639:0100 B4 3F B9 F8-70 BA CD 01-CD 21 91 E3-70 89 D6 BF .?..p....!..p...
1639:0110 C5 72 57 B3-55 80 3E 83-00 64 74 62-83 E9 04 77 .rW.U.>..dtb...w
1639:0120 0B 74 08 B0-00 BD 04 00-E8 44 00 55-AD 86 E0 95 .t.......D.U....
1639:0130 AD 86 E0 89-C2 14 00 09-E8 75 05 B0-7A AA EB 1C .........u..z...
1639:0140 51 B9 04 00-52 31 D2 95-F7 F3 95 58-F7 F3 92 50 Q...R1.....X...P
1639:0150 E2 F2 52 B1-05 58 04 21-AA E2 FA 59-09 C9 75 BC ..R..X.!...Y..u.
1639:0160 59 5A B3 01-01 F9 29 D1-B4 40 CD 21-4B EB 91 57 YZ....)***@.!K..W
1639:0170 89 F7 01 CF-01 EF 89 CD-F7 D9 F3 AA-5F C3 80 3C ............_..<
1639:0180 7A 75 09 31-C0 AB AB 46-E2 F4 E3 D5-83 E9 05 77 zu.1...F.......w
1639:0190 0B 74 08 B0-75 BD 05 00-E8 D4 FF 55-51 31 C0 99 .t..u......UQ1..
1639:01A0 31 ED B9 05-00 AC 2C 21-72 12 98 50-52 95 F7 E3 1.....,!r..PR...
1639:01B0 95 58 F7 E3-01 D5 5A 01-C2 83 D5 00-E2 E7 95 86 .X....Z.........
1639:01C0 E0-AB 92 86 E0-AB 59 09 C9-75 B3 EB 93 ......Y..u...
-> q

[Kerr-Mudd, John]

On Tue, 20 Aug 2024 12:21:45 +0100

Post by Kerr-Mudd, John
On Tue, 20 Aug 2024 08:28:46 +0100

Post by Kerr-Mudd, John
Usual '-d' parm to decode.
Last minute fix as it didn't encode short string of binary zeros at eof
correctly: (+6)
-> d 100 lD1

-> d 100 lCD

Ooops, output lth bad on encoding string with length an exactly multiple of
4.

Fixed below; sorry to all my readers (if any).

l203

-> d 100 lCB
16AD:0100 B4 3F B9 F8-70 BA CB 01-CD 21 91 E3-6E 89 D6 BF .?..p....!..n...
16AD:0110 C3 72 57 B3-55 80 3E 83-00 64 74 60-83 E9 04 77 .rW.U.>..dt`...w
16AD:0120 09 B0 00 BD-04 00 E8 44-00 55 AD 86-E0 95 AD 86 .......D.U......
16AD:0130 E0 89 C2 14-00 09 E8 75-05 B0 7A AA-EB 1C 51 B9 .......u..z...Q.
16AD:0140 04 00 52 31-D2 95 F7 F3-95 58 F7 F3-92 50 E2 F2 ..R1.....X...P..
16AD:0150 52 B1 05 58-04 21 AA E2-FA 59 09 C9-75 BE 59 5A R..X.!...Y..u.YZ
16AD:0160 B3 01 01 F9-29 D1 B4 40-CD 21 4B EB-93 57 89 F7 ....)***@.!K..W..
16AD:0170 01 CF 01 EF-89 CD F7 D9-F3 AA 5F C3-80 3C 7A 75 .........._..<zu
16AD:0180 09 31 C0 AB-AB 46 E2 F4-E3 D5 83 E9-05 77 0B 74 .1...F.......w.t
16AD:0190 08 B0 75 BD-05 00 E8 D4-FF 55 51 31-C0 99 31 ED ..u......UQ1..1.
16AD:01A0 B9 05 00 AC-2C 21 72 12-98 50 52 95-F7 E3 95 58 ....,!r..PR....X
16AD:01B0 F7 E3 01 D5-5A 01 C2 83-D5 00 E2 E7-95 86 E0 AB ....Z...........
16AD:01C0 92 86 E0-AB 59 09 C9-75 B3 EB 93 ....Y..u...
-> q

[Kerr-Mudd, John]

On Tue, 20 Aug 2024 17:10:08 +0100
"Kerr-Mudd, John" <***@127.0.0.1> wrote:
[was 203]

Hardcoded some constants, and other savings - now 191 bytes:

-> d 100 lBF
16AD:0100 B4 3F B9 C8-6E BA C3 01-CD 21 91 E3-F9 89 D6 89 .?..n....!......
16AD:0110 D7 01 CF B3-55 80 3E 83-00 64 74 54-31 C0 AB AB ....U.>..dtT1...
16AD:0120 BF 75 75 57-83 E9 04 77-04 51 B9 00-00 AD 86 E0 .uuW...w.Q......
16AD:0130 95 AD 86 E0-89 C2 14 00-09 E8 75 05-B0 7A AA EB ..........u..z..
16AD:0140 1C 51 B9 04-00 52 31 D2-95 F7 F3 95-58 F7 F3 92 .Q...R1.....X...
16AD:0150 50 E2 F2 52-B1 05 58 04-21 AA E2 FA-59 09 C9 75 P..R..X.!...Y..u
16AD:0160 C3 59 5A B3-01 01 F9 29-D1 B4 40 CD-21 4B EB 90 .YZ....)***@.!K..
16AD:0170 B8 75 75 AB-AB AA 97 57-80 3C 7A 75-09 31 C0 AB .uu....W.<zu.1..
16AD:0180 AB 46 E2 F4-E3 DC 83 E9-05 77 03 51-31 C9 51 31 .F.......w.Q1.Q1
16AD:0190 C0 99 31 ED-B9 05 00 AC-2C 21 72 12-98 50 52 95 ..1.....,!r..PR.
16AD:01A0 F7 E3 95 58-F7 E3 01 D5-5A 01 C2 83-D5 00 E2 E7 ...X....Z.......
16AD:01B0 95 86 E0-AB 92 86 E0-AB 59 09 C9-75 BB EB A2 ........Y..u...
-> q
Sun's out; that'll do.

[Kerr-Mudd, John]

On Thu, 22 Aug 2024 13:44:42 +0100

Post by Kerr-Mudd, John
On Tue, 20 Aug 2024 17:10:08 +0100
[was 203]
-> d 100 lBF
16AD:0100 B4 3F B9 C8-6E BA C3 01-CD 21 91 E3-F9 89 D6 89 .?..n....!......
16AD:0110 D7 01 CF B3-55 80 3E 83-00 64 74 54-31 C0 AB AB ....U.>..dtT1...
16AD:0120 BF 75 75 57-83 E9 04 77-04 51 B9 00-00 AD 86 E0 .uuW...w.Q......
16AD:0130 95 AD 86 E0-89 C2 14 00-09 E8 75 05-B0 7A AA EB ..........u..z..
16AD:0140 1C 51 B9 04-00 52 31 D2-95 F7 F3 95-58 F7 F3 92 .Q...R1.....X...
16AD:0150 50 E2 F2 52-B1 05 58 04-21 AA E2 FA-59 09 C9 75 P..R..X.!...Y..u
16AD:0170 B8 75 75 AB-AB AA 97 57-80 3C 7A 75-09 31 C0 AB .uu....W.<zu.1..
16AD:0180 AB 46 E2 F4-E3 DC 83 E9-05 77 03 51-31 C9 51 31 .F.......w.Q1.Q1
16AD:0190 C0 99 31 ED-B9 05 00 AC-2C 21 72 12-98 50 52 95 ..1.....,!r..PR.
16AD:01A0 F7 E3 95 58-F7 E3 01 D5-5A 01 C2 83-D5 00 E2 E7 ...X....Z.......
16AD:01B0 95 86 E0-AB 92 86 E0-AB 59 09 C9-75 BB EB A2 ........Y..u...
-> q

Bigger version (215 bytes) - allows 'y' for space compression.

-> d 100 ld7
16AD:0100 B4 3F B9 C8-6E BA C3 02-CD 21 91 E3-F9 89 D6 89 .?..n....!......
16AD:0110 D7 01 CF B3-55 80 3E 83-00 64 74 5D-31 C0 AB AB ....U.>..dt]1...
16AD:0120 BF 75 75 57-83 E9 04 77-04 51 B9 00-00 AD 86 E0 .uuW...w.Q......
16AD:0130 95 AD 86 E0-89 C2 14 00-09 E8 75 05-B0 7A AA EB ..........u..z..
16AD:0140 25 3D 20 20-75 04 B0 79-EB F4 51 B9-04 00 52 31 %= u..y..Q...R1
16AD:0150 D2 95 F7 F3-95 58 F7 F3-92 50 E2 F2-52 B1 05 58 .....X...P..R..X
16AD:0160 04 21 AA E2-FA 59 09 C9-75 BA 59 5A-B3 01 01 F9 .!...Y..u.YZ....
16AD:0170 29 D1 B4 40-CD 21 4B EB-87 B8 75 75-AB AB AA 97 )***@.!K...uu....
16AD:0180 57 80 3C 7A-75 09 31 C0-AB AB 46 E2-F4 E3 DC 80 W.<zu.1...F.....
16AD:0190 3C 7A 75 0A-B8 20 20 AB-AB 46 E2 E5-E3 CD 83 E9 <zu.. ..F......
16AD:01A0 05 77 03 51-31 C9 51 31-C0 99 31 ED-B9 05 00 AC .w.Q1.Q1..1.....
16AD:01B0 2C 21 72 12-98 50 52 95-F7 E3 95 58-F7 E3 01 D5 ,!r..PR....X....
16AD:01C0 5A 01 C2 83-D5 00 E2 E7-95 86 E0 AB-92 86 E0 AB Z...............
16AD:01D0 59 09 C9-75 AC EB 93 Y..u...
-> q

[Kerr-Mudd, John]

On Thu, 22 Aug 2024 17:52:28 +0100

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 13:44:42 +0100

Post by Kerr-Mudd, John
On Tue, 20 Aug 2024 17:10:08 +0100
[was 203]
-> d 100 lBF
16AD:0100 B4 3F B9 C8-6E BA C3 01-CD 21 91 E3-F9 89 D6 89 .?..n....!......
16AD:0110 D7 01 CF B3-55 80 3E 83-00 64 74 54-31 C0 AB AB ....U.>..dtT1...
16AD:0120 BF 75 75 57-83 E9 04 77-04 51 B9 00-00 AD 86 E0 .uuW...w.Q......
16AD:0130 95 AD 86 E0-89 C2 14 00-09 E8 75 05-B0 7A AA EB ..........u..z..
16AD:0140 1C 51 B9 04-00 52 31 D2-95 F7 F3 95-58 F7 F3 92 .Q...R1.....X...
16AD:0150 50 E2 F2 52-B1 05 58 04-21 AA E2 FA-59 09 C9 75 P..R..X.!...Y..u
16AD:0170 B8 75 75 AB-AB AA 97 57-80 3C 7A 75-09 31 C0 AB .uu....W.<zu.1..
16AD:0180 AB 46 E2 F4-E3 DC 83 E9-05 77 03 51-31 C9 51 31 .F.......w.Q1.Q1
16AD:0190 C0 99 31 ED-B9 05 00 AC-2C 21 72 12-98 50 52 95 ..1.....,!r..PR.
16AD:01A0 F7 E3 95 58-F7 E3 01 D5-5A 01 C2 83-D5 00 E2 E7 ...X....Z.......
16AD:01B0 95 86 E0-AB 92 86 E0-AB 59 09 C9-75 BB EB A2 ........Y..u...
-> q

Bigger version (215 bytes) - allows 'y' for space compression.
-> d 100 ld7
16AD:0100 B4 3F B9 C8-6E BA C3 02-CD 21 91 E3-F9 89 D6 89 .?..n....!......
16AD:0110 D7 01 CF B3-55 80 3E 83-00 64 74 5D-31 C0 AB AB ....U.>..dt]1...
16AD:0120 BF 75 75 57-83 E9 04 77-04 51 B9 00-00 AD 86 E0 .uuW...w.Q......
16AD:0130 95 AD 86 E0-89 C2 14 00-09 E8 75 05-B0 7A AA EB ..........u..z..
16AD:0140 25 3D 20 20-75 04 B0 79-EB F4 51 B9-04 00 52 31 %= u..y..Q...R1
16AD:0150 D2 95 F7 F3-95 58 F7 F3-92 50 E2 F2-52 B1 05 58 .....X...P..R..X
16AD:0160 04 21 AA E2-FA 59 09 C9-75 BA 59 5A-B3 01 01 F9 .!...Y..u.YZ....
16AD:0180 57 80 3C 7A-75 09 31 C0-AB AB 46 E2-F4 E3 DC 80 W.<zu.1...F.....
16AD:0190 3C*79*75 0A-B8 20 20 AB-AB 46 E2 E5-E3 CD 83 E9 <zu.. ..F......
16AD:01A0 05 77 03 51-31 C9 51 31-C0 99 31 ED-B9 05 00 AC .w.Q1.Q1..1.....
16AD:01B0 2C 21 72 12-98 50 52 95-F7 E3 95 58-F7 E3 01 D5 ,!r..PR....X....
16AD:01C0 5A 01 C2 83-D5 00 E2 E7-95 86 E0 AB-92 86 E0 AB Z...............
16AD:01D0 59 09 C9-75 AC EB 93 Y..u...
-> q

Argh! byte at 191 needs to be 'y', not 'z'; I did a careless cutnpaste.

Post by Kerr-Mudd, John
--
Bah, and indeed Humbug.

[JJ]

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 17:52:28 +0100

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 13:44:42 +0100

Post by Kerr-Mudd, John
On Tue, 20 Aug 2024 17:10:08 +0100
[was 203]

[snip]

BTW, was there a tool specifically for converting DEBUG's dump to binary? Or
converting it to a series of DEBUG's Edit command?

[Kerr-Mudd, John]

On Fri, 23 Aug 2024 14:32:02 +0700

Post by JJ

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 17:52:28 +0100

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 13:44:42 +0100

Post by Kerr-Mudd, John
On Tue, 20 Aug 2024 17:10:08 +0100
[was 203]

[snip]
BTW, was there a tool specifically for converting DEBUG's dump to binary? Or
converting it to a series of DEBUG's Edit command?

Of course! I published a dump (:-) of it here a while back.
I called it
xxd-r.com
in a nod to the full unix 'xxd' utility.

See other post

PS all this time I was worried about eof/ partial reads - simpler to
append the padding and do a std loop.

-e -d with both z (tested for trailing zeros) and y compress, 201 bytes

-> d 100 lc9
1638:0100 B4 3F B9 C8-6E BA C3 02-CD 21 91 E3-F9 89 D6 89 .?..n....!......
1638:0110 D7 01 CF B3-55 80 3E 83-00 64 74 57-31 C0 AB AB ....U.>..dtW1...
1638:0120 BF 75 75 57-AD 86 E0 95-AD 86 E0 89-C2 09 E8 75 .uuW...........u
1638:0130 0A 80 F9 04-72 05 B0 7A-AA EB 25 3D-20 20 75 04 ....r..z..%= u.
1638:0140 B0 79 EB F4-51 B9 04 00-52 31 D2 95-F7 F3 95 58 .y..Q...R1.....X
1638:0150 F7 F3 92 50-E2 F2 52 B1-05 58 04 21-AA E2 FA 59 ...P..R..X.!...Y
1638:0160 83 E9 04 77-BF 5A B3 01-01 F9 29 D1-B4 40 CD 21 ...w.Z....)***@.!
1638:0170 4B EB 8D B8-75 75 AB AB-AA 97 57 80-3C 7A 75 09 K...uu....W.<zu.
1638:0180 31 C0 AB AB-46 E2 F4 E3-DC 80 3C 79-75 0A B8 20 1...F.....<yu..
1638:0190 20 AB AB 46-E2 E5 E3 CD-51 31 D2 31-ED B9 05 00 ..F....Q1.1....
1638:01A0 AC 2C 21 72-12 98 50 52-95 F7 E3 95-58 F7 E3 01 .,!r..PR....X...
1638:01B0 D5 5A 01 C2-83 D5 00 E2-E7 95 86 E0-AB 92 86 E0 .Z..............
1638:01C0 AB-59 83 E9 05-77 B4 EB 9C .Y...w...
-> q

[Kerr-Mudd, John]

On Fri, 23 Aug 2024 14:32:02 +0700

Post by JJ

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 17:52:28 +0100

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 13:44:42 +0100

Post by Kerr-Mudd, John
On Tue, 20 Aug 2024 17:10:08 +0100
[was 203]

[snip]
BTW, was there a tool specifically for converting DEBUG's dump to binary? Or
converting it to a series of DEBUG's Edit command?

xxd-r from a while back; I've not checked it for improvements recently.

-> d 100 lEA
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0110 56 BA 00 02-53 31 DB 89-D7 B9 00 40-B4 3F CD 21 ***@.?.!
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0180 B4 40 CD 21-C3 4E 6F 74-20 64 62 67-20 64 75 6D ***@.!.Not dbg dum
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$
-> q

[JJ]

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 14:32:02 +0700

Post by JJ

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 17:52:28 +0100

Post by Kerr-Mudd, John
On Thu, 22 Aug 2024 13:44:42 +0100

Post by Kerr-Mudd, John
On Tue, 20 Aug 2024 17:10:08 +0100
[was 203]

[snip]
BTW, was there a tool specifically for converting DEBUG's dump to binary? Or
converting it to a series of DEBUG's Edit command?

xxd-r from a while back; I've not checked it for improvements recently.
-> d 100 lEA
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$
-> q

That's just a plain hex to binary converter. There are plenty of them
already.

What I meant by DEBUG dump is the literal output of the (MS) DEBUG's [D]ump
command which include the memory address and the ASCII representation of the
data.

So that, I could just copy and paste your DEBUG dump output without having
to edit and filter it to include only the data part. i.e. the tool should be
capable of ignoring the memory address and the ASCII parts.

[Kerr-Mudd, John]

On Sat, 24 Aug 2024 05:36:52 +0700

Post by JJ

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 14:32:02 +0700

[snip]

Post by JJ

Post by Kerr-Mudd, John

Post by JJ
BTW, was there a tool specifically for converting DEBUG's dump to binary? Or
converting it to a series of DEBUG's Edit command?

xxd-r from a while back; I've not checked it for improvements recently.
-> d 100 lEA
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$
-> q

That's just a plain hex to binary converter. There are plenty of them
already.

It is? I disagree.

Post by JJ
What I meant by DEBUG dump is the literal output of the (MS) DEBUG's [D]ump
command which include the memory address and the ASCII representation of the
data.

That's the intention of xxd-r. Do let me know how it didn't work for you.

Post by JJ
So that, I could just copy and paste your DEBUG dump output without having
to edit and filter it to include only the data part. i.e. the tool should be
capable of ignoring the memory address and the ASCII parts.

Indeed. That's why I wrote it.

[JJ]

Post by Kerr-Mudd, John
On Sat, 24 Aug 2024 05:36:52 +0700

[snip]

Post by Kerr-Mudd, John

Post by JJ
What I meant by DEBUG dump is the literal output of the (MS) DEBUG's [D]ump
command which include the memory address and the ASCII representation of the
data.

That's the intention of xxd-r. Do let me know how it didn't work for you.

Post by JJ
So that, I could just copy and paste your DEBUG dump output without having
to edit and filter it to include only the data part. i.e. the tool should be
capable of ignoring the memory address and the ASCII parts.

Indeed. That's why I wrote it.

Here's the output. Under DOSBox, BTW.

C:\>type xxd.txt
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0110 56 BA 00 02-53 31 DB 89-D7 B9 00 40-B4 3F CD 21 ***@.?.!
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0180 B4 40 CD 21-C3 4E 6F 74-20 64 62 67-20 64 75 6D ***@.!.Not dbg dum
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$

C:\>xxd-r<xxd.txt>out.com

C:\>dir out.com

Volume in drive C is C_DRIVE
Volume Serial Number is 49D7-AF21
Directory of C:\

OUT COM 100 08/25/2024 0:15a
1 File(s) 100 Bytes
0 Dir(s) 748,780,781,568 Bytes free

C:\>type out.com
Not dbg dump
Usage is: xxd-r<dbgfile>comfile
dbgfile: grdb/MS debug "d"umpc.MJ 2018 LGPL license

[Kerr-Mudd, John]

On Sun, 25 Aug 2024 00:18:53 +0700

Post by JJ

Post by Kerr-Mudd, John
On Sat, 24 Aug 2024 05:36:52 +0700

[snip]

Post by Kerr-Mudd, John

Post by JJ
What I meant by DEBUG dump is the literal output of the (MS) DEBUG's [D]ump
command which include the memory address and the ASCII representation of the
data.

That's the intention of xxd-r. Do let me know how it didn't work for you.

Post by JJ
So that, I could just copy and paste your DEBUG dump output without having
to edit and filter it to include only the data part. i.e. the tool should be
capable of ignoring the memory address and the ASCII parts.

Indeed. That's why I wrote it.

Here's the output. Under DOSBox, BTW.
C:\>type xxd.txt
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$
C:\>xxd-r<xxd.txt>out.com

Executing a dump file?!

Post by JJ
C:\>dir out.com
Volume in drive C is C_DRIVE
Volume Serial Number is 49D7-AF21
Directory of C:\
OUT COM 100 08/25/2024 0:15a
1 File(s) 100 Bytes
0 Dir(s) 748,780,781,568 Bytes free
C:\>type out.com
Not dbg dump
Usage is: xxd-r<dbgfile>comfile
dbgfile: grdb/MS debug "d"umpc.MJ 2018 LGPL license

Ah, yes; you need xxd-r as a com file to run it; I posted it as a debug
dump, so it's a catch22 situation.

If you've got a hex to bin program already, then you can have it in
hex format. But it's a bit hardcode and paranoid about splitting input; a
slimmer version is on it's way.

Still here's the warty one:

BABB0181 3E82002D 68746AE8 8B00E362 813D2D64 7407B03E E86200E3 5589D6B0
3AE85900 E35383C7 0483E904 7705E858 00E346B0 20AE75E7 BB31008A 05473C30
7211244F D43780F2 0175054E 8A24D510 880446E2 0E80FA00 74044A4E B4FFE828
00E3164B 74B980FC FF75D086 04984642 EBCBBAAD 01B409CD 21B44CCD 21F2AE74
07E80500 09C975F5 C35053B3 0189F129 D1B440CD 2189D65B 585053BA 0003B900
F031DBB4 3FCD2189 D7915B58 C34E6F74 20646267 2064756D 700D0A55 73616765
2069733A 20787864 2D723C64 62676669 6C653E63 6F6D6669 6C650D0A 64626766
696C653A 20677264 62206F72 204D5320 64656275 67202264 22756D70 0D0A24

[Kerr-Mudd, John]

On Sat, 24 Aug 2024 21:37:56 +0100

Post by Kerr-Mudd, John
On Sun, 25 Aug 2024 00:18:53 +0700

Post by JJ

Post by Kerr-Mudd, John
On Sat, 24 Aug 2024 05:36:52 +0700

[snip]

Post by Kerr-Mudd, John

Post by JJ
What I meant by DEBUG dump is the literal output of the (MS) DEBUG's [D]ump
command which include the memory address and the ASCII representation of the
data.

That's the intention of xxd-r. Do let me know how it didn't work for you.

Post by JJ
So that, I could just copy and paste your DEBUG dump output without having
to edit and filter it to include only the data part. i.e. the tool should be
capable of ignoring the memory address and the ASCII parts.

Indeed. That's why I wrote it.

Here's the output. Under DOSBox, BTW.
C:\>type xxd.txt
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$
C:\>xxd-r<xxd.txt>out.com

Executing a dump file?!

Post by JJ
C:\>dir out.com
Volume in drive C is C_DRIVE
Volume Serial Number is 49D7-AF21
Directory of C:\
OUT COM 100 08/25/2024 0:15a
1 File(s) 100 Bytes
0 Dir(s) 748,780,781,568 Bytes free
C:\>type out.com
Not dbg dump
Usage is: xxd-r<dbgfile>comfile
dbgfile: grdb/MS debug "d"umpc.MJ 2018 LGPL license

Ah, yes; you need xxd-r as a com file to run it; I posted it as a debug
dump, so it's a catch22 situation.
If you've got a hex to bin program already, then you can have it in
hex format. But it's a bit hardcode and paranoid about splitting input; a
slimmer version is on it's way.

Snipped dreadful old code;
Try this instead:

-> d 100 l7B
1639:0100 B4 3F B5 FD-BA C3 01 CD-21 91 E3 F9-89 D7 89 D6 .?......!.......
1639:0110 57 81 3D 2D-64 74 06 B0-3E F2 AE E3-4F B0 0A F2 W.=-dt..>...O...
1639:0120 AE E3 22 B0-20 F2 AE 8A-05 47 3C 30-72 24 24 4F ..". ....G<0r$$O
1639:0130 D4 37 88 C2-8A 05 47 24-4F D4 37 88-D4 D5 10 88 .7....G$O.7.....
1639:0140 04 46 49 E2-E2 5A 89 F1-29 D1 43 B4-40 CD 21 4B .FI..Z..)***@.!K
1639:0150 EB AE 3C 20-75 ED 38 05-74 C3 EB E7-4E 6F 74 20 ..< u.8.t...Not
1639:0160 61 20 64 62-67 20 66 69-6C 65 0D 0A-5A B9 10 00 a dbg file..Z...
1639:0170 51 89 D7-BE 5C 01 F3-A4 59 EB CF Q...\...Y..
-> q

Silly me- you'll need in hex format!

B43FB5FD BAC301CD 2191E3F9 89D789D6 57813D2D 647406B0 3EF2AEE3 4FB00AF2
AEE322B0 20F2AE8A 05473C30 7224244F D43788C2 8A054724 4FD43788 D4D51088
044649E2 E25A89F1 29D143B4 40CD214B EBAE3C20 75ED3805 74C3EBE7 4E6F7420
61206462 67206669 6C650D0A 5AB91000 5189D7BE 5C01F3A4 59EBCF


(Will give incorrect results if given a nondump input file containing '>')

[JJ]

Post by Kerr-Mudd, John
Snipped dreadful old code;
-> d 100 l7B
1639:0100 B4 3F B5 FD-BA C3 01 CD-21 91 E3 F9-89 D7 89 D6 .?......!.......
1639:0110 57 81 3D 2D-64 74 06 B0-3E F2 AE E3-4F B0 0A F2 W.=-dt..>...O...
1639:0120 AE E3 22 B0-20 F2 AE 8A-05 47 3C 30-72 24 24 4F ..". ....G<0r$$O
1639:0130 D4 37 88 C2-8A 05 47 24-4F D4 37 88-D4 D5 10 88 .7....G$O.7.....
1639:0150 EB AE 3C 20-75 ED 38 05-74 C3 EB E7-4E 6F 74 20 ..< u.8.t...Not
1639:0160 61 20 64 62-67 20 66 69-6C 65 0D 0A-5A B9 10 00 a dbg file..Z...
1639:0170 51 89 D7-BE 5C 01 F3-A4 59 EB CF Q...\...Y..
-> q
Silly me- you'll need in hex format!
B43FB5FD BAC301CD 2191E3F9 89D789D6 57813D2D 647406B0 3EF2AEE3 4FB00AF2
AEE322B0 20F2AE8A 05473C30 7224244F D43788C2 8A054724 4FD43788 D4D51088
044649E2 E25A89F1 29D143B4 40CD214B EBAE3C20 75ED3805 74C3EBE7 4E6F7420
61206462 67206669 6C650D0A 5AB91000 5189D7BE 5C01F3A4 59EBCF
(Will give incorrect results if given a nondump input file containing '>')

Uh... I think you're rushing it.
The generated binary from the XXD-R DEBUG dump should be 234 bytes.
Below is the output. D2B is the binary from the above converted hex codes.

C:\>dir d2*

Volume in drive C is C_DRIVE
Volume Serial Number is 49D7-AF21
Directory of C:\

D2B COM 123 08/25/2024 3:47p
1 File(s) 123 Bytes
0 Dir(s) 748,778,061,824 Bytes free

C:\>type xxd.txt
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0110 56 BA 00 02-53 31 DB 89-D7 B9 00 40-B4 3F CD 21 ***@.?.!
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0180 B4 40 CD 21-C3 4E 6F 74-20 64 62 67-20 64 75 6D ***@.!.Not dbg dum
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$

C:\>d2b < xxd.txt > out.com

C:\>dir out.com

Volume in drive C is C_DRIVE
Volume Serial Number is 49D7-AF21
Directory of C:\

OUT COM 1,212 08/25/2024 3:50p
1 File(s) 1,212 Bytes
0 Dir(s) 748,778,061,824 Bytes free

[Kerr-Mudd, John]

On Sun, 25 Aug 2024 15:59:28 +0700

Post by JJ

Post by Kerr-Mudd, John
Snipped dreadful old code;
-> d 100 l7B
1639:0100 B4 3F B5 FD-BA C3 01 CD-21 91 E3 F9-89 D7 89 D6 .?......!.......
1639:0110 57 81 3D 2D-64 74 06 B0-3E F2 AE E3-4F B0 0A F2 W.=-dt..>...O...
1639:0120 AE E3 22 B0-20 F2 AE 8A-05 47 3C 30-72 24 24 4F ..". ....G<0r$$O
1639:0130 D4 37 88 C2-8A 05 47 24-4F D4 37 88-D4 D5 10 88 .7....G$O.7.....
1639:0150 EB AE 3C 20-75 ED 38 05-74 C3 EB E7-4E 6F 74 20 ..< u.8.t...Not
1639:0160 61 20 64 62-67 20 66 69-6C 65 0D 0A-5A B9 10 00 a dbg file..Z...
1639:0170 51 89 D7-BE 5C 01 F3-A4 59 EB CF Q...\...Y..
-> q
Silly me- you'll need in hex format!
B43FB5FD BAC301CD 2191E3F9 89D789D6 57813D2D 647406B0 3EF2AEE3 4FB00AF2
AEE322B0 20F2AE8A 05473C30 7224244F D43788C2 8A054724 4FD43788 D4D51088
044649E2 E25A89F1 29D143B4 40CD214B EBAE3C20 75ED3805 74C3EBE7 4E6F7420
61206462 67206669 6C650D0A 5AB91000 5189D7BE 5C01F3A4 59EBCF
(Will give incorrect results if given a nondump input file containing '>')

Uh... I think you're rushing it.

yup! OK will do a bit of investigating.

Post by JJ
The generated binary from the XXD-R DEBUG dump should be 234 bytes.
Below is the output. D2B is the binary from the above converted hex codes.
C:\>dir d2*
Volume in drive C is C_DRIVE
Volume Serial Number is 49D7-AF21
Directory of C:\
D2B COM 123 08/25/2024 3:47p
1 File(s) 123 Bytes
0 Dir(s) 748,778,061,824 Bytes free
C:\>type xxd.txt

You've omitted the top
'> d 100 lxxx'
line that D2B uses to do a rudimentary test for a debug dump file; in this
case its 'undumping' starting at the second line.

Post by JJ
1638:0100 BA 93 01 81-3E 82 00 2D-68 74 65 31-DB BE EA 41 ....>..-hte1...A
1638:0120 5B 91 E3 55-81 FE EA 41-75 0E B0 2D-AE 74 04 B0 [..U...Au..-.t..
1638:0130 3E F2 AE 80-3D 64 75 35-B0 3A F2 AE-75 D6 B0 20 >...=du5.:..u..
1638:0140 F2 AE 75 D0-87 F7 B3 32-AC 3C 30 72-0F 24 4F D4 ..u....2.<0r.$O.
1638:0150 37 80 F2 01-75 05 4F 8A-25 D5 10 AA-4B 74 04 E2 7...u.O.%...Kt..
1638:0160 E7 EB B1 87-F7 B0 0A F2-AE 75 A9 EB-CB BA 85 01 .........u......
1638:0170 B4 09 CD 21-B8 01 4C CD-21 B3 01 5A-89 F1 29 D1 ...!..L.!..Z..).
1638:0190 70 0D 0A 55-73 61 67 65-20 69 73 3A-20 78 78 64 p..Usage is: xxd
1638:01A0 2D 72 3C 64-62 67 66 69-6C 65 3E 63-6F 6D 66 69 -r<dbgfile>comfi
1638:01B0 6C 65 0D 0A-64 62 67 66-69 6C 65 3A-20 67 72 64 le..dbgfile: grd
1638:01C0 62 2F 4D 53-20 64 65 62-75 67 20 22-64 22 75 6D b/MS debug "d"um
1638:01D0 70 63 2E 4D-4A 20 32 30-31 38 20 4C-47 50 4C 20 pc.MJ 2018 LGPL
1638:01E0 6C 69-63 65 6E 73-65 0D 0A 24 license..$
C:\>d2b < xxd.txt > out.com
C:\>dir out.com
Volume in drive C is C_DRIVE
Volume Serial Number is 49D7-AF21
Directory of C:\
OUT COM 1,212 08/25/2024 3:50p
1 File(s) 1,212 Bytes
0 Dir(s) 748,778,061,824 Bytes free

But I can't account for the wrong output length; it was OK here.

[Kerr-Mudd, John]

On Sun, 25 Aug 2024 10:34:42 +0100

Post by Kerr-Mudd, John
On Sun, 25 Aug 2024 15:59:28 +0700

[cut old stuff & testing]


Please test this slightly shorter one:

D2B.dbg
-> d 100 l76
1639:0100 B4 3F B5 FD-BA C3 01 CD-21 91 E3 F9-89 D7 89 D6 .?......!.......
1639:0110 57 81 3D 2D-64 74 06 B0-3E F2 AE E3-50 B0 0A F2 W.=-dt..>...P...
1639:0120 AE E3 22 B0-20 F2 AE 8A-05 47 3C 30-72 24 24 4F ..". ....G<0r$$O
1639:0130 D4 37 88 C2-8A 05 47 24-4F D4 37 88-D4 D5 10 88 .7....G$O.7.....
1639:0140 04 46 49 E2-E2 5A 89 F1-29 D1 43 B4-40 CD 21 4B .FI..Z..)***@.!K
1639:0150 EB AE 3C 20-75 ED 38 05-74 C3 EB E7-4E 6F 74 20 ..< u.8.t...Not
1639:0160 61 20 64 62-67 20 66 69-6C 65 0D 0A-24 5A BA 5C a dbg file..$Z.\
1639:0170 01 B4-09 CD 21 C3 ....!.
-> q

D2B.hex
B43FB5FD BAC301CD 2191E3F9 89D789D6 57813D2D 647406B0 3EF2AEE3 50B00AF2
AEE322B0 20F2AE8A 05473C30 7224244F D43788C2 8A054724 4FD43788 D4D51088
044649E2 E25A89F1 29D143B4 40CD214B EBAE3C20 75ED3805 74C3EBE7 4E6F7420
61206462 67206669 6C650D0A 245ABA5C 01B409CD 21C3

Post by Kerr-Mudd, John
--
Bah, and indeed Humbug.

[JJ]

Post by Kerr-Mudd, John
D2B.dbg
-> d 100 l76
1639:0100 B4 3F B5 FD-BA C3 01 CD-21 91 E3 F9-89 D7 89 D6 .?......!.......
1639:0110 57 81 3D 2D-64 74 06 B0-3E F2 AE E3-50 B0 0A F2 W.=-dt..>...P...
1639:0120 AE E3 22 B0-20 F2 AE 8A-05 47 3C 30-72 24 24 4F ..". ....G<0r$$O
1639:0130 D4 37 88 C2-8A 05 47 24-4F D4 37 88-D4 D5 10 88 .7....G$O.7.....
1639:0150 EB AE 3C 20-75 ED 38 05-74 C3 EB E7-4E 6F 74 20 ..< u.8.t...Not
1639:0160 61 20 64 62-67 20 66 69-6C 65 0D 0A-24 5A BA 5C a dbg file..$Z.\
1639:0170 01 B4-09 CD 21 C3 ....!.
-> q
D2B.hex
B43FB5FD BAC301CD 2191E3F9 89D789D6 57813D2D 647406B0 3EF2AEE3 50B00AF2
AEE322B0 20F2AE8A 05473C30 7224244F D43788C2 8A054724 4FD43788 D4D51088
044649E2 E25A89F1 29D143B4 40CD214B EBAE3C20 75ED3805 74C3EBE7 4E6F7420
61206462 67206669 6C650D0A 245ABA5C 01B409CD 21C3

I used that D2B.hex to generate the 118 bytes D2B.com.

I used D2B.com with that D2B.dbg which includes the starting end the ending
`->` lines to generate out.com. The result is 1150 bytes.

Then I used D2B.com with that D2B.dbg without the starting end the ending
`->` lines (i.e. just the dump) to generate out.com. The result is 689
bytes.

None of them is the correct conversion, and now I'm confused on what data
format the tool actually expecting.

In my initial message, I was asking for a tool which can simply convert the
(MS) DEBUG dump output as-is without any further editing. I'm not looking
for a tool which require custom marking in the source data. I was hoping
that such tool(s) was already made back in the mid 80s to mid 90s.

[Kerr-Mudd, John]

On Mon, 26 Aug 2024 01:44:31 +0700

Post by JJ

Post by Kerr-Mudd, John
D2B.dbg
-> d 100 l76
1639:0100 B4 3F B5 FD-BA C3 01 CD-21 91 E3 F9-89 D7 89 D6 .?......!.......
1639:0110 57 81 3D 2D-64 74 06 B0-3E F2 AE E3-50 B0 0A F2 W.=-dt..>...P...
1639:0120 AE E3 22 B0-20 F2 AE 8A-05 47 3C 30-72 24 24 4F ..". ....G<0r$$O
1639:0130 D4 37 88 C2-8A 05 47 24-4F D4 37 88-D4 D5 10 88 .7....G$O.7.....
1639:0150 EB AE 3C 20-75 ED 38 05-74 C3 EB E7-4E 6F 74 20 ..< u.8.t...Not
1639:0160 61 20 64 62-67 20 66 69-6C 65 0D 0A-24 5A BA 5C a dbg file..$Z.\
1639:0170 01 B4-09 CD 21 C3 ....!.
-> q
D2B.hex
B43FB5FD BAC301CD 2191E3F9 89D789D6 57813D2D 647406B0 3EF2AEE3 50B00AF2
AEE322B0 20F2AE8A 05473C30 7224244F D43788C2 8A054724 4FD43788 D4D51088
044649E2 E25A89F1 29D143B4 40CD214B EBAE3C20 75ED3805 74C3EBE7 4E6F7420
61206462 67206669 6C650D0A 245ABA5C 01B409CD 21C3

I used that D2B.hex to generate the 118 bytes D2B.com.
I used D2B.com with that D2B.dbg which includes the starting end the ending
`->` lines to generate out.com. The result is 1150 bytes.

That's the correct procedure, but sadly not the correct outcome.

Post by JJ
Then I used D2B.com with that D2B.dbg without the starting end the ending
`->` lines (i.e. just the dump) to generate out.com. The result is 689
bytes.

That wouldn't work properly; my program (when it's working properly) skips
to the first line after one with with a '>' in it; as one would get from a
redirected debug dump.

Post by JJ
None of them is the correct conversion, and now I'm confused on what data
format the tool actually expecting.
In my initial message, I was asking for a tool which can simply convert the
(MS) DEBUG dump output as-is without any further editing. I'm not looking
for a tool which require custom marking in the source data. I was hoping
that such tool(s) was already made back in the mid 80s to mid 90s.

I'm sorry; it seems to work for me under XP.

Maybe someone else has done an xxd port from linux.
Yup:

https://sourceforge.net/projects/xxd-for-windows/

[Kerr-Mudd, John]

On Mon, 26 Aug 2024 13:24:20 +0100

Post by Kerr-Mudd, John
On Mon, 26 Aug 2024 01:44:31 +0700

Last chance: could it be that in your environment ds<>es? - here's the same
code with a push pop at the start & a few more exits if run out of text..

1E07B43F B5FDBAC3 01CD2191 E3F989D7 89D65781 3D2D6474 06B03EF2 AEE354B0
0AF2AEE3 26B020F2 AEE3208A 05473C30 7226244F D43788C2 8A054724 4FD43788
D4D51088 04464974 0FE2E05A 89F129D1 43B440CD 214BEBAA 3C2075ED 380574BF
EBE74E6F 74206120 64626720 66696C65 0D0A245A BA6201B4 09CD21C3

[JJ]

Post by Kerr-Mudd, John
Last chance: could it be that in your environment ds<>es? - here's the same
code with a push pop at the start & a few more exits if run out of text..

No. It wouldn't be a DOS compatible system if DS!=ES at COM program startup.
So, same result in Windows XP. And I did tested it.

Post by Kerr-Mudd, John
1E07B43F B5FDBAC3 01CD2191 E3F989D7 89D65781 3D2D6474 06B03EF2 AEE354B0
0AF2AEE3 26B020F2 AEE3208A 05473C30 7226244F D43788C2 8A054724 4FD43788
D4D51088 04464974 0FE2E05A 89F129D1 43B440CD 214BEBAA 3C2075ED 380574BF
EBE74E6F 74206120 64626720 66696C65 0D0A245A BA6201B4 09CD21C3

This one works but still require the `->` custom marker, which I don't want,
because it won't work for standard DEBUG dump from anyone.

[Kerr-Mudd, John]

On Wed, 28 Aug 2024 09:17:20 +0700

Post by JJ

Post by Kerr-Mudd, John
Last chance: could it be that in your environment ds<>es? - here's the same
code with a push pop at the start & a few more exits if run out of text..

No. It wouldn't be a DOS compatible system if DS!=ES at COM program startup.
So, same result in Windows XP. And I did tested it.

Post by Kerr-Mudd, John
1E07B43F B5FDBAC3 01CD2191 E3F989D7 89D65781 3D2D6474 06B03EF2 AEE354B0
0AF2AEE3 26B020F2 AEE3208A 05473C30 7226244F D43788C2 8A054724 4FD43788
D4D51088 04464974 0FE2E05A 89F129D1 43B440CD 214BEBAA 3C2075ED 380574BF
EBE74E6F 74206120 64626720 66696C65 0D0A245A BA6201B4 09CD21C3

This one works

Phew!

Post by JJ
but still require the `->` custom marker, which I don't want,
because it won't work for standard DEBUG dump from anyone.

Oh dear. I felt sure I'd catered for that.
So I just tested, yup, it's OK here.

[Kerr-Mudd, John]

On Wed, 28 Aug 2024 08:53:42 +0100

Post by Kerr-Mudd, John
On Wed, 28 Aug 2024 09:17:20 +0700

Post by JJ

Post by Kerr-Mudd, John
Last chance: could it be that in your environment ds<>es? - here's the same
code with a push pop at the start & a few more exits if run out of text..

No. It wouldn't be a DOS compatible system if DS!=ES at COM program startup.
So, same result in Windows XP. And I did tested it.

Well something was different - ah well, we got there.

Post by Kerr-Mudd, John

Post by JJ

Post by Kerr-Mudd, John
1E07B43F B5FDBAC3 01CD2191 E3F989D7 89D65781 3D2D6474 06B03EF2 AEE354B0
0AF2AEE3 26B020F2 AEE3208A 05473C30 7226244F D43788C2 8A054724 4FD43788
D4D51088 04464974 0FE2E05A 89F129D1 43B440CD 214BEBAA 3C2075ED 380574BF
EBE74E6F 74206120 64626720 66696C65 0D0A245A BA6201B4 09CD21C3

This one works

Phew!

Post by JJ
but still require the `->` custom marker, which I don't want,
because it won't work for standard DEBUG dump from anyone.

Oh dear. I felt sure I'd catered for that.
So I just tested, yup, it's OK here.

The prog tests the first 2 chars of the input for '-d',
if so it is deemed to be a DOS DEBUG file, if not a scan for '>' is
performed to "check" for a GRDB one. if neither it puts out an error
message.
It is then assumed that the remaining lines of input are of
format:

[prelude][space] [set of hex pairs] [double space] [other stuff to eol]

where:
[prelude] is typically segaddr:offset but must have no embedded
spaces.

[set of hex pairs] is e.g. [01 02 03 04-AB CD ..] with either space or '-'
between the pairs (anything <'0' actually).

[other stuff to eol] *can* contain spaces, the prog just skips
until LF seen

{-q should get ignored}

Given that you have a H2B prog and 'debug' you can see for yourself the
simplicity of the code.

[Kerr-Mudd, John]

On Wed, 28 Aug 2024 09:22:02 +0100
"Kerr-Mudd, John" <***@127.0.0.1> wrote:

[]



Now scans for a '-' prompt (skips a '>' if it's next) then allows
for spaces between the prompt and 'd'/'D'.

134 bytes

-> d 100 l86
16B1:0100 B4 3F B5 FD-BA 86 01 CD-21 91 E3 68-89 D7 89 D6 .?......!..h....
16B1:0110 57 B0 2D F2-AE 75 55 80-3D 3E 75 02-47 49 B0 20 W.-..uU.=>u.GI.
16B1:0120 F3 AE 0A 45-FF 3C 64 75-E8 B0 0A F2-AE E3 28 83 ...E.<du......(.
16B1:0130 C7 09 83 E9-09 76 20 8A-05 47 3C 30-72 24 24 4F .....v ..G<0r$$O
16B1:0140 D4 37 88 C2-8A 05 47 24-4F D4 37 88-D4 D5 10 88 .7....G$O.7.....
16B1:0150 04 46 49 74-02 E2 E0 5A-89 F1 29 D1-43 B4 40 CD .FIt...Z..)***@.
16B1:0160 21 C3 3C 20-75 EF 38 05-74 BF EB E9-5A BA 75 01 !.< u.8.t...Z.u.
16B1:0170 B4 09 CD 21-C3 4E 6F 74-20 61 20 64-62 67 20 66 ...!.Not a dbg f
16B1:0180 69-6C 65 0D 0A-24 ile..$
-> q


Avoids address by moving di ptr +9 after lf. (grdb outputs last line can
put a '-' between the address and 1st hex, scanning for a space missed
that pair).

[wolfgang kern]

Post by JJ
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.
__
wolfgang

[Kerr-Mudd, John]

On Fri, 23 Aug 2024 14:44:20 +0200

Post by wolfgang kern

Post by JJ
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.
"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.

[wolfgang kern]

On 23/08/2024 21:17, Kerr-Mudd, John wrote:
...

Post by Kerr-Mudd, John

Post by wolfgang kern
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.
"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.

depending on file size limits part of the address field may be useful,
and the ASCII trail were just ignored by hex2bin.

Post by Kerr-Mudd, John
I could post code in hex, if that's more acceptable - it's just easier
for me to just CnP a debug dump.

your style is readable for me (after eye recovers from wrong treatment).

Post by Kerr-Mudd, John
I did hex2bin and v versa a while back; OK I'll revisit it to have a
prog that does both.

AFAIR early DOS had debug.com, later vsn debug.exe.
hex_dump options were a bit different.

my OS contains only bin2hex as part of the implied debug+disass.
the address field vary with the chosen range and always show ASCII:

xxxx_xxxx 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 8+1+8 chars.
so line length is 71 or 76 which fit into 80 char screens and .nws too.
__
wolfgang

[Kerr-Mudd, John]

On Fri, 23 Aug 2024 23:00:32 +0200

Post by wolfgang kern
...

Post by Kerr-Mudd, John

Post by wolfgang kern
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.
"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.

depending on file size limits part of the address field may be useful,
and the ASCII trail were just ignored by hex2bin.

You have to code for it, or maybe you'd pick up displayed valid hex codes

Post by wolfgang kern

Post by Kerr-Mudd, John
I could post code in hex, if that's more acceptable - it's just easier
for me to just CnP a debug dump.

your style is readable for me (after eye recovers from wrong treatment).

Post by Kerr-Mudd, John
I did hex2bin and v versa a while back; OK I'll revisit it to have a
prog that does both.

AFAIR early DOS had debug.com, later vsn debug.exe.
hex_dump options were a bit different.

My xxd-r allows for both grdb and debug.exe dumps. I haven't tested it
under earlier DOS versions with possibly different dump format.

Post by wolfgang kern
my OS contains only bin2hex as part of the implied debug+disass.

: 1 2 3 4 5 6

Post by wolfgang kern
0123456789012345678901234567890123456789012345678901234567890123456789
xxxx_xxxx 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 8+1+8 chars.
so line length is 71 or 76 which fit into 80 char screens and .nws too.

I think xxd-r should handle that; it relies on there being 16 (hex pairs
+blank) +1 per line. Hmm, I should count pairs, not cols.

[Kerr-Mudd, John]

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 23:00:32 +0200

Post by wolfgang kern
...

Post by Kerr-Mudd, John

Post by wolfgang kern
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.
"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.

depending on file size limits part of the address field may be useful,
and the ASCII trail were just ignored by hex2bin.

You have to code for it, or maybe you'd pick up displayed valid hex codes

Post by wolfgang kern

Post by Kerr-Mudd, John
I could post code in hex, if that's more acceptable - it's just easier
for me to just CnP a debug dump.

your style is readable for me (after eye recovers from wrong treatment).

Post by Kerr-Mudd, John
I did hex2bin and v versa a while back; OK I'll revisit it to have a
prog that does both.

AFAIR early DOS had debug.com, later vsn debug.exe.
hex_dump options were a bit different.

My xxd-r allows for both grdb and debug.exe dumps. I haven't tested it
under earlier DOS versions with possibly different dump format.

Post by wolfgang kern
my OS contains only bin2hex as part of the implied debug+disass.

: 1 2 3 4 5 6

Post by wolfgang kern
0123456789012345678901234567890123456789012345678901234567890123456789
xxxx_xxxx 00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 8+1+8 chars.
so line length is 71 or 76 which fit into 80 char screens and .nws too.

I think xxd-r should handle that; it relies on there being 16 (hex pairs
+blank) +1 per line. Hmm, I should count pairs, not cols.

My latest won't cater for that format; it assumes that a double space
implies end of hex pairs; it would fail in the middle of your output.

Counting down pairs might be better, but needs more coding to handle a
short line at the end.

[Kerr-Mudd, John]

On Fri, 23 Aug 2024 20:17:59 +0100

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 14:44:20 +0200

Post by wolfgang kern

Post by JJ
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.
"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)



Both : hex1a (-d for dump, else assume input is display hex)

B43FB552BAC301CD2191E3F989D6BF855457803E8300647529ACD41086E02704
F01440AA4384F375F380E3BF7504B80D0AABE2E55AB30189F929D1B440CD214B
EBBEAC3C30721709ED741288C295244FD43730F775F588D4D510AA31C095E2E2
EBD2


So latest Base85a

B43FB9C86EBAC301CD2191E3F989D689D701CFB355803E830064744E31C0ABAB
BF757557AD86E095AD86E089C209E8750A80F9047205B07AAAEB1C51B9040052
31D295F7F39558F7F39250E2F252B105580421AAE2FA5983E90477C85AB30101
F929D1B440CD214BEB96B87575ABABAA9757803C7A750931C0ABAB46E2F4E3DC
5131ED31D2B90500AC2C21721298505295F7E39558F7E301D55A01C283D500E2
E79586E0AB9286E0AB5983E90577C3EBAB

[wolfgang kern]

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 20:17:59 +0100

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 14:44:20 +0200

Post by wolfgang kern

Post by JJ
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.
"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.

Post by Kerr-Mudd, John
Both : hex1a (-d for dump, else assume input is display hex)
B43FB552BAC301CD2191E3F989D6BF855457803E8300647529ACD41086E02704
F01440AA4384F375F380E3BF7504B80D0AABE2E55AB30189F929D1B440CD214B
EBBEAC3C30721709ED741288C295244FD43730F775F588D4D510AA31C095E2E2
EBD2
So latest Base85a
B43FB9C86EBAC301CD2191E3F989D689D701CFB355803E830064744E31C0ABAB
BF757557AD86E095AD86E089C209E8750A80F9047205B07AAAEB1C51B9040052
31D295F7F39558F7F39250E2F252B105580421AAE2FA5983E90477C85AB30101
F929D1B440CD214BEB96B87575ABABAA9757803C7A750931C0ABAB46E2F4E3DC
5131ED31D2B90500AC2C21721298505295F7E39558F7E301D55A01C283D500E2
E79586E0AB9286E0AB5983E90577C3EBAB

even space(s) saved ...it's much harder to read than B4 3F B9 C8 6E
and for odd file size just fill up with NOP or SPACE until 512 bounds.
__
wolfgang

[Kerr-Mudd, John]

On Sat, 24 Aug 2024 10:13:38 +0200

Post by wolfgang kern

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 20:17:59 +0100

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 14:44:20 +0200

Post by wolfgang kern

Post by JJ
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.
"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.

Post by Kerr-Mudd, John
Both : hex1a (-d for dump, else assume input is display hex)
B43FB552BAC301CD2191E3F989D6BF855457803E8300647529ACD41086E02704

[...]

Post by wolfgang kern
even space(s) saved ...it's much harder to read than B4 3F B9 C8 6E
and for odd file size just fill up with NOP or SPACE until 512 bounds.

Would you prefer a version that puts a space every 4 pairs? (106 bytes)

B43FB552 BAC301CD 2191E3F9 89D6BF8A 5457803E 83006475 31ACD410 86E02704
F01440AA 4384F375 F3F6C307 7503B020 AA80E3BF 7504B80D 0AABE2DD 5AB30189
F929D1B4 40CD214B EBB6AC3C 30721709 ED741288 C295244F D43730F7 75F588D4
D510AA31 C095E2E2 EBD2


(More spaces=more lines!)

[wolfgang kern]

On 24/08/2024 15:14, Kerr-Mudd, John wrote:
...

Post by Kerr-Mudd, John

Post by wolfgang kern
even space(s) saved ...it's much harder to read than B4 3F B9 C8 6E
and for odd file size just fill up with NOP or SPACE until 512 bounds.

Would you prefer a version that puts a space every 4 pairs? (106 bytes)
B43FB552 BAC301CD 2191E3F9 89D6BF8A 5457803E 83006475 31ACD410 86E02704
F01440AA 4384F375 F3F6C307 7503B020 AA80E3BF 7504B80D 0AABE2DD 5AB30189
F929D1B4 40CD214B EBB6AC3C 30721709 ED741288 C295244F D43730F7 75F588D4
D510AA31 C095E2E2 EBD2

my personal preference is based on the limited eyesight and familiarity
with bytes in hex format. But I could live with quads as well :)
__
wolfgang

[Kerr-Mudd, John]

On Sat, 24 Aug 2024 10:13:38 +0200

Post by wolfgang kern

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 20:17:59 +0100

Post by Kerr-Mudd, John
On Fri, 23 Aug 2024 14:44:20 +0200

Post by wolfgang kern

Post by JJ
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.
"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.

Smaller than linelength?! Ah debug's 'E' command must have separated hex
pairs. Just for you:

debug hex2bin.com
; 0 1 2 3 4 5 6 7 8 9 A B C D E F
e100 BA C3 01 B9 3C FE B4 3F CD 21 91 E3 F4 89 D6 89
e110 D7 57 AC 3C 30 72 0E 24 4F D4 37 30 F3 75 05 4F
e120 8A 25 D5 10 AA E2 EB 5A 89 F9 29 D1 43 B4 40 CD
e130 21 4B EB CF
rcx
34
w
q

[]

[wolfgang kern]

Post by Kerr-Mudd, John

Post by wolfgang kern

Post by Kerr-Mudd, John
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.

Smaller than linelength?!

I never tried to enter more than 16 bytes at once.

Post by Kerr-Mudd, John
Ah debug's 'E' command must have separated hex
debug hex2bin.com
; 0 1 2 3 4 5 6 7 8 9 A B C D E F
e100 BA C3 01 B9 3C FE B4 3F CD 21 91 E3 F4 89 D6 89
e110 D7 57 AC 3C 30 72 0E 24 4F D4 37 30 F3 75 05 4F
e120 8A 25 D5 10 AA E2 EB 5A 89 F9 29 D1 43 B4 40 CD
e130 21 4B EB CF
rcx
34
w
q

DX=01c3 CX=FE3C AH=3F INT21 swap ax,cx JCXZ RET :)

yes, that's what I'm familiar with since almost five decades.
BUT as said before, conversion itself is a short task.
So writing a tool apart from DOS-debug can use any format.
__
wolfgang