|Mailing List email@example.com Archived Message #7||back to list|
In <firstname.lastname@example.org>, on 08/11/18
at 04:51 PM, Lewis <email@example.com> said:
Okay. that would imply that even if one or more of the files inside theDepending on your definition of broken, the answer probaby yes.
PF was broken, the CRC should still match.
If I extract the PF to a temporary directory:That's the only test mode that's available. Well that's not quite true.
[d:\] e_pf.exe AOSBOOT.PF test\ <Enter>
e_pf.exe AOSBOOT.PF test\ /B
which requests bootdisk unpacker mode, which I have never used. I'm
pretty sure I've never had the need to build e_pf either.
Can I assume you copied AOSBOOT.PF from the stick?
all files extract cleanly. If I then compare those files to the filesCan I assume you rebuilt the failing .pf file and the USB stick and that
used to create the PF, they all compare without errors.
the failure persists?
Did you happen to be able to see the name of the failing file? I suspect
A count of the dots might help too. I guess we are configured for dots
rather than the default progress bar character.
If the problem persists, please open a ticket for this in the mantis
bugtracker, since it is related to the ArcaOS installer, and attach the
failing .pf file.
The unpacking code in e_pf and in memdisk are entirely different. e_pf
does not appear to check the CRCs. I guess Veit only implemented what he
needed at the time.
Mail to ListMaster