BlueLabel

I just edited my post above with a procedure that should do the trick for you.

Noticed a few people looking for how to do a complete install of MapPoint or Streets & Trips in an unattended fashion. 1. Copy the contents of both CDs to the same directory, ignoring any duplicates. 2. (If you don't want to do this step, see below for an alternative) Use Orca (the Microsoft MSI Editor available at MSDN) to edit MapPoint\MSMap\data.msi. Find the table (the left column in Orca) called Media and change the volume label for the second table entry (DiskId 2 aka 'Run Disc') to whatever volume label you plan to use for your CD/DVD installation. 3. The setup command you want to use is: setup.exe /qb INSTALLLEVEL=500 If you wanted to just install the runtimes, you use: setup.exe /qb or more completely: setup.exe /qb INSTALLLEVEL=100 You don't need to worry about labeling your CD/DVD with any particular volume label as long as it's consistent with the label you set in the MSI above. Alternatively, you could set the volume label of the DVD to 'GEO11NA' instead of editing the MSI file directly. As long as all the files are under the same tree, setup will run just fine. The two install levels (100 and 500) denote whether to do a typical or a complete install. Enjoy, -BL.

Sorry I've been a bit indisposed...glad to see it incorporated and that it's of some use. Hasi -- nice example usage. I might have a few examples to post in short order that others might find of use. Is there a 'script repository' or perhaps a 'cond repository' thread anywhere? Or do we just let folks search and stumble upon it?

No, I'm not...but the drivers themselves aren't the issue. All the drivers do, in fact, get installed automatically. That's not what I was originally trying to do. There are certain hardware-specific applications that I was interested in. In my situation, I've got several Dell laptops to contend with that are different models and have different hardware configurations. The ASF Management and Broadcom Diagnostics applications, for instance, will only work if the system in question has a Broadcom card in the first place. This isn't a driver question -- the drivers are in fact already installed and working just fine. Another example, that's relevant for me -- some of these laptops have NVidia cards and some have ATI cards. Again, the drivers get installed fine...but what I want to do is also have the option to install tweaks/tools based on which card is in the system, so conceptually I do: if(This machine has an NVidia card) { Add menu entries for NVDVD, NVHardPage, GeForceTweakUtility, etc. } if(This machine has an ATI card) { Add menu entries for ATI Tray Tools, etc... } The hardware selection aspect is just one example (the one I happened to use the most so far in my builds). You can also do funky things like (on Dells and other systems that have a service/asset tag accessible) make menu options available only on certain specific machines. Another use I've had for this functionality already is not making applications with a large footprint available if the hard drive is below a certain size, for instance. I'm sure everyone here whose had a lot more sleep than I have will come up with infinitely more ways to use the functionality provided. Hope this helps...

Working through the night trying to get the unattended CD/DVD I'm trying to setup I ran into a limitation of WPI and pulled together an enhancement that others might find of use: My problem is that I want to create a single DVD that brings up WPI, but only with certain applications available to install. Why? In my case, it's hardware-specific information, but it can be almost any reason. The attached version of WPI, which for simplicity I'll dub WPI-BL, adds a new entry in the Config screen for each application called 'Condition' that expects a Javascript statement. When generating the menu, WPI will evaluate the condition -- if it evaluates to true (1) then it's displayed...if it evaluates to false (0) then the entry won't appear on the menu. As a practical example: fso.FileExists("%windir%\\System32\\Drivers\b57xp32.sys") || fso.FileExists("%windir%\\System32\\Drivers\\bcm4sbxp.sys") This will check to see if (in this case) the Broadcom Ethernet drivers are installed in the system. I have attached to an entry that installs the Broadcom Advanced Diagnostics for Windows. Installing this (or even making it an option) just doesn't make sense on a system that doesn't have the right network card. fso.FileExists("%windir%\\System32\\atiddc.dll") This checks to see if the ATI drivers are installed...I have this condition attached to an entry to install some ATI-specific software. In my environment, I need a swiss army knife installation CD -- I know what all the hardware combinations are and rather than be inundated with options for things that don't make sense on the machine I'm on at the moment, we just hide them...but I still have all the convinience of keeping a single image to maintain. Enjoy... WPI_BL.zip

No...this doesn't really have anything to do with categories. When you go into the 'Config' section in WPI, it lists all the applications there in the order you added them to WPI. What I did was make the order they're listed in on the Config page more intuitive (at least to me) by sorting that list by the 'Install Order' field. The 'Install Order' field specifies the order in which applications will get installed -- it's essentially a priority list. Things like Prepare.cmd and Cleanup.cmd are given the lowest and highest install orders because they should run at the beginning and end of the RegOnceEx process. Hope this clarifies it a bit. If it doesn't, download the configwizard.js I put up and try it and perhaps it'll make more sense when you can see it. As to your other issue...I've read the thread and I understand the problem but I haven't run into it yet myself, but I suspect I will as I add to my list of applications. Until I do, it'll be a bit tough for me to help you on this one.

I did a quick search and couldn't find what I wanted, so I whipped it together in a couple of minutes. Attached is a slightly modified configwizard.js that always writes out config.js as a sorted list, sorted by order number. I found it really useful in setting up WPI. When you go back into Config after you've saved it, the list of applications under 'Navigation' will be sorted in order, in the way they'll eventually end up in RunOnceEx. It helped me to get a good idea of the flow of application priorities. Hope you guys find it useful. This modified configwizard.js is based on the version of WPI I downloaded this evening, which I presume is 3.2? The WPI.hta is dated 12/29/04 11:30PM (CST). Hasi -- if you'd like to incorporate my changes (really only a few lines) into your official releases, you're more than welcome to. Enjoy, BL. configwizard.js