Alanoll

This is just a friendly public service annoucement to all those posting in the Unattend Forums..... There really are a subset of rules to this place. They're not much. Infact, I believe it's one sentence. Perhaps at most three. It can be find clicking the little link right below where it reads.... Right above where you're reading this. For those that don't see it. Click here. Please remember to use CODE tags when you post CODE. This does not just include batch files, but also INI files, SVCPACK.INF, INF files in general, CMD files, BAT files, REG files, or anything that may be considered code. It helps to tidy up the board, and make it look alittle bit cleaner. It also helps for those of us who skim, to recognize it's code, and to disregard untill we find the question in the post, and then go back. PS: Usage is as follows: THanks to Mac for that.....

but that's what /f is supposed to do. Force the entry..... by the way, you don't need to put all those returns when posting.....it may not look right in your little box, but it willl.....as another note....please use CODE tags. It makes it look all perty like.

why are you people messing aruond with REPLACING the msgina.dll file when they can easily coexist along side of eachother? there is a key called GinaDLL in the HKLM\Software\Microsoft\Windows NT\WinLogon (close there abouts). Just create the key, and give it the path to your file. Or maybe if it's in system32, it doesn't need a path..... either way, no overwriting renaming or whatever. Just name you file what ever you want, and tell the key above what to look for.

try putting the kill command later in the script.... I have AIM and DeadAIM in my routine, and I install AIM, then start AIM....but while it's starting I install something else, THEN kill it later on to make sure it loads fully. Maybe you need to do the same thing?

these would most likely be the neccesary ones.... HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shellex\ContextMenuHandlers\EditPlus HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{63AFBDFB-5EF8-4791-AF79-9A3C0DE48974} HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{63AFBDFB-5EF8-4791-AF79-9A3C0DE48974}\InProcServer32 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\EditPlus 2 HKEY_LOCAL_MACHINE\SOFTWARE\Classes\*\shellex\ContextMenuHandlers\EditPlus\: "{63AFBDFB-5EF8-4791-AF79-9A3C0DE48974}" HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{63AFBDFB-5EF8-4791-AF79-9A3C0DE48974}\InProcServer32\: "C:\Program Files\EditPlus 2\eppshell.dll" HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{63AFBDFB-5EF8-4791-AF79-9A3C0DE48974}\InProcServer32\ThreadingModel: "Apartment" HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{63AFBDFB-5EF8-4791-AF79-9A3C0DE48974}\: "EditPlus Context Menu Handler" plus my registration information @ [HKEY_CURRENT_USER\Software\ES-Computing\EditPlus 2\Install] "License"=hex:xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,\ xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,\ xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx,xx Basically, the only registry entries the Installer truly adds, is the Contect Menu and Uninstall entries. THe other ones were about renaming a file "eppshell.dll" but that would be taken care of if you just copy the files over to where you want them....

way too much time on your hands there..... can't you do something useful? like.....sleep or eat? I personally enjoy watching Monty Python and the holy grail with the Henry V subtitles.....it's pretty hilarious.

I was trying to get you to post the other files you're using..... as AaronXP said, T-12 is CMDLINES territory not SVCPACK. It doesn't neccesarily have to be a PAUSE either, just SOMETHING that requires a prompt, like a copy or something, and you just can't see it if you use cmdow.

maybe it's just me....but..... It only adds like 3 registry entries, IF that. The "setup" program just copies files from the temp location to the location of your choice.

RED ADD %KEY%\105 /V 4 /D "TASKKILL.EXE /F /FI \"WINDOWTITLE eq Messenger*\"" That should do it You do add it to your REG ADD entries or it doesn't run when it's supposed, but rather when the keys are imported but not executed.

you can do that with almost any method. CMD is just easier.

No, he can't. Majority of his CDs are considered Warez and as such are against the rulez. Sorry. If Hiren's CD is just a CD with alot of utilities on it, you could possibly get a copy of the Ultimate Boot CD i think it's called and use it. flyakite.msfnhosting.com is Flyakite's guide. and Gosh's site is in his signature.

The way MCT has it, is for an INF file not BATCH.should most likely be this... Just put it in a seperate batch file, execute it, and then OPEN up regedit. See if it retained the quotes properly. You can safely delete the key after looking so you don't get the RunOnceEX screen upon restart.

you can't split it, unless you split it and have the second half run after a restart.....

there is an option of taskkill to select which part of the process is killed, like a specific folder in explorer.exe instead of killing the entire shell. again, taskkill /? will tell you how. (It's one of the options with the quotes)

INF are good for the sole purpose, of everthing is in one files. And there in lies the problem, one file. Some like smaller files. But you can do ALMOST everything from a INF file that you can with a batch file. Embedding quotes in an INF is simple enough, """ will embed the quote. and \" will embed it in the batch file. I personally consider is a tier level of how hard thigns are. CMD then INF. It's easier to use a CMD file. However, REG adds another complexity of it's own.

it's SVCPACK.INF first of all, but it's probally a typo in your post. Do you have a CMDLINES.TXT file or are you just using SVCPACK.INF? Do you have any batch files running?

i really should change that first post. It should be fixed.....atleast I've had no problems...if you have any issues with a MSI you have, make sure you have the latest MSI in the first post. The link is near that top.

hmmm.... I've found a place in my install routine for almost every other progam made at MSFN..... I guess I could find a place for this Very Very nice indeed.

%SOURCEPATH% is the Path to the Windows Setup files......usually D:\I386. You may want to use %SOURCEDRIVE% instead as it is would just be D: form the above example.

if you use nLIte.... use a pure source. Also on the first try, use ONLY the recommended settings. Don't delve too deep if it doesn't work. Try a base CD if you use nLite without adding anything either. Go one step at a time.

I was saying the Nullsoft installer is dated that. The MSI however is not. I'll see about adding a date.

ok ok..... expect it soon....

it's built on 6/23/04

now now guys, no need to be so harsh with the poor man..... always remember to search before posting. This is alot of information here, and you can find it through searching. Just remember to change "30 Days" to "Anytime".

it's going to be part of SP2. SO you could wait till it comes out, should be about a month if they keep their schedule...... You don't NEED it. Though if you're having problems with your Wireless Network, it may help