On Sat, Sep 11, 2004 at 10:17:26AM -0400, Patrick J. LoPresti wrote: > > 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.
without, it fails just after disk c check: la valeur suivante dans le fichier .SIF utilis� par le programme d'installation est endomag� ou manquante: Valeur 0 � la ligne de la section [SourceDisksFiles] avec la cl� "sp4.cab" it is the same with OEMDIR (value 11 which is system dir from http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/windows2000/techinfo/reskit/en-us/ierk/AppxH_b.asp, but which one SystemRoot SystemRoot\system Systemroot\system32 ??? it fails with the same error with file in $oem$\$$\systemXX i also try to copy at hand files from $win_nt$.~ls\$oem$\$$ to $win_nt$.~bt\systemXX without success ... > > Have fun! > fun of funky ms & dell engineers ... Regards Julien ------------------------------------------------------- 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
