Jump to content
  • entries
  • comments
  • views

About this blog

Weird and wonderful little things I discover about computers..

Entries in this blog


Ok so I had to reinstall some software, and kept getting repeated installation failures even after system cleansing, restarts, safe mode, etc. Every time it would say:


"Installation failed due to one or more unresolved issues. Error I-001" followed by "Error: Cannot find installation. Check this program is installed before attempting to install" - LOL?!


Anyway, eventually I figured out that if you delete the following hidden folder, you remove the issue.. It's just InstallShield confusing itsself.


C:/Program Files (x86)/InstallShield Installation Information/ <--- Delete that folder and start the installation again. Problem solved.


Note: This is for Windows Vista/7 64bit.. For 32 bit I assume it will be in "Program Files" instead.

Note 2: In Windows XP it should be C:/Program Files/common/InstallShield Installation Information/ - I found that info online and dont use XP any more so I cannot guarantee it.


If ever you run into a similar problem, this solved them all for me without causing any problems. The folder is simply recreated properly. The folder you delete obviously has some corrupt / invalid data in it.


blog-0399027001323514510.jpgOk I got bored of junk default screensavers and wanted something with a little more class.. And despite not being much of a fan of Macs, I do LOVE their screensavers..


So I proceeded to find the Aurora screensaver and Flurry screensaver for Windows! Nifty!


But, both of them were getting literally 2-3FPS... Even on minimal settings.. WTF?


Wanna know the GENUINE fix for this issue on downloaded screensavers? Change the file extension from .scr to .sCr - I'm not kidding.. Try it for yourself.


I still hardly believe it myself, but I tried it and it genuinely 100% fixed the problem.. If I rename it back to .scr, it's slow again.. I have NO IDEA why windows does this (especially since its OWN screensavers are lower case .scr...) but it's genuinely a reality!


So there you have it.. Windows can't read its own file extension properly unless you randomly capitalise the 'c', despite the default ones not needing it.. Bizarre.