Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

RHMMMM

Member
  • Content count

    5
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About RHMMMM

  1. Hey guys, I need a little help making my image work on a Precision T7400 (beast of a machine). The image works on all the Optiplex models from a GX240 thru a 755 (all with the Intel drivers). The T7400 uses the "Dell SAS 6/iR Integrated Workstation Controller" and I have put the drivers in the [sysprepMassStorage] section of the sysprep.inf file I'm using, but the darn thing still won't work! On first start, the machine begins booting and I see the XP screen, then it BSOD's and restarts. NOW, if I shut it off, put the hard drive on the Intel controller ports on the motherboard and start the machine back up, Mini-Setup works and all drivers are detected (I'm using the Vernalex sysprep driver scanner as part of my pre-sysprep process). It even detects the SAS controller. After the machine boots into Windows after completing Mini-setup, I can swap the drive back to the SAS controller and it boots fine. BOTTOM LINE: The initial Mini-Setup won't work when the drive is attached to the SAS controller despite the drivers and PnP IDs being listed in sysprep.inf. The PnP ID is "PCI\VEN_1000&DEV_0058&SUBSYS_021D1028" and is listed below, at the bottom of the section. (Note, you'll see that the drivers are on D: partition, I have tried moving them to C: and still get the same result, BSOD) Here's the sysprep file I'm using (with some stuff ****'ed out), please let me know what I'm doing wrong here: [Unattended] DriverSigningPolicy=Ignore InstallFilesPath=D:\i386 TargetPath=\WINDOWS KeepPageFile=1 OemSkipEula=Yes UpdateInstalledDrivers=Yes UpdateUPHal=ACPIAPIC_UP, %WINDIR%\Inf\Hal.inf [GuiUnattended] AdminPassword=* TimeZone=35 OEMSkipRegional=1 OemSkipWelcome=1 OEMDuplicatorstring="***********" EncryptedAdminPassword=NO [UserData] FullName="*****" OrgName="*****" ComputerName=* ProductKey=******* [SysprepMassStorage] PCMCIA\*PNP0600=%systemroot%\inf\mshdc.inf PCMCIA\KME-KXLC005-A99E=%systemroot%\inf\mshdc.inf PCMCIA\_-NinjaATA--3768=%systemroot%\inf\mshdc.inf PCMCIA\FUJITSU-IDE-PC_CARD-DDF2=%systemroot%\inf\mshdc.inf PCMCIA\LOOKMEET-CBIDE2______-6C0A=%systemroot%\inf\mshdc.inf *AZT0502=%systemroot%\inf\mshdc.inf PCI\CC_0101=%systemroot%\inf\mshdc.inf PCI\VEN_10B9&DEV_5215=%systemroot%\inf\mshdc.inf PCI\VEN_10B9&DEV_5219=%systemroot%\inf\mshdc.inf PCI\VEN_10B9&DEV_5229=%systemroot%\inf\mshdc.inf PCI\VEN_1097&DEV_0038=%systemroot%\inf\mshdc.inf PCI\VEN_1095&DEV_0640=%systemroot%\inf\mshdc.inf PCI\VEN_1095&DEV_0646=%systemroot%\inf\mshdc.inf PCI\VEN_0E11&DEV_AE33=%systemroot%\inf\mshdc.inf PCI\VEN_8086&DEV_1222=%systemroot%\inf\mshdc.inf PCI\VEN_8086&DEV_1230=%systemroot%\inf\mshdc.inf PCI\VEN_8086&DEV_7010=%systemroot%\inf\mshdc.inf PCI\VEN_8086&DEV_7111=%systemroot%\inf\mshdc.inf PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf PCI\VEN_8086&DEV_2421=%systemroot%\inf\mshdc.inf PCI\VEN_8086&DEV_7199=%systemroot%\inf\mshdc.inf PCI\VEN_1042&DEV_1000=%systemroot%\inf\mshdc.inf PCI\VEN_1039&DEV_0601=%systemroot%\inf\mshdc.inf PCI\VEN_1039&DEV_5513=%systemroot%\inf\mshdc.inf PCI\VEN_10AD&DEV_0001=%systemroot%\inf\mshdc.inf PCI\VEN_10AD&DEV_0150=%systemroot%\inf\mshdc.inf PCI\VEN_105A&DEV_4D33=%systemroot%\inf\mshdc.inf PCI\VEN_1106&DEV_0571=%systemroot%\inf\mshdc.inf PCI\VEN_1000&DEV_0054&SUBSYS_1F041028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0054&SUBSYS_1F061028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0054&SUBSYS_1F071028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0054&SUBSYS_1F081028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0054&SUBSYS_1F091028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0058&SUBSYS_1F101028=D:\HARDWARE\T7400\SAS\symmpi.inf PCI\VEN_1000&DEV_0058&SUBSYS_021D1028=D:\HARDWARE\T7400\SAS\symmpi.inf [TapiLocation] AreaCode=*** LongDistanceAccess="9" [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes [Proxy] Proxy_Enable=0 Use_Same_Proxy=0 [GuiRunOnce] Command0="regedit.exe /s C:\Windows\sysprep\sourcepath.reg" Command1="C:\Windows\sysprep\PageFileRAMSize.exe" Command2="regedit.exe /s C:\Windows\sysprep\ClearPageFileDefaultSetting.reg" Command3="cmd /q /c rd c:\windows\sysprep /s /q" Thanks for any help!
  2. Was wondering if there is a tool out there for version management that works with images. It would be nice to see a tool that automatically tracks the software/patches/etc that are included in an image - it would make updating it a whole lot easier. Any suggestions?
  3. So the advice above worked, plus I used the Vernalex driver scanner. Thanks!
  4. Thanks for the advice, I'll try it tomorrow and update the thread. I'm also going to try some other things I found. If anyone else has more insight, by all means, I'd appreciate it.
  5. I would really appreciate any help with this: I'm creating a HII and am having a heck of a time getting drivers to load. I would use the driverpacks, but the image size is an issue and can't include all of them. I'm building the image on a Dell Optiplex 755. The only driver I loaded was the AHCI SATA driver during the Windows install. All of the other devices were unrecognized and I left them that way. I made my changes to the image. I have all the drivers and have (manually) enumerated the DevicePath key in the registry - of course I found the Vernalex program after I did it by copying the paths into notepad. I was going to use the OemPnPDriversPath line, but unfortunately, in my org, the drivers HAVE to be on the D: drive - so I did the DevicePath key. I ran sysprep -mini -reseal. When the machine booted back up, nothing changed. All of the unrecognized devices were still unrecognized. BUT, if I told Device Manager to update the driver, it found the correct one automatically (thru the DevicePath key, I assume. Should I be running sysprep with the -pnp switch? I have already seen this post: http://www.msfn.org/board/Forcing-PnP-Enum...p;hl=devicepath Should I run that command (RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers) in a GUIRunOnce script? I'm baffled as to why the devices didn't auto detect during sysprep. They are all PnP - doesn't sysprep force a driver redetect? Or is that only with the -PnP switch? I thought the -PnP switch was only for nonPnP device detection? Thanks for any help!
×