Powerhouse

Sorry for the delay, was working on some other projects the last few days. So without further delay, here are the updates on the new scripts... 1. They all seem to work fine from within Windows. Yet when doing an unattended install, none of them (meaning CursorXP, IconPackager, BootSkin, or WindowBlinds) is able to load the skin I have listed. So what I was able to get out of the brief install screens during RunOnceEx... CursorXP complained about not being able to find Themes\"themename". IconPackager didn't list any problem, yet the skin I wanted loaded wasn't. BootSkin didn't load the correct skin (and the skin I wanted again wasn't installed). WindowBlinds seemed to load correctly, and tried to install the Skin, yet the skin wasn't found. When I mean the skin's weren't loaded, I mean they aren't even listed under the tools - shell folder under Program Files. I'm thinking there is a problem with the following part of the .au3 file.. $search = FileFindFirstFile ( @WorkingDir & "\Skin\*.bootskin" ) If $search <> -1 Then Do Sleep ( 500 ) $File = FileExists( $DL_1 & "\BootSkin.exe" ) Until $File = 1 Also, I believe there needs to be a delay at the end of each script, to enable it to finish processing, before the next script begins. I'll add a 7 second delay at the end of each script and see if that helps.

Ok, found an Issue I'm hoping someone can help me with. I have read in the nForce Forums, that there is an issue with getting Winamp to play on a 5.1 speaker setup (no sound from the rear speakers). The fix is to go into Options\Preferences and under Plug-Ins choose Output. Click on Directsound, and the click configure and enable hardware acceleration. This allows Winamp to output to 5.1 speakers. However, after using the MSI install with the following winamp.ini file, I no longer see directsound listed in Output (only waveOut output v2.0.2a). [sETUP] XAGENT=0 XLIBRARY=1 XINTEX=1 XHOTKEY=1 XJUMP=1 XTRAY=1 XMODERNSKIN=1 XAUDIO=1 XWMA=1 XMID=1 XMOD=1 XOGG=1 XAAC=1 XMP3ENC=1 XMP4=1 XCDPLAY=1 XSONIC=1 XCDDB=0 XWAV=1 XVIDEO=0 XNSV=1 XAVI=1 XVISUAL=0 XTINYFULL=0 XAVS=0 XMILKDROP=0 XEXTRA=1 XSIGNAL=1 XWRITEWAV=1 XDCOUT=1 XREGOPT=1 XDIRCONT=1 XTYPECONT=1 XNETSCAPE=0 XAUDIOCD=1 XDESKTOP=0 XQUICKLAUNCH=1 XSTARTMENU=1 XALLSHORT=0 XINET=0 XSKIN=AR7 XName = "xxxxxxxxxx" XKey = "xxxx-xxxxx-xxxxx-xxxx" INSTALLDIR = C:\Program files\Winamp It looks like XDCOUT=1 should enable this in Winamp, but it apparently doesn't. Another issue is the Skin install. I have the skin AR7 already in the Winamp folder (C:\Program Files\Winamp\Skins\AR7), yet when I load the MSI with the above INI file, only the Modern Skin is installed. Am I missing something? Any help with this would be much appreciated. Update #1: Bah, found that I was missing the XSKINSETTING= section and this fixed the skin loading problem. So just need how to put the directsound plug-in back in the Output section. Update #2: Ok, found the two missing files...out_ds.dll and out_disk.dll. These are found in your Winamp.rar files (specifically dcout.cab and writewav.cab). Just copying these files to the Plugin folder fixes the problem. I'm guessing these files aren't included in the MSI file?

I've tried some switches as well, and can't get this to install silently. I see there is a link that says he has a custom.msi script, but have yet to hear back from him (been a few weeks now). Anyone else have the switches to install WinMX silently???

****, lots of testing... Ok, here is what I found. Changing WinWaitDelay to 1000 (instead of 250) makes a big impact on how the scripts run. Currently, sometimes the scripts run to fast, and if you dont have a fast PC, it wont be able to keep up. 1. IconPackager: I believe you have a different version than I do. I am using 250h, so when you try to install the skin, it's looking for something different. So unless I can get your version, or I send you mine, wont be able to work on this. I believe the 250h is the newest version out. 2. BootSkin: Looks good, am going to test it Unattended and will let you know. Update: Just did another unattended and BootSkin again stalls at the first "Next" screen. Once you click Next the script continues. Then, the part about installing the Skin, never comes (Skin isn't copied over, and the default Skin is used). 3. WindowBlinds: Here is the old version that works... WindowBlinds_440.au3

