MSFN Forum: c_20127.nls error after sysprep. - MSFN Forum

Jump to content


If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
  • 5 Pages +
  • 1
  • 2
  • 3
  • 4
  • 5
  • You cannot start a new topic
  • You cannot reply to this topic

c_20127.nls error after sysprep. Rate Topic: -----

#41 User is offline   JakeLD 

  • Newbie
  • Group: Members
  • Posts: 20
  • Joined: 24-November 06

Posted 08 August 2007 - 11:13 AM

This is how to fix this issue

Apply this reg file before launching sysprep:

ChangeSourceFile.reg
Windows 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.fon
8514fixe.fon
8514fixg.fon
8514fixr.fon
8514fixt.fon
8514oem.fon
8514oeme.fon
8514oemg.fon
8514oemr.fon
8514oemt.fon
8514sys.fon
8514syse.fon
8514sysg.fon
8514sysr.fon
8514syst.fon
85775.fon
85855.fon
85f1257.fon
85s1257.fon
agentdp2.dll
agentdpv.dll
agt0405.dll
agt0405.hlp
agt0406.dll
agt0406.hlp
agt0407.dll
agt0407.hlp
agt0408.dll
agt0408.hlp
agt0409.dll
agt0409.hlp
agt040b.dll
agt040b.hlp
agt040c.dll
agt040c.hlp
agt040e.dll
agt040e.hlp
agt0410.dll
agt0410.hlp
agt0413.dll
agt0413.hlp
agt0414.dll
agt0414.hlp
agt0415.dll
agt0415.hlp
agt0416.dll
agt0416.hlp
agt0419.dll
agt0419.hlp
agt041d.dll
agt041d.hlp
agt041f.dll
agt041f.hlp
agt0816.dll
agt0816.hlp
agt0c0a.dll
agt0c0a.hlp
agtintl.dll
app775.fon
app850.fon
app852.fon
app855.fon
app857.fon
app866.fon
battc.sys
cga40737.fon
cga40850.fon
cga40852.fon
cga40857.fon
cga40866.fon
cga40869.fon
cga40woa.fon
cga80737.fon
cga80850.fon
cga80852.fon
cga80857.fon
cga80866.fon
cga80869.fon
cga80woa.fon
compbatt.sys
coue1257.fon
couf1257.fon
coure.fon
couree.fon
coureg.fon
courer.fon
couret.fon
courf.fon
courfe.fon
courfg.fon
courfr.fon
courft.fon
ctype.nls
c_037.nls
c_10000.nls
c_10006.nls
c_10007.nls
c_10010.nls
c_10017.nls
c_10029.nls
c_10079.nls
c_10081.nls
c_10082.nls
c_1026.nls
c_1250.nls
c_1251.nls
c_1252.nls
c_1253.nls
c_1254.nls
c_1255.nls
c_1256.nls
c_1257.nls
c_1258.nls
c_20127.nls
c_20261.nls
c_20866.nls
c_20905.nls
c_21866.nls
c_28591.nls
c_28592.nls
c_28593.nls
C_28594.NLS
C_28595.NLS
C_28597.NLS
c_28598.nls
c_28599.nls
c_28603.nls
c_28605.nls
c_437.nls
c_500.nls
c_737.nls
c_775.nls
c_850.nls
c_852.nls
c_855.nls
c_857.nls
c_860.nls
c_861.nls
c_863.nls
c_865.nls
c_866.nls
c_869.nls
c_874.nls
c_875.nls
c_932.nls
c_936.nls
c_949.nls
c_950.nls
dos737.fon
dosapp.fon
ega40737.fon
ega40850.fon
ega40852.fon
ega40857.fon
ega40866.fon
ega40869.fon
ega40woa.fon
ega80737.fon
ega80850.fon
ega80852.fon
ega80857.fon
ega80866.fon
ega80869.fon
ega80woa.fon
enum1394.inf
enum1394.sys
ftdisk.sys
geo.nls
isapnp.sys
locale.nls
l_except.nls
l_intl.nls
modern.fon
mouhid.sys
roman.fon
script.fon
sere1257.fon
serf1257.fon
serife.fon
serifee.fon
serifeg.fon
serifer.fon
serifet.fon
seriff.fon
seriffe.fon
seriffg.fon
seriffr.fon
serifft.fon
smae1257.fon
smaf1257.fon
smalle.fon
smallee.fon
smalleg.fon
smaller.fon
smallet.fon
smallf.fon
smallfe.fon
smallfg.fon
smallfr.fon
smallft.fon
sortkey.nls
sorttbls.nls
ssee1257.fon
ssef1257.fon
sserife.fon
sserifee.fon
sserifeg.fon
sserifer.fon
sserifet.fon
sseriff.fon
sseriffe.fon
sseriffg.fon
sseriffr.fon
sserifft.fon
streamci.dll
symbole.fon
unicode.nls
vga.sys
vga737.fon
vga775.fon
vga850.fon
vga852.fon
vga855.fon
vga857.fon
vga860.fon
vga863.fon
vga865.fon
vga866.fon
vga869.fon
vgaf1257.fon
vgafix.fon
vgafixe.fon
vgafixg.fon
vgafixr.fon
vgafixt.fon
vgaoem.fon
vgas1257.fon
vgasys.fon
vgasyse.fon
vgasysg.fon
vgasysr.fon
vgasyst.fon
wst_czec.fon
wst_engl.fon
wst_fren.fon
wst_germ.fon
wst_ital.fon
wst_span.fon
wst_swed.fon



