FireGeier

Member
  • Content count

    405
  • Joined

  • Last visited

Community Reputation

0 Neutral

About FireGeier

  1. Hello kal! Ah... I forgot about this simple way of doing it. Than you will not have any problem usualy. Well there is no problem, if you copy a file to the target system generaly, but if you use UseConfigSet tag in Autounattend.xml, than you will have the problem described here. If you do it in an other way, than you'll have no problems - or better, you should not have. Thanks, I'll add that as a workaround, if the "simple" method should not work. Regards, Martin
  2. Hello kal! Great input and great work! That's highly appreciated! You're 100% right. It can happen like you've described, even if in very less cases only. My very first German Vista Guide was using an exe-file a member of German windows-unattended.de has written. It's called FWDT.exe and it is almost doing the same like your AppsRoot.exe. The "problem" of this exe solution is, that you have to find a way to copy the AppsRoot.exe over to the target drive to execute it. That means you've to integrate to install.wim or you have to use $OEM$ folder and UseConfigSet - what has a known issue, too. Many users found it to complicated and so I switched back to the simple method you've mentioned first. As far as I've got feedback the simple method is working in about 99% of setups. Don't missunderstand... I don't want to criticise, cause I know that your solution is the 100% perfect way of doing it and you did great work! Thanks! Regards, Martin
  3. Hello Mateus! Are you doing it like described inside my Guide here and here? If yes, than please look for a workaround here. Regards, Martin
  4. We will soon. Soon? How soon is "soon"? That message was written April 20th and it is now almost September. Come on guys I think there are many eager people (like me) who want to see your project completed instead of sticky's. There is a guide here and other helpfull projects - like this here from maxXPsoft. Or look here at nuihs vlite project. I think there are enough options on the board to get an unattended Vista setup. No one gets paid for the work here - AFAIK - so these are all free time projects... if you think a guide should be published sooner, feel free to write one. Martin
  5. Hello Dobby! Thanks, for your feedback! Yes, you're right. I've to apologise for the bad English. So any help with the grammar would be highly appreciated. Thanks, for pointing that out! Martin
  6. Why?
  7. No, there is nothing like that for Autounattend.xml and no regtweak AFAIK, too. I'm not 100% sure for the regtweak but 100% sure for Autounattend.xml. Regards, Martin
  8. Hello Wabaunza! I can't see a sysprep command to leave the audit mode inside your xml. I just see the one to enter audit mode: <RunSynchronousCommand wcm:action="add"> <Path>%WINDIR%\system32\sysprep\sysprep.exe /quiet /audit</Path> <Order>2</Order> <Description>Sysprep</Description> To leave audit mode add the following line as the last synchronous command in auditUser pass: %WINDIR%\system32\sysprep\sysprep.exe /quiet /oobe /reboot or, if you want to generalize your setup at the same time: %WINDIR%\system32\sysprep\sysprep.exe /generalize /quiet /oobe /reboot Regars, Martin
  9. Hello Ozzie! What are you trying exactly? Martin
  10. Does this mean, it don't gives you the double entries? Martin
  11. In audit user mode I got it almost to work with cmd /c in front. So in your case it should look like this: Try out and see, if it's working. And if you want to set it to the default user profile, than you need to follow the copy profile guide in addition. Martin
  12. Yeah, I agree that's right. I clean the sandbox folder, too, after the update run. But one update run means that all updates are integrated and than the sandbox will be cleared. In your case sandbox is cleared after every single hotfix. I would say that both procedures are making sense. You clear it after every single hotfix cause the next fix will be like a new integration. If you put everything together in one xml, than you don't have the option to clear the sandbox between single fixes. But you supposed to put them in one xml to get dependency checked. I like your way of integration as well, just wondering if the dependency will be checked. To me they do. Martin
  13. Hi chiners! Dejavu... look here. Or are you asking for the regkey to remove the US keyboard? Regards, Martin
  14. Ok... I understand, than that's the difference. I'm using the "xml-method" cause this was one of two procedures, where I could find something in WAIK help about dependency check. I would have prefered the method with all updates in one command line semicolon-seperated, but I never got this to work. So I ended up with the "xml-method". So it may has something to do with this dependency check? On the other hand the error came up for some guys here, too, when using peimg to integrate the hotfixes. Peimg command does not check dependency, AFAIK. Very strange... can't see any logic behind ATM... Martin
  15. Max is right, WSIM can corrupt the xml even if you don't integrate fixes. For me it happens almost when changing an Autounattend.xml that does already exist - removing an entry for example. It's not happening all the time but it can happen. Most of these corruptions don't realy matter but sometimes they do. On the other hand, that doesn't mean automatically, that slipstreaming the updates could not be a problem, too. Max do you may integrate the updates in an other way than described in WAIK help or my guide? Martin