DeTard

Well, I finally got my CD burnt, and it is still complaining to me. I have checked [ForceCopyDriverCabFiles], and it is listed in there, but doesn't seem to matter. What it is telling me is: "The entry "ALIIDE.SYS" in the [sourceDisksFiles] section of the INF file is corrupt or missing." From my original, SP2-integrated XP CD, the line in Layout.INF was: aliide.sys = 1,,5248,,,,3_,4,1,,,1,4 Which I changed to: aliide.sys = 1,,7311,,,,3_,4,1,,,1,4 Since that was the correct size now. Unfortunately, I do not know where to go next with this. Any help would be appreciated... I have editted this post so that no one follows what I did and to leave it as reference for later.

That is odd, it wasn't missing from mine, instead setup thought it was corrupt because the wrong size was present. The size should be 7311, or omitted entirely (right??). About to test this here.... BTW, I'm sending Bâshrat a bill for 5 CDR's that I wasted.... LOL JK! To be honest, these things are absolutely amazing, and one of the best additions to a UXPCD, and the reason for my recent donation.

Hasi, right now I'm not doing enough installs to warrant you doing a massive re-write, but it might be something to consider in the future. I'm only doing about 30-35 at the moment, and I expect that number to keep rising. The request is more of an aesthetic thing.

Thanks guys, this is exactly what I was wondering. Hasi, I've been thinking about this, and since you are already creating several RunOnceEx screens, would it hurt to reuse the ORDR numbers? If you have one screen that has ORDR numbers 1-15, then have another screen created, wouldn't those same ORDR numbers become available again? Would it be an option in a future version to remove the disabling of ORDR when installing by Category?

That's not what I meant..... I know about ordr (and yes, that's what it's called). This is a topic not talked about previously, or documented anywhere, so please stop and read it this time. What I want to know is if I am Installing by Category and I want to specify the order within that Category.

I can't seem to find anyone else asking this question, so I guess I'll raise it. Is there a way to install by category, but then specify the order in which things are installed still? I would like to be able to have all my 'Multimedia and Codecs' installed, but only in a specific order so the proper file associations are used (the last installed being the one that takes precedence). Can I just use the order number in addition to installing by category, or does it force it into installing alphabetically? I know I can make it go the way I want it by numbering the apps in the program title, but I'd like to do it the "right" way if one does exist.

@buzzman2005 The only real problem I see with the idea of having a separate RunOnceEx window (other than hasi busting his hump to get the code for it) is that it could very well break the expect order of software to be installed. I don't have software install by order of category, I have it installed in order of when it really needs installed to meet the prerequisites of later applications/commands. Such as the need to install Firefox before any application that would need to install plugins (Flash/Shockwave, Office 2003, Acrobat, etc). But that doesn't necessarily mean that I want all my Internet Applications installing at the same time. I also try to separate things out by the how critical they are. Since I have a few applications that need .NET Framework installed, it must be one of the first things ran. I really do have to agree with hasi that it is fairly minor, and this is supposed to be "unattended".

Cool, that should work exactly how I want it. Had I looked at the code just a little bit longer I would have realized it was just this simple to have case sensitivity only removed from the environment variables!

Actually, the fallback to using the registry is very effective. If you looked at the registry values during install (by bringing up command line with Shift+F10 and using Reg.exe), you will see the value is always there. Even if you don't modify for testing purposes, the registry will work for you I'm certain.

Oh, forgot to mention... The OTHER place it looks (if all else fails) is in your registry for HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath This usually always works (during the install anyhow, not testing necessarily)

If you WANT, do a search in generate.js and replace the filename with WIN51IP. It's entirely up to you if you do this, but remember, new builds will need the update as well.

@Astalavista Build 2.99a And don't worry about it, it just really did feel like you were talking about me only. I'm over it... @dlevens This is because you are using your old config.js You need to use the new config file, but copy and paste your own items into it. There are new variable definitions in the new config.js including uid. Also, the file WIN51 is what it looks for in the root of the drive. If your hard drive has that file at the root, or if any other disc has it, it will be detected.

