meister

Sometimes it's there, sometimes not. Well isn't that just great for someone like me who's never used it before and is expecting it to just work??? Hahahaha. Oh well, now I know. THANK YOU so much! It was holding me back on a few things. Will

One quick question....how did you get Iexpress to see a cmd file? When i add a cmd file to "Packaged Files" then Next to "Install Program to Launch" I don't see any cmd files listed. What I just tried though, thanks to your guidance, I took my non working SED and edited it, changing AppLaunched= to the cmd file instead of tha bat (i just renamed my bat to cmd) and in one quick test it worked. Is that how you did it?

I added the SET command: @echo off title Test color 71 set pause The output of set is from command.com, not cmd.exe! And a lot of the variables are truncated to 8.3 format. Getting somewhere...

Nope, that's not it, heck, that's the only part that works right. I end up with a title to my batch file where all the commands run. Try this, create test.bat with this code: @echo off title Test color 71 pause Run it and you get a Dos box titled Test, with a grey background and blue lettering. Now open Iexpress, create a new directive file, purpose=extract files and run installation program, set the install program to Test.bat you just created and watch what happens. You'll get 2 bad command or file name errors then it pauses...it's a dos environment issue of some sort that's driving me nuts! If I use Winzip self extractor to create the EXE it works great. So I'm at a loss as to why Iexpress is failing.

As I play around with this some more and still not getting anywhere, let me just ask this instead. When I run Setup.bat it changes the color because of the color 71 command on the third line. Why would I get a bad command or file name error when it's packaged as an EXE. Obviously it can't find color, whether it's an internal or external command. My question is why?

As far as i know, you can't run a cmd file with Iexpress, which is why it's a bat. Pardon the code as i'm no programmer. It started as a simple zipped up file because I don't always have my laptop, and if I was on site someplace and needed to ghost a machine, here was a quick way to get a ghost cast server up and running. It just copies the ghost files, and the DOS nic drivers we use, so I can run ghostcast from any pc, and create a boot floppy. I thought throwing it all into an EXE would make life easy, but it's just personal now...i have to get it running. This is the start of my setup.bat file rem @echo off cmd /C title My Ghostcast setup color 71 pause if not exist "C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template" mkdir "C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template" set ghostall=C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template ECHO. ECHO . Expanding files echo %ghostall% echo This should have echoed ghostall pause 7za e -o"%ghostall%" -y .\DOSNIC.7z if not exist "C:\Program Files\Symantec\Ghost" mkdir "C:\Program Files\Symantec\Ghost" ECHO. ECHO . Setting up and sharing the Ghost directory if it's not already ECHO. pause net share Ghost="C:\Program Files\Symantec\Ghost" ECHO . Copying files ECHO. set ghostprog=C:\Program Files\Symantec\Ghost echo %ghostprog% echo This should have echoed ghostprog pause xcopy .\gdisk.exe "%ghostprog%" xcopy .\gdisk32.exe "%ghostprog%" xcopy .\"ghost boot wizard.exe" "%ghostprog%" xcopy .\"Ghost Boot Wizard.lnk" "%ALLUSERSPROFILE%\desktop" /y /q /c xcopy .\ghost32.exe "%ghostprog%" xcopy .\ghost.exe "%ghostprog%" I have no issues when I run setup.bat. It's only after it's packages with Iexpress. I start by creating a new package in Iexpress and including all of the necesary files in one folder. On the Install Program to Launch screen I select setup.bat. Everything packages fine. When I run the EXE it expands everything but when it hits the Color command I get a bad command or file name. The same is true of the first IF statement...and so on.. Thank you.

Not too sure where to post this, but these forums are always such a huge help. I created a simple batch file to run some commands and copy files, and it works great. The folder contains all the files and no matter where I put the folder, the batch file works. So I thought it would be even better if it was packaged as an EXE, I used Iexpress on WindowsXP. Iexpress unpackages everything to a temp folder, then runs my setup.bat file. The first few commands that worked before it was packaged were Title, Color, an IF statement and a SET statement. When you double click the package the files expand (echo is on and there are lots of pauses). If, color and title are bad command or file name and the set error is out of environment space. I would think it has to be DOS related since the batch file can no longer run the If command, it doesnt' know where to find that internal command. Any ideas? Thanks a bunch!

Well not the hardware wizard per se, I'm not in windows adding a driver when it happens. I sysprep my image and shutdown. When I bring it back up my runonceex.cmd runs a bunch of installations, one of which is it tests for the model PC and installs the appropriate driver pack. I have 6 different models in my environment and a packaged set of drivers for each. Apparently one of Dell's drivers (audio) have not been signed so I get this pop up and you have to hit continue anyway. But it just manifested itself all of a sudden - which makes me think the private hash somehow got tampered. When it was shutdown I did boot into BartPE and edit a text file in the root a C:\, and I know if you run Regedit from within BartPE the default behavior is Warn but allow...maybe it somehow caused the private hash mixmatch...??? ANd I'm probably misunderstanding how WatchDriverSigningPolicy.exe works, but I'm running that in the initial stage of the driver installation, still no luck.

Anyone know why with my sysprep.inf file having driversigning=ignore (I don't have access to it right now, the syntax here might be wrong but i know it's right in the file), why on earth would I still be getting prompted for "continue anyway" or "stop installation" when my runonceex is installing some programs after mini-setup? Thank you.

Here's an interesting one....I have a driver package being installed as one of my RUNONCEEX steps during setup. The policy for the machine is set to silently succeed for the unsigned driver installation behavior. Yet I'm consistently getting prompted that such and such has not undergone...Continue Anyway or Stop Installation. I've looked at the reg keys while this is happening and they are set properly, Policy=Reg_Binary=00. Any ideas?

Thanks. Doesn't seem to work for me, but quite possibly it's how i'm doing it. I'm just testing it on my laptop and have a c:\sysprep\i386\$oem$ where i have $1, $$, $Docs and $Prog folders. I know that C:\sysprep gets removed but I thought that was after text mode, so shouldn't the files be copied over to the right folders? Here's the reasoning. I have a very strict environment where the base image is created by app support, then we out in the field can customize as needed. Since the base exists at every site, no need for me to carry it with me, but if I had a sysprep for each of my sites, i'd be all set to create a new image by sysprepping that base. If I can get this to work as I think it should, it would be a god send....Thanks for any input.....Oh should have mentioned...sysprep with mini setup....that's not really text mode then is it?

Before I get into it, is the $oem$ folder discussion located at http://unattended.msfn.org/unattended.xp/view/web/18/ all about and only for creating a CD installation? When you run sysprep, how do you get it to copy from $Prog to \Program Files and $1 to the root of C:\ and so on? Thank you.