hyrax Posted June 26, 2004 Posted June 26, 2004 HI,Around a year ago I setup an unattended install of windows with a few app's, installing over a network from a network boot disk. I thought it was time to improve / update.I came across this site and have since updated my unattended installs, however I am having a problem with the $OEM$ directory.When you run setup manager, the $OEM$ directory is placed "inside" the i386 directory ( for a network install ).Does anyone have any idea why this is different to the CDROM based install ( as per this site, ie, $OEM$ along side i386 ).I spend a little while wondering why my $OEM$ wasn't copying over, then realised this to be the problem ( I had the $OEM$ along side the i386 ).Any insights?Regards,ScottHmm.. After finishing another test install, I have come across a problem with $oem$ being under i386. All files under i386 need to be in the 8.3 filename convention, hence all my directories and file names get truncated and do not run.I really just need $oem$ back along side i386... *arrgh*
hyrax Posted June 26, 2004 Author Posted June 26, 2004 http://www.microsoft.com/resources/documen...icb_ui_wbgu.aspWell it seems I have answered my own question. You can bring the $oem$ alongside, but you need to add a line to your unattended.txt file.
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