Welcome, Guest. Please login or register.

Author Topic: IBrowse 2.5 released!  (Read 8567 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline kolla

Re: IBrowse 2.5 released!
« on: September 02, 2019, 08:32:52 AM »

MUI 3.8 contains a few nasty bugs which IBrowse tries to workaround, but there are a couple of issues (at least, one can cause a crash) that can't be avoided without removing those features from IBrowse entirely :(.  Stefan Burstroem fixed these in MUI 3.9 himself many years ago.  That is the reason we recommend a minimum of MUI 3.9.

Can you be more specific? MUI 3.9 was beta at best, and though it fixes some bugs in 3.8, it also introduced new features and new bugs. So ideally, one would wish to start with MUI 3.8, and only update the classes from 3.9 that really are improvements. Well, ideally, MUI 3 for 68k should be "rebundled" :)
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline kolla

Re: IBrowse 2.5 released!
« Reply #1 on: September 04, 2019, 06:51:45 AM »
it won't decompress with some gui based unarchiving utilities.
You are just encountering a bug in xad that the OS 3.9 "Unarc" program, and certain other programs rely on. You will encounter the same bug if you use xadunfile from CLI. It happens when the archive contains directories that have been packed as if they are files, with trailing slashes.

For example in the AmiSSL-4.3.lha...
Code: [Select]
AmiSSL/
AmiSSL/C/
AmiSSL/C/AmigaOS3/
AmiSSL/C/AmigaOS3/OpenSSL
...
xad will fail to unpack the three first, and will instead print error message "opening file failed", and OS 3.9 Unarc will open a requester about error.
Normally, when creating an archive with an Amiga version of Lha, it doesn't create these "buggy paths" in the archive (at least I never saw it happen), so I suspect this only happens with some version of u*ix or Windows version of an Lha archiver. Regardless, I think xad should be fixed to handle it better (if it isn't already, not been paying attention to what goes on with xad).
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS