Chuckler Posted August 23, 2004 Share Posted August 23, 2004 Hi, I've done a lot of reading, but I'm unable to determine why my $OEM$ directory (and therefore Cmdlines.txt) are not copying to the workstation.I've followed the guide at unattended.msfn.org and done quite a lot of reading in the forums - I even have OemPreinstall set to Yes already ;SetupMgrTag[Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes"[Unattended] UnattendMode=FullUnattended OemPreinstall=Yes UnattendSwitch=Yes OemSkipEula=Yes TargetPath=\WINDOWS OemFilesPath="$OEM$" OemPnPDriversPath="Drivers\002_Nvidia_45_23;Drivers\004_sound" DriverSigningPolicy=Ignore [IEPopupBlocker] AllowedSites=www.msfn.org;www.amazon.com BlockPopups=Yes FilterLevel=Medium ShowInformationBar=Yes[GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO AutoLogon=Yes AutoLogonCount=1 OEMSkipRegional=1 TimeZone=260 OemSkipWelcome=1[UserData] ProductID=xxx FullName=xxx OrgName=xxx ComputerName=*[Display] BitsPerPel=32 Xresolution=1024 YResolution=768 Vrefresh=85[TapiLocation] CountryCode=61 Dialing=Tone AreaCode=7 LongDistanceAccess="0"[RegionalSettings] LanguageGroup=1 SystemLocale=00000c09 UserLocale=00000c09 InputLocale=0c09:00000409[FavoritesEx] Title1="MSFN" URL1="http://www.msfn.org"[Branding] BrandIEUsingUnattended=Yes[URL] Home_Page=about:blank[Proxy] Proxy_Enable=0 Use_Same_Proxy=1[GuiRunOnce][Identification] JoinWorkgroup=WORKGROUP[Networking] InstallDefaultComponents=No[NetAdapters] Adapter1=params.Adapter1[params.Adapter1] INFID=*[NetProtocols] MS_TCPIP=params.MS_TCPIP[params.MS_TCPIP] DNS=Yes UseDomainNameDevolution=No EnableLMHosts=Yes AdapterSections=params.MS_TCPIP.Adapter1[params.MS_TCPIP.Adapter1] SpecificTo=Adapter1 DHCP=Yes WINS=No NetBIOSOptions=0Any help with this is appreciated. Link to comment Share on other sites More sharing options...
MCT Posted August 23, 2004 Share Posted August 23, 2004 is your $OEM$ directory capitalized? it probly should be if it isnt, windows has some weird probs like that & the directory structure is correct? Link to comment Share on other sites More sharing options...
jrzycrim Posted August 23, 2004 Share Posted August 23, 2004 I've never needed this: OemFilesPath="$OEM$". By default, $OEM$ is used. Try removing that from your winnt.sif. To be honest, I'm not sure where setup will look if you just specify $OEM$ as the path.Edit: Looking at a couple of other Winnt.SIFs, I've seen OemFilesPath="..\$OEM$". I suppose you could either try that or just remove the line altogether... Link to comment Share on other sites More sharing options...
Chuckler Posted August 23, 2004 Author Share Posted August 23, 2004 I've never needed this: OemFilesPath="$OEM$". By default, $OEM$ is used. Try removing that from your winnt.sif. To be honest, I'm not sure where setup will look if you just specify $OEM$ as the path.Edit: Looking at a couple of other Winnt.SIFs, I've seen OemFilesPath="..\$OEM$". I suppose you could either try that or just remove the line altogether...I've also tried it with no OEMFilesPath line, and with the ..\$OEM$ line you mentioned. It's SP2 slipstreamed - anyone have trouble with that? Link to comment Share on other sites More sharing options...
MCT Posted August 23, 2004 Share Posted August 23, 2004 ya, it will look INSIDE the folder oem is in (i believe) Link to comment Share on other sites More sharing options...
Chuckler Posted August 23, 2004 Author Share Posted August 23, 2004 is your $OEM$ directory capitalized? it probly should be if it isnt, windows has some weird probs like that & the directory structure is correct?99% sure it is, I'll post a screenshot of the directory structure in a second ... Link to comment Share on other sites More sharing options...
jrzycrim Posted August 23, 2004 Share Posted August 23, 2004 Hmm. Does the rest of your winnt.sif work correctly? ProductID and all that? Link to comment Share on other sites More sharing options...
Chuckler Posted August 23, 2004 Author Share Posted August 23, 2004 Link to comment Share on other sites More sharing options...
Chuckler Posted August 23, 2004 Author Share Posted August 23, 2004 (edited) Hmm. Does the rest of your winnt.sif work correctly? ProductID and all that?Yes. Everything else is totally automated.EDIT: not totally true, I do the partitioning etc by myself, I meant that the GUI setup is all automated. Edited August 23, 2004 by Chuckler Link to comment Share on other sites More sharing options...
jrzycrim Posted August 23, 2004 Share Posted August 23, 2004 Well crikey. I'm stumped. Maybe someone else will find something. In the meantime, If I think of something, I'll post it. Link to comment Share on other sites More sharing options...
Chuckler Posted August 23, 2004 Author Share Posted August 23, 2004 Well crikey. I'm stumped. Maybe someone else will find something. In the meantime, If I think of something, I'll post it.As unbelievable as this may sound, I just repacked the ISO and this time it worked ??Nothing else changed. Wierd. Anyway, thanks for the help! Link to comment Share on other sites More sharing options...
jrzycrim Posted August 23, 2004 Share Posted August 23, 2004 Great. Glad you got it worked out. Not hard to believe. Flukes like that happen. Guess the last ISO was bad in some way. Link to comment Share on other sites More sharing options...
Alanoll Posted August 23, 2004 Share Posted August 23, 2004 you could have used the wrong file format when creating the ISO. Normal ISO-9660 will turn the $OEM$ into _OEM_ Link to comment Share on other sites More sharing options...
MHz Posted August 23, 2004 Share Posted August 23, 2004 Check this entryOemPnPDriversPath="Drivers\002_Nvidia_45_23;Drivers\004_sound"I believe that you are making 2 strings into 1Try this insteadOemPnPDriversPath="Drivers\002_Nvidia_45_23";"Drivers\004_sound"I think that the inverted comma's left out maybe causing the problem? Link to comment Share on other sites More sharing options...
oTec Posted September 15, 2004 Share Posted September 15, 2004 i've had the same problem m$ told me to not put the oemfilespath inside the winnt.sif file and create the $OEM$ with a $1 underneath it and put the stuff i want to copy to machine under the dir $1 thats working then.i.e. $OEM$ -> $1 -> Install -> Settings.vbsA folder called Install will be on the root c:\ after installing with the slipstreamed sp2 cd. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now