-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wine with ATDH1150USB Atmel CPLD Programming Cable #15
Comments
I have not used this in quite a while. xftd2xx.h:xxx:y: warning: ‘dllimport’ attribute directive ignored [-Wattributes] I suspect this is the core of the problem. |
Hi, Yes, I confirm this is what I am seeing.
|
Try checking out the new suppressImportDLL branch. |
Hi, The warnings went away, however, Wine still has trouble loading the DLL. Is it possible that this would have worked before despite the warnings in the previous compilation? I'm wondering if the problem has to do with where wine is looking for the files or a 32-bit/64-bit problem. On the off chance, I saw another issue mention copying the file to ftd2xx.dll, but that didn't seem to work either. I'm out of my element here so I'm reaching, but the error "(error c000012f)" seems non-specific. In any event, I can't say enough how much I appreciate this -- I'm fairly certain there is a lot of diverse hardware that would be able to work under Wine with something like this.
|
There were some problems due to changes in Wine over the last 8 years or so. I've just finished testing with my hardware on both 32-bit and 64-bit Debian systems running recent versions of Wine. As far as I can tell, it's all working again. Remember that you must follow the instructions in the README to: Good luck! |
So, here is what I'm starting with:
Initially I was getting lots of stuff missing (as below), but this was resolved with
Anyway, so after resolving the package dep, here's what I did (I'm assuming I set the path correctly, as the autodetect failed.):
At which point I got:
I think the Finally, here is what I ultimately ran:
And here's what I got:
When trying to use it:
Is there something different I should try? Should I try the master branch? |
You're making progress. Yes, switch back to the master branch. The main problem you're having is that the ftd2xx.dll.so is not being installed in the correct directory for your wine installation. My systems are running Debian 11 with wine version 8 from winehq. The directory where wine puts its dll.so files seems to depend on the version and the packager. On my WineHQ packaged systems: It's quite likely that this winelibdir script is not working properly on your system. $ find [top directory of wine install] -name libwinmm.a We're looking for the directory containing the unix libraries supporting windows executables. I'll try to update winelibdir to automate this better once I hear back from you. |
Ok, using the master branch I still have trouble, however, considering you are using Wine 8, I'm happy enough to move to Wine 8 from Wine HQ. I was hesitant because I didn't want to create a mess of packages, but I don't rely on it heavily and it sounded like the new Wine was fairly compelling. Having this working is more than enough reason to move. It might take me a moment to switch but I'll let you know as soon as I have it up. Below is what happened with the master branch on the current setup with v6 wine:
|
Before you switch to the Wine HQ package, could you try to locate the directory containing the windows support libraries in the Ubuntu packaged version of Wine you already have installed? Do you have directories called i386-unix or x86_64-unix as part of your wine installation? $ find [top directory of wine install] -name libwinmm.a Another way would be to set the WINEDLLPATH env variable to the directory containing the libftd2xx.dll.so file. This worked for me even after I deleted the .dll.so file from the system directory. Just after you build the 32-bit version, do not install it. Instead: $ export WINEDLLPATH=$(pwd) |
see |
Hi, So I have the following directories:
This is what I ran that produced the previous output against the master branch:
Searching the entire filesystem from root, I do not have the file you mention, but I do have: |
As far as not doing a
The file you mention (libftd2xx.dll.so) doesn't exist. I assume you mean
Investigating that file, I have:
Finally, trying to use it by running:
Here's the output:
|
Sorry about getting the dll file name wrong. You fixed that. I found this post that claims: Error c000012f means Wine can't load the DLL (nnn.dll) because the he required Microsoft Visual C++ Redistributables files can't be found or there is a 64 - 32 bit mismatch. I'd test this by removing all copies of ftd2xx.dll.so When I run: You should see (nearly) the same. |
No, this is old-school 32-bit stuff:
|
Well designed apps would start even if the ftd2xx support were not present. |
Yeah, I searched for lingering copies and removed them. Yes, I have WinCUPL working just fine. Wine itself works without issue. I'm onto installing Wine HQ version 8.0 |
After removal, you get the same cryptic c000012f error message? |
So, it looks like I had some utter nonsense inside of Thanks for pointing out that the message should have disappeared. I thought I scoured the filesystem pretty closely, but once I started broadening my search to anything containing 'ftd' that showed up and I looked inside. Now I'm on Wine 8, however, so it might take me a sec to get going again. |
So, I've moved everything over to WineHQ v8.0.1 and everything compiled cleanly, but no matter what I do I can't seem to get Wine to see the dll. I confirm that Wine is working for other programs (WinCUPL, etc.):
This is how I compiled things:
The .dll appears to be as expected:
Everything looks to have compiled cleanly:
|
My ftd2xx.dll.so is 378680 bytes long. If this matches yours, then the problem is likely elsewhere. I assume you get the error message whether or not the FTDI USB device is plugged in. |
The filesize on this end for ftd2xx.dll.so is 378784 bytes. Sure, the software is from: In the previous version of wine, the software eventually managed to start but was unable to detect the unit so I figured I'd have better luck with V8. Now it fails to find the .dll all together, which is odd. The software should start regardless of whether the hardware is plugged in, but will fail to load entirely if that .dll is not present. I have tried making sure it is plugged in and taking note of udev rules as well nonetheless. |
Oh, one thing to add is that
The wine prefix was generated via the following:
Also, one needs mfc42 for this software:
|
Renaming to I have a strong suspicion that it has to do with the following error: The full list of messages that comes up when starting is this:
However, it is very notable that |
I think I see the problem... It's a long shot, but you might try installing the FTDI 1.4.22 windows drivers after removing the 2.x drivers. It's possible the ATMISP will work with the older version. Worth a try, anyway. Note that the unix dll.so shared libraries do not normally live inside the windows .wine prefix. Note also that I never encountered the 'status c0000135' error with or without the library's presence. So, I think whats happening is that the 2.x driver is not finding the Unix shim library it needs. This shim could be adapted for the 2.x FTDI driver, but it would be a new project. If this turns out to be the case, I'll update the project README so no one else needs to find this out the hard way. Sorry. |
FYI- I always get same wineusb:query_id Unhandled ID query type 0x5 In addition, when the windftd2xx shim is working properly, I see these messages: 0090:fixme:ntoskrnl:IoIsWdmVersionAvailable unknown major 1 minor 0xA |
Do you have a place I might be able to pull the recommended version of the FTDI driver from? There is also an older version of ATMISP, however, it doesn't seem to install in Wine for me. Peter |
Not at my computer. You can download the 1.4 2xx drivers from FTDI's website. Can provide link this evening.
On May 28, 2023 12:33:01 PM PDT, peterzieba ***@***.***> wrote:
Do you have a place I might be able to pull the recommended version of the FTDI driver from?
There is also an older version of ATMISP, however, it doesn't seem to install in Wine for me.
Peter
--
Reply to this email directly or view it on GitHub:
#15 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
- brent
|
I couldn't install the ATMISP67 either. (Kept getting error 1603 near the end of the install) A few weeks ago, I set up an older MacBook Air to dual boot Debian and Windows 10. https://www.ebay.com/itm/325670376430 This is legit. I believe OEMs buy blocks of Win 10 licenses and, at least in Germany, they are free to resell those they don't use. The license is valid for only a single computer. I don't see why you couldn't run this windows in VirtualBox or some other VM, |
Hi, I've tried to pick this up again to see if I could get it to work in a newer version of Ubuntu/Wine and well as using ATMISP 7.2 which has a slightly older version of the FTDI driver. 24.04.1 LTS / WineHQ v10.0 Everything seems to have compiled and installed properly, however, it still does not work. What is interesting is it starts and does seem to detect the device to some extent as the error message while plugged in is:
If the cable is unplugged I instead see:
Finally, and this might be a red herring, however, upon plugging in the device the following console message comes from Wine:
Is there any chance this is actually pretty close to working with the exception of some descriptor being sent over? One thing that sticks out is even though the 0403:6010 ID seems completely generic, in dmesg, there is this:
I almost feel like it might be as simple as this needing to be passed on through. Any thought would be greatly appreciated. |
Hi,
Trying to get this to work with a programming adapter which is a pretty basic FTDI adapter on Ubuntu 22.04.2 LTS with Wine.
FTDID=0403:6010 wine ~/.wine/drive_c/ATMISP7/ATMISP.exe
0024:err:module:import_dll Loading library FTD2XX.dll (which is needed by L"C:\ATMISP7\ATMISP.exe") failed (error c000012f).
0024:err:module:LdrInitializeThunk Importing dlls for L"C:\ATMISP7\ATMISP.exe" failed, status c0000135
It's very possible I'm missing something basic, however, "make" and "make install" seemed to be successful.
I'm running a 64-bit Distribution, however, the software is 32-bit executable. Do I need to do anything special in these circumstances, or is it possible the problem I am experiencing is elsewhere?
Any help would be greatly appreciated.
Regards,
Peter
The text was updated successfully, but these errors were encountered: