Problem with WB5.51 on XP x64

Install goes OK, wblinds doesn't run

G'day all,

I've just installed the trial version of WB 5.51 on my XP x64 system.

The install seemed to go OK, but when I rebooted, I see the dreaded "Windowblinds is missing a core DLL file (WBLIND.DLL)" message.

In the WB install dir, sure enough there's no wblind.dll, but there is a wblind64.dll, and if I manually run wbload.exe, I get the default wb skin applied.

But then I can't run wbconfig or anything else to configure wb, I always get the wblind.dll message.

Obviously, they've made some changes to the libraries, but there doesn't seem to be anything in the readmes or anywhere else to help me figure out what to do to fix this behaviour.

I'm guessing that the wblind64.dll could be renamed and that might work, but since that particular dll is locked now that the default wb skin is applied, I can't do anything about that until I reboot (without wb) and try some things then.

I can't find any decent reference to this issue anywhere on the forum (all the references to this error message imply that whatever was causing it was fixed a couple of versions ago - which doesn't apply in this case).

Any suggestions or comments would be welcome!
Cheers,
PC Pete
1,163 views 1 replies
Reply #1 Top
BTW, I've tried to use the WB settings in Display Preferences, but while the default skins are listed, whenever I try to apply any of them, I get four (4) 32set.exe application faults. But at least part of WB is sort of working!

Oh, and after rebooting and renaming wblind64.dll to wblind.dll, wbconfig now starts up but immediately crashes with a UAE. So I guess I'm on the right track...

I can't find any details on the standalone (stub) *64.exe files in the wb directory, so if anyone could point me to some documentation, I'll try and fix this myself and get back with some answers...

I've also checked the install log, and it looks like wblind.dll was installed - but it's definitely nowhere on my system. I'm not sure what to make of that - there are some other anomalies in the install log, like wblind4.dll was created (and it doesn't exist anywhere, either).

Maybe I'm seeing symptoms of a completely different issue?