Jump to content

greyhawk3

Members
  • Content Count

    9
  • Joined

  • Last visited

About greyhawk3

  • Rank
    Wanderer

Profile Information

  • OS
    Windows 7
  1. At long last, I figured out a solution ! Damn thing still dies in the right in the middle of my x64 RUNONCE script. However, last night I finally made a completely operational x64 disc ! I added an AUTOUNATTEND.XML to my x64 media and from a FirstLogon definition, my script added HKLM RunOnce registry entries for each of the items to be installed. It almost worked on the 1st try ! And to my surprise, my sister had several months ago given me her Compaq desktop for safe keeping and it just happened to have a x64 processor, so I was able to test this right away ! For those who might find
  2. What is the source of MS AIO discs ? Are these discs that are for internal use ?
  3. Folks: I've been stuck for weeks on the horns of the following dilemma: The x64 installation goes thru nearly the entire process, thru half of my GUIRunOnce script (which has existed for years), then stops at this point, never to be heard from again. I watch the script until Adobe Reader completes, supposed to be followed by Adobe AIR, but it never starts, in fact nothing else in the script launches. Let's say we break out of this hang-up, by restarting the PC. My GUIRunOnce script is over and the WinToolkit installer tries to complete but hangs also. Finally, another reboot and we arri
  4. Folks: Regretfully, I tried to d/l just the latest 100 or so updates from McRip's and I wound getting the entire x64 collection: over 350 MSUs ! Frankly, that's useless bec the final ISO probably won't even fit on a DVD DL, even if the resulting WIM actually worked. I found this link, which explains how to use KUC to determine which updates will work w/ a given image. What I really want is something that will list the essential updates, as I'm entirely sure that all of those updates aren't essential for a baseline Windows 7. I've installed from a more-or-less virgin Win7 SP1 and it never t
  5. This thread is closed. Thanks to all, esp bphlpt who directed me to the thread regarding KB2592687. I removed that update, as well as the Mar'13 rollup and I have at least two working x64 discs (Eng+Spa.) If I owned a PC capable of 64-bit VM guests, in spite of the hours it would take, I'd still try and narrow it down to the precisely troublesome update, in order slipstream all available updates. As I close, I want to reiterate that WinToolkit is great tool and has been a big help in the deployment of Win7 WRT my repair jobs.... .
  6. Did you install KB2574819 befor (prerequisite)? MfG, Thiersee Edit: OK, I saw KB2574819 in the INI-file I started over from completely scratch (w/o any presets) and happened to receive [yesterday] a Core 2 Duo PC for repair, so I temporarily have a 64-bit test bed. I know I've eliminated those two x86 updates that I previously overlooked. My 1st attempt which was (from scratch) as described in my original post and failed as before. My most recent attempt eliminated the dot Net installer and Mar 2013 rollup, which at least eliminated the premature launch of the WinToolkit installer b
  7. 1st let me say what an excellent tool WinToolkit is. Have been using it successfully for a month or two now, since at least rev .13. I'm currently using rev .22 and have encountered a problem with my x64 disc. I'm always starting from an unmodified MSOFT SP1 ISO and have perfected a set of (tested) presets called StdPresets-x86-r2.ini. Essentially I'm integrating [DPS] mass storage drivers, a bunch of Windows Updates (been using WSUSOffline for years), IE9 (d/l'd from WinCert's repo), and the dot .Net 4.5 addin (also from WinCert.) updates. I slipstream my INSTALL.WIM, gen a new ISO, te
×
×
  • Create New...