%OEM% Folder Location in XP (i386 or root?)

[ScottCooperDotNet]

I've been working on an OEM version of XP that installs some extra files (in this case, Windows Themes) but have run into conflicting information regarding the location of the $OEM$ folder. Since I am installing off CD, it only works when $OEM$ is at the same level (root) of the CD. Yet some places, including Microsoft's KB say it should be inside i386 for certain installation methods. Can you explain the details?

[Martin H]

As the MSFN 'Unattended Guide' states, then the $OEM$ folder should be in the root for CD based installs...

The page you're linking too, and which states to place $OEM$ under I386, is reffering to network based installations only...

[Bezalel]

I've been working on an OEM version of XP that installs some extra files (in this case, Windows Themes) but have run into conflicting information regarding the location of the $OEM$ folder. Since I am installing off CD, it only works when $OEM$ is at the same level (root) of the CD. Yet some places, including Microsoft's KB say it should be inside i386 for certain installation methods. Can you explain the details?

It depends how you are starting the setup. If you are starting the setup by booting from the CD the $OEM$ folder should be in the root of the CD. If you start setup by running winnt32 then the $OEM$ folder should be in I386.

[komsboy_more]

It depends how you are starting the setup. If you are starting the setup by booting from the CD the $OEM$ folder should be in the root of the CD. If you start setup by running winnt32 then the $OEM$ folder should be in I386.

hey man ....but i think different ..... if you use an answer file ....you can place your $OEM$ folder in the root...and use it from 2 different way :

1st . - if you want to install a fresh version of your Windows XP ...place your $OEM$ folder in root then place answe file(WINNT.SIF) in i386 folder

2nd . - if you want to install via winnt32.exe (under another windows running) use this command after winnt32.exe ....it should be work for you

for example if your CD-Drive is "d:" :

d:\i386\winnt32.exe /unattend0:i386\winnt.sif

explain of command :

/unattended : say wiinnt32.exe that be run in unattended mode

:\i386\winnt.sif : set the way of answer file .

my recommended answer file is here for installing xp:

----------------------------------

;SetupMgrTag

[Data]

AutoPartition=0

MsDosInitiated=0

UnattendedInstall=Yes

AutomaticUpdates=No

[unattended]

UnattendMode=FullUnattended

FileSystem=*

OemSkipEula=Yes

OemPreinstall=Yes

TargetPath=\WINDOWS

Repartition=No

UnattendSwitch=yes

WaitForReboot=No

DriverSigningPolicy=Ignore

NonDriverSigningPolicy=Ignore

AutoActivate=Yes

NoWaitAfterTextMode=1

NoWaitAfterGUIMode=1

Hibernation=1

[systemRestore]

DisableSR=1

CreateFirstRunRp=0

[GuiUnattended]

AdminPassword=*

EncryptedAdminPassword=NO

OEMSkipRegional=1

OemSkipWelcome=1

TimeZone=160

[userData]

ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

FullName="Farzad.M."

OrgName="F.M."

ComputerName=*

[TapiLocation]

CountryCode=98

Dialing=Tone

AreaCode=021

[RegionalSettings]

LanguageGroup=1,7,11

Language=00000429

SystemLocale=00000429

UserLocale=00000429

InputLocale=0429:00000429

[Display]

Xresolution=1024

YResolution=768

BitsPerPel=32

[Networking]

InstallDefaultComponents=Yes

[identification]

JoinWorkgroup=WORKGROUP

[branding]

BrandIEUsingUnattended=Yes

Home_Page=http://www.google.com

Search_Page=http://www.google.com

[Proxy]

Proxy_Enable=0

Use_Same_Proxy=0

[shell]

CustomDefaultThemeFile="%SystemRoot%\Resources\Themes\VistaXP.theme"

----------------------------------

you can change tapi location and regional language and other setting by your self

Good luck man

Edited June 4, 2008 by komsboy_more

[cdob]

Since I am installing off CD, it only works when $OEM$ is at the same level (root) of the CD.

As Martin H wrote already: KB314479 refers to RIS installations. This does not match CD installation.

Generally at CD boot: $OEM$ goes beside I386.

This maybe at root of the CD.

At multi boot solutions, this maybe a subdirectory. http://flyakite.msfn.org/

In addition there is another exeption:

Textmode drivers at winnt.sif [MassStorageDrivers]

http://www.msfn.org/board/TEXTMODE-MassSto...hod-t19792.html

Textmode drivers goes twice to CD:

$OEM$\TEXTMODE\

I386\$OEM$\

Be aware I386\$OEM$\ are read early at boot.

ISO9660 file system is used. Char $ is a invalid char at ISO9660 Level 1, violade ISO9660 names.

ISO9660 name has to be $OEM$, not _OEM_