Extract error with WinPE ramdisk as target

[JFX]

I just noticed that if you extract a file to the WinPE X: drive you get an error
unless the file does already exists.

X:>C:\wimlib\wimlib-imagex.exe extract E:\sources\install.wim 1 \Windows\explor
er.exe
[ERROR] Can't create file ".\explorer.exe" (status=0xc0000034): No such file or
directory
ERROR: Exiting with error code 47:
Failed to open a file.

X:>copy NUL explorer.exe
1 Datei(en) kopiert.

X:>C:\wimlib\wimlib-imagex.exe extract E:\sources\install.wim 1 \Windows\explor
er.exe
Extracting files: 2318 KiB of 2318 KiB (100%) done
Done extracting files.

[synchronicity]

Interesting. This is only a problem on the in-memory filesystem of Windows PE. It actually seems to be a bug in Windows: the FILE_SUPERSEDE flag does not have the expected (and documented) effect when the named file does not exist. Probably not many applications actually use this flag. I'll add a workaround in the next version.

[JFX]

Thanks for quick respond. I didn't even know this flag does exist until now.

[JFX]

Not worth a new topic,

it seems the new wimlib dll files have incorrect Linker Time in the PE Header.
I used that info to distinguish between beta versions.

Or it there better way to do that?

[synchronicity]

Hi,

Thanks for testing the latest BETA. However, you shouldn't be relying on build timestamps. In general you cannot assume that two files with different build timestamps are different, nor can you assume that two files with the same build timestamp are the same. I also looked at some old releases of wimlib, and the latest BETA is not the only one that does not have a valid build timestamp on libwim. Perhaps I should start numbering the BETAs I post? BETA1, BETA2, etc. (That being said, the BETA files are still for testing only and I will delete them once an actual release is made!)