Alanoll

I'm interested in what Osmosis Jones said as well. I have some programs that it makes sense to have a tree structure, but then I have Office by it's self....and then it's a tree on it's one. I've noticed that when restarting, WIHU only exits upon restart. If you run it during GUIRunOnce the desktop won't fully load prior to the restart. Is there a way to possibly add a switch to tell WIHU to call the restart command, but then exit itself? The AutoExit will exit after no user input, maybe a switch to have WIHU exit on it's own (after installation, but not restart) instead of having to click Finish?

Here is an INI file for all the hotfixes..... I'm sure someone here likes seeing them being installed, then just sitting at T-13 with nothing showing for awhile..... hotfixes.ini

has to be almost exactly similar and the HDD can't have different serial numbers

look specifically in the Windows PE subforum.

Here's mine, but this is the one I'm planning on running at CMDLINES.TXT I haven't gotten around to the app one yet..... drivers.ini

Works now... Thanks Benjamin.

I should have an updated MSI soon. I'm trying to figure out the INI thing, if I don't it's still controlled by switches. I'm going to add a switch to select which skin to use (Modern or Classic, default at the moment is Classic). But there is still an MSI.

it stops WMP from stealing the associations, or not letting other programs take them fully. You'll get that box that comes up asking which you want to use to load the file type. Navigate to that key in your registry. You have it. It's like a little mini-setup that is started when a new user is created and logged in for the first time. It creates the default settings such as file associations and WMP settings in this instance.

you have to have a batch file copied over, then that looks for the XP CD using IF EXIST or whatever method you like, and then execute it that way.

@WwTIPPYwW That's some good ol' fanshion logging. It's supposed to create a runoncex.log (i think) in the Windows directory. lol. @iN2Fun You need the full path to the INF for K-Lite(in my experience) As for the others, just glancing at them, they look right. Run the file on your machine now, and go to regedit and see if they imported correctly. Just delete the keys when you're done looking so they don't execute next reboot.

command.0=Drivers\Creative\setup.exe -s -f1"%WIHU%\Drivers\Creative\audigy.iss" -f2"%SYSTEMROOT%\Temp\creative.log" Does not appear to work. ResultCode=-5 (ISS file not found) in the log. Perhaps WIHU isn't expanding the variables before executing the string?

I shall try it later.....thanks...

alrighty. Alittle confused after reading the website. It said if found (File section) it considered it newer and deselcted. Oh well, thanks for the clarificaiton. Drivers\Creative\setup.exe -s -f1".\Drivers\Creative\audigy.iss" -f2"C:\Windows\Temp\creative.log" I have tried that with and without the .\ in the -f1 switch, but in either case it cannont find the ISS file. I could just rename them all setup.iss, and be done with it, but was curious why this didn't work. Perhaps not appending the path? Need for %WIHU% now? Also, what environment variables are available within WIHU (the windows ones)? I tried %windir% in the above statement, and it didn't work properly, had to hard code it in.

I had long suspected it was that blasted LegacyDisable, i think I even posted about it.....though I never got around to actually adding it. I'm completely renovating my DVD over the next few days, guess I'll add it.

haha, gotta love those language misunderstanding

haha.... prathapml.. I'll look into the gpedit thing. I don't really need a new PC to test it on....just the current system....(new notebook about to be formated, good for test) I'm betting of the stubpaths, but I call my regedits from CMDLINES and GUIRUNONCE....and I don't remember teh screen. I'll check on my next format to be sure. Now the AVI thing that GM spoke about interests me, I hate that little box that comes up (MPC user)

Correct me if I'm wrong.... If I set %KEY%?="Hitachi" if the drive is called "Hitachi" it won't install? But if I set %KEY%?!"Hitachi" it will install it to JUST the hitachi drive? Blasted logic problems Hardest part of programming for me.

There is that one Very much appreciated Benjamin. Looks like I'll be remaking that DVD today

Where's a list for the status flags? In the INI it said to look, but I didn't find. I kept finding the strings for them, but not the hex values.

what's wrong with the Prescott? I haven't seen anything....links anyone?

if you're willing to spend about on average 200-300 dollars more for a LCD then a CRT, then there is little difference. If you get a LCD with a contrast ratio of 400:1 or greater, a response time of about 15ms or so (no more then 20 max) and resolution of 1280*1068 you'll have no problems. Its the response time that creates the ghosting, and the lower rate, the less you'll notice. Most LCDs will expanded the image, but keep in mind the native resolution plays a big part. WHen you go to a lower resolution, its creates it so each individual pixel is expanded to cover more to make up for the resolution. But if you spend the money, you'll be fine. Try to find an NEC, they usually don't lie about their specs.

Sweet. And just because you asked me once to gramar check it and everything, finisched is spelled finished in english. no c. Looks like I shall have to remake my DVD this weekend.

some people also use a normal batch file with ECHO commands to tell them what's going on (the "basic" method, where as RunOnceEX is the "advanced" method) and so they use GUIRunOnce. Thought i should post that it won't there as expected so they don't complain later on. Though this does simplify all those IF EXIST lines for people using CMDLINES.TXT to install something from ONE cd. It won't work with two CDs if they are in different drives however. (I'm just listing possibilities that people may try to use this with)

Just alittle language error.... Sure do wish I could read German Any progress on that NOT idea? If not, it's OK, i can keep with my current method till the next incarnation of the CD (week or two ) How are the command line switches interpreted? Are they just imported as strings, and then WIHU then expands any variables and the uses them, or what? Could you possibly make a variable for within WIHU for the PATH to the WIHU executable? as if the switches are read in as strings, /Users=\users1.ini won't work. (tried it) a %WIHU% variable would be good for that instance.

this will only work from CMDLINES.TXT if the CMD file is on CD. Won't work from SVCPACK or GUIRUNONCE. So you know.