mediapla Posted November 11, 2004 Posted November 11, 2004 It is possible to have only one $OEM$ directory in the root ? I use a multiboot DVD with some XP versions, and every version has his own $OEM$. But if i wanna add new drivers,patches... i must do it with every version - a lot of work. Is there a way to point all to one .....it would save time and space...
SC00BS Posted November 11, 2004 Posted November 11, 2004 Not sure. You could try adding OemFilesPath="..\$OEM$" in winnt.sif
StormLogiX Posted November 11, 2004 Posted November 11, 2004 Not sure. You could try adding OemFilesPath="..\$OEM$" in winnt.sifDoesn't work. Just tested it.
StormLogiX Posted November 12, 2004 Posted November 12, 2004 I have thought of a workaround so you must not maintain several $OEM$ folders and synchronize them everytime you make a change in one of them.In the root of my CD i put the "$OEM$" folder with everything that belongs to it (Install, Drivers, etc.).Then I put a file "cmdlines.cmd" in it with following code:\$OEM$\cmdlines.cmd@echo offif exist \$OEM$\$1 xcopy \$OEM$\$1 "%systemdrive%"\ /e/h/r/y/z/c >nulif exist \$OEM$\$$ xcopy \$OEM$\$$ "%systemroot%"\ /e/h/r/y/z/c >nulif exist \$OEM$\$Docs xcopy \$OEM$\$Docs "%allusersprofile%"\ /e/h/r/y/z/c >nulif exist \$OEM$\$Progs xcopy \$OEM$\$Progs "%programfiles%"\ /e/h/r/y/z/c >nul[...your install code be here...]Then in every windows version on my CD, I put an $OEM$ folder with only one file and only one command in it:cmdlines.txt[COMMANDS]"\$OEM$\cmdlines.cmd"Copy this to every windows version on your CD.So when cmdlines.txt of the local $OEM$ is called, it will delegate it to the one root $OEM$ and copy everything just as a normal $OEM$ folder would do and after that you can put your normal installation code there as used.I tested it. Works perfect.p.s. What i'm not really sure of: how to put $Docs in the right folder ("C:\Documents and Settings\").Currently i just copy it in %allusersprofile% so it will get copied to "C:\Documents and Settings\All Users"
mediapla Posted November 12, 2004 Author Posted November 12, 2004 I do not know all about the timeline of the XP Install...starts cmdline.txt befor the driver installation ? - Yes, i know it works, i also use cmdlines.txt befor driver install (HDA-devices) Thats a great idea - i try it ! Thanks a lot !!!
mediapla Posted November 13, 2004 Author Posted November 13, 2004 it works at my system,but not full. It "copies" all drivers, but it doesnt install. When (in installation timeline) will pnp drivers be installed ?Can i call after T12 a pnp driver search...???
billy-h Posted November 13, 2004 Posted November 13, 2004 cmdline.txt is started after the driver installationyou dont need to use the $OEM$ in 1,after you modify it,you can copy it to others,then when you make your cd,you can also use cdimage with "-o" to make it store the same file only oncesorry,my english is so poor,hope u can understand what i said
mediapla Posted November 13, 2004 Author Posted November 13, 2004 @ billy-h: The problem is not the diskspace, its the time and work. If i wanna be up2date, i must add new drivers/patches etc. in every OEM-dir. ! CDIMAGE works fine on my Bootable DVD, it reduces 30GB to 4...
billy-h Posted November 13, 2004 Posted November 13, 2004 Oh,sorry,I dont think I follow you.The new drivers/patches are the same for every XP versions,arent they?By the way,what is the meaning of "@"
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