I have just built a K8055 kit and it has tested OK with the K8055_Demo and Version 1 .DLL on my desktop PC. However, when I upgrade the .DLL to V2.0.0.1 OR V3.0.2.0 and try the corresponding .EXE demo files, I get “Card not found” when I hit the “Connect” button and when I hit “Find” it just greys out the radio buttons in V2 and V3 K8055_C.DLL (V3.0.0.1) and produces a “run-time error ‘380’, Invalid property value” error window with V3.0.2.0. Clicking ‘OK’ to this window closes the demo program. Strangely, on my laptop, all these versions work perfectly although I have found that unplugging the USB connector whilst V3.0.2.0 is running also generates the above error window. Both PCs are running Windows XP SP2 using USB2.0 ports.
I am uncertain whether the .DLL files have to be installed in both the Windows/System32 folder as well as the same folder as the .EXE file, so I ensure that the appropriate .DLL version is in both. Are any other (System) files required ? For example, I note that trying to run the K8055_Demo.exe file in the V2 BC++ Project folder on the laptop generates the error message “Unable to locate vcl60.bpl”. This file is not in the downloaded package.
I have trawled the forum looking for clues but can only find a reference to Windows Vista problems with .DLL versions.
If you have copied the new DLL version 3 to your .EXE file folder and to the Windows/System32 folder then it should be OK.
Anyhow it seems the application is trying to use wrong DLL.
The vcl60.bpl is included to the Borland C++Builder. I think the BC++ Project files can be run only if the Borland C++Builder is installed.
Indeed, it does seem that any of the Demo applications will find their appropriate version of the K8055D.Dll file, as evidenced by hitting the ‘Show DLL’ button in the applications. But only Version 1 of the DLL will find the card. Windows, via Device Manager, shows that the card has been recognised OK. I have tried this with the .DLL file in the same folder as the .EXE, in C:\Windows\system32 and in both locations but with no combination can I get communication between the .DLL and the hardware.
I don’t know how else to proceed to diagnose and debug this further. Can you give me any pointers ? I assume that later versions of the .DLL do not have to be (re-)registered with Windows. If it is relevent, I have .NET Framework 1.1, 2.0SP2, 3.0SP2 and 3.5SP1 all installed already.
It seems the combination XP SP2 and USB seems to be problematic in some cases.
You may find a solution by Google. Just type in the words: xp sp2 usb problem
Maybe you have to update all the USB drivers according to these Microsoft’s instructions:
“When you install Windows XP Service Pack 2, the USB 2.0 drivers do not appear to update” support.microsoft.com/kb/873169
