Can't install

Can anyone please help? I had WindowBlinds running successfully (v4.5). I had a HD crash, got a new HD, reinstalled everything with no problems - except WB. Now whenever I try to install, it gets to nearly the end of the installation and shows the following:

'Heading: GLBIE.tmp. Bad image. Message: The application or DLL C:\windows\system32\OLE2.DLL is not a valid Windows image. Please check this against your installation diskette.' OLE2.DLL is in the folder. I have reinstalled it, just in case.

Then I click on 'finish', and get this message:
'Windows cannot find C:\2\2\wbconfig.exe. Make sure you typed the name correctly and try again. To search for a file, click start button and check search.' The file in C:\2

Next message;
'Could not execute the external program C:\2\2\wbconfig.exe'

I am running Windows XP Home SP2.

I'd really like WB back!
6,633 views 11 replies
Reply #1 Top
Make sure that you're trying to install the latest version of WB, if it's an older version, it may be looking for an older DLL.
If that's not the problem, you could try running the recovery console, and run chkdsk /r to restore any missing dlls.
Reply #2 Top
Thanks for your reply. I'm trying to install Windowblinds 4.5-enh.exe from the email I received from Stardock. I have reinstalled OLE2.DLL.

I have noticed that, although the installation path is specified as C:\2, the folder it goes in is the last one I used. For example, if I opened the downloaded file from the download application in Mozilla Firefox, the 2 folder will install in C:\Program Files\Mozila Firefox\2. Or if I open it from C:\downloads, it will install in C:\downloads\2. I still get the same error messages.

How weird is that?!
Reply #3 Top
The install path for WB is C:\Program Files\Stardock\Object Desktop\WindowBlinds.
Reply #4 Top
Not on my PC, it isn't! That's what I don't understand. It defaults to C:\2, although, as I've said, the \2 folder can go anywhere.
Reply #5 Top
C:\2 ???

oh man. i got enough trouble finding stuff with words and now it's numbers? I'm never gonna upgrade.
Reply #6 Top
Where is your Stardock Central installed? It should be C:\program files\stardock\SDCentral.
If it's installed to the wrong directory it could be causing the OD components to try to install to the wrong directory.

You could also try uninstalling everything and reinstall. Use ODNT Zapper. https://www.stardock.com/support/support.asp?product=5
Reply #7 Top
Ummm...I'm beginning to see a possible problem. The only product I have (and have paid for) is WindowBlinds. What is Stardock Central? Should I have it? And none of you seem to have this C:\2 folder. (I agree - what's with these numbers? )
Reply #8 Top
Sorry, I assumed you were installing the whole Object Desktop Suite, which installs via Stardock Central. (You install SDCentral, and use it to install Stardock programs) Where did you D/L WB from?
Not quite sure what to make of the C:\2 thing. WHen you install WB, if you aren't using SDCentral, make sure the install path is to C:\Program Files\.....(not sure if it should be just Windowblinds, or Stardock\Windowblinds) anyway, make sure that wierd "2" isn't in the path. Have you had this problem with anything else?
Reply #9 Top
My man - you are a star! I made sure it installed in C:\Stardock\WindowBlinds\ and hey presto! it works. Many thanks for your help!
Reply #11 Top
The "default" heirarchy for SD's Object Desktop apps is "C:\Program Files\Stardock\Object Desktop\XXX", XXX being the application name, in this case WindowBlinds. I was under the impression the standalone installer defaults to that path also, to avoid consternation if an Object Desktop subscription gets purchased subsequently, but your experience suggests otherwise.

Should you at some point in the future decide to go with the Object Desktop subscription, you'd be wise to uninstall the current version of WB (copying your skin folders to backup location first), then install Stardock Central and install all the individual apps you want from there, including WB. You still have control over the installation path if you wish to change it for any particular app, but at least that way Stardock Central will "know" about it and you won't have problems with subsequent updates.

Cheers,
Daiwa