dkreifus

I'm trying again. I just recreated the entire image. I restructed the OEMpnpdrivers folder and I'm testing it today. Do you guys image the partition, or the whole hard drive...thats still my question about this

When you make your image, do you image the partition or the drive? I believe I have pqideploy as well (made by symantec, right?) What's the difference?

We're using PE2005, and I'm not familiar with imagex. my company is not looking for newer technologies yet on that aspect. Once we got this bridge crossed, we can look at something else.

Yea, I am guessing it ghost. I just am not sure why. EDIT: I've been doing a Disk to Image and then Image to Disk clone/restore process. Maybe a partition to image and then image to disk?

I am attempting to write to the drive after I've loaded the image on it. I need to write to the sysprep file and the registry. I am using WinPE2005 and Ghost 8.2. After creating the image, I use WinPE to deploy it with the following line: The problem is that DiskPart won't recognize the drive until I reboot. This prevents my VBS script from working, so I can't get HAL recognition. Am I using the wrong Ghost parameters?

I have already contacted our MS rep to get PE 2.0. I didn't realize it was out yet. How did you solve the problem of the .cat file if your renamed the files?

I have a WinPE CD that's been working pretty good. As new computers/NICs have come along, I've added their drivers as needed to the respective directories below: *.inf to I386/inf *.cat & *sys to I386/system32/drivers We just got a new computer, an HP DC5700. It uses a driver called b57win32 (Broadcom NetXtreme Ethernet Controller). We've also been using Lenovo T43s that use the same named driver. Also Broadcom. When I put the new HP driver into the directories, it overwrote the Lenovo ones. I would think that the newer driver would include the previous drivers info. So at this point, I can have one or the other. Any ideas how to resolve this?

I have a image I've been working on. There was a VBS script that would launch sysprep and shut down the system. Because of an earlier bsmd switch, sysprep took a while, and the script eventually just failed. So I bypassed it with a commandline, which says: start /wait c:\sysprep\sysprep.exe -reseal -mini -pnp -quiet shutodwn -s The system kicks into sysprep mode, then shutdowns down as normal. When I start it up, it does the following screen: From there, it goes right to my login window. No mini setup or anything. And my sysprep.infi looks like this: ;SetupMgrTag [Unattended] EnableBigLBA=Yes ExtendOemPartition=1 ForceHALDetection=Yes InstallFilesPath=C:\sysprep\i386 OemPnPDriversPath="Drv\DX2\A\SMAXWDM\W2K_XP;Drv\DX2\D\Win2000;Drv\DX2\N;Drv\T41\A\SMAXWDM\W2K_XP;Drv\T41\D\DRIVER\2KXP_INF;Drv\T41\M\w2kxp;Drv\T41\N1\PRO1000\WS03XP32;Drv\T41\N2\PROW2100\DRIVERS;Drv\T41\P;Drv\T41\T;Drv\T41\W;Drv\T42\M\WIN2KXP;Drv\T42\TPM;Drv\T42\TS;Drv\T42\W;Drv\DC5\N;Drv\DC5\A;Drv\T43\A;Drv\T43\B;Drv\T43\N;Drv\T43\V;Drv\T43\W;Drv\DC51\A;Drv\DC51\N;Drv\DC51\V;Drv\A30\V;DRV\A30\C;DRV\chipsets" OemSkipEula=Yes TargetPath=\WINDOWS [GuiUnattended] AdminPassword="password" AutoLogon=Yes AutoLogonCount=2 EncryptedAdminPassword=NO OEMDuplicatorstring="Base XP Build 2.2" OEMSkipRegional=1 OemSkipWelcome=1 TimeZone=35 [UserData] ComputerName=* FullName="CSI" OrgName="My Company" ProductKey=MY KEY [Display] BitsPerPel=32 Xresolution=1024 YResolution=768 [TapiLocation] AreaCode=215 CountryCode=1 Dialing=Tone LongDistanceAccess="9" [Identification] JoinWorkgroup=CSI [Networking] InstallDefaultComponents=Yes [Sysprep] BuildMassStorageSection=Yes [Branding] BrandIEUsingUnattended=Yes [Proxy] Proxy_Enable=0 Use_Same_Proxy=0 [Components] accessopt=off autoupdate=off Deskpaper=Off freecell=off hearts=off media_clips=off minesweeper=off msnexplr=off OEAccess=off pinball=off solitaire=off spider=off WMAccess=off zonegames=off [SysprepMassStorage] ....stuff here Any ideas what I'm doing wrong?

Ok..I found the solution... In the BIOS, there is a setting in System Configuration => Device Configurations. It is SATA Native Mode. Set it to Disable, and you will be all set.

The HD and all that works fine. I've done it with a manufacturers DVD, with no qualms. I know its something driver related, but I just don't know what

I have an HP with Centrino Duo on them. I'm using an image thats been working on all our other machines. Whenever I being the sysprep(from ghost) or the unattended installed, I get the BSOD, and the error: STOP:0x0000007B...... I have NO idea what to do. I've added the Intel 945 chipsets to $OEM$\$1\DRV\chipsets and the line in OEMpnpDriversPath. I've even tried loading the mass storage drivers with F6. Still the error occurs. Help!

I just tried using the F6 function to add the new Mass Storage device drivers to a clean XPSP2 install. No dice. I ran an HP XP install, and it loaded perfectly. So I am stumped.

The unattended install fails right when it says "Starting Windows" in the lower left hand corner.

