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


Everything posted by r3loaded

  1. It's ok, I've worked out how to perform automated installs using the Config.xml file.
  2. Hey guys, just downloaded the earlier than expected Office 2010 RTM off TechNet. I wanted to create an unattended MSP file for silently installing Office onto all 6 computers in the house, but to my dismay, running setup /admin gave me the following error: "Files necessary to run the Office Customization Tool were not found. Run Setup from the installation point of a qualifying product". After a bit of googling, I've found out that unlike the beta, Microsoft have decided not to include the Admin directory in my copy of Office, meaning I can't create an unattended setup. While I still have a co
  3. Ok, I've fixed the shutdown problem by adding /quit at the end of the sysprep command (I think Microsoft changed sysprep's behaviour in SP1) and I've sorted the timezone prompt by adding it again to the oobeSystem pass. But OOBE is still prompting me for a product key after rebooting from audit mode! I know that while in audit mode, the system does have my product key specified stored and ready for activation. Why is OOBE then ignoring the stored product key?
  4. I believe they'll roll them out over the next couple of months
  5. I've got my unattend file for Vista SP1 mostly sorted out, but I am having a couple of quirks. My planned install process is to do most of the installation automatically, switch to audit mode where I'll manually install apps and drivers, then reboot to automate OOBE and finish up at login screen. Here are the problems I'm having: After the specialize pass finishes, the computer shuts down instead of restarting. I suspect it's to do with the sysprep command in specialize, I believe adding /quit to the end should fix it, but I haven't had time to test that yet. After finishing audit mode and re
  6. I have a bunch of drivers in INF format (along with catalogues and actual driver binaries) that are stored in a WIM data image. These are extracted to %SystemDrive%\Drivers\INF along with other installer-based drivers that I install during auditUser. I've tried adding driver paths to these INF drivers in both offlineServicing and auditSystem passes, but for some reason Windows does not load them into its driver store. In the following example script, the unattend file uses a config set with the drivers.wim image stored on a usb drive along with the unattend file. The image is extracted to the
  7. I'm even more p**sed off because MS turned down my application to the Vista Beta program, but let me into the Server 2003 SP2 and WLM programs. Looks like they don't want me testing anything interesting Now I have to use Vista like a common software pirate (ok, using my beta keys) and then paying for a £300 upgrade in January. My reward for giving them tons of feedback. Not a happy bunny.
  8. Ok, I've got that bit. The only problem is that I'm on a 32 bit system and my 64 bit laptop isn't coming for a couple of weeks. I therefore can't get the boot folder as setup won't even start. Anyone got a boot folder I can borrow? plz?
  9. Hi guys, On flyakite's Multi-Boot DVD tutorial (link), under the section "Creating the Boot Folder", it tells me that I need to execute winnt32.exe /noreboot to get the boot files. This method has worked for me in Windows Server 2003 SP1 Corporate, but when I try doing it in XP Pro SP2 Corporate, it prompts me for my product key. Upon entering it, it gives me the error "The product ID you entered is invalid". Now I definetly KNOW my key is valid - I did a clean text-mode install in VMware and it accepted it, no questions asked. However, when installing from Windows, it refused point-blank to a
  10. Hey guys, just to point out - the best way of making an XP autorun program that works just like the real thing is to ResHack the setup.exe file and change any strings that point to installation tools and utilities. You can change the text of anything (I do this to clarify which edition of XP I'm installing) and change the background and icons. The program will works exactly as before, but just customized to your needs. Get ResHack from here: http://www.angusj.com/resourcehacker/ Hope I've helped you - it's a lot quicker (and cheaper) than messing about with AutoPlay Studio, though that screens
  • Create New...