wimlib

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?

Hi,

It turned out that the windows-build.sh script had a bug that made it not use the -static-libgcc compiler flag in the MINGW32 and MINGW64 MSYS2 environments as intended, causing the DLL to depend on libgcc. I've pushed out a commit that fixed this. This did not affect the official i686 and ...

Thanks for the prompt response.

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.

That said, I haven't regression tested on older than Windows 8.1 (due to it being the minimum WIMBOOT target for us here ...

What dependency problems are you referring to, specifically? The ARM64 libwim-15.dll has the same dependencies as the x86_64 one, I believe. It only depends on standard Windows DLLs (ntdll, msvcrt, advapi32, user32, kernel32).


Also to clarify I tested the 32 bit (x86) and 64 bit (amd64) non ...

So rebuilding it with GCC :

32-bit Windows 8.1:

The program can't start because libgcc_s_dw2-1.dll is missing from your computer. Try reinstalling the program to fix this problem.

64-bit Windows 8.1:

Works fine.

Rebuilding it with CLANG :

32-bit Windows 8.1:

The program can't start ...