I've been using a standard image for my companies systems. They've been Pentium 4 machines, with no problems. We just got a Compaq laptop that has Centrino Duo on it, and I'm getting stumped on how to work with the image. I've tried running a standard unattended install, and I get the BSOD. WinPE, same thing.I have to try a normal WinXP install. It gets to the Windows BSOD, with the green loading bar, then goes BSOD Is there something special about the chipset? Can I just copy the Intel945 chipset into the $OEM$\drivers folder and add the proper directory to the OEMPreInstall line?

Is there anyway that after I ghost a machine, I can browse the C: drive? I want to be able to copy and move a few files with my boot disk, to correct an error or 2 in an image script..... I tried changing directories, and it just said the directory could not be found..

That F6 option is for WINDOWS to recognize your drives. Is this a normal XP installation? A silent one? Windows PE? We need more details. How is Windows being installed? If it is being installed on the SATA drive, and you got it to load up, then you have it recgonized.

If I have the same install on here as on others... Then I have manually added in the SATA drivers, could I run the sysprep -bmsd from here... Would it work on newer machines if the drivers are there? We're trying to use a single image on all our machines. I believe this has the same HAL as the others

Sorry.... I'm still running the clean unattended install, so I haven't gotten the Hal yet. Basically, it drops the image onto it, boots up and then gives the Windows Last Known Good Config.. and it freezes there. I tried Safe Mode..and it listed a whole bunch of drivers, and then froze.

Well, you guys were right It was the missing drivers. Here is a similiar question.. Why would it work on an IBM T43, T40, DC5100(desktop w. Sata) but not on an A30? It should be IDE?

Maybe I should give that a go. But how come my sata drivers werent listed in the bsmd list...i had to add them myself. all of our desktops/laptops have Advanced Configuration and Power Interface PC as the chip type..so I'll leave the HAL alone for now.

wait..i thought the bmsd command got the drivers off the current machine for the current setup. Does it pull all the drivers existing on the machine? So I could essentially blast a IBM or a Dell with the same image?

I actually did some more research. I opened up the txtsetup.oem and got the hardware ids... which I don't think were listed in the list it created. (it was taking way to long. I thought the process crashed. So I'll start it again if this idea doesn't work) So I added this to my code: [SysprepMassStorage] PCI\VEN_8086&DEV_27C3&CC_0104=c:\sysprep\ich6\iastor.inf PCI\VEN_8086&DEV_27C1&CC_0106=c:\sysprep\ich6\iastor.inf PCI\VEN_8086&DEV_27C5&CC_0106=c:\sysprep\ich6\iastor.inf PCI\VEN_8086&DEV_2652&CC_0104=c:\sysprep\ich6\iastor.inf PCI\VEN_8086&DEV_2652&CC_0106=c:\sysprep\ich6\iastor.inf PCI\VEN_8086&DEV_2653&CC_0106=c:\sysprep\ich6\iastor.inf PCI\VEN_8086&DEV_24DF&CC_0104=c:\sysprep\ich6\iastor.inf PCI\VEN_8086&DEV_25B0&CC_0104=c:\sysprep\ich6\iastor.inf Does that look accurate?

Ok.. I ran the sysprep -bmsd and got a very long list in the massstorage section... How do I know what to trim down? SYSPREP.txt

I have a few questions about your post... 1. What is oemsetup1.inf 2. In your script what is EOF? I dont see the command anywhere 3. What is sysprep.hold, and why am I renaming my script to it. How will sysprep call it? Can I run sysprep -bmsd somehow to do it?

Ok...Here's all my stuff since I don't know what I'm doing wrong. On the computer to be imaged: the sysprep.inf ;SetupMgrTag [Unattended] EnableBigLBA=Yes ExtendOemPartition=1 InstallFilesPath=C:\sysprep\i386 OemSkipEula=Yes TargetPath=\WINDOWS [GuiUnattended] AdminPassword="password" AutoLogon=Yes AutoLogonCount=1 EncryptedAdminPassword=NO OEMDuplicatorstring="Base XP Build 2.0" OEMSkipRegional=1 OemSkipWelcome=1 TimeZone=35 [UserData] ComputerName=* FullName="Org" OrgName="Organization" ProductKey=XXXXXXXXXXXXXXXXXXXXX [Display] BitsPerPel=32 Xresolution=1024 YResolution=768 [TapiLocation] AreaCode=215 CountryCode=1 Dialing=Tone LongDistanceAccess="9" [Identification] JoinWorkgroup=CSI [Networking] InstallDefaultComponents=Yes [Sysprep] BuildMassStorageSection=Yes [Branding] BrandIEUsingUnattended=Yes [Proxy] Proxy_Enable=0 Use_Same_Proxy=0 [Components] accessopt=off autoupdate=off Deskpaper=Off freecell=off hearts=off media_clips=off minesweeper=off msnexplr=off OEAccess=off pinball=off solitaire=off spider=off WMAccess=off zonegames=off When I checked the ghost image, there is nothing populating the [sysprepMassStorage] area. In fact, its not there. I have the drivers loaded properly for WINPE, so I know they work. For my unattended install (before it syspreps), I have unattend.txt which contains the following section: [MassStorageDrivers] "Intel(R) 82801GR SATA RAID Controller" = OEM [OEMBootFiles] iaStor.inf iaStor.sys iaStor.cat Txtsetup.oem How should I add the drivers in for sysprep? Sysprep is called with the following line: Sysprep.exe -reseal -mini -pnp -quiet