This isn't entirely accurate. The way I've gotten around it is to modify the hivesft.inf file...
Find a line that says this: HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SystemRoot%\inf" At the end of that line ( without any line breaks, and inside the double quotes ) add your driver paths like this: %SystemDrive%\D\M\AD\7 Where the \D\ is the first sub directory of your $oem$\$1 folder Place a ; (semi-colon) between each entry... and don't forget the final " (double-quote). So, for example, the new line would look like: HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SystemRoot%\inf;%SystemDrive%\D\M\AD\7;%SystemDrive%\D\L\SU\9;%SystemDrive%\D\L\AC\1\ 2K;%SystemDrive%\D\M\N\590SLI\R" I've modified the config.pl under the 'site' folder so that I can specify a 'None' option so that it doesn't modify the oempnpdriverpath at all... This will allow windows to search as many driver paths as you like. ( I've installed 3 of the driver packs in my installations ). Michael Donofrio, Lewis wrote: > > Only using the winnt32 will you get around this 16 bit issue. > > --hence we need a bartpe-unattened-project > ______________________________________________________________________ > Lewis [EMAIL PROTECTED] > Cell: (734) 323-8776 > > > ----- Original Message ----- > From: [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > Cc: benjamin.gabaud <[EMAIL PROTECTED]> > Sent: Thu Apr 12 13:15:10 2007 > Subject: [Unattended] oempnpdriverspath length problem? > > hi to all > > we tried to use and install the driverspack in the $OEM/$1 from > http://driverpacks.net/DriverPacks/ > > but we encountered a well known problem that i already saw in the list > archive : it seems that the length of oempnpdriverspath is too long > (inthe unattend.txt file) and some drivers are not accessed and not > installed > > so we tried to gather all of the drivers into a unique directory > (without subdirectory), but this is not a good method since the > installer asked us the location of some driver files > > i saw this problem have been invoked in a prior thread, but i didn't > understood if there is a good solution > > is there a well known solution in order to solve the oempnpdriverspath > length limit of 4096 (or 1024 chars with winnt.exe) ? > for instance in assembling the drivers hierarchy in a different manner? > > thanks for your help > > -- > Maurice Libes > Tel : +33 (04) 91 82 93 25 Centre d'Oceanologie de Marseille > Fax : +33 (04) 91 82 93 03 UMS2196CNRS- Campus de Luminy, > Case 901 > F-13288 Marseille cedex 9 > > Veuillez noter ma nouvelle adresse ==> [EMAIL PROTECTED] > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > > _______________________________________________ > unattended-info mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/unattended-info > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
