Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

c_20127.nls error after sysprep.

- - - - -

  • Please log in to reply
84 replies to this topic

#26
BSOD2600

BSOD2600
  • Member
  • 3 posts
Yea, I ended up 'fixing' that image by just giving it the Windows XP CD so it could copy all it needed. Then sysprepping again. All fixed.

Would be nice if nlite didn't break this...


How to remove advertisement from MSFN

#27
tappas

tappas
  • Member
  • 2 posts
Sorry to activate this old thread again but the problem is still there in the latest version 1.3RC2.

The Plan: Checking out RIS (Remote Installation Service) that ships with Windows 200(3) Server.

I use my trusted WinXP CD that has all the Service Packs and Patches up to January 2007 included.
Installed in VMware, then created the image with the RIS tool (riprep.exe). It will simply copy the installation to a Windows Server and prepares it for deployment. The image on the server installs without problems back to the PC.

Now, I take the CD from above, I only use it to make unattended install (nothing removed!). Also some of the fixes and tweaks nlite offers. I install one machine then use riprep.exe to image that one.

After it's finished I test the RIS image again. Well, during setup the error message about c_20127.nls pops up. I can click cancel and it's running through. If I click browse it's complaining about a ton of other files.

Nlite is doing something to the files that prompts this error and I have no idea what it is. Maybe it's possible to fix nlite and not use some workarounds?

#28
tappas

tappas
  • Member
  • 2 posts
No reply on how to fix that? It's a really annoying problem :(

#29
JakeLD

JakeLD

    Newbie

  • Member
  • 20 posts
When I created my nLite CD I did remove all the language file I did not need. Maybe it<s related because the missing file is some kind of language font code page. You guys did the same thing ?
Posted Image

#30
EvilBetty

EvilBetty

    Newbie

  • Member
  • 16 posts

Gonna try soon, thx for reporting.



What is the status of this issue? I'm still getting the error as of today on v1.3.5. I started from scratch with a clean config and a clean XP-SP2 source.

Hitting escape gets around it, but beleive it or not I have techs stupid enough to call me every time they see it (after the 3rd email explaining it).

#31
dexter.inside

dexter.inside

    reverse engineering guru

  • Member
  • PipPipPip
  • 331 posts
I add my sysprep drivers in folders in \WINDOWS\Driver Cache\I386. A quick workaround is to also add those files from the original CD to there. If not, there's no problem; sysprep won't break.

Remember - resealing means windows in already installed in there and works, sysprep only does minor changes. If you do something that can actually break the process, you won't be able to complete the initial reseal shutdown.

#32
nuhi

nuhi

    nLite & vLite human.dll

  • Developer
  • 4,348 posts
  • OS:none specified
  • Country: Country Flag

Gonna try soon, thx for reporting.



What is the status of this issue? I'm still getting the error as of today on v1.3.5. I started from scratch with a clean config and a clean XP-SP2 source.

Hitting escape gets around it, but beleive it or not I have techs stupid enough to call me every time they see it (after the 3rd email explaining it).


That's why in the license states "only for personal usage".
http://www.nliteos.com | http://www.vlite.net
Remove components and customize Windows

#33
EvilBetty

EvilBetty

    Newbie

  • Member
  • 16 posts

That's why in the license states "only for personal usage".


Well crap. I'm positive I could get corp to pay for licensing if you wish, otherwise I'm stuck using something else.

Do you have any plans to do this? Any plans on working this issue?

Thanks!

#34
krimson

krimson
  • Member
  • 8 posts
i have just run into this problem yesterday while using an unattended nlited sp2/ie7 XP Pro CD.
im doing mini-setup and reseal.

if i pop the cd in, and browse to d:\i386, it finds the c_20127.nl_ and then continues just fine.
it looks for it in c:\sysprep\i386
so, im going to make a new cd with some new ryan vm updates, and then see if that helps, im also going to dumps stuff from the i386 folder from the nlite'd CD into the c:/sysprep folder to see if i still get that error.. since sysprep will just delete the whole /sysprep folder anyways, it shouldnt affect my ghosting images...

i have the most recent nLite, by the way.

just wanted to let you know the problem still exists.
thanks.

update: also, if you do it like me, and copy the sysprep folder to the C:/ drive, and use the sysprep.inf of whatever.. you can edit where that looks... so, you have a couple choices..
theres an:
[Unattended] InstallFilesPath=C:\sysprep\i386
line there that you could alter for your needs.
that way, right after you sysprep, and before resealing, you can make sure the i386 files are somewhere on the pc, and then point the sysprep.inf to that folder.

im going to keep playing with it to see if i can get a working ghost image. it sucks that nlite breaks it, or sysprep doesnt like something, or whatever, but it shouldnt be too hard to work around.

Edited by krimson, 05 June 2007 - 01:31 PM.


#35
krimson

krimson
  • Member
  • 8 posts
i wanted to bump and add that i tried doing like bigfoot18 said and i added all those files into the folder (i used c:/sysprep/i386 so that it would be deleted after sysprep was done) but now i have a list of over 100 files that are still missing... fonts, .dll's, and .hlp files...

aside from writing down every single file i am missing (which is currently what i am in the process of doing), or adding the entire i386 folder to my sysprep (making my ghost images almost 500mb larger), what other solutions are there?

does anyone know why this is happening, or any way to remedy it? i have about 1000 computers to ghost in the next couple months...

i could just use the original xp sp2 cd, but it needs about 100 updates after installation, and that takes FOREVER...

#36
EvilBetty

EvilBetty

    Newbie

  • Member
  • 16 posts

does anyone know why this is happening, or any way to remedy it? i have about 1000 computers to ghost in the next couple months...



First off, you can always use this for your service packs and hot fixes:
http://www.ryanvm.net/msfn/

Secondly... it seems nuhi is not interested in discussing or working with the enterprise image community. The stance I'm picking up on is that if your getting this error your using sysprep. If your using sysprep, your using this product outside the "personal use" license, and he does not seem to have plans to license this tool otherwise.

It's too bad I know my company would shell out for something like this, and could prevent a lot of system administrators some heart ache and work.

#37
dexter.inside

dexter.inside

    reverse engineering guru

  • Member
  • PipPipPip
  • 331 posts

Secondly... it seems nuhi is not interested in discussing or working with the enterprise image community. The stance I'm picking up on is that if your getting this error your using sysprep. If your using sysprep, your using this product outside the "personal use" license, and he does not seem to have plans to license this tool otherwise.

Well I am interested, and I will be setting up my project on SourceForge soon. I am also one of those frustrated admins :P

#38
Innocent Devil

Innocent Devil

    Senior Member

  • Member
  • PipPipPipPip
  • 633 posts
just For the Info :) :

Probably this issue can be solved by looking at u r setuplog.txt

This logs vary neat scktch of how the setup is performing. btw by some change u can increase the verbosity of the setup logging (i dont know which is , plz let me know)

The setup is done by setupapi.dll.(All setup routines call setupapi procedures)

This dll seeks the help of dosnt.inf,txtsetup.sif and layout.sif to accomplish the task.

It has only directives like processing sif or inf files to get sections,parameters and values
(say winnt.sif ,[unattended] ,Unattended = 1)

"find filenames from dosnet.inf or txtsetup.sif and paths from txtsetup.sif or layout.inf and copy/install it"

By that time we have cd in cd drive and all file paths can be correctly mapped

Now the files are copied to the locations specified in txtsetup.sif
Then builds the bare registry using hive*.inf files
Sets up bootloader,boot.ini
Thus Textmode is over and it reboots...

The setuplog.txt and setupapi.log begins here
The next steps prepare the system to continue install

these steps are similar to "ComplianceCheck" in Vista

After processing paramters from SIF and so and so...

it comes to "BEGIN_SECTION,Initializing regional settings"

here it processes intl.inf, the Language Settings

At this stage the problematic files are being copied.
These goes to nonstandard (not in %path% variable )locations like windows\fonts\,WINDOWS\msagent\intl\,WINDOWS\help\

This is normal scenario wen installing from cd , completes without err as the files are readily availabe from <CDROM>:\I386

##########################################################

The problem :

Sysprep -reseal -mini-setup Scenario:

reads the c:\sysprep.inf file and process the language settings

