inserting drivers to WDS boot.wim error

Trying to install NIC driver to WDS image.  Keep getting this error.
C:\Program Files\Windows AIK\Tools\PETools>peimg /inf="G:\Dell Vostro Drivers\drivers\network\R248117\XP32\*.inf" /image=c:\WIAK_Mount
Preinstallation Environment Image Setup Tool for Windows
Copyright (C) Microsoft Corporation. All rights reserved.

No Windows PE image was specified; specify one with /image=<path>.

Here is the command I am using.  It's been a long day.  What am I missing?
C:\Program Files\Windows AIK\Tools\PETools>peimg /inf="G:\Dell Vostro Drivers\drivers\network\R248117\XP32\*.inf" /image=c:\WIAK_Mount
LVL 32
nappy_dThere are a 1000 ways to skin the technology cat.Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

65tdRetiredCommented:
Has the image been mounted using the imagex cmd?
0
65tdRetiredCommented:
What version of OS is the boot image?
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

nappy_dThere are a 1000 ways to skin the technology cat.Author Commented:
I m running Windows 2003 Server with SP2 and WDS.

The image I am trying to inject drivers into is an XPsp3 image for the Dell Vostro 230.

The image was mounted using the command  imagex /mountrw <winpe.wim> 2 <winpe-directory>

@65td, I did see that article previously but it did not have any insight into why I am getting this error message.
0
James HaywoodCommented:
It may be just a typo but you have put WIAK rather than WAIK?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
merowingerCommented:
maybe not the failure point, but use the current WAIK version (WAIK for Windows 7) and inject the drivers with the dism.exe command line tool.
0
65tdRetiredCommented:
What is  the Version of WAIK?
How's the disk space?
Try rebooting WDS server.

This MS doc may help no clear answer on that error:
http://support.microsoft.com/kb/923834

Once the image is mounted can one get /info from it?

imagex cmds:
http://technet.microsoft.com/en-us/library/cc749447%28WS.10%29.aspx 
0
nappy_dThere are a 1000 ways to skin the technology cat.Author Commented:
doh! *blushing*  Thanks.  I was a long 10 hour Saturday :)
0
James HaywoodCommented:
Been there, done that. Spent 2 days wrestling with a system for some else (not even technical!) to point out the network cable was connected to the wrong socket - arrrgghhh!!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.