[Bug 11811] New: App sees no COM ports although COM1... 5 defined in dosdevices

http://bugs.winehq.org/show_bug.cgi?id=11811

Summary: App sees no COM ports although COM1...5 defined in
                    dosdevices
           Product: Wine
           Version: 0.9.56.
          Platform: PC
               URL: http://rosepointnav.com/CoastalExplorer/Trial/default.ht
                    m
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=11072)
 --> (http://bugs.winehq.org/attachment.cgi?id=11072)
Screen shot w/ error message

Coastal Explorer has an Options section for connecting the app to COM ports for
I/O (Tools -> Options -> Instruments -> Port Settings).  All available COM
ports are listed when running under Windows.  Under Wine, none are found (see
attached screen shot).  Defined COM1...4 (/dev/ttyS0...3) and COM5
(/dev/ttyUSB0) were all chmod to 666 to ensure permissions weren't a problem;
the problem remains.

Without serial I/O, the app's function of reading a GPS' serial stream and
writing commands to an autopilot controller (also via serial stream) is lost. 
Without it CE functions only as a trip planner and tide predictor.

[Bug 11811] App sees no COM ports although COM1...5 defined in dosdevices

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #1 from RBEmerson   2008-03-01 21:04:41 ---
Created an attachment (id=11073)
 --> (http://bugs.winehq.org/attachment.cgi?id=11073)
Stderr o/p during bug event

All of the stderr o/p except for the last four lines (each begins w/ "fixme")
occurs at app startup.

[Bug 11811] App sees no COM ports although COM1...5 defined in dosdevices

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #2 from RBEmerson   2008-03-01 21:11:24 ---
NB: The app is functional, even at this reduced level, *only* with native
comctl32.dll.  Using builtin comctl32 breaks the toolbar/menus seen at the top
of the screen (toolbar w/ icons isn't drawn) in the screen shot.  There is no
way (e.g., with keystrokes) to open the Options window or reach Port Settings
without the toolbar.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Lei Zhang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
            Summary|App sees no COM ports       |Coastal Explorer sees no COM
                   |although COM1...5 defined in|ports
                   |dosdevices                  |

--- Comment #3 from Lei Zhang   2008-03-02 01:00:26 ---
(In reply to comment #2)
> NB: The app is functional, even at this reduced level, *only* with native
> comctl32.dll.  Using builtin comctl32 breaks the toolbar/menus seen at the top
> of the screen (toolbar w/ icons isn't drawn) in the screen shot.  There is no
> way (e.g., with keystrokes) to open the Options window or reach Port Settings
> without the toolbar.

you should just mention bug 11548

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #4 from RBEmerson   2008-03-02 18:22:02 ---
Attaching a GPS receiver to the Keyspan serial/USB adapter (known to work under
Windows, and identified as /dev/ttyUSB0 when connected under Linux), as
expected, had no influence on the app.  The Instruments portion of Options
includes a search for GPS data on serial ports.  As before, nothing was found
and the "computer" (sic) is reported to have no COM ports (links in
.wine/dosdevices/ are not being used).

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #5 from Lei Zhang   2008-03-03 00:08:08 ---
Can you make sure the device works properly under Linux first, and make sure
the serial port works under wine? AFAIK most GPS devices with a serial
interface are very easy to talk to with just a terminal program.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #6 from RBEmerson   2008-03-03 05:42:08 ---
(In reply to comment #5)
> Can you make sure the device works properly under Linux first, and make sure
> the serial port works under wine? AFAIK most GPS devices with a serial
> interface are very easy to talk to with just a terminal program.

The GPS receiver I used is essentially a 4800 baud ASCII source.  It transmits
ASCII sentences blindly (no handshaking, no RTS/CTS exchange, etc.).  In fact,
this particular combination (GPS receiver and laptop) were used together for
two or three years, running CE under Windows on my boat.  I tried the receiver
on the outside chance that the app was actually seeing the ports but not
reporting them because of no data on any port.  For several reasons, I doubted
that would work but it'd be silly not to try it.

However, my thinking is still centered on the fact CE sees no ports at all, not
the default COM1-4, or the added COM5 (/dev/ttyUSB0).  To that end, please
recommend a Windows app (HyperTerminal???) known to work reliably as a COM port
test tool.  I can handle reading the ports on the Linux side, to verify they're
working.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #7 from Juan Lang   2008-03-03 14:10:41 ---
This is probably due to how the app is enumerating the COM ports.  On the hunch
that it's using setupapi, could you try the workaround in bug 9902?  Here's the
.reg file to import from that bug:
http://bugs.winehq.org/attachment.cgi?id=10210

You could also attach a +setupapi trace to confirm the hunch.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #8 from RBEmerson   2008-03-03 18:40:45 ---
(In reply to comment #7)
> This is probably due to how the app is enumerating the COM ports.  On the hunch
> that it's using setupapi, could you try the workaround in bug 9902?  Here's the
> .reg file to import from that bug:
> http://bugs.winehq.org/attachment.cgi?id=10210
>
> You could also attach a +setupapi trace to confirm the hunch.

I read the bug comments (I've used the app, SOB, under Windows - there are many
similarities in function, if not form, with CE) and .reg file - this sounds
like a promising route.

Being a noob and wanting to avoid complicating things with a bad guess on my
part, would someone please post the type-in to add the .reg file cleanly? 
Ditto for using "+setupapi" in the right place.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #9 from RBEmerson   2008-03-03 18:47:49 ---
(In reply to comment #6)
[...]
> The GPS receiver I used is essentially a 4800 baud ASCII source.  It transmits
> ASCII sentences blindly (no handshaking, no RTS/CTS exchange, etc.).

[...]

For the record, the NMEA (National Marine Electronics Assn.) standard for
serial comms calls for ASCII strings sent at 4800 baud, 8N1.  Some apps
(including CE) will accept and send at other rates.  And to add to the fun,
UAIS (Universal Automatic Identification System - very loosely, a VHF band ID
transonder system) receivers usually send their sentences at 38,400 baud.

"Standards are so wonderful because there are so many to chose from."

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #10 from Juan Lang   2008-03-04 09:25:17 ---
> Being a noob and wanting to avoid complicating things with a bad guess on my
> part, would someone please post the type-in to add the .reg file cleanly?

regedit foo.reg
> Ditto for using "+setupapi" in the right place.

WINEDEBUG=+setupapi wine foo.exe >& log.txt

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #11 from RBEmerson   2008-03-04 12:48:08 ---
Created an attachment (id=11112)
 --> (http://bugs.winehq.org/attachment.cgi?id=11112)
+setupapi trace w/ manual port config attempted

This trace was taken while launching Coastal Explorer (CE) and using the manual
port setup feature (Tools -> Options -> Instruments -> Port Settings...).  CE
reported no COM ports found and none were created.  The app was terminated
normally.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #12 from RBEmerson   2008-03-04 12:51:22 ---
Created an attachment (id=11113)
 --> (http://bugs.winehq.org/attachment.cgi?id=11113)
+setupapi trace w/ automatic port config attempted

Situation as in Attachment 11112 except automatic port setup was selected.  No
ports detected, as before.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #13 from RBEmerson   2008-03-04 13:24:35 ---
(In reply to comment #10)
> > Being a noob and wanting to avoid complicating things with a bad guess on my
> > part, would someone please post the type-in to add the .reg file cleanly?
>
> regedit foo.reg
> > Ditto for using "+setupapi" in the right place.
>
> WINEDEBUG=+setupapi wine foo.exe >& log.txt

The traces were run and posted.

After running the traces, I planned to update the registry and re-run the
traces for comparison.  For some reason:
 regedit ~/RegEdit_COM.reg
is totally unproductive.  RegEdit_COM.reg contains the registry information in
Attachment 10210, cut and pasted and verified by inspection.  Regedit runs
briefly (too briefly, for this platform) without comment.  Inspecting
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceClasses{4D36E978-E325-11CE-BFC1-08002BE10318}##?#ACPI#PNP0501#1#{4D36E978-E325-11CE-BFC1-08002BE10318}#
there is only one entry, a symbolic link.  If I understand the proposed
changes, there should be five COM ports defined.  What went wrong?

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #14 from RBEmerson   2008-03-04 21:58:52 ---
Sigh... I even tried importing the registry patch and... nothing.  No error
message, no change in the registry, nothing.  What blindingly obvious point
have I missed?

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #15 from RBEmerson   2008-03-05 12:37:51 ---
(In reply to comment #14)
> Sigh... I even tried importing the registry patch and... nothing.  No error
> message, no change in the registry, nothing.  What blindingly obvious point
> have I missed?

I missed the point I was looking in the wrong place in the registry.  Thank you
to Juan Lang for his help with the registry patch and installation.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #16 from RBEmerson   2008-03-05 13:04:27 ---
Created an attachment (id=11130)
 --> (http://bugs.winehq.org/attachment.cgi?id=11130)
+setupapi trace run w/ revised registry keys

The recommended registry changes were made and confirmed as being present. 
Launching Coastal Explorer with
n5470@gazebo:~> WINEDEBUG=+setupapi wine "C:\Program Files\Coastal
Explorer\Chart.exe" >& COMTestLog03.txt
produced no change in CE's behavior.  It still reports "no COM ports found" as
before.  A copy of the CE Application.log from the run is attached for
inspection.  The log format is nn.nnn:dd.ddd where nn.nnn is the total elapsed
time from start of execution and dd.ddd is the elapsed time between log
entries.  Note that there is only one mention of COM ports:
7.167:0.003: Created AlarmController: 0x000001e8 (0x19)
29.096:21.929: Enumerating COM ports:
53.518:24.422: Shutting down...
53.563:0.045: Shutdown complete

The shutdown was requested and is normal behavior.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #17 from RBEmerson   2008-03-05 13:06:28 ---
Created an attachment (id=11131)
 --> (http://bugs.winehq.org/attachment.cgi?id=11131)
App's native log from run to create attachment 11130

Application.log, created by Coastal Explorer, during the run that produced the
trace shown in Attachment 11130.  Note there is only one reference to COM
ports:
7.167:0.003: Created AlarmController: 0x000001e8 (0x19)
29.096:21.929: Enumerating COM ports:
53.518:24.422: Shutting down...
53.563:0.045: Shutdown complete

That there is no listing of ports below the line at 29.096 is not a good sign:
no ports found.  Shutdown is normal.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #18 from RBEmerson   2008-03-05 13:09:32 ---
(From update of attachment 11131)
0.008:0.000: Coastal Explorer 1.1.61 was started at 13:27:48 on 3/5/2008

0.068:0.060: Module file name: "C:\Program Files\Coastal Explorer\Chart.exe"

0.078:0.010: Set working directory to: "C:\Program Files\Coastal Explorer"

0.176:0.098: Creating application window

0.517:0.341: MainFrame Window is 0x00010040

0.519:0.002: Showing application window

0.963:0.444: Checking for updates

0.984:0.021: InternetGetConnectedState: started

0.985:0.001: InternetGetConnectedState: complete

0.986:0.001: Created UpdateChecker: 0x00000078 (0x17)

0.987:0.001: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\Updates\Coastal Explorer.upd")

1.028:0.041: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\Updates\Coastal Explorer.upd") complete

1.031:0.003: Intializing alerts...

1.035:0.004: Intializing AIS...

1.038:0.003: Initializing ENC names database...

1.062:0.024: Initializing chart folder list...

1.145:0.083: Initializing navigation objects...

1.146:0.001: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\NavObjects\Vessel.nob")

1.160:0.014: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\NavObjects\Vessel.nob") complete

1.192:0.032: Initializing Maptech SDK support...

1.597:0.405: Maptech MTsdk lib vers 5.2.0.1 - Dec  6 2004, 17:12:44

1.599:0.002: Initializing chart database...

1.778:0.179: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\Updates\Coastal Explorer.upd")

1.779:0.001: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\Updates\Coastal Explorer.upd") complete

1.786:0.007: CheckUnitCharts(2, "C:")

1.815:0.029: Scanning "C:" for charts (serial #0x00000001)...

1.816:0.001: Folder "C:\BSB_ROOT" will be scanned for charts...

1.816:0.000: Folder "C:\CA_CHTS" will be scanned for charts...

1.817:0.001: Folder "C:\CHARTKIT" will be scanned for charts...

1.817:0.000: Folder "C:\Charts" will be scanned for charts...

1.817:0.000: Folder "C:\ENC_ROOT" will be scanned for charts...

1.817:0.000: Folder "C:\Index" will be scanned for charts...

1.818:0.001: Folder "C:\PhotoCht" will be scanned for charts...

1.818:0.000: Folder "C:\Program Files\Digital Ocean" will be scanned for
charts...

1.818:0.000: Folder "C:\SENC" will be scanned for charts...

1.818:0.000: Folder "C:\SoftCht" will be scanned for charts...

2.730:0.912: 424 chart files found; 155 KAP files found.

2.731:0.001: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000001.xml")

3.008:0.277: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000001.xml") complete

3.010:0.002: Checking for new and/or removed charts...

3.047:0.037: Checking for orphaned KAP files

3.049:0.002: Found 0 orphaned KAP files

3.050:0.001: CheckUnitCharts(2, "C:") complete

3.050:0.000: CheckUnitCharts(23, "X:")

3.071:0.021: Scanning "X:" for charts (serial #0x00000002)...

3.072:0.001: Folder "X:\BSB_ROOT" will be scanned for charts...

3.072:0.000: Folder "X:\CA_CHTS" will be scanned for charts...

3.073:0.001: Folder "X:\CHARTKIT" will be scanned for charts...

3.073:0.000: Folder "X:\Charts" will be scanned for charts...

3.073:0.000: Folder "X:\ENC_ROOT" will be scanned for charts...

3.073:0.000: Folder "X:\Index" will be scanned for charts...

3.073:0.000: Folder "X:\PhotoCht" will be scanned for charts...

3.074:0.001: Folder "X:\Program Files\Digital Ocean" will be scanned for
charts...

3.074:0.000: Folder "X:\SENC" will be scanned for charts...

3.074:0.000: Folder "X:\SoftCht" will be scanned for charts...

3.108:0.034: 7 chart files found; 0 KAP files found.

3.110:0.002: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000002.xml")

3.125:0.015: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000002.xml") complete

3.127:0.002: Checking for new and/or removed charts...

3.127:0.000: CheckUnitCharts(23, "X:") complete

3.128:0.001: CheckUnitCharts(24, "Y:")

3.145:0.017: Scanning "Y:" for charts (serial #0x00000003)...

3.146:0.001: Folder "Y:\BSB_ROOT" will be scanned for charts...

3.146:0.000: Folder "Y:\CA_CHTS" will be scanned for charts...

3.146:0.000: Folder "Y:\CHARTKIT" will be scanned for charts...

3.147:0.001: Folder "Y:\Charts" will be scanned for charts...

3.147:0.000: Folder "Y:\ENC_ROOT" will be scanned for charts...

3.147:0.000: Folder "Y:\Index" will be scanned for charts...

3.147:0.000: Folder "Y:\PhotoCht" will be scanned for charts...

3.148:0.001: Folder "Y:\Program Files\Digital Ocean" will be scanned for
charts...

3.148:0.000: Folder "Y:\SENC" will be scanned for charts...

3.148:0.000: Folder "Y:\SoftCht" will be scanned for charts...

3.155:0.007: 0 chart files found; 0 KAP files found.

3.156:0.001: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000003.xml")

3.157:0.001: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000003.xml") complete

3.157:0.000: CheckUnitCharts(24, "Y:") complete: no charts!

3.158:0.001: CheckUnitCharts(25, "Z:")

3.160:0.002: Scanning "Z:" for charts (serial #0x00000000)...

3.160:0.000: Folder "Z:\BSB_ROOT" will be scanned for charts...

3.161:0.001: Folder "Z:\CA_CHTS" will be scanned for charts...

3.161:0.000: Folder "Z:\CHARTKIT" will be scanned for charts...

3.161:0.000: Folder "Z:\Charts" will be scanned for charts...

3.161:0.000: Folder "Z:\ENC_ROOT" will be scanned for charts...

3.162:0.001: Folder "Z:\Index" will be scanned for charts...

3.162:0.000: Folder "Z:\PhotoCht" will be scanned for charts...

3.162:0.000: Folder "Z:\Program Files\Digital Ocean" will be scanned for
charts...

3.162:0.000: Folder "Z:\SENC" will be scanned for charts...

3.162:0.000: Folder "Z:\SoftCht" will be scanned for charts...

3.199:0.037: 0 chart files found; 0 KAP files found.

3.200:0.001: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000000.xml")

3.260:0.060: ReadXml("c:\windows\profiles\All Users\Application Data\Rose Point
Navigation Systems\CV_00000000.xml") complete

3.261:0.001: Checking for new and/or removed charts...

3.275:0.014: CheckUnitCharts(25, "Z:") complete

3.303:0.028: Initializing ports...

3.305:0.002: Initializing ENC sub-system...

4.162:0.857: Initializing gazetteer...

5.599:1.437: Initializing Guide Books...

5.873:0.274: Initializing Tide Database...

6.032:0.159: Loaded Tides Database

6.034:0.002: Initializing Weather Database...

6.817:0.783: Initializing autopilot...

6.821:0.004: Initializing package handler...

6.824:0.003: Settting app state to 'ready'

6.845:0.021: Created TerraTileCache: 0x000001e0 (0x18)

6.992:0.147: ReadXml("c:\windows\profiles\n5470\Local Settings\Application
Data\Rose Point Navigation Systems\AutoSave.nob")

6.993:0.001: ReadXml("c:\windows\profiles\n5470\Local Settings\Application
Data\Rose Point Navigation Systems\AutoSave.nob") complete

6.994:0.001: Creating initial chart viewer...

6.994:0.000: Attempting to open most recent file...

7.000:0.006: OnOpenDocument: C:\Program Files\Coastal Explorer\20080224001.nob

7.003:0.003: ReadXml("C:\Program Files\Coastal Explorer\20080224001.nob")

7.011:0.008: ReadXml("C:\Program Files\Coastal Explorer\20080224001.nob")
complete

7.164:0.153: Initialization complete in 7.164 seconds.

7.167:0.003: Created AlarmController: 0x000001e8 (0x19)

29.096:21.929: Enumerating COM ports:

53.518:24.422: Shutting down...

53.563:0.045: Shutdown complete

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #19 from RBEmerson   2008-03-05 14:00:27 ---
Created an attachment (id=11137)
 --> (http://bugs.winehq.org/attachment.cgi?id=11137)
App's native log from run under WinXP

Note the creation of ports COM6...8 (the telnet port should have been removed -
the IP addy's dead for testing).  The read failures are acceptable - the ports
are driven by a Keysapn 4-port serial/USB adapter and not available at the
moment.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #20 from Juan Lang   2008-03-05 18:25:03 ---
Created an attachment (id=11147)
 --> (http://bugs.winehq.org/attachment.cgi?id=11147)
Another reg fix

It looks like it's trying to enumerate the interface GUID_CLASS_COMPORT.  Could
you import this one as well and see what it does?

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Juan Lang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #21 from RBEmerson   2008-03-05 21:20:03 ---
(In reply to comment #20)
> Created an attachment (id=11147)

--> (http://bugs.winehq.org/attachment.cgi?id=11147) [details]
> Another reg fix
>
> It looks like it's trying to enumerate the interface GUID_CLASS_COMPORT.  Could
> you import this one as well and see what it does?

Installed and run - no change in the "No COM ports" message.

The relevant part of the Application.log reads:
6.110:0.148: Initialization complete in 6.110 seconds.
6.112:0.002: Created AlarmController: 0x000001ec (0x17)
25.654:19.542: Enumerating COM ports:
82.749:57.095: Shutting down...
82.823:0.074: Shutdown complete

The trace will go up as soon as I hit commit for this post.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #22 from RBEmerson   2008-03-05 21:23:49 ---
Created an attachment (id=11152)
 --> (http://bugs.winehq.org/attachment.cgi?id=11152)
+setupapi trace run w/ GUID_CLASS_COMPORT reg mod

New reg mod but no change in bug; no COM ports reported.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #23 from RBEmerson   2008-03-08 21:48:59 ---
No change in this bug under Wine 0.9.57.  ~/.wine was deleted and created from
scratch with winecfg after installing 0.9.57.  Comctl32.dll was replaced with
the native version to enable menu access needed to check COM port registration,
if any.  None found.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #24 from RBEmerson   2008-03-09 14:34:33 ---
(In reply to comment #23)
> No change in this bug under Wine 0.9.57.  ~/.wine was deleted and created from
> scratch with winecfg after installing 0.9.57.  Comctl32.dll was replaced with
> the native version to enable menu access needed to check COM port registration,
> if any.  None found.

Problem duplicated on a second platform running openSUSE 10.3 and Wine 0.9.57
(fresh ~/.wine).

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Lei Zhang  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #25 from Lei Zhang   2008-03-10 01:42:29 ---
Ok, I have a CF GPS plugged into my laptop. Linux sees it just fine. Gave
Coastal Explorer a quick try.

So, in addition to Juan's registry files, in order for Coastal Explorer to just
find the COM port, it looks like you need to have the proper registry values
in:

- HKLM\HARDWARE\DEVICEMAP\SERIALCOMM

This existed when I first ran wineprefixcreate, but it has no entries. I think
after I ran Coastal Explorer, it got deleted.

- HKLM\SYSTEM\CurrentControlSet\Services\Mouclass\Enum

This registry key never existed.

I have no idea what these keys do exactly, so I can't actually help you fix
this.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #26 from RBEmerson   2008-03-10 14:09:22 ---
The following is from the application's company:
"Coastal Explorer enumerates the
'HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM' registry key to get a list
of COM port. Given that it only accesses that key with a read-only request, it
should be impossible for the key to be accidentally deleted!

"Coastal Explorer also uses the hardware setup API in order to find the
'friendly name' of each port. This is not depended upon, however, since not all
COM port drivers implement it correctly. If you see a COM port listed anywhere
in Coastal Explorer and the name is plain and un-friendly like 'COM3' then it's
because the driver for that port isn't 'complete'. When something shows up like
'Keyspan USA-19HS (COM5)' then it's because COM5 was found in the above
mentioned registry and the 'Keyspan USA-19HS' was found using the device setup
API."

The Keyspan USA-19HS is a serial/USB converter, with built-in kernel support in
many distros including openSUSE (not Debian or Ubuntu).

If the SERIALCOMM key is being tossed out, the obvious questions are what does
this, when, and why.

At the moment, inspecting HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP shows only one
entry: Scsi (Scsi Port 0 and Scsi Port 1 - both identified as using the "WINE
SCSI" driver).  This despite the fact the USA-19HS is connected and powered up.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #27 from RBEmerson   2008-03-10 14:38:21 ---
Looking at the proposed registry patches and the recent comments about how CE
works, it appears the reason the patches don't work is they've gone to the
wrong place, or at least not where, if I understand the comments correctly, CE
is looking for info about serial ports.  I tried installing them on the Wine
0.9.57 install and fresh .wine with no change (COM ports not found).

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Hans Leidekker  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #28 from Hans Leidekker   2008-03-17 15:42:29 ---
If you have a Windows machine available, use regedit to export the key
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM after plugging in the
Keyspan USA-19HS and import it in Wine.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #29 from RBEmerson   2008-03-17 21:28:58 ---
Created an attachment (id=11464)
 --> (http://bugs.winehq.org/attachment.cgi?id=11464)
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM w/ Keysapn adapter

Native HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM with Keyspan Adapter
in place.  "\Device\19H2KP0"="COM4" is added with the Keyspan adapter in
place.

Attempts to add this to the registry with:
regedit ~/Documents/Serialcomm_02.reg 
were unsuccessful, or at least SERIALCOMM doesn't show up in the registry. 
Note that in the native registry, SERIALCOMM always contains:
"Winachsf0"="COM3"
regardless of the state of the adapter.

Under Wine, SERIALCOMM is not found at all, only SCSI is in
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP even though the adapter's status light
is flashing as expected.  It should be noted that the kernel in openSUSE 10.3,
my test platform, is known to support Keyspan adapters (Debian and Ubuntu, at
least, do not).

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #30 from Hans Leidekker   2008-03-19 09:10:23 ---
It's a volatile key so you have to keep some app running in the background:

$ notepad &
$ regedit ~/Documents/Serialcomm_02.reg
$ ln -s /dev/ttyS0 ~/.wine/dosdevices/com4
$ wine CE.exe

Where com4 should match what's in the registry file for your Keyspan device
and /dev/ttyS0 should be the com port that your GPS device is attached to.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #31 from RBEmerson   2008-03-19 21:22:34 ---
Things started working, with a COM port, as expected.

(In reply to comment #30)
> It's a volatile key so you have to keep some app running in the background:
>
> $ notepad &
> $ regedit ~/Documents/Serialcomm_02.reg
> $ ln -s /dev/ttyS0 ~/.wine/dosdevices/com4
> $ wine CE.exe
>
> Where com4 should match what's in the registry file for your Keyspan device
> and /dev/ttyS0 should be the com port that your GPS device is attached to.

The registry patch was changed to COM5 to avoid a collision with COM4, defined
earlier.  The link was adjusted to link /dev/ttyUSB0 to [...]/com5 - note the
use of the USB system in place of a standard serial port.

CE's automatic port detection process found COM3 and COM5 (expected results). 
The port definition tool showed COM5 to be a "listener" operating in "NMEA0183"
format at 4800 baud.  CE has a NMEA input logging tool and I was able to
capture the input stream and later play it back (<SHIFT>right-click in the
chart area, choose NMEA Log Playback in the resulting menu, follow the file
selector prompts).  I hope to collect a much richer NMEA stream in the next
couple of days, and play it back to see how CE responds to a full data stream.

CE has a "Troubleshooter" function that displays NMEA data seen and sent on any
one port.  I was able to see data moving in both directions (i.e., GPS data in,
autopilot steering commands out).  Note that the Troubleshooter window is
almost the same size as the Instruments window and Troubleshooter appears
behind Instruments.  Drag the Instruments window to see the Troubleshooter
enough to raise it to the top of the window stack.  (this will be reported in a
new Bug)

- - -

The next step, it seems to me, is to be able to create, dynamically (as the
number of serial/USB ports in use by CE changes - as it very realistically can)
the needed registry entries when CE alone launches, without another, background
app (e.e., notepad) running to keep transient patches in place.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #32 from RBEmerson   2008-03-19 21:26:59 ---
The following "err:" messages are probably tied to the use of COM5:
fixme:menu:TrackPopupMenuEx not fully implemented
err:comm:get_baud_rate tcgetattr error 'Input/output error'
err:comm:set_baud_rate tcgetattr error 'Input/output error'
fixme:menu:TrackPopupMenuEx not fully implemented

I didn't try to shift the GPS' data rate from 4800 baud (NMEA default rate) and
data was received in good order, so I'm not sure what the complaint really is,
but there it is.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #33 from Hans Leidekker   2008-03-20 03:45:48 ---
> Things started working, with a COM port, as expected.

Hey, that's great!
> The next step, it seems to me, is to be able to create, dynamically (as
> the number of serial/USB ports in use by CE changes - as it very
> realistically can) the needed registry entries when CE alone launches,
> without another, background app (e.e., notepad) running to keep transient
> patches in place.

Yes, and it should be a pretty straightforward extension of our hal support.
> err:comm:get_baud_rate tcgetattr error 'Input/output error'
> err:comm:set_baud_rate tcgetattr error 'Input/output error'

I think this means that your Linux serial driver doesn't support getting
or setting the baud rate.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #34 from RBEmerson   2008-03-20 08:12:46 ---
A few thoughts on the COM port issue...

First, the Keyspan driver is bundled with most Linux distros (but not all,
Ubuntu and Debian do not include it because of, I think, GPL issues).  Put
another way, this is not a driver or module I added to my initial system
installation, it's a default item.

Second, in testing the application just now, the error messages didn't show up
at all.  I selected a number of different rates up to 38400 and down to 110
(hint: very much not recommended for the CPU-bound!).  Without a terminal to
watch the serial output, it's dangerous to assume the data was sent properly. 
However, the status light on the converter changed its blink rate consistent
with moving from 4800 to 38400 and down from 4800 to 300 and 110.  More
importantly, the gripes about get and set serial rates didn't show up.

Third, further testing shows that the message is related to the automatic port
detection process.  The problem arises when testing COM3 (a legacy of the
native SERIALCOMM keys).  Since COM3 is a "nonsense" port (not tied to any
existing hardware), the error message is, in fact, appropriate (i.e., COM3
won't allow a get or set rate because it's not really there).  Removing COM3
from the SERIALCOMM key and doing an autodetect shows the problem is fixed: no
(bogus) port, no error message.

Finally, it appears that "all" that's needed to support the creation of the
needed transient COM port entries in SERIALCOMM and this bug can be closed out.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #35 from Austin English   2008-10-23 15:22:36 ---
Is this still an issue in current (1.1.6 or newer) wine?

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #36 from Juan Lang   2008-10-23 15:57:21 ---
Still an issue.  The serial ports need to be added dynamically to the registry,
and there isn't any code to do that yet.  (There should probably be a .sys kind
of like mountmgr.sys that handles them.)

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Andrew Charles Hurst  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #37 from Andrew Charles Hurst   2008-11-03 13:43:58 ---
Hi folks,
I'm thinking of picking this up to get a firmware loader working through the
serial ports for my Digifly Vario.

I see that wine.inf (via wineboot) does create \DEVICEMAP\SERIALCOMM.
The entries COM1 etc are never populated, however.
In theory one simply scans .wine/dosdevices for com ports people have
symlinked.
I think mountmgr.sys type implementation is too much: either the symlink is
there, or it's not.

However, at the moment, something is wiping the SERIALCOMM and PARALLEL PORTS
entries: I think it might be create_scsi_entry code in dlls/kernel/oldconfig.c.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Mike Davies  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #38 from Mike Davies   2008-11-06 12:33:33 ---
(In reply to comment #37)
> Hi folks,
> I'm thinking of picking this up to get a firmware loader working through the
> serial ports for my Digifly Vario.
>
> I see that wine.inf (via wineboot) does create \DEVICEMAP\SERIALCOMM.
> The entries COM1 etc are never populated, however.
> In theory one simply scans .wine/dosdevices for com ports people have
> symlinked.
> I think mountmgr.sys type implementation is too much: either the symlink is
> there, or it's not.
>
> However, at the moment, something is wiping the SERIALCOMM and PARALLEL PORTS
> entries: I think it might be create_scsi_entry code in dlls/kernel/oldconfig.c.

According to Microsoft http://support.microsoft.com/kb/102988/en-us this part
of the registry (HKLM\hardware) gets wiped each time windows starts.

If you are working on this great - sooner the better please :-)

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #39 from Andrew Charles Hurst   2008-11-06 16:34:06 ---
Thanks for the info Mike,

should be fairly straightforward to build an entry per com* symlink in
dosdevices,
and can read HKCU\Software\Wine\something for anything other than default
(115200 8,n,1) config.

All I need is the right place to do it..
i think in kernel/oldconfig.c following the example of create_scsi_entry().

I think Vitaliy would be a good person to quiz about this.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #40 from Vitaliy Margolen   2008-11-06 20:47:38 ---
(In reply to comment #39)
Should work. AJ doesn't like it but there is no other good place for it.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #41 from Andrew Charles Hurst   2008-11-11 14:31:51 ---
Created an attachment (id=17220)
 --> (http://bugs.winehq.org/attachment.cgi?id=17220)
Proposed patch

This adds the SERIALCOMM entries.
Vitaliy, could you take a look?

Thanks
Andy

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download, patch

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |hardware

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #42 from Mike Davies   2008-11-12 05:04:07 ---
(In reply to comment #41)
> Created an attachment (id=17220)

--> (http://bugs.winehq.org/attachment.cgi?id=17220) [details]
> Proposed patch

Work OK for me ! The program I am testing is SX-Key v3.2.3.

My only comment is that it's case sensitive. i.e. it likes com1 but not COM1. I
don't know if this is an issue or not.

Mike

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #43 from Andrew Charles Hurst   2008-11-12 13:03:30 ---
I don't know if it's an issue either..
The drive letters ARE case sensitive, so 'd:' works, 'D:' is missed.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #44 from Andrew Charles Hurst   2008-11-12 13:36:30 ---
The docs
(http://www.winehq.org/site/docs/wineusr-guide/misc-things-to-configure)
only mention lowercase 'com1,2..' names,
I'll just email the patch and see how we go.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Andrew Charles Hurst  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #17220|0                           |1
        is obsolete|                            |

--- Comment #45 from Andrew Charles Hurst   2008-11-19 09:16:56 ---
Created an attachment (id=17358)
 --> (http://bugs.winehq.org/attachment.cgi?id=17358)
Patch:

This is the patch I sent most recently to wine-patches.
I think it's there, fingers crossed it'll be accepted soon.

Have also patched a bug which allows enumeration of potentially unlimited COM
ports by mistake when using e.g. CreateFile(.."\.\COM236"..
since it read only the char directly after "COM" in
ntdll/directory.c/get_dos_device()

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Andrew Charles Hurst  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #17358|0                           |1
        is obsolete|                            |

--- Comment #46 from Andrew Charles Hurst   2008-11-19 13:44:09 ---
Created an attachment (id=17361)
 --> (http://bugs.winehq.org/attachment.cgi?id=17361)
Patch:

Spotted a mistake in RtlMultiByteToUnicodeN params: BytesInMultiByteString
should include the null terminator

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Shane Kennedy  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #47 from Shane Kennedy   2008-11-28 19:05:26 ---
Which wine version does the patch apply to, and has it been incorporated in
later/latest version ?

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Andrew Charles Hurst  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #17361|0                           |1
        is obsolete|                            |

--- Comment #48 from Andrew Charles Hurst   2008-11-29 03:24:39 ---
Created an attachment (id=17535)
 --> (http://bugs.winehq.org/attachment.cgi?id=17535)
Patch

Newest iteration of patch. Scans /dev/ttyS* and then dosdevices/com* to
override.

The patch will apply to any recent wine version (since 2006?) - I don't think
oldconfig.c has been touched in a while.
It hasn't been accepted into the source tree, since they are keen on
implementing the HAL instead of adding to the local hacks for hardware support.

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #49 from Louis Lenders   2009-08-26 18:23:50 ---
*** Bug 17698 has been marked as a duplicate of this bug. ***

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #50 from Louis Lenders   2009-08-26 18:27:10 ---
*** Bug 15091 has been marked as a duplicate of this bug. ***

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Saulius K.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Graham Inggs  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #51 from Bruno Jesus  2011-11-17 19:53:50 CST ---
Almost 3 years without user posts, application is not available for download
anymore. Can anyone with an old copy of the application retest in latest wine?

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #52 from Graham Inggs  2011-11-18 04:43:31 CST ---
I have just tested one of the other applications affected by this bug,
HyperTerminal Private Edition 6.3, in a clean WINEPREFIX in Wine 1.3.32 and the
problem still exists.

I created a symbolic link for COM1, documented here:
http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure
ln -s /dev/ttyS0 ~/.wine/dosdevices/com1

HyperTerminal does not list any COM ports, only a TCP/IP (Winsock) connection
is available.

I then created a registry entry for the serial port, as suggested in this bug
report:
http://bugs.winehq.org/show_bug.cgi?id=4282
Add the following lines to .wine/system.reg [Hardware\Devicemap\SerialComm]
"Serial0"="COM1"

HyperTerminal now shows COM1 and TCP/IP (Winsock)as available connections.

What is the status of Andrew Hurst's patch, was it ever included in Wine?

HyperTerminal Private Edition 6.3 is available for download here:
http://www.hilgraeve.com/htpe/support/htpe63.exe

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #53 from Saulius K.  2011-11-18 11:36:14 CST ---
Then there is "floAt's Mobile Agent" from bug 15091 :
http://sourceforge.net/projects/fma/files/FMA%20(Beta)/

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #54 from Graham Inggs  2011-12-08 08:24:47 CST ---
I believe this is a duplicate of bug 1700 (which should be re-opened).

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #55 from André H.  2013-06-04 15:51:10 CDT ---
What about cleaning up the patch some more and resend?

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

nucleo  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                   |                            |m

--- Comment #56 from Anastasius Focht  ---
*** Bug 26806 has been marked as a duplicate of this bug. ***

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #11147|application/octet-stream    |text/plain
          mime type|                            |

[Bug 11811] Coastal Explorer sees no COM ports

http://bugs.winehq.org/show_bug.cgi?id=11811

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #11464|application/octet-stream    |text/plain
          mime type|                            |

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

http://bugs.winehq.org/show_bug.cgi?id=11811

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
            Summary|Coastal Explorer sees no    |Multiple applications fail
                   |COM ports                   |to enumerate serial ports
                   |                            |('HKLM\HARDWARE\DeviceMap
                   |                            |\Serialcomm' registry
                   |                            |entries)(Coastal Explorer,
                   |                            |GPS apps, HyperTerminal)
              Alias|NoCOMsFound                 |

--- Comment #57 from Anastasius Focht  ---
Hello folks,

refining summary to allow for easier search and collecting dupes here.
Obviously still present as of Wine 1.7.9

Regards

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

http://bugs.winehq.org/show_bug.cgi?id=11811

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |4633

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

http://bugs.winehq.org/show_bug.cgi?id=11811

Fred Wright  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #58 from Fred Wright  ---
One thing I haven't seen mentioned in this thread is that the DEVICEMAP keys
are *volatile*, which means that adding them manually only lasts as long as the
current incarnation of wineserver.  Obviously the best solution is for
wineserver to create the keys when it starts up, but in the meantime, the
options are:

1) Launch wineserver with -p, then edit the registry.

2) Leave regedit running (after making the edit(s)) until the serial
application is launched.

3) Create a wrapper that keeps wineserver up while making the necessary
registry fixes and running the application.

I've implemented #3 as a Python script, which I'll upload.

The application I'm using only seems to care about the values, not the value
names, so I elected to derive the value names from the actual device names, but
with a bit of "Windowsification".  E.g., "/dev/cu.XXX" -> "\Device\cu.XXX". 
Actual Windows systems have names of the form "\Device\Serial0",
"\Device\BthModem0", etc., which are somewhat less informative.

I've tested this with SXBlue Config running under Wine 1.62 on OSX 10.9.1.  It
also has code to perform the equivalent setup for parallel ports, but that's
untested.

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

http://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #59 from Fred Wright  ---
Created attachment 47420
  --> http://bugs.winehq.org/attachment.cgi?id=47420
Wrapper script (in Python) to work around DEVICEMAP bug

To observe the effects, just run "portwine.py regedit" and examine the
SERIALCOMM and/or PARALLEL PORTS keys under HKLM\HARDWARE\DEVICEMAP.

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #60 from [e-mail] ---
The patch mentioned at comment #48 still applies against git, expect this part
of it (taken from the .rej file)

--- dlls/kernel32/oldconfig.c
+++ dlls/kernel32/oldconfig.c
@@ -606,5 +749,6 @@
         return; /* someone else already loaded the registry */

/* create some hardware keys (FIXME: should not be done here) */
-    create_hardware_branch();
+    create_scsi_branch();
+    create_serialcomm_branch();
 }

wine 1.7.51

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #17535|0                           |1
        is obsolete|                            |

--- Comment #61 from André H.  ---
Created attachment 52383
  --> https://bugs.winehq.org/attachment.cgi?id=52383
Updated patch

Updated patch from comment #48

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #62 from André H.  ---
I just sent a patch to the mailing list, please test it:
(Already successfully tested it with "Terminal")

https://source.winehq.org/patches/data/114615

[Bug 11811] Multiple applications fail to enumerate serial ports ('HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

--- Comment #63 from André H.  ---
Totally new approach: https://source.winehq.org/patches/data/115289

[Bug 11811] Multiple applications fail to enumerate serial ports (' HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #64 from [e-mail] ---
(In reply to André H. from comment #63)
> Totally new approach: https://source.winehq.org/patches/data/115289

patching file programs/wineboot/wineboot.c
Hunk #3 succeeded at 1288 (offset -1 lines).

wine 1.9.22-git.

[Bug 11811] Multiple applications fail to enumerate serial ports (' HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

Alex Henrie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #65 from Alex Henrie  ---
This bug also affects TI Connect:
https://education.ti.com/en/software/details/en/B59F6C83468C4574ABFEE93D2BC3...

[Bug 11811] Multiple applications fail to enumerate serial ports (' HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

Alex Henrie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
      Fixed by SHA1|                            |a6cdfea1c1afa064e8d352935c4
                   |                            |ce8b2140a4294

--- Comment #66 from Alex Henrie  ---
Fixed by
https://source.winehq.org/git/wine.git/commitdiff/a6cdfea1c1afa064e8d352935c...

After the next biweekly Wine release, I will update
https://wiki.winehq.org/Wine_User%27s_Guide#Serial_and_Parallel_Ports with
information about how to use HKEY_LOCAL_MACHINE\Software\Wine\Ports to override
the serial and parallel port autodetection.

[Bug 11811] Multiple applications fail to enumerate serial ports (' HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

Alex Henrie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |mountmgr.sys

[Bug 11811] Multiple applications fail to enumerate serial ports (' HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #67 from Alexandre Julliard  ---
Closing bugs fixed in 2.8.

[Bug 11811] Multiple applications fail to enumerate serial ports (' HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

Alex Henrie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #68 from Alex Henrie  ---
*** Bug 30409 has been marked as a duplicate of this bug. ***

[Bug 11811] Multiple applications fail to enumerate serial ports (' HKLM\\HARDWARE\\DeviceMap\\Serialcomm' registry entries)(Coastal Explorer, GPS apps, HyperTerminal)

https://bugs.winehq.org/show_bug.cgi?id=11811

Alex Henrie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #69 from Alex Henrie  ---
*** Bug 40121 has been marked as a duplicate of this bug. ***