Help - Search - Members - Calendar
Full Version: c_20127.nls error after sysprep.
MSFN Forums > Member Contributed Projects > nLite
Pages: 1, 2

   
Google Internet Forums Unattended CD/DVD Guide
mjerris
When I install from an Nlite created xp pro w/ sp2 cd and later run sysprep on that install, on first boot I get an error related to the c_20127.nls file not being found, if I browse to the system 32 directory the file is there and the install conitnues with a few more similar errors, all with files on the local machine properly, and the minisetup completes normally. This error does not occour on an install made with a normal slipstreamed xp2 CD.

Any help would be appretiated.

Thanks
Mike
mjerris
Has anyone else seen this issue. I continue to have this issue after minisetup is run after a sysprep from an nlite install.

Mike
camoman
I am getting the same error.. has anyone found a fix yet?
nuhi
I never tried sysprep so it would speed things up if you explain to me how to reproduce the problem in short.

Thanks
camoman
Well I slipstreamed sp2 in with XP and all the hotfixes using nlite, took out movie maker and a few other things. Then used that CD to load a laptop with XP at which point I ran sysprep using reseal option.. upon booting back up you get numerous erros .. I have talked to a few people now that have had the same problem..
shortie
Hi nuhi, hi all:

sysprep is used for cloning, making a single installation usable on several different computers withput having to mess around with SIDs etc.
Myself I use sysprep in very large evnviroments using the same sysprepped image on laptops and desktops.
This is what you do:

