What about wimfltr.sys/wimmount.sys required for mount/unmount, and wingapi version 6.0.6001 or 6.1.7600. ?
I have a message box Mount Error: (0,0,0) if image_path don't exist. I create it, it's OK.
Another message with unmount "UnMount Error: (0,0,0)", classic for me with wimmount driver, if I open the explorer on the mounted folder, even if I go out explorer before unmount the image.I delete the folder and it's OK (Dism /Get-MountedWimInfo : no image mounted...)
The image could not be fully unmounted.The following files or folders could not be deleted. Please close all applications that have these files in use before trying to unmount again:with imagex /logfile [6496] [ INFO ] ImageUnmarshallHandle: Reconstituting wim at E:\Windows\Win7Ultimate32\sources\install.wim.[6496] DeleteAndRestoreDirectory:(161): The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process.[6496] RestoreMountDirectory:(222): The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process.[6496] WIMUnmountImageHandle:(1240): The directory could not be completely unmounted. This is usually due to applications that still have files opened within the mount directory. Close these files and unmount again to complete the unmount process.[5532] [ INFO ] ImageUnmarshallHandle: Reconstituting wim at E:\Windows\Win7Ultimate32\sources\install.wim.
you can use either one or switch between the 2 using wimutil.ini to set the path to the dll.keep in mind that the extract option only works with wimgapi 6.1xI don't have any checks in place at the moment to check if there are conflicts using wimmount.sys with wimfltr.sys running. it can be added in the future if it is found necessary.By default WimUtil will look for wimgapi.dll in your system dir. (ie. Windows\System32)you can overide this behavior by specifing the path to wimgapi.dll in an ini file.WimUtil.ini[WimUtil]wimgapi.dll=x86\wimgapi.dll
I still have the issue with unmount and explorer whatever the tool used WimUtil, Imagex or Dism It works fine if I close any explorer.
The progressbar remains static for me ?
To recover wimmount.inf, wimmount.sys, wimserv.exe and wimgapi.dll from source win7 DVD. Is x86 versions works on a x64 HostOS ?
Quote from: ChrisR on April 01, 2011, 12:06:19 PMI still have the issue with unmount and explorer whatever the tool used WimUtil, Imagex or Dism It works fine if I close any explorer.I can't reliably reproduce this. one time I had an issue and I ran dism /Cleanup-wim and haven't seen the problem since.
x86 works on x64 HostOS but you must use a 32bit wimgapi.dll (dllcall uses different int types for 32/64) personally i made a winbuilder script that extracts the needed files with 7zip.
I have every time as soon as explorer is open on my x64 Hostos (With or Without AV),Which causes an error message at the end. To see google I'm not the only !!!What about the idea, If the folder is empty after unmount then delete/re-creation and no error.
Good if x86 works on x64 hostOS . in the other way on a x86 HostOS we must extract the files from SysWOW64. I was also thinking to do this script but if you've already and want to share it.
I figured out how to reproduce.
great work indeed, congradulations I feel my dream of not using any service (wimfltr , wimmount etc) to build a pe2/3 coming true slowly.
The problem is not in Wimutil, it is the same thing with imagex or dism. It is linked to wimgapi(6.1)/wimmount.sys.
"WimUtil.exe x86" always gives "No drivers could be found." error, and never works."WimUtil.exe x64" do not give such error,
WimUtil.exe Extract "D:\1\boot.wim" 2 D:\1\ExtractTest==> give "Syntax Error: Not enough arguments."
WimUtil.exe Capture "D:\1\FilesInside" D:\1\Test.wim "Test" ==> give "Syntax Error: Not enough arguments."
check for driver files is currently on program startup.
WimUtil.exe Capture "D:\1\FilesInside" D:\1\Test.wim "Test" "my test wim"
..... why MS decided to scrap a perfectly good filesystem overlay for a sparse filesystem I will never understand. :(
it would be nice to add wimgapi.dll to WimUtil.exe as WimUtil feature on next version, without requiring WimUtil.ini , and priority to wimgapi.dll if exists on wimutil.exe folder,this way it would be easier to test wimgapi.dll versions and easier script writing......
the description is mandatory at the moment. also I have the wrong argument count being check for, (6 instead of 5) so you will need to use a compression flag for testing until i get a new test version released. (new version will have /xpress by default if no compression option supplied)
WimUtil.exe extractIs it possible to make the filename in destination_path not mandatory, just the folder path (it would be, in this case, identical to the filename image)domage that we can not retrieve the entire image or a folder !
Yes, I think also and, No need to write wimutil.ini [WimUtil] wimgapi.dll=wimgapi.dll
Is it possible to have the flags capture, extract, info, mount, unmount like other flags with "/"and like imagex, it would be easier for understanding and for scripts writing.
WimUtil.exe extractIs it possible to make the filename in destination_path not mandatory, just the folder path (it would be, in this case, identical to the filename image)
changed. wimutil will 1st look in the current dir for wimgapi.dll UNLESS wimutil.ini specifies a path.
does anyone else have a comment on how the command line should be structured?should I switch to using /mount and /MountDir: syntax like dism???
WimUtil.exe extractIs it possible to make the filename in destination_path not mandatory, just the folder path (it would be, in this case, identical to the filename image)what I meant, is to make the filename Optional in desination_path (just the filename) and in this case, use the filename of the image_path. This is not a priority.
I have a problem on the extraction with (log attached : Error Failed to extract from image. Make sure your path exist (0,0,0))E:\WimUtil\x64\WimUtil.exe extract E:\WimUtil\Wim\Test.wim 1 Driverx64\wimgapi.dll E:\WimUtil\extract\wimgapi.dllThe same command line with version 3.0.0 works well.
I think there is a misunderstanding about wimgapi.dll,The idea is to use the one of the current folder if exists and otherwise to use the one from @SystemDir (do not remove it please). Unless the path to wimgapi.dll is indicated in wimutil.ini
It seems well to harmonize all flags /hide, /ini, /boot, ... and therefore have /mount, /unmount, /capture, ... which are flags for me.It's just cosmetic and just my opinion but I think good for wimutil.
minor thingWimUtil.exe Capture "D:\1\FilesInside" D:\1\Test.wim "Test" /xpressworksWimUtil.exe Capture "D:\1\FilesInside" D:\1\Test.wim "Test"not;).
Several trials successfully (Win7 x86/x64 SP1) using WimUtil and the new package I have, by cons, some problems with Wimfltr and Wimgapi6.0 (Mount Error: (0,0,2).
I finished developments (at last awaiting for amendment and validation) of Win7PE SE for use also with Win7 SP1 as source CD and of course WimUtil.See topics Win7PE SE things.
New version ready!- Fixed required # cmd line args for capture- Changed search order for wimgapi.dll. Program will 1st look for wimutil.ini, if not specified then in @scriptDir, if not exist then look in @SystemDir.- Extract syntax change. requires a directory path to extract instead of a directory and file name path. the old method is no longer supported. if you want to rename the file after extraction do so manually.- Extract will now create the destination directory if it does not exist.- WimUtil.ini now accepts paths relative to @ScriptDir- Commands are now prefixed with /- Some tweaks to [Info] section in .ini output.
I finished developments (at last awaiting for amendment and validation) of Win7PE SE for use also with Win7 SP1 as source CD and of course WimUtil.