amorf Posted July 28, 2004 Posted July 28, 2004 for the batch file i used first the cmd method and everything was working perfectly...i got drivers installed and all my apps...Now i tried the runonceEx method...and the problems started i can not get the drivers installed... i have not change anything i my winnt.sif file.. i only got the paths from the cmd file and converted them to a runonceex version ...am i missing something ?what should i change ??Thanks in advance..And forgive me about me English
Solid as a rock Posted July 28, 2004 Posted July 28, 2004 for the batch file i used first the cmd method and everything was working perfectly...i got drivers installed and all my apps...Now i tried the runonceEx method...and the problems started i can not get the drivers installed... i have not change anything i my winnt.sif file.. i only got the paths from the cmd file and converted them to a runonceex version ...am i missing something ?what should i change ??Thanks in advance..And forgive me about me English i am sure someone will ask you to show your runonce.exe so attach it to your post.... i dont have any experience with runonce so i cant help you.....
kmosh Posted July 28, 2004 Posted July 28, 2004 First, the Runonceexe can run only One command.secondly, you can use the $oem$ method so windows will install your drivers automaticly...
jrzycrim Posted July 28, 2004 Posted July 28, 2004 First, the Runonceexe can run only One command.I could have sworn that I've installed many applications from RunOnceEx, Hmmm, my computer must be unfamiliar with this rule...
fillalph Posted July 29, 2004 Posted July 29, 2004 Read the MSFN Guide on RunOnceEx: http://unattended.msfn.org/xp/runonceex.htmAaron did an excellent job and I think it covers everything very well.]Bonkers[
Vann Posted July 29, 2004 Posted July 29, 2004 RunOnceEx programs are run after drivers are installed, so it's not ideal to install drivers during that stage. In fact, that's why cmdlines.txt exists, so you can install necessary drivers before booting into Windows (e.g., video or network drivers that Windows can't automatically detect).
nodiaque Posted July 29, 2004 Posted July 29, 2004 why not simply put it into a folder (i.e. $oem$\drivers) and say windows to search for drivers there?
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