Install Windows XP with everything needed on a desktop (laptops don't work for that), use FAT32 so you can mofify things in the image, Customize everything in the default userprofile, so you make sure that every new user get it. When this is done, create an image. This is helpful if you want a strting point later on, e.g. update software or drivers, hotfixes.
When done start up windows xp open a dos-prompt:
change into your sysprep folder
now:
sysprep -bmsd (creates the mass-storage section)
convert c: /FS:NTFS (say no, and the yes, so it will be converted after the next reboot
sysprep -clean (all drivers, etc will be unloaded)
sysprep -mini -quiet -reseal ( this will kick out the sid's, and force a mini-setup when the maschine is powered up again.

When sysprep is finished, the pc will be shutdown. Now take a new image. This image can now be cloned onto the maschine.

If you power the pc up, it converts the partition, reboots, and then after aminute or two it asks for the files needed.


If you have any questions feel free to contact me.


shortie


P.s.: In oder to use the image on laptops and desktops you must change the computer-type two Advanced configuration and the IDE controller to standard ide.
nuhi
Fixed it...you need to selected in Compatibility Wizard Windows Activation and I added few more files to keeping...changed the title...all in all wait next version and thank you smile.gif
camoman
When will a new version with this ficx be released?
nuhi
camoman, have you tested it with nlite 1.0b1 ?
shortie
Hi there,

as you may remember I got the same probs and with your latest version it works!!

No probs at all!

Reagrds,
shortie

P.s.: By the way nltie is not just great it is awesome!!!!
hardwaregeek
QUOTE (nuhi @ May 17 2005, 09:44 AM) *
Fixed it...you need to selected in Compatibility Wizard Windows Activation and I added few more files to keeping...changed the title...all in all wait next version and thank you smile.gif



Hi nuhi! Great work!
You make my life easier! Nlite is the best thing ever happen to me.
But I still have the problem stated above. I added 39 hotfixes directly into nlite. Everything is fine if I don't sysprep my pc to make image for rest of the computers. But after I run sysprep and reboot I have c_20127.nls file missing error. When I press cancel, it went through fine. But it is a big delay for me when I deploy 100 computers coz I have to press cancel for each pc. I used RC1 through RC6 and I selected the compatilibity for windows activation and sysprep check box. Any advice for me please. Many Thanks
nuhi
Yup I know that sysprep bug is still there on reseal.

All you "need" to do is to point it to the CD or windows subfolders for missing files, they are there, it's just it don't see it...signature issue.

Since sysprep is mainly used in companies and other commercial branches and they never donated me anything I don't care either.

Don't get me wrong, it's not like I'm holding the fix, it is hard, I tried many times and decided it's not worth the hassle...like the dos winnt.exe bug. (winnt32 works ok)
hardwaregeek
You are absolutely right!!!!!!!!!! Thank you very much for your effort. thumbup.gif
Telenut
QUOTE (nuhi @ Feb 2 2006, 10:45 PM) *
Yup I know that sysprep bug is still there on reseal.

All you "need" to do is to point it to the CD or windows subfolders for missing files, they are there, it's just it don't see it...signature issue.

Since sysprep is mainly used in companies and other commercial branches and they never donated me anything I don't care either.

Don't get me wrong, it's not like I'm holding the fix, it is hard, I tried many times and decided it's not worth the hassle...like the dos winnt.exe bug. (winnt32 works ok)


Hi,
I completely understand that! Paying lots of money for usless crap is no problem here, but donations... how how.. Anyway, I still don't use nLite at work since the sysprep problem is still there. If it is fixed, I could send a link to this thread to the boss tongue.gif
On the other hand, I don't work at a commercial company, but a university hospital.
sflesch
nuhi, I saw another article (something about Active Directory) you mentioned the c_20127.nls error would be fixed and we should look for 'sysprep fixed' in the changelog. I noticed it appears in the latest version (07?). My question though:

Do I need to do everything from scratch, or can I just take my existing N-Lite prepped files and run the latest version.

Thanx
Sean
nuhi
sflesch, from scratch.
And some reported that networked install will still have some issues with sysprep.
I tested the reseal without problem.
edenkers
You can get around this problem by creating a i386 folder in the sysprep folder and then put the files that are being requested in that folder. You can get the files from the "nlited" windows XP folder or from the CD that you burned.

e
nuhi
edenkers, does that means that this problem is still present? Which files did you miss and could you please explain in short how to repeat it?
ChamPro
Unfortunately, I'm still having this (similar) problem with reseal. I just keep getting the errors for missing files. It's starts off with the c_20127.nls which you can find already installed on the harddrive and the rest of the files are to be found in the i386 directory on the WinLite CD.

I made sure I checked the box on the Compatibility box for Windows Activation and Sysprep, but it didn't change anything. Is there some setting that I've chosen that screwed up everything?

Here's a incomplete list of those missing files (I just got tired of listing them by using a floppy):
CODE
2,520 8514FIX.FO_
3,146 8514OEM.FO_
2,802 8514SYS.FO_
4,800 AGT0407.DL_
4,828 AGT040C.DL_
4,450 AGT0410.DL_
10,991 APP850.FO_
2,741 CGA40850.FO
2,633 CGA40WOA.FO
2,307 CGA80850.FO
2,289 CGA80WOA.FO
5,558 COURE.FO_
7,168 COURF.FO_
66,082 c_20127.nls
11,099 DOSAPP.FO_
3,027 EGA40850.FO
2,977 EGA40WOA.FO
2,445 EGA80850.FO
2,463 EGA80WOA.FO
14,881 SERIFE.FO_
18,135 SERIFF.FO_
7,419 SMALLE.FO_
7,399 SMALLF.FO_
14,686 SSERIFE.FO_
18,028 SSERIFF.FO_
2,467 VGA850.FO_
2,445 VGA860.FO_
2,481 VGA863.FO_
2,473 VGA865.FO_
2,089 VGAFIX.FO_
2,335 VGASYS.FO_


These are my options with sysprep:
CODE
Use Mini-Setup
Detect non-plug and play hardware
Reseal


This is my nLite setup:
CODE
[Main]
Env = 1.2.1 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 2
Target = Windows XP Professional SP:2 - 5.1.2600.2180 - English (United States)

[Tasks]
Remove Components
Unattended Setup
Hotfixes and Update Packs
Tweaks
Create a Bootable ISO
Options

[Components]
;# Applications #
Briefcase
;# Network #
MSN Explorer
Windows Messenger
;# Operating System Options #
Blaster/Nachi removal tool
Tour
;# Compatibility #

[KeepFiles]
msconfig.exe

[RemoveFiles]
clock.avi

[Options]
CABNoHigh
ClassicSetup
ProfilesDir = "%SystemDrive%\Documents and Settings"
TargetPath = "WINDOWS"
temp_dir = %USERPROFILE%\Local Settings\Temp
AdvTweaks
NoISOPreset

[Patches]
DoUxTheme
DoSFC

[Services2]

[Tweaks]
Desktop-Internet Explorer icon-Hide
Explorer-Show Statusbar in all windows
Explorer-Show the full path in the Address Bar
Internet Explorer-Disable Market Place bookmark
Internet Explorer-Disable Media Player 6.4 created bookmarks
Internet Explorer-Disable Outlook Express link creation
Internet Explorer-Enable Google URL-Search
Internet Explorer-Set Homepage-www.google.com
Internet Explorer-Set IE-Cache limit to-200 MB (default)
Internet Explorer-Set popup-blocker to high
Privacy-Remove Alexa
Start Menu-Control Panel-Display as a menu
Taskbar-Lock the Taskbar-Yes
Visual Effects-Menu animation-Disable
Visual Effects-Smooth edges of screen fonts-ClearType

[Unattended]
ComputerType = Automatic
MaximumDataStorePercentOfDisk = 10
RestorePointLife = 30
DesktopTheme = Windows XP style|Silver|Normal size
IISInstall = 2
AutoUpdates = 1
AutoUDay = 4
AutoUHour = 3
ProgFilesPath = "\Program Files"

[GuiRunOnce]

[Drivers]

[Hotfixes]
HotfixingReports
WindowsXP-KB873339-x86-ENU.exe
WindowsXP-KB885835-x86-ENU.exe
WindowsXP-KB885836-x86-ENU.exe
WindowsXP-KB886185-x86-enu.exe
WindowsXP-KB887472-x86-enu.exe
WindowsXP-KB888302-x86-ENU.exe
WindowsXP-KB890046-x86-ENU.exe
WindowsXP-KB890859-x86-ENU.exe
WindowsXP-KB891781-x86-ENU.exe
WindowsXP-KB893756-x86-ENU.exe
WindowsInstaller-KB893803-v2-x86.exe
WindowsXP-KB894391-x86-ENU.exe
WindowsXP-KB896358-x86-ENU.exe
WindowsXP-KB896423-x86-ENU.exe
WindowsXP-KB896424-x86-ENU.exe
WindowsXP-KB896428-x86-ENU.exe
WindowsXP-KB898461-x86-ENU.exe
WindowsXP-KB899587-x86-ENU.exe
WindowsXP-KB899589-x86-ENU.exe
WindowsXP-KB899591-x86-ENU.exe
WindowsXP-KB900725-x86-ENU.exe
WindowsXP-KB901017-x86-ENU.exe
WindowsXP-KB901214-x86-ENU.exe
WindowsXP-KB902400-x86-ENU.exe
WindowsXP-KB904706-v2-x86-ENU.exe
WindowsXP-KB905414-x86-ENU.exe
WindowsXP-KB905749-x86-ENU.exe
WindowsXP-KB908519-x86-ENU.exe
WindowsXP-KB908531-v2-x86-ENU.exe
WindowsXP-KB910437-x86-ENU.exe
WindowsXP-KB911280-v2-x86-ENU.exe
WindowsXP-KB911562-x86-ENU.exe
WindowsMedia-KB911564-x86-ENU.exe
WindowsXP-KB911567-x86-ENU.exe
WindowsXP-KB911927-x86-ENU.exe
WindowsXP-KB912919-x86-ENU.exe
WindowsXP-KB913580-x86-ENU.exe
WindowsXP-KB914388-x86-ENU.exe
WindowsXP-KB914389-x86-ENU.exe
WindowsXP-KB916595-x86-ENU.exe
WindowsXP-KB917344-x86-ENU.exe
WindowsXP-KB917422-x86-ENU.exe
WindowsXP-KB917953-x86-ENU.exe
WindowsXP-KB918439-x86-ENU.exe
WindowsXP-KB918899-x86-ENU.exe
WindowsXP-KB919007-x86-ENU.exe
WindowsXP-KB920214-x86-ENU.exe
WindowsXP-KB920670-x86-ENU.exe
WindowsXP-KB920683-x86-ENU.exe
WindowsXP-KB920685-x86-ENU.exe
WindowsXP-KB921398-x86-ENU.exe
WindowsXP-KB921883-x86-ENU.exe
WindowsXP-KB922582-x86-ENU.exe
WindowsXP-KB922616-x86-ENU.exe
WindowsXP-KB922819-x86-ENU.exe
WindowsXP-KB923191-x86-ENU.exe
WindowsXP-KB923414-x86-ENU.exe
WindowsXP-KB924191-x86-ENU.exe
WindowsXP-KB924496-x86-ENU.exe
WindowsXP-KB925486-x86-ENU.exe
RVMAddonsWGA_1.5.708.0.7z
WMP11.7z
ProgramAddons Firefox 2.0.cab
aawsepersonal.cab
spybotsd14.cab


And this is my sysprep.inf:
CODE
;SetupMgrTag
[Unattended]
    InstallFilesPath=C:\sysprep\i386
    TargetPath=\WINDOWS

[GuiUnattended]
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    OEMDuplicatorstring="DUIRT WinLite 20061118"
    TimeZone=35
    AutoLogon=Yes
    AutoLogonCount=1

[UserData]
    ProductKey=REMOVED
    FullName=""
    OrgName="Drexel University"

[TapiLocation]
    CountryCode=1

[Identification]
    JoinWorkgroup=DREXEL

[Networking]
    InstallDefaultComponents=Yes

[RegionalSettings]
    LanguageGroup=1
    Language=00000409

[Branding]
    BrandIEUsingUnattended=Yes

[Proxy]
    Proxy_Enable=0
    Use_Same_Proxy=0
nuhi
Gonna try soon, thx for reporting.
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 sad.gif
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
QUOTE (nuhi @ Nov 20 2006, 04:12 PM) *
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
QUOTE (EvilBetty @ May 24 2007, 04:21 PM) *
QUOTE (nuhi @ Nov 20 2006, 04:12 PM) *
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
QUOTE (nuhi @ May 25 2007, 03:47 PM) *
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.
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
QUOTE (krimson @ Jun 11 2007, 10:34 AM) *
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
QUOTE (EvilBetty @ Jun 11 2007, 08:41 PM) *
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 tongue.gif
Innocent Devil
just For the Info smile.gif :

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.


angel.gif
Suggestion:

Read documentation CAREFULLY before you do.

cool.gif

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.gif
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
JakeLD
This is how to fix this issue

Apply this reg file before launching sysprep:

ChangeSourceFile.reg
CODE
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
CODE
[Unattended]
InstallFilesPath="C:\sysprep\i386"


i386 folder (total: 249 files):

CODE
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.
Innocent Devil
So does this solve the problem ??

dexter.inside, plz update "The Art of OEM" with this
dexter.inside
QUOTE (Innocent Devil @ Aug 8 2007, 10:58 PM) *
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.
JakeLD
Well it did work for me and I've been deploying images for 6 months now. Give a try and let me know.
dexter.inside
QUOTE (JakeLD @ Aug 9 2007, 02:42 PM) *
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.gif Just tried it on XP SP3.

QUOTE (Innocent Devil @ Aug 8 2007, 10:58 PM) *
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.
CrashTGC
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
QUOTE (dexter.inside @ Aug 9 2007, 12:53 PM) *
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
QUOTE (EvilBetty @ Aug 21 2007, 10:55 PM) *
QUOTE (dexter.inside @ Aug 9 2007, 12:53 PM) *
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.gif
EvilBetty
QUOTE (dexter.inside @ Aug 21 2007, 03:02 PM) *
QUOTE (EvilBetty @ Aug 21 2007, 10:55 PM) *
QUOTE (dexter.inside @ Aug 9 2007, 12:53 PM) *
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.gif


Well correct, but this problem is caused by nLite, not by Sysprep.
nuhi
It is about signatures, nlite edits files, it detects that and gets confused. It's not about missing entries or something like that.
Google Internet Forums Unattended CD/DVD Guide
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.