Hey man, you DO realize this is a 50 page thread.... right? Come on, give me a break. I tried to find it, but obviously skimmed too much, so for that sorry. Don't assume no one reads, I've read at LEAST 30 pages of this thread which took me about 4 hours (mostly because I was testing what I was reading). Just because I missed one thing, don't generalize.

Ran into a problem with the fix for case sensitivity. Seems it makes the whole script lowercase (which is fine in most cases), but if you require a certain case (such as serial numbers or running a method with rundll32.exe, this is a real problem. To remove this (which means you have to make sure your variables are lowercase), comment out line 104: u[0] = pth.toLowerCase(); Here's an example of something passed to rundll32.exe that requires proper case: rundll32.exe advapi32.dll,ProcessIdleTasks The above runs the task that BootVis would run to optimize boot time.

@Astalavista Thanks for the heads up on the bug with the message. Quick fix, comment out window.alert(getText(msgStartInstall)); in generate.js and the message should never show.

I've been fighting with getting WPI to properly detect my CD drive... and finally figured it out. Could you PLEASE say that %cdrom% should be lower case somewhere? Out of habit and convention, I always use caps for environment variables, and this is the only time where it's kicked me in the a**.

Whipped up a quick VBS script for you guys! ****** EDITED TO DISABLE AUTOLOGON IF "NO" IS CLICKED ****** Option Explicit ' Set Registry path used for AutoLogon Dim WinLogon WinLogon = "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" Dim Passwd Dim AutoLogon ' Do not allow user to not enter a new password. ' I use this so that I cannot really forget to ' create a new, non-trivial password. Although ' technically this isn't "unattended", I feel ' it's a worthwhile compromise. Consider ' putting it at the end of RunOnceEx so it's ' practically done with everything if you walk ' away after getting Setup started. Do While Passwd = "" Passwd = InputBox("Enter a new Administrator Password", "Update Password") Loop ' Message Box with Yes and No buttons ' Yes = 6 ' No = 7 AutoLogon = MsgBox("Do you want to enable Administrator AutoLogon?", VBYesNo, "Set AutoLogon") Dim WshShell set WshShell = WScript.CreateObject("Wscript.Shell") Dim objEnv set objEnv = WshShell.Environment("Process") Dim Systemroot Systemroot = objEnv("SYSTEMROOT") ' Use net command to change the administrator password WshShell.Run Systemroot + "\system32\net.exe user administrator " + Passwd ' If user says yes to above Message Box, then make ' registry modifications If AutoLogon = 6 Then WshShell.RegWrite WinLogon + "\DefaultUsername", "Administrator" WshShell.RegWrite WinLogon + "\DefaultPassword", Passwd WshShell.RegWrite WinLogon + "\AutoAdminLogon", "1" Else WshShell.RegDelete WinLogon + "\DefaultUsername" WshShell.RegDelete WinLogon + "\DefaultPassword" WshShell.RegWrite WinLogon + "\AutoAdminLogon", "0" End If Let me know what you think...

Has anyone had any luck doing this if you use an encrypted admin password? I used the deployment tools to create my initial WINNT.SIF, and then further modified it to include things like OemPnPDriversPath, etc. But the problem I am having is that, although my password is created correctly, it gives me a message that it couldn't logon because the password is incorrect. Then I manually type in the username and password, and Voila!, I get in. I just don't want to risk the chance that someone will get this CD and find out a password. I guess the next thing I could do instead is create a simple password, no encryption, and then at the end of RunOnceEx use a VBS script to popup an InputBox that you can't cancel that changes the password. Any thoughts on this?

The way I do it is with RunOnceEx as follows: REG ADD %KEY%\045 /VE /D "MRU-Blaster 1.5" /f REG ADD %KEY%\045 /V 1 /D "%CDROM%\Software\MRUBlaster\mrublastersetup.exe /VERYSILENT" /f REG ADD %KEY%\045 /V 2 /D "%SystemRoot%\system32\taskkill.exe /IM mrublaster.exe /F" /f REG ADD %KEY%\045 /V 3 /D "%SystemRoot%\system32\taskkill.exe /IM scheduler.exe /F" /f Hope this helps!

ClarkKent: Just so you know, the spaces do not effect the functionality of each parameter. md10md: Did you make sure that if your file is WINNT.SIF that you deleted WINNT.SI_?