Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


Everything posted by chon_

  1. HI HAs anyone succesfully accomplished this task? I tried a lot of times, I always get the following error: Error in: C:\WINDOWS\SYSTEM32\iedkcs32.dll Entry Missing: BrandIEActiveSetupAnd it won't install, tried everythng, i don't know what to do next....
  2. you need a reboot between IE7 and kb947864
  3. @Atheros Trying it now, in pass 7... I'll let you know
  4. Thanks regarding the CMDOW tool, I don't like it that much, so does my antivirus and prevents it form running, hence, it causes an error Thanks for the MSIEXEC /I tip maxXPsoft, I'll try it tonight BTW, I noticed that the error occurs only when the command line has spaces, for example, the following line does NOT cuase any trouble: %CDROM%\Install\nero\INSTALL.CMDbut, as you can see it has no spaces in it, in the other hand, the following line DOES cuase a problem: :%CDROM%\Install\Office2007\setup.exe /adminfile CUSTOM.MSPnote the blank space between setup.exe and /adminfile and between adminfile and custom.msp.
  5. I need to create a new user named Propietario with WSIM that is a member of the Administrators group and set it to autologon (in order to hide te Adminstrator account) after I installed my apps in Pass 6 Audit User. I've been messing around with it but I can`t get it to work What can I do??? The way I did it in XP was running the following CMD file: net user Propietario /add net localgroup Administradores Propietario /add net accounts /maxpwage:unlimited reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "DefaultUserName" /d "Propietario" /f reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "DefaultPassword" /d "" /f rem reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "AutoAdminLogon" /d "1" /fThis worked OK in XP, but seems like it doesn't work in vista (I've been running this cmd file in Pass 6 too). Thanks in advance
  6. I've been following FireGeier's guide to unattended vista (it's awesome BTW, congrats! ), everything works OK, but I have a doubt: in his guide he mentions that the Synchronous Commands in Pass 6 auditUser must have the comand CMD/ C (wich calls vista's command line interpreter) preceding the actual command for installing the application; for example: cmd /c %AppsRoot%\Install\AcrRead\AcroRead.msi /qb I tried to install some apps without the CMD /C instruction but the setup fails and quits. If I use the CMD /C command everything works OK. The only problem is that CMD /C opens (of course) a black command window, which I don't like. Is there any way to avoid CMD /C in the syntax? This issue is merely cosmetic, as I said, everything works fine, but I don't like black command windows open.
  7. removable media (USB, Floppy), root of your DVD (n that order)
  8. I got spanish version DVDs, that's why my installations are in spanish, it is not multilanguage (although it can be done the same way, you just need the .WIM files for each language)
  9. @gjs1992 ENTERPRISE version of vista is NOT included in the retail or OEM DVDs, as it's a "special" version sold only via specific channels to enterprise customers. That's why you won't find this version in a "standard" DVD; hence it has no corresponding numer in the WIM image. In fact, if you want to add this version to your proyect, you'll need two DVDs: one "standard" DVD, and the enterprise DVD, this will leave you with two WIM file to work with
  10. @orbit30 sorry, my mistake There's an "extra" space in the code line, is now corrected, the correct syntax should be: oscdimg -n -bD:\VistaAIO\distribucion\boot\etfsboot.com D:\VistaAIO\distribucion D:\VISTA_AIO.iso -m Sorry for the inconvinience
  11. @batson0974 Yes, the procedure is correct. All the files needed for setup are inside the .WIM files, remember that WIM stands for Windows Imaging Format, this is why you only need this file. So, if you export from your x86 install.WIM file, you're exporting all the files needed for the x86 setup. In the other hand, if you export from your install.wim file located in your x64 DVD, you are exporting the x64 needed files. As for the other files on the DVD, (like boot sector, etc) are common in both DVDs. Remember: what we're doing here is exporting from two image files(x86 and x64 Install.wim) to only one "big" install.wim file.
  12. Well, seeing how little information is around in the net about this topic and seeing there's some interest in this topic I decided to write this little guide to accomplish this task. Hope it helps. chon's guide to Windows Vista x86 and x64 Versions in one DVD NOTE: I'll be using my x64 and x86 MSDN DVDs, you can use the ones you have (retail, etc.), the procedure is the same. 1. Please download and install the Windows Automated Installation Kit (AIK) from here 2. Please create a working folder with a structure similar to this. Obviously you can change folder names according to your needs In this case, i'll be using the following folder: D:\VistaAIO. My folder structure is as follows: 3. Now, copy all the contents of your x86 DVD to the distribuition folder, in this case D:\VistaAIO\Distribucion 4. Move the file named “install.wim†from D:\VistaAIO\Distribucion\Sources to D:\VistaAIO\x86 5. Copy the file named “install.wim†from the Sources folder of your x64 DVD to the folder D:\VistaAIO\x64 6. Delete al .clg files from your distribution folder (D:\VistaAIO\Distribucion) 7. Now, with admin rights, open the Windows PE Tools Command prompt (click in Start/All programs/Microsoft Windows AIK) 8. We change directory to our working folder: CD D:\VistaAIO\Distribucion\Sources 9. OK, here's the tricky part. We are now about to export the images of each windows version to a single .WIM image file. The command to do this is IMAGEX.EXE. The syntax is as follows: imagex /export SourceImageToExport.wim SourceNumber DestinationImageFile.wim "Name of the Operating System" For example: imagex /export D:\VistaAIO\x86\install.wim 1 .\install.wim "Windows Vista Business x86" imagex /export D:\VistaAIO\x64\install.wim 1 .\install.wim "Windows Vista Business x64" This is what the first line of code does: export Version 1 of the source image file named Install.wim located in the folder D:\VistaAIO\x86 to the destination image file named Install.wim located in D:\VistaAIO\Distribucion. The number 1 corresponds to the Business edition of Windows, take a look at the following table, for the SourceNumber and its corresponding Windows Edition: Number Windows Edition 1 Business 2 Home Basic 3 Home Premium 4 Ultimate 5 Home Basic N 6 Business N 7 Starter Thus, for example if we wanted to add the 64bit Ultimate version of Windows Vista to our newly created image we type the following command: imagex /export D:\VistaAIO\x64\install.wim 4 .\install.wim "Windows Vista Ultimate x64" Please note that we only changed the number 1 for the number 4 (wich corresponds to the Ultimate version) and the name we give to the Windows Edition, for this name you can type whatever you coinsider a descriptive name of the windows version, everything else in the syntax remains the same. You can add as many Windows Editions as you want this way. If you have any doubts regarding the imagex command, you can type the following line in the command prompt at any time: imagex /export /? 10. Now that we've created our .WIM image file, let's create our ISO image file to make it ready to burn it to a DVD. To do this, still in the Windows PE Tools command prompt window, we type: oscdimg -n -bD:\VistaAIO\distribucion\boot\etfsboot.com D:\VistaAIO\distribucion D:\VISTA_AIO.iso -m This will create an ISO file named VISTA_AIO.iso in D:\ 11. We're almost done! We can now burn this image with our favorite burning software (Nero, alcohol. Etc). The final result when installing Vista, should look similar to this: That's all!!! Hope you find it useful! Let me know any comments/doubts
  13. Yes, it is possible. I've posted a little guide in another forum, but it's in spanish, i'm working on the translation now, i'll post it here within today.
  14. Weird.... Indeed, i've found that IE deletes the FLAG entry for RunOnceEx2, but it does not delete the other entries (where you put the hotfixes commands), so, although it deletes the FLAG entry, it stills executes the commands. We're doing something different here. Later today I'll check your files step by step and make some tests in virtualpc with them, i'll let you know.
  15. @rajesh.kumar Attached you'll find two files, one is named New_RunOnceEx.cmd the other is New_RunOnceEx2.cmd. Please rename New_RunOnceEx.cmd to RunOnceEx.cmd and use it in your testings as your main RunOnceEx batch file. Place New_RunOnceEx2.cmd accordingly (where original RunOnceEx2.cmd resides). I think this two files will accomplish all the tasks that you're working on. These are modified versions of CMD files based on your work. Let me know how it goes NewRunOnceExesFor_rajesh.kumar.rar
  16. I found on my testings that removing that line makes te 2nd runonceex not to run, so I think it's a MUST. Anyway, let me now your findings in this issue. If you can provide your newest RunOnceEx.cmd I think we can isolate the problem. @Neo - Matrix Yes, I meant those. Sorry, I overlooked them
  17. hmmmmm..... Very very interesting work JPamplin! Looking for this for ages! I'll try it tonight Thanks
  18. @rajesh.kumar I'm very interested in your findings because i've been following the work you've done here and I think it deserves a lot of attention. Also please can you do me a favor? can you send or posts your CMD files?? I would like to take a more indepth look at them. Thanks in advance PS: another favor: please give feedback
  19. Well, today I finish my testings in this matter. As you can see everyone has its own apporach for solving this issue, and AFAIK that's what this forums are for . Using the steps I posted here (and of course with your invaluable help ), you can install IE7 en its hofixes in a very clean way. And YES it works, tested several times. Below my findings: ADVANTAGES: 1) No need of third party software (nLite, HFSLIP, etc.) to accomplish this task 2) No file manipulation in any way (no extraction/replacement/overwriting/repackaging of files and/or hotfixes) 3) No extra registry entries need to be used/modified besides RunOnceEx 4) No need of manually registering DLLs 5) Only ONE reboot required, this is absolutely necessary, you have to reboot before applying IE7's hotfixes 6) No need of a lot of CMD files (just your good old RunOnceEx.CMD and IE7_Hotfixes.CMD) 7) No further registry/files cleaning needed 8) Very clean and highly costumizable DISADVANTAGES: 1) Status "WindowsUpdate" dialog does not show up when installing the two IE7 hotfixes. Although it only takes 20-30 seconds, some people would like to see what is happening during this time. CONSIDERATIONS: 1) Install all your software, including IE7, with RunOnceEx.CMD. 2) When doing this, use this line: REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /finstead of this: REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx /V Flags /T REG_DWORD /D 0x80 /FTo add the FLAGS key to RunOnceEx. As Yzöwl Once said, it's not technically the correct syntax, but for some strange reason if you use the other syntax it does not show the status dialog, although it does execute all the commands; why? don't ask me!, I don't know, but it happens Well, i think that's all for now, please let me know any new comments/findings/doubts. And again: thanks to all of you!
  20. @Sinistrality I totally agree with you on this: There's nothing better as doing it by your own hands, needs a lot of time and testing, but I think you learn a lot more. Personally I don't like to use nLite, I used it once and it's a great tool, but then again I like to do it "the hard way" As for That's not entirely true, as a matter of fact, the first part of RunOnceEx, where you install all of your software including IE7 Still shows the status window, the only detail (which I'm dealing with right now), is that it doesn't show the status dialog when it Install the IE7 hotfixes. Although it only takes 30 seconds to install them, I would also like to see a status window I'm currently working on this, I'll post my findings within the hour regarding this matter in this same topic. Edit: hahaha I think I found the culprit!!!!!!! I think it's working 100% now, including status dialog. Doing more testing.... results very soon.....
  21. For KB873374 use this registry tweak instead: REG ADD "HKLM\SOFTWARE\Microsoft\GdiDetectionTool" /v "GDITool" /t REG_DWORD /d "00000001" /f use /quiet /norestart for KB927978 and KB891122
  22. @Neo - Matrix About the hotfixes complaining about wrong IE version, check C:\WINDOWS\ie7_main.log. IE7 may not be fully installed (if you used silent switches and IE wasn't able to validate your copy of windows it will simply quit setup). Most likeky you still have IE6 installed. I recommend to install all the software and IE7 at last, then restart and then apply IE7 hotfixes. Why? No particular reason, but I think that if IE updates a lot of critical system files you don't want them to be overwrited by other software installations As for how to do it, well, there's a looooot of documentation herein the forums, just a quick reminder: RunOnceEx.cmd: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V Flags /T REG_DWORD /D 0x80 /F REG ADD %KEY%\230 /VE /D "Internet Explorer 7.0" /f REG ADD %KEY%\230 /V 3 /D "%CDROM%\Install\IE7\IE7-WindowsXP-x86-esn.exe /quiet /passive /norestart" /f REG ADD %KEY%\230 /V 4 /D "%CDROM%\Install\Scripts\IE7_Hotfixes.cmd" /f Where IE7_Hotfixes.cmd: FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\WIN51IP.SP2 SET CDROM=%%i: REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f REG ADD %KEY%\910 /V 1 /D "%CDROM%\Install\IE7\Hotfixes\IE7-KB929969-WindowsXP-x86-esn.exe /q /n /z" /f REG ADD %KEY%\910 /V 2 /D "%CDROM%\Install\IE7\Hotfixes\IE7-KB928090-WindowsXP-x86-esn.exe /q /n /z" /f shutdown -r -f -t 180 -c "Restarting in 3minutes..."
  23. @ Kumi and rajesh.kumar Please verify the syntax of your cmd files, here's an example: Your file: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f REG ADD %KEY11 /VE /D "MS .NET Framework v1.1 SP1" /f REG ADD %KEY11 /V 1 /D "%SystemDrive%\install\MsAddons\NETFrame\NET11\netfx.exe" /f It should be: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V FLAGS /D "dword:0x00000080" /f REG ADD %KEY%\11 /VE /D "MS .NET Framework v1.1 SP1" /f REG ADD %KEY%\11 /V 1 /D "%SystemDrive%\install\MsAddons\NETFrame\NET11\netfx.exe" /f Note the missing "%" and "\" just before the 11 from your file. Line 019 from your file has the same syntax error, this line installs IE7 but is not installing it because of this, hence hotfixes are not installing on your runonceex second run. Let me know any findings.
  24. @Yzöwl Thanks for claryfing that! You are correct!
  25. Have you tried the following registry tweak: Windows Registry Editor Version 5.00 ;Remove second language (English) [HKEY_CURRENT_USER\Keyboard Layout\Preload] "2"=-

  • Create New...