Yes, that's right! I tried a search, but the (Google) search engine told me that I don't know what I am talking about! I downloaded an application DfuSe, and tried to install it. Wine installer told me that I needed another program and offered to download. I agreed, but this was unsuccessful. However the Install Wizard went ahead and installed. But trying to run was a failure. Today, I checked .wine, and found that the whole program WAS present, so I read what I could of the Docs and other text files and found that it was a 64 bit application. And that is the problem - my venerable home assembled machine is based on a KT7 motherboard with an 800Mc/s Athlon processor, running 32 bit architecture with MEPIS 6.5, MEPIS 8.5, and Debian Lenny 5.0.7. All I wanted to know is, is there any way of running the DfuSe on this system? Thanks and Regards Alan
On Mon, May 9, 2011 at 7:19 AM, AlanLevett <wineforum-user at winehq.org> wrote:> Yes, that's right! ?I tried a search, but the (Google) search engine told me that I don't know what I am talking about! > > I downloaded an application DfuSe, and tried to install it. ?Wine installer told me that I needed another program and offered to download. I agreed, > but this was unsuccessful. ?However the Install Wizard went ahead and installed. But trying to run was a failure. > Today, I checked .wine, and found that the whole program WAS present, so I read what I could of the Docs and other text files and found that it was > a 64 bit application. > And that is the problem - my venerable home assembled machine is based on a KT7 motherboard with an 800Mc/s Athlon processor, running 32 bit > architecture with MEPIS 6.5, MEPIS 8.5, and Debian Lenny 5.0.7.You will not be able to run this program until someone builds a 64 bit cpu emulator for a 32 bit machine. Is there an alternate program you could use, either 32 bit Windows or native Linux? James McKenzie
In a word ... no. If this is indeed a 64 bit application, it is not possible to run it on a 32 bit system. This is not a Wine limitation, this is a hardware limitation. Also, a quick search showed that the software appears to rely on some proprietary Windows drivers. Wine is a user-space application, and cannot run Windows drivers. If need to use specialized hardware, make sure there are native Linux drivers for it. ----- Scott Weldon 501st_alpha1
Jim and Scott Thanks for the very prompt replies, they confirm what I thought. But Hey!, you never know, someone may have gotten a way around it! Has always been my life's work - persuading things to do what the designer never intended - nor thought of. Again, thanks Alan
userspace qemu running wine can make 64 bit wine turn over on a 32 bit system. But its a effort in how slow do you want the program to run. 501st_alpha1 Its one of those things almost no. You would have to be nuts. Same method is used to allow x86 wine to run on ppc.
"I downloaded an application DfuSe, and tried to install it... and found that it was a 64 bit application... 800Mc/s Athlon processor, running 32 bit architecture..." Will this help?: https://my.st.com/public/STe2ecommunities/mcu/Lists/ARM%20CortexM3%20STM32/Flat.aspx?RootFolder=%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2FARM%20CortexM3%20STM32%2FDFuSe%20applet%20on%20Linux&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000626BE2B829C32145B9EB5739142DC17E¤tviews=609 This is a good reminder to be aware of the experimental WINE64, speaking of 64 bit. It doesn't particularly help you in this case, but for future reference, if you try to run this 64 bit program in 64 bit Linux on a 64 bit machine, you might be able to run this program in WINE64. I contemplated whether or not it would be worth posting a long-winded deal going into every possible combination of (32 bit or 64 bit of each of the following): end (Windows) application, WINE, Linux, and processor; and say which combinations are possible, and which aren't, and why - just to iron out all the wrinkles. I determined that if I put in PasteBin, I couldn't possibly get anyone P.O.ed, so why not? And I never used PasteBin before, so it was good for me to get an account and "practice". Here it is: http://pastebin.com/Xu76cb8z . Someone might be glad it's there. I talk about processor emulators and bitage conflictions and bitage non-conflictions. Here's the meat and potato sources I reference amongst the long-windedness: http://www.thefreecountry.com/emulators/pc.shtml http://www.debian-administration.org/articles/534 (and the first one in my reply that's really long and ends in "=609") You sound like you know what you are doing, but Wikipedia/ something else search your processor's hardware name to make sure it really is only 32 bit. (see paragraph 26...I was duped into thinking my processor was 32 bit when it was actually 64 bit, because I was booted into a 32 bit OS, and it reports itself as such for compatibility.) I couldn't get a definitive answer from a semi-quick searching, but since it's on Wikipedia's "List of AMD Athlon microprocessors" and not on Wikipedia's "List of AMD Athlon 64 microprocessors," it's probably 32 bit. Cpu-world didn't say either. Cheers, Jake -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110513/f85af2f3/attachment.htm>