Powerhouse
Content Type
Profiles
Forums
Events
Posts posted by Powerhouse
-
-
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.
0 -
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).
0 -
Would just like to say thanks for working with me on these scripts, and I hope you get well soon. My only advice, take ColdEeze.....reduces the duration and severity of colds big time.
I have a question on the CursorXP script you did as well on a previous post, but lets finish the WindowBlinds, and BootSkin problems first...
0 -
Script doesn't even seem to start, get this message...
Error: "If" statement has no matching "EndIf" statement.
Also noticed there are no more Registry entries at the bottom. So not sure how your making the correct skin load.
0 -
Ok, found some new problems with the new WindowBlinds script...
1. #cs before Run causes the script to hang. Removing this causes the script to continue.
2. I get this error, when the Script is just about finished.
Line 0 (File "C:\Install\Applications\WindowBlinds\WindowBlinds_440.exe"):
$wba = FileFindNextFile($search)
Error: File Handle invalid. Make sure that the FileOpen command succeeded.
0 -
Ok, got a Problem with one of the tweaks, and needed some further assistance...
1. I've tried the Changing Wallpaper Tweak, and have yet to get it to work (either installed from the Cmdlines.txt registry import entry, or from the Current logged in user registry tweaks). Here is the command for a refresher...
;----- Change the Default Wallpaper to the one I want
[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Desktop\General]
"BackupWallpaper"="c:\\windows\\web\\wallpaper\\MX1600.jpg"
"Wallpaper"="c:\\windows\\web\\wallpaper\\MX1600.jpg"
Now, the wallpaper I have listed is a 431KB jpeg file, that I have under $$\Web\Wallpaper.
As I have said in a previous post, it appears any Jpg file, gets converted by Windows to a BMP file (which is placed under C:\Documents and Settings\"Userprofile name"\Local Settings\Application Data\Microsoft\Wallpaper1.bmp). Here is the Reg Key info, and you can see the key that converts the wallpaper...
[HKEY_CURRENT_USER\Control Panel\Desktop]
"ActiveWndTrkTimeout"=dword:00000000
"AutoEndTasks"="1"
"CaretWidth"=dword:00000001
"CoolSwitch"="1"
"CoolSwitchColumns"="7"
"CoolSwitchRows"="3"
"CursorBlinkRate"="530"
"DragFullWindows"="1"
"DragHeight"="4"
"DragWidth"="4"
"FontSmoothing"="2"
"FontSmoothingOrientation"=dword:00000001
"FontSmoothingType"=dword:00000002
"ForegroundFlashCount"=dword:00000003
"ForegroundLockTimeout"=dword:00030d40
"GridGranularity"="0"
"HungAppTimeout"="100"
"LowPowerActive"="0"
"LowPowerTimeOut"="0"
"MenuShowDelay"="4"
"PaintDesktopVersion"=dword:00000000
"PowerOffActive"="0"
"PowerOffTimeOut"="0"
"ScreenSaverIsSecure"="0"
"ScreenSaveTimeOut"="600"
"ScreenSaveActive"="1"
"SCRNSAVE.EXE"="C:\\WINDOWS\\System32\\logon.scr"
"TileWallpaper"="0"
"UserPreferencesMask"=hex:9e,3e,05,80
"WaitToKillAppTimeout"="1000"
"Wallpaper"="C:\\Documents and Settings\\Powerhouse\\Local Settings\\Application Data\\Microsoft\\Wallpaper1.bmp"
"WallpaperStyle"="2"
"OriginalWallpaper"="C:\\Documents and Settings\\Powerhouse\\Local Settings\\Application Data\\Microsoft\\Wallpaper1.bmp"
"WheelScrollLines"="3"
"Pattern Upgrade"="TRUE"
"Pattern"=""
"ConvertedWallpaper"="C:\\WINDOWS\\Web\\Wallpaper\\MX1600.jpg"
"ConvertedWallpaper Last WriteTime"=hex:00,73,d0,d7,b7,21,c3,01
Now, I've read where people have gotten this to work, and I'm wondering if there is some other setting that needs to be changed in Windows (perhaps the installation of a program like MS Plus!) to allow jpegs to be installed as Wallpaper.
Thoughts? Opinions? Help.....?
0 -
Well, I've tried both BootSkin and WindowBlinds, and am unable to get either to load the skin correctly. I have checked all the registry entries, but it appears there is something I'm missing and can't find.
The Strange thing is, if you actually click on either of the Skins (WinBlue for BootSkin, and Abracadabra - in my case - for WindowBlinds), and then apply the registry tweaks, they work fine. Must be missing some setting in the RAR.sfx files. Not really sure.
Is there a way to have AutoIt run the skin files, and perform the steps necessary to install them as part of the overall script?
So for example, after the WindowBlinds software is installed, the skin you want (*.wba file) is doubleclicked, and run (which requires the bubble in the system tray to be clicked to apply it). Or for BootSkin, when you double click the file, BootSkin comes up, and you need to click Apply, then Ok, to have the Skin installed.
0 -
Ok, the new BootSkin script is working very well. Only problem now is getting the correct Skin to load. Apparently, the two Reg keys listed don't seem to work (it keeps starting with the TimeWarp skin (and I have been unable to find where this setting is in the Registry.
These are the paths I've found so far...
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
I'll look tomarrow, if there is a hidden switch I don't know about....
0 -
Ok, I have been testing the BootSkin one, and have found a few problems (and stuff I needed to change for my install).
I guess you are installing a version that comes with LogonStudio (I have the freeware version from StarDock's website), as I dont have any of that Logon Studio stuff.
The script works good (and even the Wincustomize Window closes down now), but the Skin part doesn't work correct. Here is what I've done to correct it so far...
1. I fixed the name problem, should be this..
$SK_1 = "WinBlue.bootskin"
2. When the skin is extracted from Skins.exe, it is placed in the BootSkin folder (I changed the location in my install to GUI\BootSkin, and this is where the Skin is placed. However, this is incorrect, BootSkin reads all it's skins from the BootSkin\skins folder.
Ultimatly, what needs to happen is, the file is extracted from Skins.exe, and then executited. This will create the WinBlue folder under \skins, then BootSkin comes up, and you need to just click the Apply button. Then Click Ok when the new window pops up. Then Close the BootSkin Window.
0 -
Did the upgrade to my Unattended CD, and got some strange issues.
1. cleanup.cmd doesn't seem to work for me anymore. At least the part about it rebooting the system after its done.
2. Winzip for some reason, needs to re-register its known extensions. There was no problem with Winizip prior to installing of these updates.
0 -
Anyone figure out how to turn off the Check for Update Online after the initial install from RunOnceEX? This and having the Stupid Tray Icon (until you remove it from within Registry First Aid) are starting to p*** me off.
0 -
Wow, ok, 1 at a time....hehehe...
1. Here is the reg key I use to install a theme with WindowBlinds v4.4 (this in addition to the RunOnceEX entry above)...
;----- WindowBlinds Silent Theme install
[HKEY_CURRENT_USER\Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX]
"Skinset"="C:\\Program Files\\GUI\\WindowBlinds\\Abracadabra\\Abracadabra.UIS"
"Skinset2"="Abracadabra"
The reason why I do the reg key, is because WindowBlinds needs you to click a popup tray bubble to apply the skin. Well you can't do this during RunOnceEx, so by adding the reg change, the skin is applied.
2. I found a couple of reg entries for BootSkin, but the problem is, Bootskin wants you to Apply them when the skin is selected. So my current work around is to run the Skin from RunOnceEx...
REG ADD %KEY%\082 /VE /D "BootSkin Skin" /f
REG ADD %KEY%\082 /V 1 /D "%systemdrive%\Install\Applications\BootSkin\WinBlue.bootskin" /f
REG ADD %KEY%\082 /V 2 /D "taskkill.exe /F /IM BootSkin.exe" /f
Then add this to the registry...
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BootScreen\Parameters]
"INIPath"="C:\\PROGRA~1\\GUI\\BootSkin\\Skins\\WinBlue\\BootSkin.ini"
This enables the Skin I want. Was hoping there was an easier way though.
3. Actually still having problems with IconPackager and CursorXP. Both popup windows after they are installed. CursorXP brings up the Mouse Properties Screen (from Control Panel). While IconPackager brings up the same window. The workaround is actually easy, after cleanup.cmd is run and the system reboots the folders go away.
0 -
Ok, so I have been able to install themes for CursorXP, IconPackager, and WindowBlinds (had to use a Reg Key for WindowBlinds to make it totally work), but am not sure how to do the same with BootSkin (1.05). Here are the codes I've been using in RunOnceEx (please note, that each of the *.exe Installs were created with AutoIt 3 scripts).
REG ADD %KEY%\075 /VE /D "CursorXP 1.3" /f
REG ADD %KEY%\075 /V 1 /D "%systemdrive%\Install\Applications\CursorXP\CursorXP_1.3.exe" /f
REG ADD %KEY%\076 /VE /D "CursorXP Skin" /f
REG ADD %KEY%\076 /V 1 /D "%systemdrive%\Install\Applications\CursorXP\Abracadabra.CurXPTheme" /f
REG ADD %KEY%\077 /VE /D "IconPackager 2.5" /f
REG ADD %KEY%\077 /V 1 /D "%systemdrive%\Install\Applications\IconPackager\IconPackager_2.50.exe" /f
REG ADD %KEY%\078 /VE /D "IconPackager Skin" /f
REG ADD %KEY%\078 /V 1 /D "%systemdrive%\Install\Applications\IconPackager\Abracadabra.ip" /f
REG ADD %KEY%\079 /VE /D "WindowBlinds 4.4" /f
REG ADD %KEY%\079 /V 1 /D "%systemdrive%\Install\Applications\WindowBlinds\WindowBlinds_4.40.exe" /f
REG ADD %KEY%\080 /VE /D "WindowBlinds Skin" /f
REG ADD %KEY%\080 /V 1 /D "%systemdrive%\Install\Applications\WindowBlinds\Abracadabra.wba" /f
REG ADD %KEY%\079 /VE /D "BootSkin 1.05" /f
REG ADD %KEY%\079 /V 1 /D "%systemdrive%\Install\Applications\BootSkin\BootSkin105.exe" /f
It appears the BootSkins have 3 separate files (note one like all the other applications).
Anyone have any advice or tips on getting this to work?
0 -
Here is what I added to to RunOnceEx to get it to install silently...
REG ADD %KEY%\042 /VE /D "Registry First Aid 3.4" /f
REG ADD %KEY%\042 /V 1 /D "%systemdrive%\Install\Applications\RegistryFirstAid3\rfasetup.exe /SILENT /SP-" /f
REG ADD %KEY%\042 /V 2 /D "taskkill.exe /F /IM reg1aid.exe" /f
0 -
I'm a little lost with this one. Where are you guys getting the .msi file from? My ACDSee 7 is an .exe file (acdseepowerpack.exe).
0 -
I'm using the onboard sound for an Nforce2 chipset and here were the locations of my two keys (both set to 5.1 surround sound)...
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Enum\NVAX\NFORCE_VAD\4&24B908&0&0000\DirectSound\Speaker Configuration]
"Speaker Configuration"=dword:00000006
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Enum\NVAX\NFORCE_VAD\4&24B908&0&0000\DirectSound\Speaker Type]
"Speaker Type"=dword:0000000b
Thanks for the great help SiMoNsAyS...
0 -
OMG, this is one Registry setting I have searched the Net for, and have come up empty. Hopefully someone else has found a Reg key for this.
0 -
Hey Parathapml,
My point of the NAV problem post, was to maybe put that info in your registry section to alert people to this potential problem. In my own registry tweaks file, I put this as the header (just for my own heads up)...
;----- These NTFS tweaks improve file system performance
;----- 1st tweak could cause problems with NAV, set to 0 to fix.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"NtfsDisable8dot3NameCreation"=dword:00000000
"NtfsDisableLastAccessUpdate"=dword:00000001
"Win95TruncatedExtensions"=dword:00000001
Or you could just put a note like this...
;----- These NTFS tweaks improve file system performance
;----- If you encounter a problem with NAV starting up, You can fix this by setting
;----- the first tweak to 0, or please check the next Registry entry to fix it.
This would be the very next registry key...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"vptray"="\"C:\\PROGRAM FILES\\Symantec Antivirus\\VPTray.exe\""
Both of these solutions fix the issue.
0 -
Just reporting what I have encountered. Might not affect everyone with NAV (I just noticed the problem running SAV9). Changing the dword to 0 fixed the problem for me. I believe its a known problem with Norton.
0 -
Found another problem with one of the Registry Tweaks listed.
;----- These NTFS tweaks improve file system performance.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"NtfsDisable8dot3NameCreation"=dword:00000001
"NtfsDisableLastAccessUpdate"=dword:00000001
"Win95TruncatedExtensions"=dword:00000001
The problem was a folder opening at Windows startup called C:\PROGRA~1\Symantec. The NtfsDisabled8dot3NameCreation dword caused this problem with NAV (Check out This Thread - on page 28).
Change the dword to "NtfsDisable8dot3NameCreation"=dword:00000000
0 -
Funny you should mention WA5.05, as that is what I am using....
With 5.05, the skins don't have names like K-Jofol_V5.wal. There is a skin.xml (not sure if this is the same thing or not) as well as a bunch of sub-folders (about, fonts, images, opensource_notifier, scripts, stickmode, window, xml, etc) which appear to be different for each theme.
0 -
Another question for the Registry Experts...
I use the following key to have all folders use the Detail Mode...
;----- Detail mode in all folder
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Streams]
"Settings"=hex:09,00,00,00,04,00,00,00,00,00,00,00,00,77,7e,13,73,35,cf,11,ae,\
69,08,00,2b,2e,12,62,04,00,00,00,03,00,00,00,43,00,00,00
My question: Is there a key that will make Control Panel's view Icons instead of Detail.
0 -
Need some help...
After installing the Lusetup.exe file (downloaded from the first page) to update Live update to ver 2.5, I get a folder popping up called C:\PROGRA~1\Symantec, every time I boot into Windows.
After doing a little research, it appears that Lusetup.exe creates a second folder in Program files (C:\Program Files\Symantec) instead of using the default (C:\Program Files\Symantec AntiVirus). Is this correct? Anyone have any idea what is causing the folder C:\PROGRA~1\Symantec to open when starting Windows?
0 -
I kinda found a way to make skins available for Winamp. Basically, copy the Winamp Skins you want (from C:\Program Files\Winamp\Skins) to ($OEM$\$Progs\Winamp\Skins\). This will copy the skins you want for Winamp. Now If someone knows a Reg file to actually load the skin in Winamp instead of having to manually do it, that would be great....
0
BootSkin Skin Install from RunOnceEx...?
in Application Installs
Posted
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...