Or did I get it wrong, 64 characters starting FROM the \os\ portion?
Anyway another thing to check is that your main unattended.txt that
comes with the distribution and which you should not edit, found in
\install\lib dir includes the line:
[Unattended]
OemPreinstall=Yes
And from another discussion earlier this year where someone had a
similar problem:
> [Unattended]
> OemPnPDriversPath = "audio\RealtekALC850;misc\SMBus;net\WinXP;net\test"
Yes, there is the mistake: the directory names must not exceed 8
characters in length. Shorten "RealtekALC850" to "rtalc850" and try
again. Additionally you should lower-case directory/filenames. (from
Niels S. Richthof).
After that I'm out of ideas, using unattended 4.6 my drivers have always
copied wonderfully as long as I just have the correct .inf (or .inf and
.cab) files.
br,
Artturi
Artturi Kyrömies wrote:
Also remember, from the adding drivers part of the step-by-step guide:
*Note*: The total absolute length of any file name, including the
leading |\os\...\$oem$| portion, must not exceed 64 characters or
winnt.exe will get an error when it tries to copy the file.
So if you'd have
\\server\something\unattended\install\os\xpsp2\I386\$oem$\$1\DELL\network...already
far too long and copying the drivers would fail.
br,
Artturi
Scott Parrill wrote:
I created a directory like $oem$/$1/DELL/rxxxxxx, where rxxxxxx is
the DELL file number for the drivers. When I edit the
unattended.txt, at the point Unattended allows manual edits of the
unattended.txt, doit.bat, and postinst.bat, the appropriate paths are
listed in the OemPnPDriversPath entry.
Tomasz Chmielewski wrote:
Scott Parrill schrieb:
I am trying to get Unattended to install the network drivers for a
new DELL M70 laptop during the initial setup and seem to be failing
miserably.
I have created the $oem$/$1 directory under the i386 and placed the
drivers in it. The Linux boot for Unattended finds the drivers and
asks which drivers I would like to install. However, it appears
that the setup routine is not copying the drivers as they should
and thus, the workstation can not re-attach to the network, after
the OS install completes, to continue with the installation
procedure due to lack of network drivers.
When I look at the system drive after the install "completes", I do
not find the expected driver directories.
Does anyone have a suggestion as to what I might be doing wrong?
did you create the directories like:
$oem$/$1/network_card
$oem$/$1/sound_card
$oem$/$1/some_other_card
and added these all directories to unattend.txt (so that Windows
knows about them)?
--
------------------------------------------------------------------------
Scott Parrill | When the legends die, the dreams end.
Area Technology & Communications Manager | When the dreams
end, there is no more greatness.
Wyoming GISciences Center |
University of Wyoming |
Laramie, WY 82071 | When the
Legends Die
PH: (307)766-2524 FAX: (307)766-2744 |
Hal Bowland
[EMAIL PROTECTED] |
------------------------------------------------------- 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
--
Artturi Kyrömies
Movial admin team
mobile: +358 44 5866 377
[EMAIL PROTECTED]
-------------------------------------------------------
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
