Julien TOUCHE <[EMAIL PROTECTED]> writes: > (in french) > le fichier fourni par le fabriquant et que le programme d'installation > essaie d'installer essaye d'utiliser est endommag� ou n'est pas valide: > Types de fichiers manquant ou interdits sp�cifi�s dans la section: > Files.SCSI.perc2 > (translate in english/partial) > the file provided is corrupted or invalid: > Type of files missing or banned in the following section > Files.SCSI.perc2
I suspect the English version is actually "Illegal or Missing File Types Specified in Section Files.SCSI.Name". > [Files.Scsi.perc2] ... > dll = d1, perc2cin.dll > dll = d1, perc2evt.exe The "dll" lines are illegal in txtsetup.oem. See <http://support.microsoft.com/?id=275334>. Of course, that KB article is hideous; it refers to "OEMDIR" and gives some vague description of how to figure out what that is. They say to look at the driver's .inf file and figure out where it wants to install the DLL. Unfortunately, the destination directory is not spelled out; instead, it will be a number like 11 (called a "logical directory identifier", or LDID). This Google search should get you started: http://www.google.com/search?q=ldid+destinationdirs In my experience, you can usually just delete the "dll = ..." lines from your txtsetup.oem file and ignore the OEMDIR stuff. Have fun! - Pat ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
