well rereading my lines, i think it s very confused so let me clear a
little bit my situation.
I have made a directory
install/os/winxp/I386/$oem$ wich contains $1 subdir, wich contains
Driver subdir.
The Driver subdir contains a e1000NIC subdir that contains all files
extracted by the driver .EXE downloaded at intel.com :
e1000325.cat  e1000msg.dll  E1e5032.SYS  E1e5132.sys   NicIn32.dll
e1000325.din  e1000nt5.din  e1e5132.cat  EtCo32.dll    PROUnstl.exe
e1000325.inf  E1000NT5.SYS  e1e5132.din  Ncs2Setp.dll
E1000325.sys  e1e5032.din   e1e5132.inf  NicCo32.dll

When i boot the cd, it asked to choose the driver to add :
choice 3 [Driver]
 then everything continues till windows asks me for a file NicCo32.dll
file, so i browse but that file is in the e1000NIC directory. That
directory is in my unattended.txt at the right place in
OEMPnPDriversPath =Driver\e1000NIC
so why does it continues to ask for the location ?
2005/11/9, Toto Carpaccio <[EMAIL PROTECTED]>:
> I can t figured out what s the difference between I386\$OEM$\$$ and
> I386\$OEM$\$1 directories. Anyway i've created I386\$OEM$\$1\D\e1000
> with inf, sys and cab files. Well, to be sure not to forget something
> i 've put all files extracted by Intel .EXE package driver in it so it
> contains also an executable proinst.exe. And the script asks me for
> the location of the exe, that's strange cos i don t dig which process
> need that .exe. Anyway, it worked when i gave the location. Do you
> think if i just  remove it, it will stop asking me for that .exe ( the
> directory contains also dll and din files, maybe i have to remove them
> too)
>
> 2005/11/8, Brad Erdman <[EMAIL PROTECTED]>:
> > Hi,
> >
> > I think there is some confusion here.  Installing the network drivers
> > requires that you have the chipset drivers installed.
> >
> > To install the chipset drivers, you need to follow the instructions from
> > Intel.  This involves creating the I386\$OEM$\$$\INF directory and
> > populating it with the inf files for the chipset (a.k.a. motherboard)
> > drives.  There are a few more steps outlined in the Intel documentation.
> > If you need more help with this, let me know.
> >
> > Once you have that in place, the network drivers will install.  One
> > caveat here; make sure that the inf, sys, and cab files for the driver
> > are at the top of the driver (i.e. I386\$OEM$\$1\D\e1000, as opposed to
> > I386\$OEM$\$1\D\e1000\winXP, unless there is an inf file in the top
> > level).  I bring this up cause I got burned on it with some driver.
> >
> > Brad
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > [mailto:unattended-info-
> > > [EMAIL PROTECTED] On Behalf Of Toto Carpaccio
> > > Sent: Tuesday, November 08, 2005 10:52 AM
> > > To: [email protected]
> > > Subject: Re: [Unattended] Intel e1000 inf file
> > >
> > > Thanks,
> > >
> > > Thanks
> > >
> > > Indeed it seems that Intel give info about unattended setup but i can
> > > t find those informations. It is said PROADMIN
> > > This archive contains tools and utilities for network administrators.
> > > Includes push install and unattended install enhancements and
> > > instructions
> > > BUt i don t have it.
> > > I 've checked the e1000 folder i have inf , cab, sys, din, dll files i
> > > just put them all in /$oem$/$1/drivers
> > >
> > >
> > > 2005/11/8, Paul Griffith <[EMAIL PROTECTED]>:
> > > >
> > > > Greetings,
> > > >
> > > > www.intel.com :-)
> > > >
> > > > 1 - download the E1000 driver
> > > > 2 - extract
> > > > 3 - read readme which will tell you step by step how add the Intel
> > > drivers
> > > > to your unattended setup. Those nice folks at Intel even include a
> > batch
> > > to
> > > > do most of the work for you!
> > > >
> > > >
> > > > Thanks
> > > > Paul
> > > > On Tue, Nov 08, 2005 at 03:28:09PM +0100, Toto Carpaccio wrote:
> > > > > Hi again guys,
> > > > >
> > > > > I try to find *.inf files for e1000 intel NICS without success,
> > i'm
> > > > > shure you guys had ever have to deal with those, can you tell me
> > where
> > > > > i can find all the files needed to put in the oem directory of
> > > > > unattended ?
> > > > >
> > > > > Thanks in advance.
> > > > >
> > > > >
> > > > > -------------------------------------------------------
> > > > > SF.Net email is sponsored by:
> > > > > Tame your development challenges with Apache's Geronimo App
> > Server.
> > > Download
> > > > > it for free - -and be entered to win a 42" plasma tv or your very
> > own
> > > > > Sony(tm)PSP.  Click here to play:
> > http://sourceforge.net/geronimo.php
> > > > > _______________________________________________
> > > > > unattended-info mailing list
> > > > > [email protected]
> > > > > https://lists.sourceforge.net/lists/listinfo/unattended-info
> > > >
> > > >
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net email is sponsored by:
> > > Tame your development challenges with Apache's Geronimo App Server.
> > > Download
> > > it for free - -and be entered to win a 42" plasma tv or your very own
> > > Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> > > _______________________________________________
> > > unattended-info mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/unattended-info
> >
> >
>


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
unattended-info mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Reply via email to