WDS Boot Image with Attansic L1 Gigabit Ethernet Driver

[techietone]

Hey all

My Apologies to those that have already read this under the vista forum, I posted it initally in the wrong forum

I hope someone can help with this cos it's driving me mental

here is the problem

When booting from a standard Boot.wim via WDS i get the error message Network can't be started

so I though oh ok I need to inject the drivers

so off i went downloaded the latest version of the drivers

took a copy of the boot.wim to my local machine where i had Windows AIK installed

made two directories in a temp directory

one called mount the other called driver

extracted the driver in to the driver directory

using my imagex /mountrw c:\temp\boot.wim 1 c:\temp\mount

the image mounted no issues Wheeeyeee I thought

next used

peimg /inf=c:\temp\driver\lan\vista_32\*.inf /image=c:\temp\mount

get the message that atl01v32.inf was being installed

next i closed the image with

Imagex /unmount /commit c:\temp\mount

copied the boot.wim to my WDS server and added it as an image

I did the same for my capture image

now here is the Rub

My capture Image works perfectly

my delopyment boot image still throws the same error

and for the life of me i can't find anything i have done differently

i have gone though the injection process 4 times now each time slowly checking a double checking my results

yes the image file increase in size but still it can't find the network card

if no one has any ideas I am going to have to purchase an intel GT Desktop gigabit card, what i would perfer not to do as its a was of money really as the Attansic L1 controller works perfectly under vista 32 bit and 64bit and the only area it seems to fall down is the imaging process, I only have one machine with this type of network card (of course its my main machine so the one i am most likely to want to reimage!!!)

Any Ideas will be greatfully recieved

[techietone]

Ok problems resolved

This is what i discovered

if i looked at the local version of the image i was working on on my pc it had the driver added

I then looked at the system32\driverstore\filerepository directory when i had booted using one of the images that claimed not to have the driver and it was quite right the inf files was missing

so i mount the image directly from the server

added the inf by name instead of by wildcard i.e. *.inf

then commiteed it again

low and behold it worked this time

what i hate is there is not a logical explanation for this so if anyone can think of one i would be interested

Tone