I have a licensed copy of CCDInspector2 v2.1.5 running on my Windows XP 32-bit machine. When I try to update to v2.1.6 the installer dies with an error "The folder path 'Program Files' contains an invalid character" (see attached) and then I get an "Installation Incomplete" pop-up window. I have tried to run this update three times now tih the same unsuccessful result.

The path is the same path that v2.1.5 is currently installed and working at. Here it is cut and pasted: "H:\Program Files\CCDWare\CCDInspector2". I am running from a RAID hence the "H:\" instead of "C:\".

--- Kerry

ErrorBox.jpg (19 KB, 23 downloads)

Hi Kerry,

There was no change made to the installer since version 2.1.0, so I must think something on your computer has changed since 2.1.5.

I've installed 2.1.6 on D:\ drive and it worked with no errors.

Have you tried to uninstall 2.1.5 and then do a clean install of 2.1.6 instead of an update?

Regards,

-Paul

Well I have installed other software in the same "Program Files" path since v2.1.5 and they all installed fine, including CCDStack and PemPro.

I tried doing an automatic uninstall of v2.1.5 and it failed with a fatal error: "The folder path 'Program Files' contains an invalid character" - same error as doing the install.

I then deleted the v2.1.5 folder and cleaned out the keys using 'regedit'. No CCDInspector on the machine at all. I downloaded a new copy of the v2.1.6 installer from the CCDWare site and tried to install - same problem. I even tried to install to a location on my PC that didn't have "Program Files" in the path and I *still* got the "'Program Files' contains an invalid character" error. Where is the installer getting this "Program Files" path?

So now I am dead in the water without either version installed.

--- Kerry

** UPDATE **

Paul,

I downloaded a utility called Windows Installer Cleanup (freeware) that is designed for recalcitrant software that won't uninstall. I ran it against the installer database and deleted the old CCDInspector v2.1.5 reference OK. I then tried reinstalling v2.1.6 and it installed OK with no errors.

I suspect something in the Windows installer database was corrupted or the installer/unistaller might have a bug I tickled - don't know for sure.

--- Kerry

Hi Kerry,

Thank you for the update. I'm glad to hear everything's resolved. There's been a few reports lately of issues with the uninstall of v2.1.5 on XP. I suspect there was some Windows update after 2.1.5 that broke the installer in some way. It should work cleanly for the next update, but do let me know if you encounter any more problems.

Regards,

-Paul