If your using driverpacks, then stick to using they're method, and everything works great. That way it copies all the drivers compressed instead of extracted, since it's faster copying *297.34 MB* compared to copying *1714.7 MB* if your using all the drivers. Also, you have to worry about filling up the 4 gb partition that initially gets created and everything gets copied to. I've been using method 2, with RunOnceEx as the finisher method for at least a year now.
Maurice Libes wrote: > 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 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ unattended-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-info
