Ghost Solution Suite

I have two problems actually.

1. I will type the DA commands in and it wil just sit there - forever. I've left it over night and it still not do anything.

ghdplyaw32.exe /target=<target OS> /ddb=<CD>\windrivers /eval

2. Probably what is happening most often is after I run DA successfully and I start-up it goes through the Sysprep process, but I did not set-up Sysprep?? 

BUT

Before I can even get to the Sysprep stage I have to hold F8 and select "Last Known Good Configuration" just so it will not BSOD on me, A 7B error. I thought it retargeted all the drivers?

Anyone have any idea's here? I used the same commands as above - and when looking at the Drivers folder it has one for NIC and Storage, so I do not get why it isn't working without F8...

Thanks!

All DA does is retargets NIC and mass storage drivers. I think I read one of the Devs saying that in GSS 3.0 they will try to have it retarget all drivers, but the time is not yet right for that I suppose.

Also DA has nothing to do with Sysprep. They act kind of like the same, but they do not interact, and DA starts and finishes before Sysprep.

As far as your problem, I'm honestly not sure, what I would do is drop the /eval and /ddb and just run the /target and see what happens. If it tries to run but fails because it's missing drivers, make a new DA boot CD. If it does the same thing, re-image the PC, windows may be bad.

Jace5869:

Is the CD drive properly mounted?  Try running the DDB from a share or USB drive.

Have a look at HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath

is %SystemRoot%\inf the first entry?

Cobra7:

DA will set mini-setup to run as part of its retargeting.  It's true that DA doesn't run as part of that mini-setup, but the retargeting does require it

Well we have one of our Symantec people back. My guess was you guys were on a forum strike until the forums got fixed :)

I know DA and Sysprep are different, I do not know why Sysprep is running when I have done is run the GBW to make a Ghost boot disk with DA included. I have doen very little to set-up all the features of GSS 2.5.

Ok, so it is Mini-setup running - thanks for clearing that up.

When you say look in <REG Path>, do you mean when I restore the image or what? I do not understand when/where I need to look at the registry.

I did not know I could mount a network share to be my DDB, so does that mean I could use something like DriverPacks then?

It's just strange that I've used this exact image for several 755's, GX280's, GX270/GX260's and did not have a problem with it BSoD. It seems like these GX520's are cursed or something, but I have used the image on a couple of those before without any issues.

I know DA and Sysprep are different, I do not know why Sysprep is running when I have done is run the GBW to make a Ghost boot disk with DA included. I have doen very little to set-up all the features of GSS 2.5.<o p=""></o>

You would need to run DA for it to set up the mini-setup UNLESS the image you have is already set up to run sysprep.  GBW will not set up Sysprep<o p=""></o>

<o p=""> </o>

When you say look in <REG Path>, do you mean when I restore the image or what? I do not understand when/where I need to look at the registry.<o p=""></o>

It's the registry in the target that you need to look at.  There are at least 2 ways to do this

From the PreOs [after laying down the image]

1. Type regedit at a command prompt
2. Navigate to HKLM
3. In the File menu select ‘Load Hive…’
4. Navigate to the target’s registry files – typically c:\window\system32\config\software
5. When prompted, give it a unique name like ‘sw’
6. Navigate from HKLM\sw to Microsoft\Windows\CurrentVersion\DevicePath

Alternatively you can open the image in the GhostExplorer, navigate to \window\system32\config\software and extract it onto your local disk, and then mount it as described above

I did not know I could mount a network share to be my DDB, so does that mean I could use something like DriverPacks then?<o p=""></o>

You have to import the drivers you want in the GBW first. That would copy them into C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\windrivers - you could mount that as a share point or make a copy of it

<o p=""> </o>

<o p=""> </o>

DA initializes the plug and play detection the same as Sysprep does. <o p=""></o>

You noted that you did a /eval was the result a success? And then did you run it a second time on the same machine with out the /eval?   The eval just lets you know that the drivers are missing or are not.  The same run without the eval will make it actually run the DA steps.   I am guessing that you did run it with our the eval the second time or else it wouldn’t have kicked off the plug and play detection. <o p=""></o>

So my questions are<o p=""></o>

1. Was the eval a success?  <o p=""></o>
2. what is the full text on the screen after the DA is run?  <o p=""></o>
3. What version of the Ghost boot wizard did you make the boot disk with? <o p=""></o>

Also if you boot your machine that is BSOD and disable crash control what BSOD is being brought up on the machine that is rebooting?<o p=""></o>

<o p=""></o> 

Also here is the KB that I give to my guys when they come and ask me how to run DA.  In case anyone reading this post could use the walkthrough doc this one is one of the better ghost documents. <o p=""></o>

http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2008050913544860?Open&seg=ent<o p=""></o>

<o p=""></o> 

<o p=""></o>