is it possible to Keep the Image mounted in next release ? for every Task mounting and unmounting takes a lot of time.
Ya I know, for that we need to choose the source image at first place itself, but some operations do have to unmounts in between so that's why I made the toolkit in that way and also if you want to unmount the image at last then I have to remove the option to re-build wim image at every operations. am just working on how to use the toolkit with multiple wim indexes and also multiple operations, once it gets fixed I will push the input source wim selection to the first place and the output/rebuild to the last part of the toolkit before the make iso operations. am also planning to include a WIM Manager option to perform wim operations. there's also other option like you can mount the wim at first place and just do the save/nosave method in between and perform the unmount wim operation at the last part. will see how it can be implemented.
Hi Guys, You don't know me, but I've been around for years. I do informal software testing on my own. When I discovered the toolkit the other day, I thought it was the answer to my problems. I have been having issues with the GA Updates section. It will update the Pro image successfully, but then it shows unmounting errors late in the process of updating the Core image. It would be nice to accomodate both. Also, the option to write the ISO image choosing both BIOS and UEFI boot, generates an unboootable disc image. The screen shows error: Can't find Bootmgr. It would be great if these bugs were fixed. Thanks.....
Thanks for try the toolkit, I will check with the core image. can you provide the screenshot of the error you get when you try to integrate GA updates to core image. Then about the iso image, I have used the UDF ver as 2.00 may be that's the problem will check out and correct it. well I don't have uefi system to verify whether the iso image created with uefi boot is working or not, so if anyone try out and let me know if its working or not.
Hi, Thanks for the quick respose. I will try it later and get a screenshot. I was able to successfully integrate .NET 3.5 into both images with no problem. After this I was trying to integrate GA updates first into Pro, then Core. As far as booting goes, I was using VMWare Workstation 10.01 to host the 8.1 install. I think maybe it is necessary to have some way of capturing the original boot image from the source disc so it can be used in the destination. Later.....
You are using the toolkit within the windows user profile folder and are you using the Windows 8.1 with UAC Enabled, from the screenshots, I can say the mount folder is still in use by some other programs, though I have added a pre-cleanup for every process of toolkit, still in the windows 8.x the deletion of the files won't happens properly always. some times it leaves certain files/folders, we have to again delete those files/folders. can you move the toolkit to other either c:\ or any other drive and tryout once again. if that doesn't work then when you integrate ga to pro do quit the toolkit and again run it and try to integrate the ga to core version and see whether the same error appears or not.
Hi, You were right! I moved the toolkit folder to the root C: directory, and everything worked after that. I don't know of anything else out there that can do what your program does. Fantastic! I used Win Toolkit 1.4.29 to help generate the bootable ISO image. The only thing I can think of that would be helpful, would be some way of downloading the standard app updates, and integrating those. That would be nice! Well, So Far So Good Thanks
Hope the toolkit is working fine and about the generating bootable iso image I have check with bios type it works but for uefi can someone with uefi system do check out whether its working or not. I have used the right parameters or generating the iso but still need to know what's going wrong. About the Updated Apps, sorry I can't do anything for that coz although there is option for integrating custom apps to install.wim but still it requires the apps to be in a apps package file along with it requires some kind of key/certificate to work.
My Laptop runs UEFI in Legacy BIOS mode for Windows 7, I would have to change too many things to test it out. I have an idea though. Maybe you could test out Win Toolkit v1.4.30. This might give some leads, or even talk to the guy who keeps updating it. He's over at WinCert.net. Many times I need to use different tools to arrive at the best result. I'm going to try to integrate the games pack next, I'll let you know how it goes. I sure do appreciate your efforts, and support, though. Thanks
I know about WinToolkit,The WinTookit uses the cdimage.exe instead of oscdimg.exe and also it uses a custom bios.com and UEFI.bin instead of the etfsboot.com and efisys.bin for making a iso image. here is the difference b/w WinToolKit and MSMG ToolKit Code: "cdimage.exe" -L"DVD" -m -o -u2 -udfver102 -h -b"BIOS.com" "C:\MSMG\DVD" "C:\MSMG\ISO\W81.iso" "cdimage.exe" -L"DVD" -m -o -u2 -udfver102 -h -b"UEFI.bin" -pEF "C:\MSMG\DVD" "C:\MSMG\ISO\W81.iso" "cdimage.exe" -L"DVD" -m -o -u2 -udfver102 -h -bootdata:2#p0,e,b"BIOS.com"#pEF,e,b"UEFI.bin" "C:\MSMG\DVD" "C:\MSMG\ISO\W81.iso" Code: Oscdimg.exe -h -m -o -u2 -betfsboot.com -lW81 C:\MSMG\DVD C:\MSMG\ISO\W81.ISO Oscdimg.exe -h -m -o -u2 -udfver200 -bootdata:1pEF,e,befisys.bin -lW81 C:\MSMG\DVD C:\MSMG\ISO\W81.ISO Oscdimg.exe -h -m -o -u2 -udfver200 -bootdata:2#p0,e,betfsboot.com#pEF,e,befisys.bin -lW81 C:\MSMG\DVD C:\MSMG\ISO\W81.ISO I do use etfsboot.com and efisys.bin from WADK 8.1 Tools and UDF Version 2.00
Hi, I guess I've seen more use of Cdimage, because of its ability to optimize multiple similar images in a single ISO. This may have been more practical in the 2000/XP eras. Oscdimg, according to Microsoft is designed for WIN PE. There is a site called windowsvalley.com that describes how to make a bootable Windows 8 ISO The code looks similar to yours. The custom files you mentioned probably belong to the author of Win Toolkit, I imagine. The Game Pack is excellent, very nice work there.
The issue is not with the cdimage.exe or oscdimg.exe coz both can be used for producing a iso for microsoft os products. the oscdimg.exe is the extension of cdimage.exe. the problem is with the bootloader and the switches used for producing the iso. i have read in some other forums that eftsboot.com cannot be recognized by some dvd burning software's. soon will be fixing these issues.
Please don't use the feature - integrate terminal server patch as i just found out the registry is not getting applied to HKEY_LOCAL_MACHINE\SYSTEM instead it's pointing to HKEY_LOCAL_MACHINE\SOFTWARE. I tried correcting the path but when the HKEY_LOCAL_MACHINE\SYSTEM is used the windows installation breaks. so i will try fixing it in the next version of toolkit. the next version of toolkit will be released bit late as am re-designing the toolkit interface completely.
msmg, I just check ur tool when convert the pro version into prowmc, it add ei.cfg which make the edition turn to prowmc vl, may I know why? dont u think it should be retail not vl? (please correct me if I'm wrong or someone else have posted).this ei.cfg made by ur toolkit : Code: [EditionID] ProfessionalWMC [Channel] Retail [VL] 1 or the purposed to work with kms tool that provided by member here?
Yes at first my toolkit's wmc integration was aimed at converting pro to prowmc only iso and so I had put ei.cfg and later people asked for choosing the index number for their windows 8.1 aio source but I just left the ei.cfg so that people who want to leave the prowmc as the default image to be selected while installing the os. if people use other indexes also they can remove the ei.cfg config or modify it according to their needs. Now about the VL option, yes the prowmc is retail only iso and the ei.cfg the toolkit is writing is correct. the microsoft's default syntax for ei.cfg cofnig file is Code: [EditionID] {Edition ID} [Channel] {Channel Type} [VL] {Volume License} where {Edition ID} must be a valid Windows edition ID; {Channel Type} must be either "OEM" or "Retail"; and {Volume License} must be either 1, if this is a volume license, or 0, if this is not a volume license. For example: Code: [EditionID] SKU [Channel] OEM [VL] 0 The SKU decides the Product Edition E.g. Professional, ProfessionalWMC, Enterprise The Channel decides whether it's OEM or Retail Version and the VL decides whether it's Volume or Not So the VL will be there for every type of os be it Retail or OEM or Volume and the value of VL will be 1 for Volume and 0 for Non-Volume I have used the VL with both 0 and 1 for ProWMC both works without any problem.
msmg, just a suggestion, instead directly unmount after adding some feature/custom pack, why not add option so we can still mount the image and do another task (an example if I have add WinToGo to the wim image, then I want to add Games, instead unmount then mount back the wim image, u could add option still mounting AS LONG the wim image is the same (an example install.wim index 1) well, u can add list work to do inside the toolkit (just a suggestion by the way, and also will save time instead go back to the menu, choose what we wanna do, mount image, add feature, unmount, go back again to the menu and again and again).
Yes, am just re-designing the whole process, I do have two options in mind 1) As a First point is to offer a Select Source Menu to select the source index/indexes to service and at the end provide a Select Target Menu to Save & Re-Build Image index/indexes with an option to export Image to .ESD Format or 2) At the end of every process ask whether to un-mount the image or not. other than this the toolkit features am adding to it are also a issue, some like data-deduplication feature only can be used for x64 version of windows 8.1, wmc can only be added for windows 8.1 professional retail version and dart 8.1 for only boot.wim/winre.wim so I have to keep in mind that too how to include those if I want to keep the image in mounted state till the last process. One more problem am facing is the importing of registry keys, some keys do work properly when imported to wim but some keys do break the installation process itself. As this toolkit is a dos batch script based it has a lot of limitation when compared to a Windows GUI based. will see how best the toolkit can be made more user friendly and functional.