Sujet : Re: undump tool (was: Re: Base85 for DOS
De : admin (at) *nospam* 127.0.0.1 (Kerr-Mudd, John)
Groupes : alt.lang.asm comp.os.msdos.programmerDate : 24. Aug 2024, 21:37:56
Autres entêtes
Organisation : Dis
Message-ID : <20240824213756.58b5683f4853e4d06088de61@127.0.0.1>
References : 1 2 3 4 5 6 7 8 9 10 11
User-Agent : Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
On Sun, 25 Aug 2024 00:18:53 +0700
JJ <
jj4public@outlook.com> wrote:
On Sat, 24 Aug 2024 09:47:55 +0100, Kerr-Mudd, John wrote:
On Sat, 24 Aug 2024 05:36:52 +0700
JJ <jj4public@outlook.com> wrote:
[snip]
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.
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 V...S1.....@.?.!
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
Executing a dump file?!
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
-- Bah, and indeed Humbug.