Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About computerguru

  • Birthday 01/16/1992

Contact Methods

  • MSN

Profile Information

  • OS
    Windows 7 x86
  1. working on win 7 hal

  2. Nice guide CalBoy, this helps a lot installing apps which mayn't be installed at audit mode. Just a recommendation, if you use WinInstall LE to capture your installation routine, use a fresh, untouched windows 7 as reference OS, I mean if your OS already includes .netfx, ms visual C ++ redistributable, updated directx, the app simply overlooks installing them, but when to use those msi's on a win 7 which doesn't include them, then the apps may not work properly. @CalBoy you may also include something about WPI (Windows Post Installlation), or simply creating a autoplay menu, which let the user
  3. Now I am describing the core part. As this part covers custom setup environment, there a plenty of platforms avaliable. All these called as preinstallation environment or PE. Famous of them are BartPE, Windows Live CD, Norton GHOST, Farstone recovery console, Windows PE. Among of them WinPE seems to me as much more useful than the others, THOUGH MY EXPERIENCE SAYS THAT NORTON GHOST IS THE FASTEST OF ALL. But winpe at the same time can provide a huge of functionality we needed. WinPE is an operating environment but it just contains a command prompt by default, where X:\ refers to the %systemro
  4. Thanks a lot calBoy for your interest. Offcourse as I said knowledge and happiness increases by sharing, so don't mind posting a guide here. You're appreciated forever.
  5. So, thanks to everyone who read, practised, advised on this topic, finally I want to start the second part of my guide. Not that knowledge and hapiness increased & sorrows dicreased by sharing, so if any one have any useful correction, do this without any hesitation. I try to cover my guide in two parts 1. VHD boot method (simpler to those who pratised a lot, have many useful features like no limitation of wim file size, very fast and secure but NOT SO GOOD METHOD TO END USER). I'll explain this method later (though its recommended for the experienced user). 2. Custom setup environment met
  6. Thanks yesnovato, you shouldn't be worried about the deletion process if you follow my method, if you use firtlogoncommands method then execute your clean.cmd as the last command, so tweak2.reg then looks like Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce] "Final"="regedit /s C:\\Windows\\setup\\scripts\\tweak1.reg" ;you may put your another entries here. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce] "Final9"="C:\\Windows\\setup\\scripts\\clean.cmd" clean.cmd will be executed at your first logon, setupc
  7. Hello CalBoy, you can restar ur pc before syspreped and Daemon will continue, after that u can syspreped ur image. I hope that helps, good luck Yesnovato No no, sorry i didn't explain it correctly. Its not the installation thats the problem. Daemon tools installs fine in audit mode, but after its installed and i take the image of the drive. When its being installed it has trouble. I'll take a screen shot when I have a moment and show you what i mean. Thanks Calboy @ CalBoy, thanks for the suggetion, I'll add it shortly. Also thanks a lot for mentioning Daemon tools, it helps me a looooooot u
  8. Thanks a lot Yesnovato for testing & posting your results. But YOU TOTALLY MISUNDERSTOOD MY POST ABOUT HKCU REG ENTRIES. You called your tweaks1.reg to be merged via setupcomplete.cmd, which included HKCU entries. You was totally wrong, you have to call it to be merged via RunOnce (which you know as FirstLogonCommands) not from setupcomplete.cmd. Setupcomplete.cmd just puts a runonce (firstlogoncommand) entry to merge it which may be : regedit /s "%systemroot%\setup\scripts\tweak2.reg" put this line into your setupcomplete.cmd, and then create a .reg file with the entries below; Windo
  9. Would you mind posting how you make the image (via winPE or from desktop using WAIK), also provide your imagex command. There may be another possibility, from the image you provided it seems to me that D:\ is your DVD drive (make me sure, was I right or wrong), your DVD may be corrupted. As windows setup displays this type of error message when- 1. The install.wim file can't be found in %installationmedia%\sources location (make right if you name your image file install.wim, recheck it). 2. Your install.wim file is corrupted (to check whether it is corrupted or not, just run setup from your de
  10. Hello Computerguru The same problem, now i test with my x64 tweaks, it doesn't work and I get the $windows-bt and $windows-ls at C:\ i dont know what is the problem, I follow the tutotial. Please could you help me. Thank in advance @ Yesnovato, you MUST check the generalize checkbox, otherwise your installation traces, and the $windows-bt and $windows-ls at C:\ won't be removed. Make it right and let me no if it works. for tweaks, just use a registry file instead of tweaks.reg, which previously worked with your x64 machine, it will helpful to determine which part isn't working, tweaks.reg or
  11. You are right in one point, really there are no text mode in windows 7 installation routine. But about hardware independent setup, the file setup.exe is totally dependent on halacpi.dll( checked through dependency walker), and whenever windows setup runs, it modifies the file according to machines hardware configuration. And about what is happening during setup, I planned to post the procedure in the 2nd part of my guide, but for ONLY your case you can run procmon (a freeware process monitoring utility) during setup. Just copy the file to boot.wim, index no.1 %mountlocation%\windows\system32\p
  12. Actually you might have some mistakes yesnovato. 1st I've experimented the method, and in my case the folder c:\windows\setup\scripts was deleted (the 'rd' command removed the directory). But I think you were wrong because you had C:\$windows-LS and C:\windows-BT, as if you performed a fresh installation (from any bootable media) then there SHOULDN'T these folders (they had been created for temporary purpose, when you run setup from your desktop). For 2) I'm thinkinng about it, but just a question, do you applied my provided tweaks.reg( they only works with 32 bit os), or your own?
  13. Your question isn't so clear dude. If you wanted to mean 'keys' as 'product keys', obviously they won't be wiped out. If you wanted to mean application settings (office customization including options whether to download product updates or not), then just follow the method I previously posted. Reply if it can help you. @Yesnovato, what about you? Did you face any problems understanding?
  14. Hey thanks for the quick answer! Yeah i have a genuine product key so thats fine. What else with the generalize setting do? Also when i run sysprep with the generalize will it wipe all of my application settings? As a few of my applications i setup before hand therefore not having to do it everytime i install windows. I have to install windows across quite a few computers as i take care of multiple computers on a site, so i dont want to have to put the applications settings in for every computer. I've looked into WinPE but I would like to see if this method would be any quicker. Thanks in adva
  15. There is just a one question; do you have a genuine windows 7 product key? If your answer is yes then offcourse you can run windows update during sysprep. Windows update just requires your windows 7 product key to be genuine and also requires it to be activated, you can then run windows update. Don't worry about your product key, it won't be stolen. When you run sysprep and also select the generalize checkbox, all traces of your activation will be removed at sysprep DTC cleanup stage. Also your SID (which uniquely identifies your machine) will be removed. But if your answer is no, then you hav
  • Create New...