New
#41
Well, then, lol...
Case closed.
Ok folks, call me "MICKEY THE DUNCE", I did not run that 'UninstallCleanup.cmd' as ADMINISTRATOR and that is what prevented the install from going thru. Everything is installed now and those black and gold icons are looking like new money. Thanks all for hanging in there with me.
FyrmnJ
Using the SiCo Black Large theme and I think these icons will be a bonus to my system....
I have just disabled UAC and am about to reboot - and will post back with new pics letting you know how they look.
I just tried to install the 64bit version and got all sorts of weird behavior.
On the reboot, I get the following error message:
After clicking the OK button, I get:
And after pressing CTRL + ALT + DEL I get:
So, I went digging into the system, and using Repair, and then opening a command prompt, I found that the files shell32.dll.bak and shell32.TMP existed in both %systemroot%\System32 as well as %systemroot%\SysWOW64. So, I renamed the .TMP files back to .dll files, and rebooted - now, I don't get the first image, but the second and third are the same.
So, I go back digging in the command prompt via Repair, and on a hunch, I search for other *.TMP files in %systemroot%\System32 - and find imageres.TMP and imagesp1.TMP. Changed those, and the ones in %systemroot%\SysWOW64 and finally I am able to get a login like normal.
Finally, I log back in - with UAC still off I see the script trying to do something, and it tells me I can enable UAC now - however, the folder icons are still the same yellow ones.
I suppose something happened in the process, but I thought that when I turned off UAC, and then ran a CMD file it would run with the correct privileges. I thought this was confirmed when I tried to right click the .CMD file and use Run as Administrator and it flashed on my screen and went away that this confirmed my supposition. However, now I am not so sure.
I will run a CMD prompt manually and then run the .CMD script and see if it works this time - if not, well, at least I have eliminated one part of the problem, and I can probably just as easily move those files to their respective locations in the CMD prompt in Repair to force it to work....
Oh, yeah, I get an error both times about not being able to create the CreateRestore.vbs every time I run the install file.
I think I found the problem - there were 15 occurrences of %SOURCEFOLDER%Data that I think should be %SOURCEFOLDER%\Data.
I have made the changes and will see if this works or not.
Well, it was a combination of that and the Ampersand in the folder name. I changed the & to AND and now it is creating a restore point. Yay!
Sorry johngalt, I just had to deal with the kids... So I've missed an ampersand for the vbs? just redownloading them now to re-check everything. REALLY, really sorry about these problems.
EDIT: ah the folder name!.. I usually test the packs on my virtual Machine but I had no idea Mark was doing these icons with the installer until he told me he had trouble and pointed me here.
The '%SOURCEFOLDER%' for the path usually includes the final back-slash for the path so I will do some testing and see whats going on with these. The scripts have on a whole worked in the past.
TBH, the problem went away when I figured out it was the Ampersand - so the missing \ after the variable was probably not needed - but it made it look prettier with all the rest of the code.
As you can see from my previous post, I got it working. Thankfully, I am enough of a DOS hound from yesteryears that I was able to muck around and figure out what was going on and fix it myself.
If need be I can upload the final version. However, there is one catch - when I ran the installer with the correct parameters finally in place, it said that the icons were already installed - which was untrue, it just found the backups. It then told me to run the delete_backup, which was sitting in the data folder with an extra _ in the name, so I had to manually rename (actually I created a copy) so that I could run it.
If this is manually renamed in the script, how about adding an option (if the backups are found) to allow the user to create the delete-backups script and run it, so you can keep it as a non runnable file?
OK, I am off to play tennis - ya'll getting some rep before I leave, though....