CrashTGC Posted August 21, 2007 Posted August 21, 2007 Alternate fix:You can also just remove the "InstallFilesPath = C:\Sysprep\i386" line from sysprep.inf altogether. That is assuming that you don't have any source files that you wish for mini setup to copy over during the setup process.
EvilBetty Posted August 21, 2007 Posted August 21, 2007 I'd say this pretty much solves the issue in this topic.I would not say it solves it. It's a pretty nasty fix. It took me a week to sort through all the extra fonts and sys files that it wanted (beyond the above list) to make this work.I would still really like to see this fixed / figured out.
dexter.inside Posted August 21, 2007 Posted August 21, 2007 I'd say this pretty much solves the issue in this topic.I would not say it solves it. It's a pretty nasty fix. It took me a week to sort through all the extra fonts and sys files that it wanted (beyond the above list) to make this work.I would still really like to see this fixed / figured out.From what I've heard from my employers, Microsoft has no interest in perfecting the sysprep technology for anything but Vista related. So I'd say it's up to us... again...
EvilBetty Posted August 21, 2007 Posted August 21, 2007 I'd say this pretty much solves the issue in this topic.I would not say it solves it. It's a pretty nasty fix. It took me a week to sort through all the extra fonts and sys files that it wanted (beyond the above list) to make this work.I would still really like to see this fixed / figured out.From what I've heard from my employers, Microsoft has no interest in perfecting the sysprep technology for anything but Vista related. So I'd say it's up to us... again... Well correct, but this problem is caused by nLite, not by Sysprep.
nuhi Posted August 21, 2007 Posted August 21, 2007 It is about signatures, nlite edits files, it detects that and gets confused. It's not about missing entries or something like that.
CrashTGC Posted August 24, 2007 Posted August 24, 2007 I'd say this pretty much solves the issue in this topic.I would not say it solves it. It's a pretty nasty fix. It took me a week to sort through all the extra fonts and sys files that it wanted (beyond the above list) to make this work.I would still really like to see this fixed / figured out.Try out the alternate fix that I posted above. You don't have to copy any files into sysprep\i386 or anything. Just edit the sysprep.inf file. I'm interested to know if that fix works for others as well.
peridigm Posted August 26, 2007 Posted August 26, 2007 I'd say this pretty much solves the issue in this topic.I would not say it solves it. It's a pretty nasty fix. It took me a week to sort through all the extra fonts and sys files that it wanted (beyond the above list) to make this work.I would still really like to see this fixed / figured out.Try out the alternate fix that I posted above. You don't have to copy any files into sysprep\i386 or anything. Just edit the sysprep.inf file. I'm interested to know if that fix works for others as well.Alternate fix works like a champ.
EvilBetty Posted August 27, 2007 Posted August 27, 2007 I'd say this pretty much solves the issue in this topic.I would not say it solves it. It's a pretty nasty fix. It took me a week to sort through all the extra fonts and sys files that it wanted (beyond the above list) to make this work.I would still really like to see this fixed / figured out.Try out the alternate fix that I posted above. You don't have to copy any files into sysprep\i386 or anything. Just edit the sysprep.inf file. I'm interested to know if that fix works for others as well.Alternate fix works like a champ.Unfortunately I do have many source files in my sysprep folder being fired of by sysprep.
cpratt Posted November 8, 2007 Posted November 8, 2007 The removing the InstallFilesPath line works great for me but I don't use it the path although I might someday.It is amazing to me that when big companies like Symantec and LanDesk recommend using nLite as part of a deployment plan that they don't contribute to the tool.
Innocent Devil Posted December 6, 2007 Posted December 6, 2007 I'd say this pretty much solves the issue in this topic.I would not say it solves it. It's a pretty nasty fix. It took me a week to sort through all the extra fonts and sys files that it wanted (beyond the above list) to make this work.I would still really like to see this fixed / figured out.From what I've heard from my employers, Microsoft has no interest in perfecting the sysprep technology for anything but Vista related. So I'd say it's up to us... again... Well correct, but this problem is caused by nLite, not by Sysprep.I dont Think its a nLite problemi386 (or the source files directory) is supposed to be der (with all files)wen u specify "InstallFilesPath = C:\Sysprep\i386"its setup routinecheck my previous post der is nothing to do with nLite
nodiaque Posted February 20, 2008 Posted February 20, 2008 Add the file kbdest.dll to the list. I just did a sysprep.inf with the file list above (I had some not exist in my xp sp2) and it requested kbdest.dll
iceangel89 Posted February 25, 2008 Posted February 25, 2008 (edited) mmm... i am using nLite 1.4.1 and still having this error ... after sysprep alsoanything i need to remove or keep? if i click cancel, it still worksops i didnt read the last few posts yet? but can some1 tell me what actually needs to be done? abit lazy Edited February 25, 2008 by iceangel89
leozack Posted February 26, 2008 Posted February 26, 2008 I only got asked for c_20127.nls and app850.fon - could I stick those in the sysprep/i386 or do I need to stick all those files mentioned above in there? Or just change a path? a bit confused o_o
iceangel89 Posted February 27, 2008 Posted February 27, 2008 This is how to fix this issueApply this reg file before launching sysprep:ChangeSourceFile.regWindows Registry Editor Version 5.00; Change source path to be c\windows instead of cd-rom; Fix a sysprep bug[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]; Set C:\WINDOWS C:\WINDOWS\I386 C:\WINDOWS\SYSTEM32 C:\WINDOWS\SYSTEM32\DRIVERS as installation sources"Installation Sources"=hex(7):43,00,3a,00,5c,00,57,00,49,00,4e,00,44,00,4f,00,\ 57,00,53,00,00,00,43,00,3a,00,5c,00,57,00,49,00,4e,00,44,00,4f,00,57,00,53,\ 00,5c,00,49,00,33,00,38,00,36,00,00,00,43,00,3a,00,5c,00,57,00,49,00,4e,00,\ 44,00,4f,00,57,00,53,00,5c,00,53,00,59,00,53,00,54,00,45,00,4d,00,33,00,32,\ 00,00,00,43,00,3a,00,5c,00,57,00,49,00,4e,00,44,00,4f,00,57,00,53,00,5c,00,\ 53,00,59,00,53,00,54,00,45,00,4d,00,33,00,32,00,5c,00,44,00,52,00,49,00,56,\ 00,45,00,52,00,53,00,00,00,00,00"SourcePath"="C:\\WINDOWS""ServicePackSourcePath"="C:\\WINDOWS"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion];"RegisteredOrganization"="";"RegisteredOwner"="User""SystemRoot"="C:\\WINDOWS""SourcePath"="C:\\WINDOWS\\i386"sysprep.inf[Unattended]InstallFilesPath="C:\sysprep\i386"i386 folder (total: 249 files):8514fix.fon8514fixe.fon8514fixg.fon8514fixr.fon8514fixt.fon8514oem.fon8514oeme.fon8514oemg.fon8514oemr.fon...For Windows 2000 users, do the same thing except get the requiered files from 2000 and not XP.is this post it? so i run ChangeSourceFile.reg then change InstallFilesPath="C:\sysprep\i386" < not "C:\WINDOWS\Driver Cache" as in the Art of OEM? then the files, ...8514fix.fon8514fixe.fon8514fixg.fon8514fixr.fon8514fixt.fon8514oem.fon8514oeme.fon8514oemg.fon8514oemr.fon...so many?? and i cant seem to find any files i only tried the 1st and *.fon and *.nls and nothing is returned... even on a non nLite disk... mmm or did i nLite that too? ...
leozack Posted February 27, 2008 Posted February 27, 2008 The files are probably on there with their final letter replaced by _ possibly in an unexpanded view, meaning you'd ened to expand the .fon file out of the .fn_ file or something. Or maybe you can just rename it. I haven't tried, this is all getting a bit fiddly :/
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now