I still have the same problem with wimgapi 6.0 and wimfltr.I do not understand the reason of ERROR_FILE_NOT_FOUND (0x2)wimfltr is installed on my win7x64 hostOS and I have, in the same folder, imagex.exe, wimgapi.dll (6.0) and WimUtilThe same command line with imagex worksE:\WimUtil\x64\WimUtil.exe /mount E:\WimUtil\Wim\Test.wim 1 E:\WimUtil\1\Mount (Mount Error: (0,0,2)E:\WimUtil\x64\imagex.exe /mount E:\WimUtil\Wim\Test.wim 1 E:\WimUtil\1\Mount (work)
ok I found what is causing this error.seems wimimgapi.dll < 6.1.x does not accept a null string for the TempPath whereas 6.1.x does. why this matters:if a temp path is specified the image is mounted as RW if Null temp path the mount is ROit seems that with < 6.1 I cannot pass a null unicode string and expect that wimgapi.dll understands.easy to test for and fix but annoying.
I think, indeed, that this must be the solution for wimgapi < 6.1.I'll try your code later (not at home) or if you have a trial version.
Another little thing I've seen, I sometimes get an error on first launch of WimUtil /info,and it works very well at second trial.
Quote from: ChrisR on April 21, 2011, 06:09:27 PMAnother little thing I've seen, I sometimes get an error on first launch of WimUtil /info,and it works very well at second trial.what error do you get? can you reproduce this easily?
Faulting application name: WimUtil.exe, version: 3.1.1.0, time stamp: 0x4bc81615Faulting module name: WimUtil.exe, version: 3.1.1.0, time stamp: 0x4bc81615Exception code: 0xc0000005Fault offset: 0x0001678bFaulting process id: 0x1218
well I've been able to figure out which point the access violation occurs but what is causing it or how to fix. :(more info and code here: http://www.autoitscript.com/forum/topic/127075-wimgapi-udf/page__view__findpost__p__887806
seems wimimgapi.dll < 6.1.x does not accept a null string for the TempPath whereas 6.1.x does. why this matters:if a temp path is specified the image is mounted as RW if Null temp path the mount is ROit seems that with < 6.1 I cannot pass a null unicode string and expect that wimgapi.dll understands.easy to test for and fix but annoying.
Hi Homes32,about the issue with wimutil /mount and wimgapi 6.0.Quote from: Homes32 on April 20, 2011, 02:31:37 PMseems wimimgapi.dll < 6.1.x does not accept a null string for the TempPath whereas 6.1.x does. why this matters:if a temp path is specified the image is mounted as RW if Null temp path the mount is ROit seems that with < 6.1 I cannot pass a null unicode string and expect that wimgapi.dll understands.easy to test for and fix but annoying. The new package for Win7PE SE is almost ready, maybe still some adjustment.Is it possible to have an update for this issue ? No rush, take the time needed but I would like to update the project shortly. This, for a Perfect use of WimUtil in Win7PE SE .I think we can wait for wimUtil /info for now, waiting for support and a solution.Futher up to you.Thank you again for the Great WimUtil.exe and your Hard work
just /RW that mounts the image correctly but without permission to write with wimgapi 6.0.
fixed. new wimutil file version is 3.1.2.1
wimutil.exe "WimFile"/boot [index]
I have a small problem with the booflag, wimutil does not set it even if I use /boot switch with the /capture option.Also there is no entry about _WIM_SetBootImage in the log file using your WimGAPI UDF works.could it be that the /boot switch is ignored?
BTW: a standalone option: Quotewimutil.exe "WimFile"/boot [index]like imagex have would be nice
I suppose it could be done if you think that people would benefit from it.BTW: do you have enough experience with windows to guess at what could be causing the struct read to fail with the /info issue?