Jump to content

sprack

Member
  • Posts

    7
  • Joined

  • Last visited

  • Donations

    $0.00 

About sprack

sprack's Achievements

0

Reputation

  1. I'm kind of in the same boat. I have a Sony Vaio VGN-FE770 that will install XP_32, Vista_32 and Vista_64, but balks at the starting windows part of the DOS install in XP64 and 2003_64. I've tried loading and slipstreaming the SATA drivers, but that makes no difference. Slipstreaming SP2 didn't either. WinPE64 and WinPE2_64 both boot on it. Near as I can guess there is some bios chicanery prevent its install. Anyone know a way to start the debugger for the DOS portion of the install?
  2. You can have both. Its the same kind of config, but in the Audit phase. Just change the path to a network share or whatever. Again, the caveat is that the Audit phase won't pick up XDDM drivers. Also I've found that it will only recurse one directory beyond the share so if your share is \\server\driver and there is a video folder I've had to put all video drivers in that dir. I think you can specify multiple PathAndCredentials though. Hmm i believe in this case your are actually installing the drivers offline into the image. That's not what i want to do. I want to have 1 image that i can use on different pc's with different kind of hardware. I am going to use it for my work, i am a reseller and we have our own PC line. So each PC has different hardware. So i want to add a lot of drivers to vista. When Vista doesn't have the appropriate driver it must search for it in that c:\drivers directory. I have read somewhere you only have to put in all the *.inf drivers. but can i work with subdirs? It's confusing!
  3. How much memory do you have on your videocard or in the case of UMA video, how much did you allocate to the framebuffer. Per MS spec they will mirror that amount in main mem. IIRC its described in the WHQL docs for meeting logo requirements. And a quick note on PAE, if Vista detects it in CPUID it'll use it.
  4. To speed it up I did a perl script to do all the repetitive work, but I'm still hitting the brick wall about the QFE's being integrated with the install image. It is still just adding them to a cache and then installing at desktop. Here's my perl code for those that care. #!/usr/bin/perl -W @a = `dir \/b *.msu`; chomp @a; foreach (@a) { system("mkdir c:\\Vista_QFE\\tmp"); system("expand $_ -f:* c:\\Vista_QFE\\tmp"); my $x = `dir /s /b c:\\Vista_QFE\\tmp\\*.xml`; chomp $x; system("pkgmgr /o:\"c:\\mnt;c:\\mnt\\windows\" /l:c:\\Vista_QFE\\logfile /n:$x"); system("rmdir /s /q c:\\Vista_QFE\\tmp"); }
  5. Here's my cookbook: 1) Add them to the base install.wim offline. Mount the install.wim file to some directory on your system imagex /mountrw install.wim 1 c:\mount pkgmgr /o:"c:\mount;c:\mount\windows" /n:unattend.xml /l:logfile.txt The caveat here is you need the following entry in your unattended.xml <settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="2f63429a"> <Path>c:\drivers</Path> </PathAndCredentials> </DriverPaths> </component> </settings> Set <Path> to wherever you’re storing the drivers you want injected into the install. After this examine the logfile.txt.txt file. Near the bottom you should see something like this in between a bunch of what look like errors: 2007-02-06 12:14:03, Info CBS Pkgmgr: Install Drivers Offline Callback: SUCCESS:Added 'c:\Drivers\p4m900_15310506_vista_logo\VIAwIShld\P900LH.inf' to offline driver store at 'c:\mnt\windows\System32\DriverStore\FileRepository\p900lh.inf_9fa19d93\p900lh.inf'. (Error code (HRESULT) 0x0.) 2007-02-06 12:14:03, Info CBS Pkgmgr: Install Drivers Offline Callback: SUCCESS:Added driver 'c:\Drivers\p4m900_15310506_vista_logo\VIAwIShld\P900LH.inf' to the offline Windows image at 'c:\mnt\windows\System32\DriverStore\FileRepository\p900lh.inf_9fa19d93\p900lh.inf'. (Error code (HRESULT) 0x0.) 2007-02-06 12:14:03, Info CBS Pkgmgr: Install Drivers Offline Callback: SUCCESS:Driver package 'c:\Drivers\p4m900_15310506_vista_logo\VIAwIShld\P900LH.inf' installed! (Error code (HRESULT) 0x0.) 2007-02-06 12:14:03, Info CBS Pkgmgr: Install Drivers Offline Callback: SUCCESS:Successfully marked devices for reinstall! (Error code (HRESULT) 0x0.) If it installed properly then unmount and commit to save. Copy your install.wim over the one in the sources dir. imagex /unmount /commit c:\mount You can also build the unattended so that it calls the drivers across the network, but it doesn't appear that it will call XDDM drivers. Only WDDM drivers appear to work with the network method, whereas XDDM work if you slip them into the install.wim.
  6. I apologize if this is a dupe topic or has been answered elsewhere I feel I've scoured the forum for hints or answers without luck so far. Does anyone know how to slipstream the QFE's so that they are part of the OS on boot. Currently I'm doing this to update the base install: imagex /mountrw install.wim 1 c:\mount expand Windows6.0-KB931573-x86.msu -f:* c:\temp pkgmgr /o:"c:\mount;c:\mount\windows" /l:c:\temp\logfile /n:c:\temp\Windows6.0-KB931573-x86.xml imagex /unmount /commit c:\mount But all that appears to do is put the files in a placeholder and than run windows update on the local files once the system is up. Is real slipstreaming deprecated or am I missing something. Thanks.


×
×
  • Create New...