For Windows 2000 users, do the same thing except get the requiered files from 2000 and not XP.


#42 User is offline   Innocent Devil 

  • Senior Member
  • PipPipPipPip
  • Group: Members
  • Posts: 632
  • Joined: 04-February 05

Posted 08 August 2007 - 01:58 PM

So does this solve the problem ??

dexter.inside, plz update "The Art of OEM" with this

#43 User is offline   dexter.inside 

  • reverse engineering guru
  • PipPipPip
  • Group: Members
  • Posts: 331
  • Joined: 19-October 06

Posted 08 August 2007 - 07:28 PM

View PostInnocent Devil, on Aug 8 2007, 10:58 PM, said:

So does this solve the problem ??

dexter.inside, plz update "The Art of OEM" with this


Okay, I will. Just in time, I've been writing a Part 5 that shows simple OEM preinstall on workstations like XP.

#44 User is offline   JakeLD 

  • Newbie
  • Group: Members
  • Posts: 20
  • Joined: 24-November 06

Posted 09 August 2007 - 05:42 AM

Well it did work for me and I've been deploying images for 6 months now. Give a try and let me know.

#45 User is offline   dexter.inside 

  • reverse engineering guru
  • PipPipPip
  • Group: Members
  • Posts: 331
  • Joined: 19-October 06

Posted 09 August 2007 - 11:53 AM

View PostJakeLD, on Aug 9 2007, 02:42 PM, said:

Well it did work for me and I've been deploying images for 6 months now. Give a try and let me know.


It does :thumbup Just tried it on XP SP3.

View PostInnocent Devil, on Aug 8 2007, 10:58 PM, said:

So does this solve the problem ??

dexter.inside, plz update "The Art of OEM" with this


Done.

Also updated the \sysprep\I386 list for XP SP3 v.3180

I'd say this pretty much solves the issue in this topic.

This post has been edited by dexter.inside: 09 August 2007 - 11:57 AM


#46 User is offline   CrashTGC 

  • Group: Members
  • Posts: 2
  • Joined: 21-August 07

Posted 21 August 2007 - 01:51 PM

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.

#47 User is offline   EvilBetty 

  • Newbie
  • Group: Members
  • Posts: 16
  • Joined: 22-February 07

Posted 21 August 2007 - 01:55 PM

View Postdexter.inside, on Aug 9 2007, 12:53 PM, said:

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.

#48 User is offline   dexter.inside 

  • reverse engineering guru
  • PipPipPip
  • Group: Members
  • Posts: 331
  • Joined: 19-October 06

Posted 21 August 2007 - 02:02 PM

View PostEvilBetty, on Aug 21 2007, 10:55 PM, said:

View Postdexter.inside, on Aug 9 2007, 12:53 PM, said:

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... :no:

#49 User is offline   EvilBetty 

  • Newbie
  • Group: Members
  • Posts: 16
  • Joined: 22-February 07

Posted 21 August 2007 - 02:43 PM

View Postdexter.inside, on Aug 21 2007, 03:02 PM, said:

View PostEvilBetty, on Aug 21 2007, 10:55 PM, said:

View Postdexter.inside, on Aug 9 2007, 12:53 PM, said:

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... :no:


Well correct, but this problem is caused by nLite, not by Sysprep.

