Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Everything posted by FireGeier

  1. Hello MC! If setups does stop / fail you should have entries in the logs - setupact.log and setuperr.log in %Windir%\Panther\UnattendGC. If setup has not finished you would need any system on Media - like Bart PE or simple WinPE 2.0 to get these files from your hd. Regards, Martin
  2. Hello Yurek! Change this here inside Autounattend.xml, <Path>cmd /c ";FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppzRoot.txt SETX AppzRoot %i: -m";</Path> to: <Path>cmd /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppzRoot.txt SETX AppzRoot %i: -m"</Path> The ";" supposed not to be there. Don't know for the moment where it's comming from, but just remove it manually from your Autounattend.xml. Regards, Martin
  3. Hello jfmartel! To disable UAC during setup insert the following synchronus command into specialize pass: cmd /c reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f To enable UAC again use: cmd /c reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 1 /f Note: If you execute this last command from within a batch you don't need the cmd /c at the beginning. But to disable UAC during specialize pass without using a batch the introducing cmd /c is a must! Regards, Martin BTW, for an other way look here.
  4. Hello coucou! That was a good idea! Great work so far but I would print the whole batch files or remove them completly. For the moment it makes no sense and wasting a lot of space if you just have half of the cmd. Thanks! Martin
  5. Hello zedox! So what do you want to do? Do you want to set back the Vista installation after setup has finished - so you can a key at the end of setup? Or do you want to install full unattended without putting in any key? The latter is not possible without a prompt at the beginning, where you just click "No" to skip the product key. Or are you talking about something else? Regards, Martin
  6. Hello VATERNL! I would not recommend to use <UseConfigurationSet> tag cause it will blow up your final vista install, like described in thread urie mentioned. But you could integrate the links directly into install.wim as an option. Just mount install.wim using imagex and your ready to integrate the files or links. Regards, Martin
  7. Hello, coucou! Sorry, have been very busy the last two weeks and forgot to let you know that you could build a pdf now. The guide is not finished yet and new guide sections will be published the follwoing weeks, but I think there will not be to much changes now on the stuff published so far. Thanks & regards, Martin NOTE: This permit is grant to the member coucou only for the moment!
  8. GUIDE UPDATE: There was the wrong path to etfsboot.com file inside "Create ISO" guide AND inside create_iso.cmd: Corrected path to etfsboot.com. So changed the following two lines inside create_iso.cmd, from: IF "%VVersion%"=="x86" SET bootL=%Programfiles%\Windows AIK\Tools\PETools\x86\etfsboot.com IF "%VVersion%"=="amd64" SET bootL=%Programfiles%\Windows AIK\Tools\PETools\amd64\etfsboot.com to: IF "%VVersion%"=="x86" SET bootL=%Programfiles%\Windows AIK\Tools\PETools\x86\boot\etfsboot.com IF "%VVersion%"=="amd64" SET bootL=%Programfiles%\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com Corrected the path inside "Create ISO" guide, too, from: oscdimg -n -m -b"%Programfiles%\Windows AIK\Tools\PETools\x86\etfsboot.com" D:\VistaWork\DVD D:\VistaWork\ISO\Vistax86.iso to: oscdimg -n -m -b"%Programfiles%\Windows AIK\Tools\PETools\x86\boot\etfsboot.com" D:\VistaWork\DVD D:\VistaWork\ISO\Vistax86.iso and form: oscdimg -n -m -b"%Programfiles%\Windows AIK\Tools\PETools\amd64\etfsboot.com" D:\VistaWork\DVD D:\VistaWork\ISO\Vista64.iso to: oscdimg -n -m -b"%Programfiles%\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com" D:\VistaWork\DVD D:\VistaWork\ISO\Vista64.iso Thanks, Jesper for pointing out that mistake!!! Regards, Martin
  9. @Sgt_Strider: 1. I will finish the Windows PE guide (should be finished next weekend or a few days later) After that I will have a look at the .exe driver thing again (estimated: in about 2 weeks). Regards, Martin
  10. Hello Amit! You need to set a Description in WSIM for all these synchronous commands, than you will see the Description only instead of full path. If you don't use the description, it seems to be that setup creates one by path info. Regards, Martin
  11. You're welcome AMIT! Good to hear, that my guide isn't such bad and you got it working! It was easy, wasn't it. Regards, Martin
  12. Hello alexch! You should have a look here. Regards, Martin
  13. Hello linstead! Audit user and oobe system passes should both work. I prefere audit user pass meanwhile, cause it's easier to do a reboot. If you use audit user pass, you need to boot to audit mode using sysprep command like described in guide. Than you insert synchronous commands form insert menu and put in like the following command for example: \\servername\appsshare\Install\Firefox\Firefox_Setup_2_0_0_2.exe -ms NOET: You don't need the cmd /c here, like described inside guide. I've used cmd /c to make the AppsRoot variable usable only! Regards, Martin
  14. Well, I don't know for sure if a complete reboot is necessary and you don't have to set one. Please don't missunderstand. But system will logon to audit passes. That means from my point of view, that a new session is started and system environment is reloaded. Cause first it will run auditSystem pass and second auditUser when booting to audit mode. But I don't know everything. So might be wrong. Regards, Martin
  15. Well, can't tell for sure. But AFAIK system envrionment variables a loaded to the system environment only once - when the session starts. So if you let run the command in audit pass, than the session has already be started. SETX will set the AppzRoot variable to the registry than, but it will be present in during session after next logon. This is the reason, why I put it to specialize pass. The system will reboot, before logon to audit pass, so the session is started again and AppzRoot variable is present. Regards, Martin
  16. Hello amit! Sorry, I'm talking about that command here: cmd /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppzRoot.txt SETX AppzRoot %i: -m" Where do you put this command to? Specialize pass or audit pass? If you put it into audit pass, than please put it back to sepcialize pass. Regards, Martin
  17. Hello Amit! Have you put the FOR loop back to specialize pass? Regards, Martin
  18. That's not the problem. SETX sets it to system environment (Registry), if everything is working properly. I've always been using the SETX command during specialize pass without any probs. But amit is not the first, having problems with the command. Just can't figure out why so far, cause I've to less feedback. @amit: First remove the ";" like maxXP said. Than please make sure, to move the command back to specialize pass! If you're using SETX AppzRoot %%i: -m than your command to call the installer must look like this: cmd /c %AppzRoot%\install\Acrobat Reader\AdobeReader80.exe /sAll /rs If you're using SETX AppzRoot %%i:\ -m than you have to use b]cmd /c %AppzRoot%install\Acrobat Reader\AdobeReader80.exe /sAll /rs In your actual Autounattend.xml you're setting AppzRoot without a "\", that means it will set AppzRoot=E: for example. Than you're calling the apps installers without a "\", so your actual call looks like this for example: cmd /c E:install\Acrobat Reader\AdobeReader80.exe /sAll /rs That means there is a missing "\" and setup can't find the path. If this still should not trouble shoot it, try that: Put all the commands into one single cmd file called run.cmd for example and than let run this batch from first logon command. Use the commads without cmd /c at the beginning. Look here for more details. Could you please check if Appsroot variable is set at all. In your final Vista installation click on Start, type cmd and in the opening command prompt type: set please let me know, if you find an entry called Appsroot. Regards, Martin
  19. Hello linstead! The guide describes the procedure for installation from media, like DVD or USB-Stick/HD. If you use WDS, I guess that you're holding your apps on Server. Than just use the UNC path to point to your applications share. You don't need the %appsroot% thing than. That's just to figure out the drive letter of removable media. Regards, Martin
  20. @ jacky and maxXP: I will add a note for that, too. Thanks, Martin
  21. Hello jacky! You're right. It does work only, if you boot to audit mode using sysprep. I've explained that in Applications section. But you're rigth, would be helpfull to make a note for that in Regtweaks section, too. I will add that later. Thanks! @amit_talkin: It took about half a year - daily free time work - to write the German and English guide. Estimated 700 hours including writing, layout and testing. Thanks 'n' regards, Martin
  22. Thanks, for your feedback maxXP! Well sooner or later I'll get an OEM DVD. For the moment I'm dependent from ohters information and at least I can't verify, what kind of discs they have exactly. I will still wait a while before publishing the OEM guide than. Thanks 'n' regards, Martin
  23. @Mackhack: It's called offline_update.cmd exactly and you can find it here. Regards, Martin
  24. @spoof: Haven't tested it yet, but good to see people start acting on the idea of vista batch files and doing there own developments and improvements! BTW, is there a special reason why you use cdimage instead of ocsdimg? Good work! Regards, Martin

  • Create New...