Jump to content


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About 70runner

  1. Used the following custom xml installed in Office 2K7 root directory for unattended install with command path instruction. Worked perfectly. <!-- <Office 2007 Unattended Installer; does not install publisher, groove, onenote, infopath, asp devel, interconnect/> --> <Configuration Product="Enterpriser"> <Display Level="none" CompletionNotice="no" SuppressModal="no" AcceptEula="yes" /> <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Enterprise Setup(*).txt" /> --> <PIDKEY Value="xxxxxxxxxxxxxxxxxxxxxxx" /> <USERNAME V
  2. Thx for reply. I found a thread which listed the individual msp files. For some reason my extraction missed a couple. I tried it again and, as you say, the updates installed at the end of the office install. Version updated as well. Now, if I could only figure out how to merge the unattended office2K7 install with an unattended XP Pro install - one DVD - life would be good.
  3. I used this procedure with an unattended Office 2K7 Enterprise install. Everything seemed to go normally. When completed, I noticed the version number did not change. So I ran the SP1 exe and the first thing it does is run an update detection. It apparently did not detect SP1 so proceeded to install. When finished the version number did change. I ran the exe again to see if it would detect SP1 - it did and reported SP1 already in place. So heres the question - will the method above install the SP1 components without registering as an official SP1 update?
  4. Noob here (be gentle, I'm learning on the fly)...following is an exact replica of the orig config.xml, modified for an unattended install with corresponding changes on first line, "reboot" line, user, company, and key (not shown of course). Figure if I could get this to work, the rest should follow. I know this install/key works because I installed office on my host Vista computer. I copied the Office CD contents to the XP Pro guest drive image (using virtualbox) and placed the modified xml file in same folder as setup.exe. Then ran the command line. Office install starts up but immedia
  5. Update: Recopied files from winXP disk (SP1 version). Eliminated SP2 update, dozen addons, and all the components/tweaks. Only option I selected was drivers, added the Sata driver, and made a boot disk. Booted and installed perfectly. So I'm assuming its not a Sata driver issue. Something in the addons or tweaks :unsure: On a hunch attempted a manual install with the full monte: SP2/addons/etc. Got the same results as above...another coaster that only works inside virtualbox.... pls help SP2 is straight from windows site. Last session ini: Last_Session.ini Update 2: nlited SP2 to SP
  6. I've been building progressively more elaborate (addons and such) nlite installs on vista notebook using Virtualbox. All worked perfectly. Decided to go for it today. Booted up nlite XP CD on vista laptop, with XP SATA driver direct from Fujitsu, to do fresh install and everything proceeds normally until early in the loading phase following screen appears: Setup could not determine the type of computer, or you have chosen to manually specify the computer type. Select from the following list, select “Other” if you have device support disk provided by computer manufacturer. Standard P
  7. Yes, I ran nlite once. I did search the presets folder to check for ini files. Are the "components" settings supposed to be captured by the ini file? Is there a save settings at the end of the nlite process that I missed?
  8. Good news: successfully created a nearly unattended nlite XP Pro install iso on first attempt. Booted into virtualbox and discovered I missed the time zone setting. Otherwise all went well. Bad news: when I returned to nlite to adjust a few things, discovered the preset 'last session' load was seriously incomplete. Listing is below. None of the extensive components settings were evident. What did I do wrong??? [Main] Env = 1.4 - 2.0.50727.832.Microsoft Windows NT 5.1.2600 Service Pack 2 Target = Windows XP Professional SP1 - 5.1.2600.1106 - English (United States) [Tasks] Service Pack In
  9. faimag - I'm gonna try it again, just to make SURE I deleted all the drivers; appreciate the help
  10. Thx for the info on netmap.inf. Actually I did remove all drivers with nlite because I'm installing XP on a vista NB with complete new set of drivers. I don't quite follow -b- : I pulled the i386 folder from the installed windows directory and added the 2 win51 files. Then directed nlite to this folder. I don't have windows CD, only the restore CD.
  11. I just went through this drill with XP Pro and a Fuji laptop restore disk. The i386 folder and other installation files were contained in an encrypted folder on the restore disk, so there was no way to directly access i386 on the disk. I attempted to use the i386 folder from the windows folder and added the two other files needed, for an SP0 configuration: win51 and win51IP, provided by a forum member. Nlite process went normally, however, the winXP install failed with an error message about a missing "netmap.inf" file. Google on this issue didn't turn up much, but there seems to be a conne
  12. Made iso and attempted fresh install of XP Pro, integrated with SP2, to virtual drive for test. Install failed almost immediately, with window labeled "Network Component Upgrade". Notation within the window: "Error reading information from netmap.inf. Setup cannot continue." Goes on to say cannot find netmap.inf. There is no netmap.inf in existing i386 folder. Forum/google searches didn't turn up anything conclusive, though some connected lack of netmap.inf file to OEM configuration. Ideas???
  13. Heres the updated snapshot of nlite using the i386 folder from the hard drive windows folder with the 2 added files. Does this look like a good basis for an XP conversion? I like your idea of two cd's, one awaiting SP3 and the other with SP2.
  14. Thx for response. i386 folder properties: Snapshot of i386 contents, first page of many:
  • Create New...