Problems with UnTarBZ2

I’m trying to extract a recent copy of the OMAP source code on my Risc PC, when I try to extract it, I get the error shown below;
(I’m using !UnTarBZ2 v1.03 & running RISC OS 6.20)

Has anyone else as this problem? (The same file will extract fine on my Iyonix)

Calculating MD5 checksum of archive 12:38:53

0d7e9c7309c3b4c6e640cf713bc795e6 ADFS::Drive4.$.Rob.OMAP.src-omap/5/17/tar/bz2

Decompressing archive 12:39:05

Extracting tar file contents 12:44:07

Internal error: Undefined instruction at &0000DF28

Postmortem requested

Processor registers
a1/r0 =0×00011910, a2/r1 =0×00000000, a3/r2 =0×00000000, a4/r3 =0×00000007
v1/r4 =0×000118f8, v2/r5 =0×00011915, v3/r6 =0×00011901, v4/r7 =0×00011910
v5/r8 =0×0000f1a4, v6/r9 =0×00000000, sl/r10=0×00010d84, fp/r11=0×000117f4
ip/r12=0×00000064, sp/r13=0×000117bc, lr/r14=0×6000bf40, pc/r15=0×6000df28

Stack backtrace
Arg1: 0×000118f8 71928 → [0xffffff00 0×00000000 0×00000000 0×00000013]
df28 in function getdir
d3a8 in function ExtractFiles
Arg2: 0×00011f60 73568 → [0×00011f9c 0×00011fdc 0×00011fdf 0×00011fe2]
Arg1: 0×0000000c 12
9450 in function main
386b100 in unknown procedure
e150 in anonymous function

Removing CVS control files (if any) 12:44:07

EraseCVS (0.08, 11 Aug 2000).
Erasing CVS dirs from ‘ADFS::Drive4.$.Rob.OMAP.unzipped’

Finished 12:44:07

We have several reports of people having problems with UnTarBZ2 – I’m starting to suspect some recent changes which were submitted to the ‘tar’ program – but it could equally be that I’ve taken a newer version of bunzip2 and that might be generating broken output. Until I get a chance to properly investigate and work on this, I think it’s safer to assume UnTarBZ2 is faulty and you should try to use something else (tar -jxf on Linux/UNIX or something like 7-zip on Windows).

Sadly, I have a work trip to India coming up next week so I don’t really have any time to investigate for a few weeks. However, source code is included within the UnTarBZ2 download so it’s perfectly possibly for someone else in the community to investigate this… :)

Cheers Steve,
I’ve just tried the previous version of UnTarBZ2 and got a similar error.
It works fine on my StrongArm Risc PC running RISC OS 4.39, it just doesn’t like my Kinetic running RISC OS 6.20!

I’ve also run into this problem on RPCEmu 0.8.8 using RO 4.02 running UnTarBZ2 1.03 to decode the current full source archive (2011-12-18 06:40:42)

I get the following output:

Calculating MD5 checksum of archive 14:39:23

d2f6da67a5eeb250842e278bd71185e9 ADFS::HardDisc4.$.cvs-repos/tar/bz2
Decompressing archive 14:39:53
/ADFS::HardDisc4.$/cvs-repos.tar.bz2: done
Extracting tar file contents 14:50:05
Internal error: undefined instruction at &0000DF2C
Postmortem requested

  Arg1: 0×00011734 71476 → [0×82248f34 0×000117a4 0×80000000 0×0000f22c]

2248ed8 in shared library function
stack overwritten
Removing CVS control files (if any) 14:50:06
EraseCVS (0.08, 11 Aug 2000).

Erasing CVS dirs from ‘ADFS::HardDisc4.$.cvs-repos’
Finished 14:50:06

Disassembling the tar binary in zap shows:

0000DF24 : .0Ðç : E7D03001 : LDRB    R3,[R0,R1]
0000DF28 : ƒ,.á : E1032C83 : Undefined instruction
0000DF2C : .  ã : E3A02000 : MOV     R2,#0

Armalyser disassembles it thus:

|L0000DF24|
        LDRB    a4,[a1,a2]
        SMLABB  a4,a4,ip,a3                     ; ARMv5T
        MOV     a3,#0

The alternative version of UnTarBZ2 available from http://peter.drobe.co.uk/ appears to work OK.

Thanks for the link James, I’ll try it out on my Kinetic Risc PC and see if I still get the same issue.

I tried out the version from http://peter.drobe.co.uk on my Kinetic Risc PC and I just get the error “Unable to start application (decompression failed)”

I may have a tinker with the source later, see if I can get it to play!

I can not find that error in the source code of UnTarBZ2. Are you sure it is a error from the application or do you run it from the zip file and does that generate an error?

I get this error when I try to unpack a tar.bz2 file. The error is also displayed if I double click on any of the programs in the !UnTarBZ2.Tools directory.

Could this be an issue with my Kinetic running RISC OS 6.20?

Could this be an issue with my Kinetic running RISC OS 6.20?

Yes, I think so. Squeezed executables are rejected. The same happens on the a9home. Use the xpand utility (from the DDE) to manually decompress the binary, and see if that helps.

Thanks! I’ll give that a go.

I’ve decompressed the binary files using xpand, and everything worked!
I can now use !UnTarBZ2 on my Kinetic!

Thanks for the help everyone.

Rob, if you get the chance sometime, could you try out this version of !UnTarBZ2 on RISC OS 6 and see if it works?

Rob, if you get the chance sometime, could you try out this version of !UnTarBZ2 on RISC OS 6 and see if it works?

That version works fine!

Hi. I’d like to distribute a fixed version on the ROOL site. What are the changes in the one above? Ta.

Hi. I’d like to distribute a fixed version on the ROOL site. What are the changes in the one above? Ta.

All I did was xpand the binary from the version on http://peter.drobe.co.uk/ and recompress using the latest DDE tools (v. 22). I’ll remove the version I uploaded if you make one that works available on the ROOL site. Doesn’t pay to have too many versions rocking about ;)

If you’re doing work like this, it might be worth checking other binaries that are part of the BBE, like !Builder’s !RunImage, as there have been reports of that not working under RO6, too. Thanks!

The versions of UnTarBZ2 on the ROOL site already have all their binaries unsqueezed, so I’m a bit confused. Reading back through this thread, the real problems are with tar. I’ve downloaded Perter’s UnTarBZ2 to see what he’s done and I’ll fold his changes into the version on the ROOL site shortly.

There is now a new build of UnTarBZ2 on the ROOL site. This is a merge of Peter’s fixes to the ‘tar’ binary with the other bits from the application. Hopefully, this will work better for everyone.

This new build (downloaded on 25 Mar) doesn’t get past the self extraction stage (unless I’m doing something wrong).
It crashes with ‘abort on data transfer at &00008024’
Iyonix 5.16 or RPC 4.02

No problem here. Opening link to it in netsurf. Save to ramdisc. Set type utilit. Run it. No problem. (4 april 2012, Iyonix 5.16)

I sometimes get lines like

tar: directory checksum error (62040 != 58658)
tar: directory checksum error (62040 != 53449)

at the end of the UnTarBZ2 report that lists all the files that it is extracting. The MD5 checksum of the archive that it calculates and reports at the start agrees with the published checksum on the ROOL website. What does it mean? Should I be worried?