Uniden Sentinel 32 bit windows software on 64 bit opensuse

[gariac]

It is so aggravating that this works on wine on a Mac but not on linux.

The software is found here:
http://info.uniden.com/twiki/bin/view/U ... 4/BCD536HP

I have 64 wine and 32bit wine installed on 64 bit opensuse 13.1. I use the wine nightly builds from the repo.
Here are the messages from the terminal where I ran wine:

Code: Select all

~/.wine/drive_c/program_files_x86/Uniden/sentinel> wine BCDx36HP_Sentinel.exe
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections" in state 2
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"sectionGroup" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"section" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"userSettings" in state 2                                                 
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"HomePatrol_Sentinel.Properties.Settings" in state 6                      
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6                                                      
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6                                                        
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6                                                      
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6                                                        
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6                                                      
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6                                                        
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6                                                      
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6                                                        
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6
fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6
fixme:win:EnumDisplayDevicesW ((null),0,0x33dfa8,0x00000000), stub!

Unhandled Exception:
System.NotImplementedException: The requested feature is not implemented.
  at System.Configuration.SettingValueElement.Unmerge (System.Configuration.ConfigurationElement sourceElement, System.Configuration.ConfigurationElement parentElement, ConfigurationSaveMode saveMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationElement.Unmerge (System.Configuration.ConfigurationElement source, System.Configuration.ConfigurationElement parent, ConfigurationSaveMode updateMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationElementCollection.Unmerge (System.Configuration.ConfigurationElement sourceElement, System.Configuration.ConfigurationElement parentElement, ConfigurationSaveMode updateMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationElement.Unmerge (System.Configuration.ConfigurationElement source, System.Configuration.ConfigurationElement parent, ConfigurationSaveMode updateMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationSection.SerializeSection (System.Configuration.ConfigurationElement parentElement, System.String name, ConfigurationSaveMode saveMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionInfo.WriteData (System.Configuration.Configuration config, System.Xml.XmlWriter writer, ConfigurationSaveMode mode) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteContent (System.Xml.XmlWriter writer, System.Configuration.Configuration config, ConfigurationSaveMode mode, Boolean writeElem) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteData (System.Configuration.Configuration config, System.Xml.XmlWriter writer, ConfigurationSaveMode mode) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteContent (System.Xml.XmlWriter writer, System.Configuration.Configuration config, ConfigurationSaveMode mode, Boolean writeElem) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteRootData (System.Xml.XmlWriter writer, System.Configuration.Configuration config, ConfigurationSaveMode mode) [0x00000] in <filename unknown>:0 
  at System.Configuration.Configuration.SaveData (System.Xml.XmlTextWriter tw, ConfigurationSaveMode mode, Boolean forceUpdateAll) [0x00000] in <filename unknown>:0 
  at System.Configuration.Configuration.Save (System.IO.Stream stream, ConfigurationSaveMode mode, Boolean forceUpdateAll) [0x00000] in <filename unknown>:0 
  at System.Configuration.Configuration.Save (ConfigurationSaveMode mode, Boolean forceUpdateAll) [0x00000] in <filename unknown>:0 
[ERROR] FATAL UNHANDLED EXCEPTION: System.NotImplementedException: The requested feature is not implemented.
  at System.Configuration.SettingValueElement.Unmerge (System.Configuration.ConfigurationElement sourceElement, System.Configuration.ConfigurationElement parentElement, ConfigurationSaveMode saveMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationElement.Unmerge (System.Configuration.ConfigurationElement source, System.Configuration.ConfigurationElement parent, ConfigurationSaveMode updateMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationElementCollection.Unmerge (System.Configuration.ConfigurationElement sourceElement, System.Configuration.ConfigurationElement parentElement, ConfigurationSaveMode updateMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationElement.Unmerge (System.Configuration.ConfigurationElement source, System.Configuration.ConfigurationElement parent, ConfigurationSaveMode updateMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.ConfigurationSection.SerializeSection (System.Configuration.ConfigurationElement parentElement, System.String name, ConfigurationSaveMode saveMode) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionInfo.WriteData (System.Configuration.Configuration config, System.Xml.XmlWriter writer, ConfigurationSaveMode mode) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteContent (System.Xml.XmlWriter writer, System.Configuration.Configuration config, ConfigurationSaveMode mode, Boolean writeElem) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteData (System.Configuration.Configuration config, System.Xml.XmlWriter writer, ConfigurationSaveMode mode) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteContent (System.Xml.XmlWriter writer, System.Configuration.Configuration config, ConfigurationSaveMode mode, Boolean writeElem) [0x00000] in <filename unknown>:0 
  at System.Configuration.SectionGroupInfo.WriteRootData (System.Xml.XmlWriter writer, System.Configuration.Configuration config, ConfigurationSaveMode mode) [0x00000] in <filename unknown>:0 
  at System.Configuration.Configuration.SaveData (System.Xml.XmlTextWriter tw, ConfigurationSaveMode mode, Boolean forceUpdateAll) [0x00000] in <filename unknown>:0 
  at System.Configuration.Configuration.Save (System.IO.Stream stream, ConfigurationSaveMode mode, Boolean forceUpdateAll) [0x00000] in <filename unknown>:0 
  at System.Configuration.Configuration.Save (ConfigurationSaveMode mode, Boolean forceUpdateAll) [0x00000] in <filename unknown>:0 
Shutting down finalizer thread timed out.

[dimesio]

MacOSX does not have 64 bit Wine, so if this is not a 32 bit wineprefix, try installing to one. If that doesn't work, try installing whatever version of .NET this app requires.

[gariac]

I suspected the fact that it worked on the OSX and not linux was a clue.

In my .wine directory inside drive_c, I have "Program Files and "Program Files (x86)", so I do believe I have both 64 and 32 bit wine installed.

I never heard of wineprefix, but found the wiki:
http://wine-wiki.org/index.php/WINEPREFIX
I suspect this is the line you want me to use:
"you can have separate wine prefixes for 64bit and 32 bit as D. Kegel wrote that you can: export WINEARCH=win32 before creating the wineprefix. If you use 64 bit, to create a separate, 32 bit wineprefix using [export] WINEARCH=win32 eg code:"
But I really don't understand how to do this.

I argree it is a dotnet problem. I installed winemono from Yast, but I suspect that is only for 64 bit code. I tried to install the dotnet two provided by Uniden and even from winetricks, but the MS installer sees the 64bit wine and declares it can't install the dotnet, which is 32 bit. i gather this is where the wineprefix comes in, i.e. force 32bit wine, but I'm going to need more explicit direction on how to set that up.

[dimesio]

http://wiki.winehq.org/FAQ#32_bit_wineprefix

[gariac]

http://wiki.winehq.org/FAQ#32_bit_wineprefix

Unfortunately, this FAQ presumes I understand how wine works. (If I did, I wouldn't be on this forum.)



The instructions are

Code: Select all

At present there are some significant bugs that prevent many 32 bit applications from working in a 64 bit wineprefix. To work around this, you can create a new 32 bit wineprefix using the WINEARCH environment variable. In a terminal, type
WINEARCH=win32 WINEPREFIX=/path/to/wineprefix winecfg 

So is the idea I point to my Program Files (x86)? Something like
WINEARCH=win32 WINEPREFIX="/wine/drive_c/Program Files (x86)" winecfg

But I still don't see how this will work since environment variables don't work like this, at least on opensuse. Or by "terminal", does the FAQ mean use a CMD within wine, that is a terminal in windows?

[gariac]

OK, I did some hacking. It turns out the environment variables are set in a wine command prompt with the command "set". Here are my environment variables, somewhat truncated since the cut and paste is a mess

Code: Select all

WINEDEBUG=-all                                                                  
WINEDLLPATH=/usr/lib64/wine/                                                    
WINELOADER=/usr/bin/wine                                                        
WINELOADERNOEXEC=1                                                              
WINEPREFIX=/home/gary/.wine                                                     
WINESERVER=/usr/bin/wineserver                                                  
winsysdir=C:\windows\system32                                                   
WINEDLLPATH=/usr/lib64/wine/                                                    
WINELOADER=/usr/bin/wine                                                                                                     
winsysdir=C:\windows\system32                                                   
                                                                     

I still don't know what to do here.

[dimesio]

So is the idea I point to my Program Files (x86)? Something like
WINEARCH=win32 WINEPREFIX="/wine/drive_c/Program Files (x86)" winecfg

No. As the FAQ clearly states, you need to create an entirely new, 32 bit wineprefix and install your app to that wineprefix. If you don't have anything else you need to keep already installed to ~/.wine, you can just delete that and recreate it as a 32 bit wineprefix. Otherwise, just create a different one.
http://wiki.winehq.org/FAQ#wineprefix

But I still don't see how this will work since environment variables don't work like this, at least on opensuse. Or by "terminal", does the FAQ mean use a CMD within wine, that is a terminal in windows?

The terminal you use is whatever Linux terminal you normally use. I'm on KDE, and I use konsole. I'm also on openSUSE, and the instructions in the wiki work perfectly fine here. I'm the one who wrote the one for creating a 32 bit wineprefix.

[gariac]

If the instructions were clear, I wouldn't be asking questions. Thanks anyway for your effort.

[gariac]

If anyone else is reading this thread, here is a more detailed explanation on how to install dootnet20 and even run 32 bit code.
http://askubuntu.com/questions/231587/i ... it-machine
Using this page, I got the dotnet20 and the program running. I might still have issues with USB directly from the program, but I can edit the database, then just transfer it by making the Uniden scanner look like an external usb drive.

To install dotnet20:
WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg
env WINEARCH=win32 WINEPREFIX=~/.wine32 winetricks dotnet20

For the installation of the software, I did
WINEPREFIX=~/.wine32 wine setupprogram.exe

To run the program, just change the exe file, i.e.
WINEPREFIX=~/.wine32 wine my32bitprogram.exe

[oiaohm]

gariac with the FAQ the project is always looking to make it simpler to understand.

Unfortunately, this FAQ presumes I understand how wine works. (If I did, I wouldn't be on this forum.)

This is not meant to be the case. Wine FAQ does presume a little Linux command line knowledge. This is not how Wine works knowledge. All how wine works knowledge required to do the basics like installing applications should be in the FAQ.

WINEARCH=win32 WINEPREFIX="/wine/drive_c/Program Files (x86)" winecfg

I really don't know what in the FAQ suggested this and I don't know what to add to the faq to prevent this happening again gariac. The FAQ is broken into sections everything in a section relates to each other. 7.1 does give a basic description of what a WINEPREFIX is. Maybe we need to add a new user note read all of a section before attempting to do something.

gariac application install instructions should be added to appdb.winehq.org not the forum. Anything in the forum does get lost almost forever.

There are some current bugs in the FAQ but this was not one of them as far as I knew.

[dimesio]

WINEARCH=win32 WINEPREFIX="/wine/drive_c/Program Files (x86)" winecfg

I really don't know what in the FAQ suggested this

Absolutely nothing in the FAQ suggested this, and what the OR eventually said he did, that worked, is exactly what our FAQ says to do.

[oiaohm]

Absolutely nothing in the FAQ suggested this, and what the OR eventually said he did, that worked, is exactly what our FAQ says to do.

dimesio let be truthful we are not normal level users we read the FAQ all the time. Both of us cannot see how gariac got that outcome from what is written in the FAQ. Yet gariac said.

Unfortunately, this FAQ presumes I understand how wine works. (If I did, I wouldn't be on this forum.)

and

If the instructions were clear,

The logic to how gariac end up with that is important.

This is what I am after the answer exactly how was the FAQ not clear enough and exactly want in the FAQ is giving the wrong appearance. Ok I will accept did not read the FAQ because fearing it was complex or possible got scared off early on in the FAQ(but I want to know what).

gariac only way to make the FAQ better is feedback.

[gariac]

I'm not sure how to interpret these posts. let me just state I have no ill will to anyone involved with wine or even this thread. I just happened to find the Ubuntu explanation clearer because it walked me through all the steps.

My confusion was that wine has both a "Program Files" and "Program FIles (x86)". I got the impression I was supposed to point the wine prefix to the "Program Files (x86)" directory, not a new installation of 32 bit wine.

If I had my druthers, the FAQ would look more like that Ubuntu page I listed, but I'm not in charge. Further, somebody else might find that explanation not as clear. I'll leave it up to the powers that be. All I wanted to do is document how I got this program going in the event somebody does a google search with the same problem.

Note that it is often the case that somebody gets something working and the path they took isn't totally necessary. For instance you think you needed to install some program to satisfy a dependency but it actually wasn't required. So good technical writing is a combination of somebody clueless (AKA me) and somebody who is an expert (AKA the moderator).

And yes, there are dumb questions. I often make them.

[dimesio]

My confusion was that wine has both a "Program Files" and "Program FIles (x86)".

FYI, the "Program Files" and "Program Files (x86)" is a shared "WoW64" (Windows on Windows 64) setup. That's the normal structure of a 64 bit wineprefix.

I got the impression I was supposed to point the wine prefix to the "Program Files (x86)" directory, not a new installation of 32 bit wine.

What both oiaohm and I do not understand is how you got that impression. The word "create" is not only in the title of the section I pointed you to, it is repeated in the second sentence. I agree, experienced users don't see things the same way as inexperienced ones, but in this case, I do not see how to make it any clearer.

[oiaohm]

gariac sorry to say it a case you have baffled us. We cannot fix our FAQ if we don't understand how user goes the wrong way with it.

gariac the other thing we do need people to use our http://wiki.winehq.org/FAQ and http://appdb.winehq.org

The FAQ is designed to be generic to what ever application you are installing. The main reason for common FAQ is if wine has to change something. FAQ provides a single location to update that information.

Basically it is deadly criticial to us that the FAQ is readable as possible.

The ubuntu link you gave as what we would expect in a http://appdb.winehq.org howto. https://appdb.winehq.org/objectManager. ... &iId=17886 .net 4.0 page is not as well maintained. The appdb.winehq.org pages are vastely more detailed on what kinds of defects you can run into with a particular application.

gariac something about wine you say you are not in charge. Wine project are fully open to alteration submissions from anyone. The FAQ started to deal with my frustration in IRC at having to type the same block of text over and over again. It evolved from what I had in a irc bot. I think there is only 1 or 2 lines of my first FAQ left in it.

Yes truly anyone is welcome to submit a request to become a maintainer of documentation on any application in the appdb.

gariac you can be in charge of particular sections we have no problems with that. The reality we want the feedback.

The advantage for us is if the instuctions in the appdb.winehq.org or the wiki.winehq.org/FAQ are wrong we can request deletion and have it happen in 24-48 hours. Now if the instructions are somewhere like askubuntu.com it can take us months to years to get invalid instructions removed.

Something gariac to remember this is a Open Source project so there is absolutly no problem degating repsonsablities. The project will give you as much responsiblity as you wish to take and can handle. If you want to be in charge of something just ask.

[gariac]

If I understand something well, I have no problem writing about it. I'm not in that position regarding wine.

That said, this particular program isn't finding the device, which is a radio scanner set up to look like a USB drive. I can see that 32 bit wine has correctly mapped the USB drive in the dosdevices directory. Two drives actually. h: for the SDHC card, and h:: for the partition. But the program doesn't find them. I ran winecfg using the wine prefix. It shows up as XP, so I know it was running the right winecfg. It finds the USB drive.

[code
lrwxrwxrwx 1 gary users 10 Feb 8 19:19 c: -> ../drive_c
lrwxrwxrwx 1 gary users 8 Feb 11 16:52 d:: -> /dev/sr0
lrwxrwxrwx 1 gary users 8 Feb 11 16:52 e:: -> /dev/sdf
lrwxrwxrwx 1 gary users 9 Feb 8 19:19 f:: -> /dev/sdf1
lrwxrwxrwx 1 gary users 8 Feb 8 20:09 g:: -> /dev/sdg
lrwxrwxrwx 1 gary users 29 Feb 11 16:51 h: -> /var/run/media/gary/2C9A-1B21
lrwxrwxrwx 1 gary users 9 Feb 8 20:09 h:: -> /dev/sdg1
lrwxrwxrwx 1 gary users 10 Feb 11 16:51 i: -> /home/gary
lrwxrwxrwx 1 gary users 9 Feb 9 01:14 j:: -> /dev/sdh1
lrwxrwxrwx 1 gary users 8 Feb 11 16:52 k:: -> /dev/sdh
lrwxrwxrwx 1 gary users 1 Feb 8 19:19 z: -> /
[/code]

2C9A-1B21 is the SDHC.

As a sanity check, I downloaded a 32 bit windows program that is designed to find usb devices, including drives.
http://www.nirsoft.net/utils/usb_devices_view.html
It doesn't find the Uniden scanner which is in USB drive mode.

Is there some very simple windows program known to work under 32 bit wine that can find the USB drive so that I know the 32 bit wine is not the problem. That is, I am trying to do a sanity check to make sure the problem is not with 32 bit wine but the Uniden Sentinel coding.

[oiaohm]

gariac you are making a big mistake. Wine is in fact not built todo what you are expecting.
http://wiki.winehq.org/USB
Wine usb support is almost non existent.

http://www.nirsoft.net/utils/usb_devices_view.html
This is basically telling the truth. Custom patching of wine is required to get USB devices to appear as anything more than a generic drive. Wine does not tell the difference between a generic drive and a usb device when it comes to dosdevices. USB device as a drive is detected by Linux made into drive by Linux then wine gets the report from Linux on what is drives this becomes dosdevices.

Wine main objectives have not included controlling devices.

[gariac]

OK. I thought USB drives were different since they are more uniform across the various platforms. That is, all operating systems have native drivers to see usb drives. I guess I need to set up a VM.

Incidentally, i do use my Garmin USB GPS under wine. There are several threads on the internet about this. It is a matter of creating a symbolic link. Basically
com1 -> /dev/ttyUSB0

[dimesio]

Can you browse the mounted "drive" in a native file manager? If the drive is mounted as an ordinary mass storage device that can be accessed from native apps, Wine should be able to see it, too. However, if the app uses a special driver to access the "drive," that won't work in Wine.

Incidentally, i do use my Garmin USB GPS under wine. There are several threads on the internet about this. It is a matter of creating a symbolic link. Basically
com1 -> /dev/ttyUSB0

Devices that are pure serial over USB will usually work that way. The key is "pure"--as with drives, devices that need special drivers won't work.