#50 User is offline   nuhi 

  • ON PAUSE - nLite & vLite human.dll
  • Group: Developers
  • Posts: 4,299
  • Joined: 25-October 03

Posted 21 August 2007 - 02:52 PM

It is about signatures, nlite edits files, it detects that and gets confused. It's not about missing entries or something like that.

#51 User is offline   CrashTGC 

  • Group: Members
  • Posts: 2
  • Joined: 21-August 07

Posted 24 August 2007 - 01:27 PM

View PostEvilBetty, on Aug 21 2007, 03:55 PM, said:

View Postdexter.inside, on Aug 9 2007, 12:53 PM, said:

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.

#52 User is offline   peridigm 

  • Group: Members
  • Posts: 1
  • Joined: 26-August 07

Posted 26 August 2007 - 01:27 PM

View PostCrashTGC, on Aug 24 2007, 02:27 PM, said:

View PostEvilBetty, on Aug 21 2007, 03:55 PM, said:

View Postdexter.inside, on Aug 9 2007, 12:53 PM, said:

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.

#53 User is offline   EvilBetty 

  • Newbie
  • Group: Members
  • Posts: 16
  • Joined: 22-February 07

Posted 27 August 2007 - 09:45 AM

View Postperidigm, on Aug 26 2007, 02:27 PM, said:

View PostCrashTGC, on Aug 24 2007, 02:27 PM, said:

View PostEvilBetty, on Aug 21 2007, 03:55 PM, said:

View Postdexter.inside, on Aug 9 2007, 12:53 PM, said:

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.

#54 User is offline   cpratt 

  • Group: Members
  • Posts: 3
  • Joined: 29-October 07

Posted 08 November 2007 - 04:48 PM

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.

#55 User is offline   Innocent Devil 

  • Senior Member
  • PipPipPipPip
  • Group: Members
  • Posts: 632
  • Joined: 04-February 05

Posted 06 December 2007 - 11:56 AM

View PostEvilBetty, on Aug 22 2007, 01:43 AM, said:

View Postdexter.inside, on Aug 21 2007, 03:02 PM, said:

View PostEvilBetty, on Aug 21 2007, 10:55 PM, said:

View Postdexter.inside, on Aug 9 2007, 12:53 PM, said:

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... :no:


Well correct, but this problem is caused by nLite, not by Sysprep.


I dont Think its a nLite problem
i386 (or the source files directory) is supposed to be der (with all files)
wen u specify "InstallFilesPath = C:\Sysprep\i386"
its setup routine
check my previous post der is nothing to do with nLite

#56 User is offline   nodiaque 

  • Code Master
  • Pip
  • Group: Members
  • Posts: 98
  • Joined: 21-July 04

Posted 20 February 2008 - 05:45 PM

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

#57 User is offline   iceangel89 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 453
  • Joined: 10-February 07
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 25 February 2008 - 01:30 AM

mmm... i am using nLite 1.4.1 and still having this error ... after sysprep also

Posted Image

anything i need to remove or keep? if i click cancel, it still works

ops i didnt read the last few posts yet? but can some1 tell me what actually needs to be done? abit lazy :P

This post has been edited by iceangel89: 25 February 2008 - 02:58 AM


#58 User is offline   leozack 

  • Junior
  • Pip
  • Group: Members
  • Posts: 85
  • Joined: 01-December 07

Posted 26 February 2008 - 09:59 AM

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

#59 User is offline   iceangel89 

  • Advanced Member
  • PipPipPip
  • Group: Members
  • Posts: 453
  • Joined: 10-February 07
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 26 February 2008 - 10:36 PM

View PostJakeLD, on Aug 9 2007, 01:13 AM, said:

This is how to fix this issue

Apply this reg file before launching sysprep:

ChangeSourceFile.reg
Windows 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.fon
8514fixe.fon
8514fixg.fon
8514fixr.fon
8514fixt.fon
8514oem.fon
8514oeme.fon
8514oemg.fon
8514oemr.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.fon
8514fixe.fon
8514fixg.fon
8514fixr.fon
8514fixt.fon
8514oem.fon
8514oeme.fon
8514oemg.fon
8514oemr.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? ...

#60 User is offline   leozack 

  • Junior
  • Pip
  • Group: Members
  • Posts: 85
  • Joined: 01-December 07

Posted 27 February 2008 - 11:02 AM

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 :/

Share this topic:


  • 5 Pages +
  • 1
  • 2
  • 3
  • 4
  • 5
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy