Wbconfig fails to run?

Please post a directory listing of your WindowBlinds directory.

Yes, wbconfig.exe fails to run, so does every other exe in the directory.  Here is my WindowsBlinds Directory. I can post a link to a jpg of this directory if necessary. Many Thanks for your help. Chris

FOLDERS

5imple Alpha
A Touch of Glass
Airframe
Anomaly
Apollo
Aquarium II
Artasia 3.5
Aura
Base
bazoob
Beacon
Blackcomb
ChristmasTime
Colony
Colours1
copper_deck_2
Corvette II
Cyclops
Devoir
Dissident
Dogmax
DreamLand VS
Fresco
GALAXY
Growler
Guardian
Hi-Fidelity
intrastate
lang
LaST (Cobalt) V1-2
LightBlue II
Longhorn M4 Plex
MacPC
mozmodern
My Halloween
Nascent
Noire
Orion(Cobalt)
Oxidized
passive
PocketPC
PreLuna II
Progressive
Quantria
Retro
Skeech
skincast
SoftCrystal
SouLuna
StealthOS
TabletPC
UniQue Blue
url
VectorCell
VistaXP
VistaXPWBv30
Windows 3.11
Xanth
XP Charcoal II
XP Copper  II
XPCobalt II

FILES
_Disabled.bmp
_XPDisabled.bmp
32Set.exe
Activate.exe
anim.dll
aot.wbp
bms.bmp
bms5.bmp
Clock.dll
core.dll
eula.txt
forums.url
INSTALL.LOG
null.bmp
od.ico
order.html
order.txt
quickl.wbp
readme.txt
rollup.wbp
Screen.exe
sig.bin
sig.bin.LOG
skincst.exe
Skins.mdb
smart.dll
tray.dll
tray64.dll
txtscroll.dll
ui64.dll
unzip32.dll
url.wbp
UserPermissions.txt
wb.bmp
wb.chm
wb.ico
wb.txt
wbback.bmp
wbconfig.exe
wbdb.dll
wbhelp.dll
wbhelp64.dll
WBInstall64.exe
wblind.dll
wblind64.dll
wbload.exe
wbload64.dll
wbmdi.bmp
wbmnu.bmp
wbperapp.ini
WbSrv.dll
wbtd.bmp
wbui.dll
wise_post.exe
x64.exe
xplogon.bmp
xpui.uis

Here is the start of the wb5.log file: Does the fact that I have an older  Nvidia PCI-E Quadro card have something to do with it?  I'm pretty sure that it is not DX9 compatible.

-- [Application] ----------------------------------------------------
Name:   Stardock Central
Path:   C:\Program Files\Stardock\SDCentral
Version: 2.20.357, build: 103

-- [System Information] ---------------------------------------------
Platform: Microsoft Windows Windows XP, 5.1.2600 Service Pack 2
Display: NVIDIA Quadro PCI-E Series
Driver Version: 7.7.5.6
System Dir: C:\WINDOWS\system32
Time / Date: 14:10:50 -- Tuesday, November 29, 2005

-- [Installing] -----------------------------------------------------
Server:  http://sdcentral2.stardock.com
Server Dir: public
Network Id: odnt
Name:  WindowBlinds 5
App Id:  wb5
Installed: False
Version: 5.00.001
Type:  production
Reg Key: WindowBlinds
Install Dir: C:\Program Files\Stardock\Object Desktop\WindowBlinds
Exe:  wbconfig.exe
Last Updated: 11/28/2005

Here is a link to an jpg of the directory

http://emctempest.com/ebay/WB5Details.JPG

Thanks,

Chris

Chris (The Figurehead), please zip the sig.bin and the sig.bin.log file and email them to [email protected] so I can see what was awry there. Remove them and right-click on the WindowBlinds 5 component in Stardock Central and select the "Activate w/logging" option.

That should fix you up, as your account looks right here. If not, find the activate.log in the SDCentral dir and please send that to me as well.

Both the sig.bin & sig.bin.log files are locked. I cannot copy, move or paste them anywhere, let alone zip them. I unloaded everything I am running from Stardock.  Still no copy/paste/cut/etc.  I will reboot and see if I can get them to zip.

As for the WB5 right click in Stardock Central, I do not get any option for "activate w/logging". Here's what I get:

Run App

Uninstall

Open Folder

Hide Folder

Check for App updates

Register Products

Archive App

Restore Archive

Refresh

I am gonna send this, reboot, try to get those two files to you, and then repost what happened. Thanks......

Look for a .cmd file autorunning on your PC - use msconfig.

Thats why sig.bin is locked.

I rebooted, still no luck. So I stopped a stardock file (TrayServer.exe) from loading (via msconfig) and the SIG.bin file did not exist anymore, but the sig.bin.log is still there. I will email it to you. Then I tried to run WB5 from OD via Stardock Central, it ran, asked me for my OD SN & email, and it activated WB5 and all is well. it is running perfectly right now. Thank you for your help. Let me know if there is anything else I can do to help anyone else with this problem. The sig.bin.log file looks messed up with a bunch ascii on the 1st and last lines, but then again, I do not know what is suppoesed to be there. Thanks again, Chris