wimlib

Got it working!!!

Been working on this since my last post - it's been more than a month already!

Using fashionable vibe coding, I got it to the point where it'd create a WIM that works, for a given definition of works:

- The WIM file is created and the process doesn't abort
- The WIM file can be extracted using ...

Also, here should be just the modified files, assuming Claude AI hasn't hallucinated too badly, of course: I truly hope this would be the healing salve for these kinds of (wishfully formerly) fatal read errors?

When wimlib is being consumed from Windows PE/RE, sometimes a read error occurs:
WhatsApp Image 2026-02-05 at 21.29.00.jpeg
Which is always fatal during unsafe compaction passes:
WhatsApp Image 2026-02-05 at 00.23.13.jpeg

The thing with these types of failures is, they are almost always ...

Yeah sounds crazy. Since everything else does seem to work (no checksum or other errors) for 99.99% of the image (for now), I'll just replace the broken files with their backups (eliminating the broken WIM backings in the process) and do a safe compaction pass (recompressing the whole disk from ...

A follow-up to this question, I enhanced ZIPmagic's CHKDSK code to check for these additional return codes, when reading 1 byte from a WIMBOOT hosted file (per your suggestion from way back when) fails:

(dw = 31) // A device attached to the system is not functioning
(dw = 4447) // The WOF driver ...

So I've got a very interesting scenario. Either due to a corrupt internal SSD , or a corrupt external thumb drive , or corrupt memory (investigations are still ongoing); I ended up with 5,002 unreadable files, and 2,318 checksum mismatched files - inside a 1 TB WIMBOOT archive which contains many ...

Since this is off-topic from ARM64 support, can you please create a new thread? Please include a clear report of the issue, including the error message(s) you're currently seeing and attaching the DLL that's not working. Please use the latest git master branch only, without anything reverted , and ...

if "$cc" --version | grep -q '(GCC)'; then
configure_args+=("CC=$cc -static -static-libgcc -static-libstdc++")
fi

That's also the old code, not the new code, so make sure you've run 'git pull'...


To clarify after doing the git pull, this is the code I ended up with:

if ! "$cc" --version ...

synchronicity wrote: Thu Feb 08, 2024 3:21 am

Yes, I haven't seen the issue on newer operating systems such as Windows 10, and surely wouldn't run into it on Windows Server 2022 either.

Why not do the build on one of those, then?

I'm already building on Windows 11, do you mean I should try building on Windows 8.1 instead?