[JakeLD]

I'm working on XP SP2 master image thats fits on all PCs possible and i'm having the same issue. I build my image using the last version of nLite, I did removed all unused language files to make the image smaller. Maybe its linked with the issue ? Did you guys removed some language files 2 ?

Also I found on some forums that if you install your OS from a CD the source path in regedit will be D: (CD-Rom letter), but is has to be C: since your making a master image and the XP CD you used early w'ont be loaded to the PC. SO by changing the value to C:, the c_20127.nls file should be found. I'm testing it write now, I'll get back to you.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
"SourcePath"="C:\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"SystemRoot"="C:\\WINDOWS"
"SourcePath"="C:\\"
"PathName"="C:\\WINDOWS"

[BSOD2600]

Just a ditto post. After sysprep'ing an image built with nLite 1.2.1 and XP+SP2, I'm getting a message about a missing c_20127.nls too.

[bigfoot18]

I have this problem also with my images.
To fix it , I did the following:

Create a folder called I386.
Put the following files in it:

8514fix.fon
8514oem.fon
8514sys.fon
app850.fon
cga40850.fon
cga40woa.fon
cga80850.fon
cga80woa.fon
coure.fon
courf.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
dosapp.fon
ega40850.fon
ega40woa.fon
ega80850.fon
ega80woa.fon
geo.nls
locale.nls
l_except.nls
l_intl.nls
serife.fon
seriff.fon
smalle.fon
smallf.fon
sortkey.nls
sorttbls.nls
sserife.fon
sseriff.fon
symbole.fon
unicode.nls
vga850.fon
vga860.fon
vga863.fon
vga865.fon
vgafix.fon
vgaoem.fon
vgasys.fon

Make sure to remove the hidden attribute on the files.

In the sysprep. inf add the following line to the [Unattended] section:
InstallFilesPath=C:\i386

That should fix the error messages after syspreping.

[BSOD2600]

Well I added all of those files you suggested bigfoot18, but now it says its missing agt0407.dll.

What the heck are all these missing files related to?
Why does nlite break sysprep?

[bigfoot18]

Oops forgot to add the msagent files to that directory. I took them out of the list because I thought they were specific to what i was removing.. Guess not.
got to windows\msagent\intl and copy all the dlls from there to the i386 folder.
that should fix your problem.
I dont have a clue why it breaks sysprep, just how to work around it.

[BSOD2600]

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

[tappas]

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?

[tappas]

No reply on how to fix that? It's a really annoying problem

[JakeLD]

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 ?

[EvilBetty]

nuhi, on Nov 20 2006, 04:12 PM, said:

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).

[dexter.inside]

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.

[nuhi]

EvilBetty, on May 24 2007, 04:21 PM, said:

nuhi, on Nov 20 2006, 04:12 PM, said:

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".

[EvilBetty]

nuhi, on May 25 2007, 03:47 PM, said:

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!

[krimson]

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.

This post has been edited by krimson: 05 June 2007 - 01:31 PM

[krimson]

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

[EvilBetty]

krimson, on Jun 11 2007, 10:34 AM, said:

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.

[dexter.inside]

EvilBetty, on Jun 11 2007, 08:41 PM, said:

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

[Innocent Devil]

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

Quote

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.

Suggestion:

Read documentation CAREFULLY before you do.



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.

This post has been edited by Innocent Devil: 08 August 2007 - 06:12 AM

[nuhi]

Innocent Devil, interesting, I wonder what others think of this.

[dexter.inside]

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

This post has been edited by dexter.inside: 08 August 2007 - 09:45 AM