I am also having the same problem, I did the same steps as him. I have .net 1.1 and 2.0 beta and Ms office 2003 with seems to include debugging tools (which are currently disabled)

Note: I have 2x Geforce 6600gt's (dont know if that's useful or not)

Should I have posted in this or create a new topic? I didn't see any stickies that had a faq or other rules, etc.

I hope this can be fixed quickly because i bought OD mainly for wb 5.0

Would it be possible to get a list of dependencies of WB and OD in general? I've uninstalled unused windows components, hopefully wb doesn't depend on something that's been uninstalled
----------------------------------------------

WindowBlinds 5 BETA Troubleshooting Report:

STATUS : WB+ SRV+ HLP+ UI+

WindowBlinds is installed correctly on this PC.

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

You have one monitor in total.

(MAG LT565 LCD Display) 1 is attached to NVIDIA GeForce 6600 GT
'NVIDIA GeForce 6600 GT' also exists as device '\\.\DISPLAY2', but is not attached to the desktop.
'NetMeeting driver' also exists as device '\\.\DISPLAYV1', but is not attached to the desktop and is a mirror driver.
'RDPDD Chained DD' also exists as device '\\.\DISPLAYV2', but is not attached to the desktop and is a mirror driver.

There are one of two problems that can cause this issue:

1. Your system does not have database support. Although it is installed by default, the access driver might have been corrupted or lost. To verify whether it's installed:

-Open up your control panel located in the "Start Menu"
-Open up "Administrative Tools"
-Then "Data Sources (ODBC)"
-Click the "Drivers" tab
-Move the scrollbar to the right (Scrolling down the columns)
-Verify the filename ODBCJT32.DLL is listed

2. A file required for Windowblinds to run is missing.

Please make sure you have the file "skins.mdb" located within your Windowblinds directory (C:\Program Files\Stardock\Object Desktop\Windowblinds)

-Mike
[Stardock Support]

I have an AMD64 bit processor running XP Pro 32-bit.

The beta does not support the 64bit processor. Based on some other threads I've seen it requires a whole different version of Windowblinds and they will work on it after they finish with the normal version.

Beldroan: You are correct, a 64-bit processor does not imply a 64-bit OS. The OS version makes all the difference.
For this process, you might need your Windows XP disk handy:

-Go to Start->Run
-Type in "sfc /scannow" and press enter

This utility will verify the integrity of all of your Windows files and will overwrite any that may be corrupt or otherwise incorrect.

Let me know if this fixes your issue.

-Mike
[Stardock Support]

Checked this.  Everything seems to be there.  I don't have the CD with me so I can't run the sfc test.

Ran the SFC command and found no errors. Going to try to do the whole uninstall / install 4.6 / uninstall / install latest again routine.

Okay.. I researched some other things. THIS is what I had to do to get it working. Hope this helps others who are at WinXP SP2 and either have OEM or no CD.

From Microsoft site:

For original equipment manufacturer (OEM) Editions of Windows 2000 or Windows XP
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Step 1: Modify the registry keys
1. Locate the I386 folder on your hard disk, and then make a note of its path.
2. Click Start, and then click Run.
3. In the Open box, type regedit, and then click OK.
4. In Registry Editor, locate and then click the following key:
HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Setup
5. Right-click the Installation Sources entry, and then click Modify.
6. In the Value data box, change the value to the path of the I386 folder on your hard disk, and then click OK.
7. Repeat steps 5 and 6 for each of the following entries:
• SourcePath
• ServicePackSourcePath
8. Quit Registry Editor.

Step 2: Install Mdac.inf
1. Click Start, click Run, type C:\Winnt\Inf in the Open box, and then click OK.
2. On the Tools menu, click Folder Options.
3. On the View tab in the Advanced Settings box, click Show hidden files and folders, and then click OK.
4. Right-click Mdac.inf, and then click Install.
5. If you are prompted for your Windows CD, insert the Windows CD in the CD-ROM drive or DVD-ROM drive.
6. Click the I386 folder on your hard disk (typically, C:\I386), and then click OK.

Notes
• If you do not have the CD for your current Windows installation, click Browse, and then locate and select the I386 folder.
• If the I386 folder is a subfolder of the Windows folder, on some computers, you cannot select it.

In this case, type the full path in the Copy files from box (for example, type C:\Windows\I386 or C:\Winnt\I386), and then click OK.
7. Restart your computer.

I had the same problem as nanolithium i tried what beldroan said and that elimated the problem of wb buging me about the data source but i still don't have any skins in my directory. under my data sorce drivers ODBCJT32.DLL is not listed. if you could help i'd really like that

Ahhh, it's MDAC that WB wants. I too experience this problem, because I run a stripped down install using nLite (Link).

Glad to see someone discovered what exactly was causing the problem. A question for the WB devs though, why does the new WB required MDAC for skin manifest storage? I assume WB4 just used a flat file, did you guys just want to move to a real DB?

I still need help with windowblinds listing my skins its not asking for a data source but no skins are showing up in my directory.

I still need help with windowblinds listing my skins

This may be a stupid question, but did you click the little "refresh" button below the preview window in the WB config panel after placing or loading skins into "C:\Program Files\Stardock\Object Desktop\WindowBlinds" folder?

Note - I had to move the horizontal scrollbar below the skin listing in config panel after clicking refresh, to get them to display.

Just a thought.

have we given up trying to fix this issue?  don't want to have to pull windowblinds off my system, but I am being left with little choice.

still getting the db error.