Now it searches for those files in path specifiedby "InstallFilesPath" of Sysprep.inf

From ref.chm of deploy.cab

InstallFilesPath
Specifies the location of files necessary for installation during Mini-Setup, such as the language files, so that the installation does not stop to prompt for end-user input.

Syntax InstallFilesPath = path_to_installation_files_on_computer
Value path_to_installation_files_on_computer
Valid only for Sysprep.inf.

Example InstallFilesPath = C:\Sysprep\i386

Comments For example, if there is a copy of the \i386 folder in the root of the end user's system drive, you need to specify InstallFilesPath in the Sysprep.inf file so that Setup can find the files, such as:
InstallFilesPath = "C:\Sysprep\i386"
InstallFilesPath does not support environment variables (for example, %SYSTEMDRIVE%). Instead, you must use a valid path with an actual drive letter. Enclose path_to_installation_files_on_computer in quotation marks if it is a long file name.


:angel
Suggestion:

Read documentation CAREFULLY before you do.

B)

Doesn't the OEMs ship their image with C:\sysprep\i386 ?
as, that after running sysprep, the folder get automatically deleted and no space wasted on end user's system.

To Nuhi:

There is nothing wrong with nLite on this issue AFAIK.
Good is that u addded a sysprep compatibility that saved OOBE,
which otherwise will result some weired error i got with some old builds trying to do the same. :wacko:

Edited by Innocent Devil, 08 August 2007 - 06:12 AM.

"The level of security that Vista is trying to achieve to protect video and audio is more extreme than anything the US government has ever considered necessary for protecting its most sensitive classified data."

Read Full Article @ [A Cost Analysis of Windows Vista Content Protection]

Don't be lame [Linux is NOT Windows]

#39
nuhi

nuhi

    nLite & vLite human.dll

  • Developer
  • 4,348 posts
  • OS:none specified
  • Country: Country Flag
Innocent Devil, interesting, I wonder what others think of this.
http://www.nliteos.com | http://www.vlite.net
Remove components and customize Windows

#40
dexter.inside

dexter.inside

    reverse engineering guru

  • Member
  • PipPipPip
  • 331 posts
Did someone use environment variables in sysprep.inf ? I didn't.
That's the point of keeping sysprep in C:\sysprep, unlike Vista/Server 2008 that keeps it in C:\Windows\system32\sysprep

Edited by dexter.inside, 08 August 2007 - 09:45 AM.


#41
JakeLD

JakeLD

    Newbie

  • Member
  • 20 posts
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.
Posted Image

#42
Innocent Devil

Innocent Devil

    Senior Member

  • Member
  • PipPipPipPip
  • 633 posts
So does this solve the problem ??

dexter.inside, plz update "The Art of OEM" with this
"The level of security that Vista is trying to achieve to protect video and audio is more extreme than anything the US government has ever considered necessary for protecting its most sensitive classified data."

Read Full Article @ [A Cost Analysis of Windows Vista Content Protection]

Don't be lame [Linux is NOT Windows]

#43
dexter.inside

dexter.inside

    reverse engineering guru

  • Member
  • PipPipPip
  • 331 posts

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
JakeLD

JakeLD

    Newbie

  • Member
  • 20 posts
Well it did work for me and I've been deploying images for 6 months now. Give a try and let me know.
Posted Image

#45
dexter.inside

dexter.inside

    reverse engineering guru

  • Member
  • PipPipPip
  • 331 posts

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.

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.

Edited by dexter.inside, 09 August 2007 - 11:57 AM.


#46
CrashTGC

CrashTGC
  • Member
  • 2 posts
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
EvilBetty

EvilBetty

    Newbie

  • Member
  • 16 posts

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
dexter.inside

dexter.inside

    reverse engineering guru

  • Member
  • PipPipPip
  • 331 posts

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
EvilBetty

EvilBetty

    Newbie

  • Member
  • 16 posts

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
nuhi

nuhi

    nLite & vLite human.dll

  • Developer
  • 4,348 posts
  • OS:none specified
  • Country: Country Flag
It is about signatures, nlite edits files, it detects that and gets confused. It's not about missing entries or something like that.
http://www.nliteos.com | http://www.vlite.net
Remove components and customize Windows




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN