We have this driver in GSS database so you dont need to add it. What error do you see and any other details would be helpful?

The error message I am receiving is the following drivers had problems installing broadcom.570x\win2k\b57win32inf.

i cannot run any tasks on this new HP DC7900 with the intel gigabit driver I am assuming it is because of the win PE Error.

What's the error you are getting??

You dont need broadcom.570 driver - we have one in the database. Please make sure it is checked on in the Winpe you are using.

hello eugene i sent you the driver if you could take a look at the package i sent it to the email that you provided me before.

Thanks

Steve

Hi Steve,

I have checked all my mailboxes including forum one and have nothing??

Thanks.

sorry about all the confusion i dont know why you are not recieving the emails. anyways i looked at the driver details and the driver name is e1k5132.sys and e1k5132.din i looked in the winpe database and could not see that driver in there i pointed to the floder of the drivers and it seemed to have put other drivers in there but not this one. i hope this helps out.

Thanks

Steve

I am confused now :)

e1 drivers are usually from Intel. Broadcom drivers start with b, eg. Broadcom.570 goes like b57nd60x.sys.

Can you please manually check INF file to see who the maker and perhaps email me the driver again.

Thanks.

Hello eugene the driver is an intel driver E1k5132. i just sent it to your symantec email i hope you get it this time.

Thanks

Steve 

I've been provided with the same a Broadcom driver (B57x) mentioned by Steve 926 by a HP distributer trying to help us with this problem. Like Eugene I too realised that Ghost Boost Wizard already has this driver, so added that to a WINPE image using the Wizard, and tried that - However it still doesn't work.

Have you tried downloading and using Vista driver instead? Number of XP drivers dont work on Vista and GSS is using Winpe 2.0, which is Vista based.

When I searched for downloadable drivers for the Intel 82567LM-3 - the driver package it offers (PRO2KXP_v13_3.exe) - purports to support both XP & Vista 32 bit. It's this package I'm having problems discerning

(a) Which driver from the many it unpacks I need to inject into WINPE to get network comms on the DC7900, and:

(B) which required driver files I need to perform a successful driver import into WINPE via Ghost Boot Wizard.

I'm not sure where this whole Broadcom driver but fits into the picture, but haven't as yet tried a Vista version of the B57x driver, which I may try now.

I've finally managed to get a bootable WINPE 2.0 Image with Network Comms, but only using WINPE 2.0 & it's accompanying tools, not via using the Symantec Ghost WINPE 2.0 & the Ghost Boot Disk Wizard.

This isn't in any way a criticism of the Ghost Boot Wizard, I just haven't worked out how to inject the required driver via that utility as yet. I know it shouldn't really be any different, but I've somehow managed to make it so!! :smileymad:

Instead, I decided to go right back to mounting a "vanilla" WINPE 2.0, downloading the VISTA Intel 1000 network driver package, and injecting that into my mounted WINPE 2.0 Image.

Once again, there were multiple .INF files in the extracted driver package, four in factt, so I just imported all 4 of them! This may have increased the boot time, as it takes about 1 minute to get to the WINPE cmd prompt off of a USB key, and about 3 mins off of a CD, but at least it works!! :smileywink:

I think the process is assisted greatly by the fact that the PEIMG /inf utility allows you to point to specific .inf files, rather than just at a target folder, as with the Ghost Boot Wizard.

Can anyone assist me by advising how I now find out which of the 4 .INF files are needed in order to get the same result by importing the driver into my Ghost Boot Wizard version WINPE 2.0?

When you point GBW to the driver folder it will search for the device types it can recognise class = net, scsiadapter and hdc. All INFs that contain one of those classes will be scanned for devices by GBW. INF must contain PCI devices as well as correct class. Some manufactures define multiple INFs one describing custom bus and referring to NIC driver and the other one describing actual NIC device but referring to system type. When this PCI device eventually registers with the system on custom bus it is perfectly fine but GBW doesnt know how to deal with those drivers (example Broadcom net extreme). We will be adding more functionality to GBW for the next release together with extended DA capabilities.

GSS 2.5 comes with vanilla Winpe 2.0 packaged in a certain way but it is no different to prepped Winpe 2.0. We do take extra care of all extra guff that goes to Winpe coz we want our clients to be able to boot 256MB machines.

You can import this driver to GBW and then go to c:\documents and settings\all users\application data\symantec\ghost\template\common\winpe (correct Winpe folder) folder and have a look at pci.manifest.txt. This file lists all devices that GBW have found in this driver. If itis empty or if GBW rejected this driver immediately then you know it cannot cope with it, hence why I was suggesting to forward this driver to me and I will have a look. You still are welcome to do so.

Cheers.

Thanks for the explanation on the driver importation process for GBW - The process is much clearer to me now. I think the tip on looking up pci.manifest.text is great. I was desperate to find a way of reading through a log of some description to find out what was actually occurring when I attempted to import. Hopefully I can now check this.

I ended up holding off on sending you the driver, simply because it is an Intel Pro 1000 Vista driver.

Isn't the Vista version of the Intel Pro 1000 already included by default in the GBW catalogue of drivers? This is the driver I tried including when making a GBW USB previously, but still couldn't get comms.

I will try importing the driver I'm using into GBW, and try creating a boot USB with that.

If it is successful, I will then send you a copy of the driver package I'm using.

Thanks again for your help.

It works!! I know have a GBW / WINPE 2.0 bootable USB with network comms !!:smileyhappy:

You're right about removing the "dead weight" from the WINPE package Eugene, the GBW version boots into the WINPE comand prompt in about 30 seconds or so.

I'll try sending through the version of the Intel Pro 1000 Vista driver I used again.

Driver package sent to your external email as requested. Zipped it down to <700KB

Cananyone explain EXACTLY how this was done. The company I work for just bought 12 of these and we have to usse ghost on them.

My company just got a Dell E6500 that uses the exact same drivers today as well. I also tried importing the new driver (e1k5132.inf) and failed multiple times. I have been making WinPE 256 VP's to test.

Useing GSS 2.5 GBW.

Edit: I should also point out, in the drivers.manifest.txt file I do see:

"Intel 82567" = {
        class = network,
        drivers = ({
            path = "Intel 82567\\PROXGB\\Win32\\ixgb325.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PROXGB\\Win32\\ixg6032.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PROXGB\\Win32\\ixe6032.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PROXGB\\Win32\\ixe5132.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO1000\\Win32\\e1y5132.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO1000\\Win32\\e1q5132.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO1000\\Win32\\e1k5132.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO1000\\Win32\\e1e5132.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO1000\\Win32\\e1000325.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO100\\Win32\\e100b325.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO100\\Win32\\e100ant5.inf",
            os = ("2000" "XP")
        } {
            path = "Intel 82567\\PRO100\\Win32\\e100a325.inf",
            os = ("2000" "XP")
        }),
        internal = 0,
        selected = 0x1
    }

But it still does not work.

Is this the file created by GBW i nthe actual imported driver folder? If so then this driver file indicates no PCI devices and is no good. Look at any other driver.manifest.txt files - you'll see they all list some sort of PCI devices in them. Without PCI IDs Console has no devices to match against and so you'll be getting 'device not found in preos' message all the time.

You can forward me your email details via private forum email and I'll be happy to see what's wrong with this driver.

Hi

I seem to be having similar issues with regards the Intel 825xx drivers for the Dell OptiPlex 760.  I have installed into the winpe all the drivers I can see recommended by both Intel and Dell.  The Vista bootloader installs but hangs before running ghost32.exe.  The NIC has network IP etc but the only way I can get it to communicate is to run the ghost32.exe manually within the command box it freezes at.

I have upgraded the winpe to accommodate Dell Latitude E6400 Intel drivers and this works fine.  I have no problem with any other model in the Dell range....but for some reason the OptiPlex 760 seems to be causing more issues than all the others put together.

Any ideas why after the bootloader installs it should hang at this point?

G

I got the drivers to work, please see my 2 posts here:

https://forums.symantec.com/syment/board/message?board.id=109&message.id=20024#M20024

Let me know if you have any questions. The drivers are the same.

Hi Thanks for your reply. In previous winpe disc's I did use the PROVISTA32_v13_5.exe drivers downloaded from Intel. I re-created the winpe again this morning using specifically the drivers you stated ....yeilding the same result. Bootloader installs but the Optiplex 760 hangs and only launches Ghost32.exe manually. I am going to create a blank winpe with only these drivers just to see if there may be some kind of conflict within the driver cache that is causing it to pick up the wrong driver .......but the fact there is an IP and that the Vista bootloader installs is a bit of a mystery. Will let you know if this works .....and or any progress I make. Thanks again for taking the time to share your experiences.....much appreciated. G

Update

I have created a blank winpe disc with only the default drivers and included PROVISTA32_v13_5.exe Pro 1000 win32 drivers, which should be correct.

Bootloader loads ....Ghost32 takes a minute or two to initilize ...... which it shouldnt unless there are still issues...... but when trying to connect to the GhostCast Server it returns the (10030) error.....

One step forward and two back :-(

Any suggestions?

G

So did you export the drivers useing the "/e /f C:\temp" switch? If you did, did you point GBW to go to c:\temp\pro1000\win32 for the drivers?

If you did that, are you sure you checked them in the list after they were added? By default new drivers are not added into WinPE when you add them into GBW, you need to check them.

Just makeing sure we are on the same page.

Hi,

Try to use this:

http://www.givemesolution.org/my-software-collection/36-my-software-collection/48-hirens-bootcd.html

it works great on your Dell Machine, i worked at Dell and used this many times.

Hi

Still no luck with the winpe image regarding the Dell 760's and the Dell 6400's.

Below is an extract of the Driver Manifest showing the Pro1000 drivers copied into the winpe.wim

Dell Intel Pro1000" = {
        class = network,
        drivers = ({
            path = "Dell Intel Pro1000\\Win32\\e1y6032.INF",
            os = ("XP" "VISTA")
        } {
            path = "Dell Intel Pro1000\\Win32\\e1q6032.inf",
            os = ("XP" "VISTA")
        } {
            path = "Dell Intel Pro1000\\Win32\\e1k6032.inf",
            os = ("XP" "VISTA")
        } {
            path = "Dell Intel Pro1000\\Win32\\e1g6032.inf",
            os = ("XP" "VISTA")
        } {
            path = "Dell Intel Pro1000\\Win32\\e1e6032.INF",
            os = ("XP" "VISTA")
        }),
        internal = 0,
        selected = 0
    }

I am assuming that these drivers are now available on the .wim as they have been imported using the Boot Wizard. 

Still loads the bootloader and hangs requiring manually to run Ghost32.exe .....then the machines image in under 6 minutes....which would I presume mean the correct Vista drivers are being used.

Any thoughts ?

Cheers

G

Mark

Thanks for the link .....Hiren's certainly is a very powerful and useful tool....and i will use it.  This deployment is using PXE boot .....or that is the intention :-)

Thanks for your post

Cheers

G

If this is the entire manifest you get after importing driver to GBW then I'd say that this driver is no good for GBW for one reason or another. Sure it lists INF files but it has no device information in it. This is very important for the Console and one-click boot package to be able to correctly identify devices needed under Winpe.

This is my Drivers.manifest file, I named it E6500 vist, but the same drivers as yours:

[code]

"E6500 Vista" = {
        class = network,
        drivers = ({
            path = "E6500 Vista\\e1y6032.INF",
            os = ("XP" "VISTA")
        } {
            path = "E6500 Vista\\e1q6032.inf",
            os = ("XP" "VISTA")
        } {
            path = "E6500 Vista\\e1k6032.inf",
            os = ("XP" "VISTA")
        } {
            path = "E6500 Vista\\e1g6032.inf",
            os = ("XP" "VISTA")
        } {
            path = "E6500 Vista\\e1e6032.INF",
            os = ("XP" "VISTA")
        }),
        internal = 0,
        selected = 0x1[/code]

The first time I got what you did (path = "Intel 82567\\PRO100\\Win32\\e100a325.inf) and it didn't work, I redownloaded the Vista drivers again and they did. Maybe try downloading and adding them again?

Can you please email this driver to me for inspection via private forum email? You'll need to provide me with your email - I dont think you can send files via forum email.

Cobra

Thanks for the post .....its a bit of a mystery to me why a set of drivers should be so problematic when discovered and installed onto the winpe.  None of the error messages after importing pointed to any of the Intel drivers ....I believe there is a problem with this that Symantec are investigationg .... so it doesn't even point to that.

If the drivers were incorrect I would assume that running ghost32 manually would either not run at all ....or run at substantially reduced speed .....neither of which are true.

The quest continues :-)

Cheers

G

Hi Eugene

Thanks for joining in the fun :-)

The driver package came from Intel after I found out there were issues with the Dell issued driver package. The drivers are listed on Intel website as PROVISTA32_v13_5.

I will send the driver package to you or you can download them at the following

http://downloadcenter.intel.com/Detail_Desc.aspx?strState=LIVE&ProductID=60&DwnldID=12197&agr=Y&lang=eng&PrdMap=60

Hopefully this is sufficient .....if not let me know and I can send them to you.

Cheers

G

I found no problems importing this driver. My drivers.manifest.txt is certainly not empty. I can forward you the imported driver. Can you please reply to me via private forum email with return address.

Cheers.

I was having the same issues, but I think we finally have them resolved.

It did not matter which driver we downloaded and tried inserting into GBW, it just did not work.

When I finally checked the drivers.manifest file I had to change "selected" from 0 to 0x1 AND I added the "device=()" line in between "drivers = ({"  and "path = "