RyanVM Posted September 16, 2003 Share Posted September 16, 2003 I'm trying to use cmdlines.txt to install the hotfixes/apply registry settings before booting into a GUI. I've got the file in the $OEM$ directory, and it's setup like this:[COMMANDS]".\Updates\update.bat" The Updates directory is in the $OEM$\$1 directory (as the MSFN guide says to). However, cmdlines.txt fails to launch when I run setup. Does one have to use FullUnattended in order for it to work? I ask because I use DefaultHide so I can use my install CD with other people, allowing them to use their own name and CDKey rather than mine Another somewhat related question - does start /wait work for batch files called by cmdlines.txt? Is it even necessary or will it wait automatically for one to finish before launching the next? Link to comment Share on other sites More sharing options...
chon_ Posted September 16, 2003 Share Posted September 16, 2003 shouldn't your path be:".$1\Updates\update.bat"?and yes, /wait is absolutely necessary, believe me, if not used, you'll have a bunch of setups running simultanously Link to comment Share on other sites More sharing options...
webmedic Posted September 16, 2003 Share Posted September 16, 2003 for cmdlines text you can only call files right there so that will not workit should be something like this. [COMMANDS]".\update.bat"then your bat can call other dirs but cmdlines.txt has to stay local. You will need to place update.bat in the same dir as cmdlines.txt Link to comment Share on other sites More sharing options...
GreenMachine Posted September 16, 2003 Share Posted September 16, 2003 For a more in depth discussion on cmdlines.txt ... Written for Windows 2000, but still relevant. However, it is erroneously stated that files to be run must be on the hard disk. I NEVER copy installation files to the hard disk: all installations are called from a batch file, which is called from cmdlines.txt, and use relative paths to $OEM$ subdirectories on the install CD. Link to comment Share on other sites More sharing options...
webmedic Posted September 16, 2003 Share Posted September 16, 2003 actually durring textmode everything under $OEM$\$1 $OEM$\$$ $OEM$\c$OEM$\detcare copied to your hard drive and when you run your scripts they are being called from the hard drive if under those directories. The only exception is ny scripts right under $OEM$ which are always run from the cd. Link to comment Share on other sites More sharing options...
kenneth11zz Posted September 16, 2003 Share Posted September 16, 2003 I'm just wondering... Is there a way to tell Windows Setup not to copy the programs to hard drive to install the programs from the $1\Insall folder? Why it can't simply just install it directly from the CD? I'm just curious.-Kenneth Link to comment Share on other sites More sharing options...
GreenMachine Posted September 16, 2003 Share Posted September 16, 2003 It can, and does for me. As Webedic says, $$,$1,C,D etc. are copied to the HDD. That is why I never use them. Root files as well as user-defined folders are not copied to the HDD, can be referenced from the batch file with relative paths, and run from the CD. If in doubt, either watch the CD whilst your programs are running - or eject it and see at which point you get an error.Example:CMDLINES.TXT:[COMMANDS]".\INSTALLS.CMD"INSTALLS.CMD:@ECHO OFFTITLE Post Install Setup:: ---------- Update MS Components ECHO Starting DirectX 9 Install.START "DirectX 9 Install" /WAIT ".\DIRECTX\DXSETUP.EXE" /opk...Directory Structure:$OEM$ - DIRECTX - IE - PROFILES - SVCPACKThat's all. No $anything, no install. No clean up of hard drive later. Link to comment Share on other sites More sharing options...
webmedic Posted September 16, 2003 Share Posted September 16, 2003 not sure but it does not do it that way and another thing something about the installer doesn't like dirs with $ in them so it would be really hard to get to it on the cd anyway if it was under any dirs that had $ in them. Link to comment Share on other sites More sharing options...
GreenMachine Posted September 17, 2003 Share Posted September 17, 2003 @WebMedic: Are you sure? I am very open to discussion, but please be sure before you call me wrong. I've been doing installs that way for months. It works exactly as I described. All my files are under a directory with $ ($OEM$), are not copied to the hard drive, and are installed correctly. If it was really hard, you can be sure I would not be doing it, but really hard does not mean impossible or wrong.Peace. Link to comment Share on other sites More sharing options...
webmedic Posted September 17, 2003 Share Posted September 17, 2003 no sorry to explain if you are doing it from cmdlines.txt and your files are only under $OEM$ like you mentioined above then your are fine my post said this $OEM$\$1$OEM$\$$you will not be able to find those dirs. As long as it is all under $OEM directly like you explain and as long as all your stuff is installed from cmdlines.txt then you are ok. The only place were the $OEM can be accessed is from cmdlines.txt. I hope that clears things up. By the way this is waht I'm going to try next. I will still have a install dir and and a drivers dir on the hard drive but most everything will stay on the cd. I'm jsut trying to get my inf installers to run more than one at a time and then I'm going for this method also. I should be there sometime tomarrow. Link to comment Share on other sites More sharing options...
GreenMachine Posted September 17, 2003 Share Posted September 17, 2003 I must have mis-understood. I guess it was the "etc", "only exception" and "does not do it that way" that threw me off...I must of also mis-stated: My files are in sub-directories of $OEM$. $OEM$ itself only contains CMDLINES.TXT and INSTALLS.COM. I never reference $OEM$ directly: all my calls use relative paths from inside of it. (See earlier example) Link to comment Share on other sites More sharing options...
webmedic Posted September 17, 2003 Share Posted September 17, 2003 yes my fault I'm not explaining myself well .I understood you are using subdirs. They can be seen fine from cmdlines.txt. However cmdlines.txt is in a virtual world that lives under $OEM$. It is possible to get outside of that but everything that is not addressed directly will default to someplace under $OEM$.for instance c:\install\apps\myapp\myapp.exe will still get ouside of it but only if you use full pathsFrom guirunonce it has issues accessing dirs that have a $ in the name. I hope I explained better. I must be getting to tired and I'm not explaing well or maybe I'm thinking to fast and not explaining the little bits or something. Again sorry for any missinformation or understanding. Link to comment Share on other sites More sharing options...
RyanVM Posted September 17, 2003 Author Share Posted September 17, 2003 OK, I'll put update.bat into the $OEM$ directory with cmdlines.txt and we'll see how it goes My batch file uses all relative paths, so I should be OK. Link to comment Share on other sites More sharing options...
Sunil Posted September 17, 2003 Share Posted September 17, 2003 Guys, all the files go into the $OEM$ folder along with CMDLINES.txt eg the updates.com script file and all the files it refrences fgoes into the folder with it. Link to comment Share on other sites More sharing options...
RyanVM Posted September 17, 2003 Author Share Posted September 17, 2003 Out of curiosity, where in the install process is cmdlines.txt supposed to run? I just tried again with update.bat in the $OEM$ directory and still no-go.I don't even see where it's trying to be executed... 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