JFX Posted April 20, 2012 Author Share Posted April 20, 2012 (edited) Update: Version 2.2.1.1- fixed command line -drivers not worked in some cases (Thanks Atari800XL)- fixed command line -NT5/-NT6 not standalone (Thanks IceBlackIce)- fixed command line -RunAfter not works with relative path (Thanks IceBlackIce)- fixed some bugs with the ISO file option (Thanks Lancelot)- fixed Windows 7 N and KN versions were not accepted for nativeVHDBoot- fixed GUI respond a bit slow in last versions- added bootmenu now contains edition name and VHD mark- added log file now contains details of successfull and failed driver integrations (Win7 only) Edited March 9, 2013 by JFX Link to comment Share on other sites More sharing options...
IceBlackIce Posted April 20, 2012 Share Posted April 20, 2012 I think there's an issue with the RunAfter command, when running from winpe i must specify the full path of the command, even if the file is in the same folder as winntsetup. Link to comment Share on other sites More sharing options...
JFX Posted April 21, 2012 Author Share Posted April 21, 2012 (edited) Thanks, have fixed this.Btw: You will need to add leading and trailing quotes if the command includes spaces.-RunAfter:"myprogram.exe parameter 1 parameter 2 parameter n"RunAfter will now also add infos to log file. Edited March 9, 2013 by JFX Link to comment Share on other sites More sharing options...
IceBlackIce Posted April 23, 2012 Share Posted April 23, 2012 I just tested the ThinPC installation and it was successful.One more issue, when installing windows7, from what I understand the program applies the selected image to the disk right? I tested with one that had applied a different language (and installs fine when running from the setup) and it doesnt work using WinNTSetup, it crashes after the first reboot (when installing devices) Link to comment Share on other sites More sharing options...
JFX Posted April 23, 2012 Author Share Posted April 23, 2012 (edited) One more issue, when installing windows7, from what I understand the program applies the selected image to the disk right?Yes, it applies the WIM file and setup bootmgr and the \Boot\BCD store I tested with one that had applied a different language (and installs fine when running from the setup) and it doesnt work using WinNTSetup, it crashes after the first reboot (when installing devices)Not sure want happened there. How was that image created? Edited March 9, 2013 by JFX Link to comment Share on other sites More sharing options...
IceBlackIce Posted April 23, 2012 Share Posted April 23, 2012 It was a vanilla image with a dism command adding a language package. Link to comment Share on other sites More sharing options...
JFX Posted April 23, 2012 Author Share Posted April 23, 2012 (edited) Need more infos, simple /Add-Package for langpack works alright for me.Did you used /Set-UILang, /Set-UILangFallback, /Set-Syslocale, /Set-UserLocale, /Set-InputLocale, /Set-AllIntl, /Set-SKUIntlDefaults, /Set-SetupUILang ?Why are there so many possibilities anyway Edited April 23, 2012 by JFX Link to comment Share on other sites More sharing options...
IceBlackIce Posted April 24, 2012 Share Posted April 24, 2012 (edited) This was the command to insert the language pack into the wim fileDism /image:%systemdrive%\work /add-package /LogPath:AddPackage.log /packagepath:win7_x86_en.cabThis is the info of the index I was trying to install with Winntsetup ... <IMAGE INDEX="3"> <DIRCOUNT>11677</DIRCOUNT> <FILECOUNT>57208</FILECOUNT> <TOTALBYTES>8853805585</TOTALBYTES> <CREATIONTIME> <HIGHPART>0x01CB8901</HIGHPART> <LOWPART>0xEF63352E</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01CCF24D</HIGHPART> <LOWPART>0x85A2AD04</LOWPART> </LASTMODIFICATIONTIME> <WINDOWS> <ARCH>0</ARCH> <PRODUCTNAME>Sistema operativo Microsoft® Windows®</PRODUCTNAME> <EDITIONID>HomePremium</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <HAL>acpiapic</HAL> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>en-US</LANGUAGE> <LANGUAGE>pt-PT</LANGUAGE> <DEFAULT>pt-PT</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>6</MAJOR> <MINOR>1</MINOR> <BUILD>7601</BUILD> <SPBUILD>17514</SPBUILD> <SPLEVEL>1</SPLEVEL> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 7 HOMEPREMIUM</NAME> <DESCRIPTION>Windows 7 HOMEPREMIUM</DESCRIPTION> <FLAGS>HomePremium</FLAGS> <HARDLINKBYTES>3557736550</HARDLINKBYTES> <DISPLAYNAME>Windows 7 Home Premium</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 7 Home Premium</DISPLAYDESCRIPTION> </IMAGE>I also have the lang.ini in the sources folder, but I dont believe Winntsetup cares for it.I cant test it another time atm or see the exact details of the crash... but if I had to guess I would say its because I didnt use an english image and added the portuguese language, but did the other way around and somehow that messes up something when trying to apply that image instead of installing it.-edit-Since I couldnt try again, i've made some digging and found this:http://technet.microsoft.com/en-us/library/dd799255%28WS.10%29.aspxImportantYou can use the default image file (Install.wim) included with the Windows product DVD only with Windows Setup (Setup.exe). Do not deploy this default image directly using ImageX.That could explain it =) Edited April 24, 2012 by IceBlackIce Link to comment Share on other sites More sharing options...
JFX Posted April 24, 2012 Author Share Posted April 24, 2012 (edited) Thanks for the infos.Indeed Winntsetup doesn't use language.ini it only get information form the image index xml you posted.It actually don't touch any language settings, besides setting the received language in the BCD store.Well i tried a few different language packs on my german install.wim file and had no problem.I have no idea's what could be the cause here ...ImportantYou can use the default image file (Install.wim) included with the Windows product DVD only with Windows Setup (Setup.exe). Do not deploy this default image directly using ImageX.That could explain it =)hmm maybe, thought that's actually what I did with WinNTSetup very often with no problem Edited April 24, 2012 by JFX Link to comment Share on other sites More sharing options...
trashy Posted May 1, 2012 Share Posted May 1, 2012 I've been using winntsetup for a while with great results.New problem when installing Win7 or Vista.Mount Installation drive as,option is unavailable.Tried v2.1 with same results.I'm puzzled never had this happen before.Tried from inside xp win7 and pe with same results. Link to comment Share on other sites More sharing options...
steve6375 Posted May 1, 2012 Share Posted May 1, 2012 (edited) HiI decided to test this by booting to a vanilla WinPE v3 ISO (ver 6.1.7077) from a USB flash drive and the trying to use R-Click to mount an XP ISO - but nothing seems to happen after I select the ISO from the file dialogue window and click Open.I also tried running imdiskinst.exe and got a 'can't start because crtdll.dll is missing' message.Is WinPE v3 not supported?P.S. When installing Win 7 to VHD you say- requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as SourceWhy not 7 HP or Pro? What is the restriction? Edited May 1, 2012 by steve6375 Link to comment Share on other sites More sharing options...
JFX Posted May 1, 2012 Author Share Posted May 1, 2012 (edited) I've been using winntsetup for a while with great results.New problem when installing Win7 or Vista.Mount Installation drive as,option is unavailable.Tried v2.1 with same results.I'm puzzled never had this happen before.Tried from inside xp win7 and pe with same results.This option is not supported for Vista installations, but for Windows 7 and later it should be avalible.I'll take a look at it.HiI decided to test this by booting to a vanilla WinPE v3 ISO (ver 6.1.7077) from a USB flash drive and the trying to use R-Click to mount an XP ISO - but nothing seems to happen after I select the ISO from the file dialogue window and click Open.I also tried running imdiskinst.exe and got a 'can't start because crtdll.dll is missing' message.Is WinPE v3 not supported?Yes all versions of WinPE are supported.This seem to be a problem of the imdisk installer. You could add crtdll.dll from an x86 Windows 7 in the same folder as imdiskinst.exe or unpack it with 7zip and run install.cmd manually.Seems Olaf has ruined the silent install anyway with that msgbox pop up.I'll make 2 new install packages to fix this and also add support for vanilla x64 Winpe. P.S. When installing Win 7 to VHD you say- requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as SourceWhy not 7 HP or Pro? What is the restriction?All Windows 7 versions would support VHD booting, but it's a license restriction.During logon there is a check made for Kernel-NativeVHDBoot, think through SLGetWindowsInformationDWORD.You would get an error and stuck on logon screen, if you use a lower edition than Ultimate.I proplery could fix that , but some people would have a problem with this. Edited March 9, 2013 by JFX Link to comment Share on other sites More sharing options...
trashy Posted May 1, 2012 Share Posted May 1, 2012 Thank you very much for the reply.It was Vista (of course) works fine for Win7. Any options to manualy set as C.If it's not an easy answer,don't put yourself out (Vista's a pain).Love the new v2.2. I'm stuck on XP and it works perfect. I use both nLite and RVM_Integratorto tweak my installations. WinNTSetup The best hands down!Thanks again. Link to comment Share on other sites More sharing options...
JFX Posted May 2, 2012 Author Share Posted May 2, 2012 (edited) Sadly Vista is very limited in offline servicing.The only way to change the drive letter of vista installations would be to use the normal setup.exe.And creating a new sysprep image. Edited March 9, 2013 by JFX Link to comment Share on other sites More sharing options...
JFX Posted May 16, 2012 Author Share Posted May 16, 2012 (edited) I'll make 2 new install packages to fix this and also add support for vanilla x64 Winpe. A bit late, but here are 2 new imdisk installer that works (silently) in all WinPE.Also linking to new Alpha version, as there won't be any new version in the near future ...This version has a lot of rewritten code and was not tested fully.If someone noticed bugs or even mange to crash it, please report. Edited March 9, 2013 by JFX Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now