Hmm, I actually seem to have the problem with WinRAR. It's installed, yet not associated with any *.rar files. Do you think that each app is canceling out the others associations?

Time for an update... So I ran my Unattended CD with the changes to CursorXP, WindowBlinds, and BootSkin, and found these problems... 1. CursorXP: The Mouse properties comes up, when I click OK to close the window, the script seems to finish, but the correct skin is not installed (it's not even listed). 2. WindowBlinds: Wrong Skin is installed (its acutally the default skin that is listed that is installed). Again, the skin I want loaded isn't listed in the application. I'm guessing that the Skin.exe portion of the script isn't running correctly. 3. BootSkin: Waits for the first Input (up until after the Browse section), then it will pickup and run the rest of the script. However, the correct skin isn't installed (and again it's not even listed in the application). I believe there might need to be some delays put in between the launching of the various parts of each script (as this seems the most likely cause, as each script seems to run fine, once I'm in Windows). I'm going to play around a bit with each script, and I'll post back what I find.

So I have Winzip9sr1 installed (through the method listed in this thread. I'm using this line in my RunOnceEx.cmd file... REG ADD %KEY%\067 /VE /D "WinZip v9sr1" /f REG ADD %KEY%\067 /V 1 /D "%systemdrive%\progra~1\WinZip\winzip32.exe /noqp /autoinstall" /f However, .zip files aren't registered in the system upon first boot (brings up the printer error). Which is strange as I have booth WinRAR and Winzip installed and you would think one or the other would register .zip files. Anyway, if I open Winzip for the first time, I get the message... For full access to WinZip's shell interface, WinZip must be properly associated with Zip files. However, WinZip is not currently associated with Zip files. Associate WinZip with Zip files now? So am I missing a switch in my RunOnceEX, or do I need to adjust a registry setting to fix this? Or maybe just install WinZip before WinRAR (or after)? Anyone have a clue, cause I sure don't...

Yep, works good. Funny thing about these scripts...I might have problems having to click buttons on occasion, but when you do it from RunOnceEx, they always work without a problem. Kinda strange, but that's why I'm not a programmer...hehehe After seeing the work you've done to BootSkin to get it to load a Skin, I can't wait to see you fix IconPackager. I've been trying it, and its a b***h. Lots of screens you need to click just to install and load the Package. Oh, and one more thing about the... If WinExists ( "Object Desktop" ) Then WinClose ( "Object Desktop" ) The problem apears to be the time set to wait in the script. For IconPackager, I set the Sleep time to 5000, and now the Window will close. I think there wasn't enough time between when the Finish section was done, and when the above command was run.

Hmmm, no replies, thought people would actually be interested in this. Anyway, here is what I've got so far, from RunOnceEx... REG ADD %KEY%\001 /VE /D "Some music while everything installs..." /f REG ADD %KEY%\001 /V 1 /D "%systemdrive%\Windows\system32\oobe\images\title.wma" /f However, doing it like this causes WM9 to startup, and you have to fill in all the info before the music starts to play. So my new question is....how does MS do it from oobe, with WMP9 running? Is there some kind of switches I need to run it hidden?

Ok, strange stuff. If #cs is listed before run, I get the following error... Line 0 (File "D:\the location of the file on my hard drive\BootSkin\BootSkin_1[1].05.au3.exe): Run ($DL_1 & "\BootSkin.exe") Errir: Unable to execute the external program. The system cannot find the file specified. The actual file name is BootSkin_1.05.exe, so not sure where it's getting BootSkin.exe from (I also removed the #ce just in case it might have caused problems too). So if I remove that line, the script runs again. Now, here is the second weird thing. The program comes up, but nothing happens. I have to click Next at the Welcome screen. Then I have to click Browse, enter the location of the program (C:\Program Files\Tools - Shell\BootSkin), click OK, then Next, and then the script starts running again. If I check the Tray, it just says "Line: WinWaitActive". I'm wondering if your running this on a virtual system, and its super fast, so you wont see some of these problems?

Script seems to hault at the WinCustomize Window. Doesn't search for the Skin at all... Also, the part where... ; WinCustomize Window Sleep ( 500 ) If WinExists ( "WinCustomize" ) Then WinClose ( "WinCustomize" ) Doesn't seem to work (doesn't work in IconPackager either). The folder WinCustomize comes up, but WinClose doesn't seem to do anything. Not sure if maybe the Window isn't active, or maybe WinClose isn't recognized (after all the script haults at this point). I'm thinking maybe you need to do a Control+W to close the window (or ALT, F, C).

Ok, after doing lots of research on the matter, I found a file that needs to be copied as well as the reg tweaks to make BootSkin work from RunOnceEx. Basically, you need to run BootSkin, install the skin you want to use. Then copy the file vidstub.sys (from c:\windows\system32\drivers). For Example, I'm using a skin called ab_bs. So after installing the skin, I copies vidstub.sys. I put this file in my $$\System32\drivers folder. Then I copied these registry entries into my softwaretweaks.reg file (that installs after RunOnceEX)... ;----- BootSkin Silent Theme install ;[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BootScreen\Parameters] ;"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\ab_bs\\BootSkin.ini" ;[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\BootScreen\Parameters] ;"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\ab_bs\\BootSkin.ini" ;[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BootScreen\Parameters] ;"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\ab_bs\\BootSkin.ini" That's it. When Windows starts up, the correct Bootskin is running.

Ok, saw in This Thread how to turn off the splash screen, and the title.wma music. But I was wondering if there was a way to play this wma file (or any wma file) while all the programs in RunOnceEx are being installed?

Any update on the BootSkin problems Nologic? Just as an update, the Registry settings don't seem to work. The correct Skin has to be "Activated" within BootSkin for it to take affect.

So after searching through hundreds of threads, I have yet to see a Registry setting (or any setting for that matter), to choose a screen saver. Does anyone have the tweak to set this up?

Hey NoLogic, I figured out how to load Themes for CursorXP, thanks to your hard work. Here is the script... Using this method, you can load any CursorXP theme you put in the \Themes folder, as long as you specifiy the name of the theme in $SK_1. Couldn't have done it without all your input (as in fact, I only added on the last little bit...

Well, instead of using ProcessWait (skins.exe), why not just put a sleep value there. Not really sure you need it though, as the point of the script is to install a skin (just 1).

Go figure, I go to tell you the good news, and my cable service goes out. Well, that last fix did the trick. I had to make one change, that was to increase the Sleep time to 2 seconds before clicking button18... EndIf ;ProcessWaitClose( "Skins.exe" ) ControlClick ( "Installation Complete", "&Finish >", "Button3" ) ; Configuration ProcessWait ( "wbconfig.exe" ) ;WinWait ( "WindowBlinds Advanced Configuration" ) Sleep ( 2000 ) If $SK_1 <> "" Then ControlFocus ( "WindowBlinds Advanced Configuration", "", "Button18" ) ControlClick ( "WindowBlinds Advanced Configuration", "", "Button18" ) This gave it time to pick the correct skin, and then apply it (with a setting of 500, it would just select the default skin selected because it was so quick). Thanks for all the help with that problem, now for the BootSkin issue....

Hmmm, this is so strange. It looks like it should work, yet it never selects the Find another skin link (and the script is paused). If I manually click the Find another skin link, the script will continue, and everything works.

Still stuck as listed above. Not sure why it wont select the "Find another skin" button. Especially when the whole rest of the script works fine. Maybe you need a pause in there somewhere. Are you sure it's button 18, maybe that is the problem?

Nope, same thing happens as my above post.

It happens before the name is being sent. So basically, the WindowBlinds Advanced Configuration comes up, and just sits there. If I click on Find another skin, it will fill in the skin name, and continue on with the script.

Ok, now your really close, it still hangs at the Find Skin Screen. However, if I click the Find Another Skin button, the script continues to run, and the skin is installed without a problem. So just need to figure out why it hangs at the Find Skin Screen...

Hehehehe, no problem, your on the right track. It does Hang (well after 4 seconds). I guess the steps appear to be the following... 1. Click Find another Skin. 2. Enter Skin name. 3. Click Enter. 4. Click Apply this skin now. 5. Wait 4 seconds for skin to load. It's hanging at the Find another Skin part. I'm testing your new script now.... [update] Nope, new script above still hangs at the Find another Skin section. If I click find another skin, it will continue on with the script (all they way through to step 5), but the Skin doesn't load. Its as if, the Apply this skin now button wasn't clicked.

Ok, script gets hung at the "WindowBlinds Advanced Configuration" screen. It appears to be getting stuck at the Finding Skin screen (not sure if it is even looking, but I see where your going, and this looks promising).