http://bugs.winehq.org/show_bug.cgi?id=34529
Bug #: 34529
Summary: Game attempts to create and read from root Z:\ drive
instead of C:\ (c_drive) directory.
Product: Wine
Version: 1.7.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nemstar(a)zoho.com
Classification: Unclassified
When running the PC version of the game Shadowgun: Deadzone
(http://www.madfingergames.com/deadzone/) which is free to download and play,
I encounter a problem. The game is attempting to write to the root directory
which is the Z:\ drive by default in wine. It attempts to create a directory
named /users/<player name> with data files that pertain to the game. I know
this because I set up a test bed and used root and the directory /users/<player
name> and files within it were created successfully and the game ran as
intended.
If the Z:\ drive is removed using winecfg (as none root user) and the file is
placed or created in ~/.wine/c_drive/users/<player name>, then the game will
read the correct file on the C: drive and run as intended. If the Z:\ drive is
re-enabled, then the game will try to read from the root file system on Z: and
can not find /user/<player name> so it will not connect to a match or save
settings.
This is the case when ran as any user.
Obviously the game should not be trying to create a new directory under
C:\users in any circumstance, or as Z:\users if root is mounted as Z:\.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=21448
Summary: RollerCoaster Tycoon 3 does not accept the original
disc
Product: Wine
Version: 1.1.36
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thomas.mertes(a)gmx.at
Created an attachment (id=25828)
--> (http://bugs.winehq.org/attachment.cgi?id=25828)
Error log and content of message box when starting RollerCoaster Tycoon 3
When starting RollerCoaster Tycoon 3 it asks for the original disc although the
original disk is in. There are some errors logged (see attachment) and then a
message box appears:
Please insert the original disc instead of a backup. See
www.securom.com/copy for more details
Greetings Thomas
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38690
Bug ID: 38690
Summary: corrupted serial communications
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jpyle490(a)gmail.com
Distribution: ---
Serial communications are corrupted/laggy/ugly. Tested on a Dell Latitude D630
running Linux Mint 17.1 and Wine 1.7.38 from WineHQ PPA, as well as Wine 1.6.2
on the same hardware from the Ubuntu repo. The issue occurs whether it's the
hardware 16550 serial port or a USB attached one. (In this Linux system case
the USB adapter was Prolific-based.)
I observed the same symptoms on Mac OS X Mavericks, compiling Wine 1.7.43 via
Macports, using an FTDI-based USB adapter.
The primary test scenario included Tera Term 4.87 talking to a Cisco router's
console port at 9600 N,8,1 without flow control. Data back from the Cisco was
incomplete, latent and just generally ugly. Using the same hardware and
minicom running natively in either Linux or OS X there were no issues.
Tera Term to a router provided the cleanest environment in which to observe
what was happening. I can't get serial communications to work properly
regardless of the Windows app or the serially-connected device.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52065
Bug ID: 52065
Summary: Rockstar Games Launcher Installer is leaking memory
Product: Wine
Version: 6.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: ---
When installing Rockstar Games Launcher via its installer, the installer never
quits and is shown to be stuck on the loading bar. During that, the app is
leaking memory really fast, filling up my 32GBs of ram in approximately 1
minute.
I can only track the issue down to 6.20 since that's the version the installer
started working at, but it's present in 6.22 too.
Strangely enough, after you kill its process, the installer actually succeeds
at its jos and successfully installs the launcher.
I don't know what I can provide to help with this, apart from the link to the
installer, so let me know.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38101
Bug ID: 38101
Summary: Devil May Cry 4 flickering/texture tearing to eventual
white screen
Product: Wine
Version: 1.7.34
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shomari.sharpe(a)gmail.com
Distribution: ---
on starting the game (Directx 9c version) there is lots of flicker present.
Upon turning "ON" the VSYNC option in the game the flicker is reduced. The
title screen will display until it eventually turns to a black and white
alternating flickering.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39806
Bug ID: 39806
Summary: Devil May Cry 4 Frozen Screen Glitch
Product: Wine
Version: unspecified
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: dijscales(a)gmail.com
Created attachment 53141
--> https://bugs.winehq.org/attachment.cgi?id=53141
Details of the Problem
The screen will randomly freeze while I am playing the game. I can't even play
for very long before it freezes. I tried to fix it by changing the config.ini,
but that did nothing.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45711
Bug ID: 45711
Summary: Devil May Cry 4 DX10: Transparent sections of textures
rendered as solid black or grey
Product: Wine
Version: 3.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: nenxvrr4.tgj(a)20mail.it
Distribution: ---
Created attachment 62142
--> https://bugs.winehq.org/attachment.cgi?id=62142
Forest level in Devil May Cry 4 illustrating problem.
Transparent sections of textures are rendered as solid black or grey e.g a leaf
appears as a leaf on a black rectangle. This also affects other assets such as
paintings.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45712
Bug ID: 45712
Summary: Devil May Cry 4 DX10: Shadows are rendered as
"lights", vice versa
Product: Wine
Version: 3.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: nenxvrr4.tgj(a)20mail.it
Distribution: ---
Created attachment 62143
--> https://bugs.winehq.org/attachment.cgi?id=62143
Game screenshot showing light and shadow being reversed.
Shadows appear as "light" while light appears as shadows. This also causes
levels to be unusually dark.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50631
Bug ID: 50631
Summary: Old programs on https://www.winehq.org/irc
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jkfloris(a)dds.nl
Distribution: ---
On https://www.winehq.org/irc the following programs are mentioned.
X-Chat last update 2010
Sidenet last update 2006
WineDoors last update 2013
Cedega
IEs4Linux
Do people really still use these programs?
Perhaps the last four programs can be replaced by PlayOnLinux and PlayOnMac
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50866
Bug ID: 50866
Summary: Accessing https://www.winehq.org/pipermail/ will make
the whole website inaccessible
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: huupoke12(a)gmail.com
Distribution: ---
After accessing https://www.winehq.org/pipermail/ (the trailing slash is
present), the user can't access any other www.winehq.org webpages.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=30186
Bug #: 30186
Summary: Wine Bugzilla quick search return zero result for
keywords
Product: WineHQ Bugzilla
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
If I remember correctly, it works yesterday.
Today I try to search some short keywords in Wine Bugzilla quick search box,
and found it doesn't work as before:
For example, search for "win","mac","wow", "aj", "a", the result is empty.
Here is a example URL:
http://bugs.winehq.org/buglist.cgi?query_format=specific&order=relevance%20…
Bug or feature?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=21424
Summary: Cygwin 1.7.1 bash crashes
Product: Wine
Version: 1.1.36
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
cygwin installs now, but one sees the following crash
10 [main] bash 9 _cygtls::handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
1271 [main] bash 9 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
err:ntdll:RtlpWaitForCriticalSection section 0x736d2784 "loader.c:
loader_section" wait timed out in thread 0036, blocked by 003c, retrying (60
sec)
during postinstall, and also when running bash interactively.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52081
Bug ID: 52081
Summary: usbip: error: vhci driver is not loaded
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
When trying to install and use the usbip-win client
https://github.com/cezanne/usbip-win/releases/download/v0.3.5/usbip-win-0.3…
trying to attach a remote usb device fails with the
usbip: error: vhci driver is not loaded
This happens with the released version of usbip-win v0.3.5 as well as with a
self-compiled version of usbip-win where the has_certificate function is
disabled. Below are the steps to reproduce. In order to test this, are usbip
server (in my case this is on "donglerasp") where "usbipd -D" is running and a
usb device is exported with
usbip bind --busid=1-1.2.3
$ wine usbip.exe install -w
usbip: error: root driver already exist
0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000011FC20
$ wine usbip.exe list -r donglerasp
Exportable USB devices
======================
- donglerasp
1-1.2.3: unknown vendor : unknown product (0529:0001)
:
/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.3
: unknown class / unknown subclass / unknown protocol (ff/00/00)
: 0 - unknown class / unknown subclass / unknown protocol
(ff/00/00)
0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000011FC20
$ wine usbip.exe attach -r donglerasp -b "1-1.2.3"
usbip: error: vhci driver is not loaded
0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA,
000000000011FC20
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34497
Bug #: 34497
Summary: ProAIS2 Serial Port enumeration requires Registry
Local_Machine/…/Enum/SERIAL/COM1/COM1/*
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winehq(a)paul.sladen.org
Classification: Unclassified
ProAIS2 (Marine AIS software from SRT in the UK, and re-badged by large numbers
of OEMs) performs Serial Port detection by enumerating the registry. The
following keys need to be added:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\SERIAL\COM1\COM1]
"ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}"
"FriendlyName"="Serial Port (COM1)"
"PortName"="COM1"
in addition to the matching
ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1
If only the ClassGUID/FriendlyName are set, then the port will be found, but
immediately switched to in-case. PortName is being prefixed with "\\.\"
("\\\\.\\") to form "\\.\COM1".
Kudos to Doug Brown for tracking down most of the issue:
http://www.downtowndougbrown.com/2013/03/getting-x-ctu-in-wine-to-detect-yo…
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49972
Bug ID: 49972
Summary: Termie 1.0 crashes after selecting a serial port.
Product: Wine
Version: 5.18
Hardware: x86-64
URL: http://termie.sourceforge.net/#downloads
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ArchLinux
Created attachment 68373
--> https://bugs.winehq.org/attachment.cgi?id=68373
Console messages
Summary
Termie 1.0 crashes after selecting a serial port.
Download location
http://termie.sourceforge.net/#downloadshttp://termie.sourceforge.net/Termie-1.0-Binary.zip
$ sha256sum Termie-1.0-Binary.zip
53469ffdb38058b985482cbfac3f4c0575eeafa4e1b766b5f0c2af43acb7cba6
Termie-1.0-Binary.zip
$ unzip Termie-1.0-Binary.zip
Steps to reproduce:
1)Start the program:
$ wine Termie.exe
After a long time (+- 20 seconds) the program opens.
2) Select one of the comm port. Now the program crashes.
3) Press ctrl-c in the console to kill wine.
4) restart Termie.
$ wine Termie.exe
Now wine gives this error.
"[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.IOException: Broken pipe."
Every time Termie is restarted via step 3, it crashes the same way.
My versions
$ wine --version
wine-5.18 (Staging)
$ pacman -Q wine
wine-staging 5.18-1
uname -a
Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000
x86_64 GNU/Linux
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49974
Bug ID: 49974
Summary: termite-3.4 can't connect to com5 -> /dev/ttyACM0
Product: Wine
Version: 5.18
Hardware: x86-64
URL: https://www.compuphase.com/software_termite.htm
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ArchLinux
Created attachment 68375
--> https://bugs.winehq.org/attachment.cgi?id=68375
console messages
Summary
termite-3.4 can't connect to com5 -> /dev/ttyACM0
Prepare wine:
$ rm -rf ~/.wine/
$ wineserver -k
$ wineboot
Download location
https://www.compuphase.com/software_termite.htmhttps://www.compuphase.com/software/termite-3.4.exe
$ sha256sum termite-3.4.exe
ca440b6c7f6eaa812ba5f8bf42aed86e02022ca50a1c72585168c9b671d0fe19
termite-3.4.exe
Steps to reproduce:
1) Install the program:
$ wine termite-3.4.exe
Accept the defaults.
Now termite starts.
2) Press settings.
The dropdown box only shows COM1. Choose baud rate 9600 and press OK.
Now termite reports "Failed to initialize the port. Please verify the COM port
settings."
3) Press "Connect".
Now that termite reports "Waiting for port"
4) Press close.
Now termite closes.
As a sanity test, I open moserial, choose /dev/ttyACM0 9600,8N1, press connect,
and I see the messages my MCP2221 serial to USB converter is sending to me.
/dev/ttyACM0 is detected by wine:
$ ls -l ~/.wine/dosdevices/
total 0
lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:25 c: -> ../drive_c
lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:35 com1 -> /dev/ttyS0
lrwxrwxrwx 1 cedric cedric 12 Oct 10 19:35 com5 -> /dev/ttyACM0
lrwxrwxrwx 1 cedric cedric 8 Oct 10 19:26 d:: -> /dev/sr0
lrwxrwxrwx 1 cedric cedric 1 Oct 10 19:25 z: -> /
My versions
$ wine --version
wine-5.18 (Staging)
$ pacman -Q wine
wine-staging 5.18-1
uname -a
Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000
x86_64 GNU/Linux
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49752
Bug ID: 49752
Summary: Mikster MPC4 System: 'Selected serial port not exist'
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: amad4wine2020(a)gmail.com
Distribution: ---
Log in as 'Adm' user, go to the 'Controllers list', press the 'Add' button,
select the appropriate 'Port COM' and 'Baud rate', press the 'Test' button, you
will probably get an error message containing the phrase 'Selected serial port
not exist'.
I have tried the following registry keys:
[System\\CurrentControlSet\\Enum\\SERIAL\\COM2\\COM2] 1598720497
#time=1d67e260ec36dbc
"ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}"
"FriendlyName Value"="Serial Port (COM2)"
[Software\\Wine\\Ports] 1598713705
#time=1d67e163e9541c4
"COM2"="/dev/ttyS1"
Unfortunately, it makes no difference.
Download links from the software's website:
https://mikster.eu/en/download-center/https://mikster.eu/wp-content/uploads/2019/03/installmpc482ENG.zip
P.S. The installer will silently install FirebirdSQL 1.5 and enable Firebird
Guardian, it does not work well with winehq-devel.
Unpack the installmpc482ENG.exe and rename the included
installmpc482ENG/firebird/FirebirdWin32.exe before continuing with the
installation.
Install the renamed FirebirdWin32.exe manually (uncheck the 'Use the Guardian
to control the server?' option during the installation).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39810
Bug ID: 39810
Summary: Office 2010 Pro Plus uninstallation fails
Product: Wine
Version: 1.7.55
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: isiraseneviratne(a)yahoo.com
Distribution: ---
After launching the uninstaller (through either the CD Setup or Wine
Uninstaller), selecting the Remove option and then selecting Continue results
in a message saying that setup was unable to finish successfully.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=35904
Bug ID: 35904
Summary: USB connection not recognized by Axon MultiClamp
Commander 700B.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
The "Axon MutiClamp Commander 700B" is a devices which connected with USB to
the PC. The software for controlling the device installs and runs well, but it
does not identify the USB device.
For this reason, the application "MutiClamp Commander 700B" in Winehq's AppDB
has currently status "Garbage".
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51391
Bug ID: 51391
Summary: On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a
network firewall dialog, breaks user32:win
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog
(see the screenshots for the TestBot WineTest runs on w7u_2qxl and w8). Despite
that ntoskrnl.exe:ntoskrnl succeeds.
However it leaves that dialog open which then causes two failures in
user32:win:
https://test.winehq.org/data/patterns.html#user32:win
win.c:3394: Test failed: GetActiveWindow() = 00000000
win.c:3394: Test failed: GetFocus() = 00000000
Notes:
* These are the same failures as in bug 51390. If it is decided that user32:win
is the test that needs fixing then this bug could be merged.
* But if the decision is that ntoskrnl.exe:ntoskrnl should either not trigger
such a dialog or close it, then this bug should remain separate.
* Most of ntoskrnl.exe:ntoskrnl is skipped on Wow64 so this issue does not
happen in newtb-w864-32.
* The 64-bit ntoskrnl.exe:ntoskrnl test also does not trigger that dialog for
some reason.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=19713
Summary: Some serial port communication functions behave
differently in Wine and Windows.
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fenixk19(a)mail.ru
Created an attachment (id=23025)
--> (http://bugs.winehq.org/attachment.cgi?id=23025)
Test program
This makes test program to hang in Wine, but in MS it is ok. Test program
attached.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37846
Bug ID: 37846
Summary: Communication broken using FTDI USB Serial Device
converter (FT232RL) / Mostly send using CS-51PLUS
Product: Wine
Version: 1.7.30
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lgeorgieff(a)gmail.com
Distribution: ---
Created attachment 50402
--> https://bugs.winehq.org/attachment.cgi?id=50402
WINEDEBUG="+comm" wine .wine/drive_c/Program\ Files\
\(x86\)/Icom/CS-51PLUS/CS51PLUS.exe log
Hi,
I am using FTDI USB Serial Device converter to program ham radio.
Cable have FT232RL chip and software is CS-51PLUS.
Reading from radio is OK but when I try to write (send) configuration to the
radio communication is broken after while and I get error message.
The same cable and software on the same machine runs without problems on QEMM's
virtual windows.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13296
Summary: regression problem in upgrade to Ubuntu Hardy/1.0-rc1:
Palm Hotsync over serial Segmentation Fault
Product: Wine
Version: 1.0-rc1
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jan-winehq(a)h-i-s.nl
Created an attachment (id=13150)
--> (http://bugs.winehq.org/attachment.cgi?id=13150)
Logging output
I upgraded to Ubuntu Hardy, and wine 1.0-rc1.
Hotsync manager 1.0 for Palm Pilot worked fine before.
http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362
Now it crashes half-way synchronising over the serial port, sometimes after a
few seconds, sometimes much later in the process.
These crashes reproduce well, and yield a segmentation fault without further
information
$ wine hotsync.exe
Segmentation fault
$
I do not know if this means that a part of Wine crashes, or just the
application.
I added logging, where it seems that the problem lies within the call below:
0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0
I am not sure if the problem lies with wine, or that other problems with Ubuntu
Hardy may relate to this.
It is disappointing that an application that used to work fine, and I came to
depend on, is now broken.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=25083
Summary: HyperTerminal unable to loop back on COM1 (RS-232)
Product: Wine
Version: 1.3.6
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: graham(a)nerve.org.za
On a machine with an on-board RS-232 port at COM1, HyperTerminal (as shipped
with Windows XP) is firstly unable to detect the port until changes are made in
the WINE registry, thereafter, after attaching a simple loopback adapter (pins
2 and 3 of a DB9F shorted) no characters are echoed to the screen.
Obtaining the software:
>From a Windows XP installation, copy the files hypertrm.exe and htrn_jis.dll
from 'C:\Program Files\Windows NT' and hticons.dll and hypertrm.dll from
C:\Windows\System32' into a suitable directory below .wine/drive_c
or
Download a free 30 day trial of HyperTerminal Private Edition 7.0 from
http://www.hilgraeve.com/hyperterminal/
Create 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
At this point, starting HyperTerminal will result in no serial ports being
shown.
Now, create a registry entry in WINE for the serial port, mentioned 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"
Now HyperTerminal can be started, COM1 can be selected and configured, but no
characters are echoed to the screen.
However, the free terminal program, simply named 'Terminal' and available here:
https://sites.google.com/site/terminalbpp/
Does echo characters to the screen.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47873
Bug ID: 47873
Summary: kernel32:comm fails randomly
Product: Wine
Version: 4.17
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
kernel32:comm fails randomly on multiple Windows versions:
comm.c:708: Found Com port COM1. Connected devices may disturb results
comm.c:859: Test failed: WaitCommEvent failed with a timeout
comm.c:870: recovering after WAIT_TIMEOUT...
comm.c:880: Test failed: WaitCommEvent error 0
comm.c:881: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0
comm.c:885: WaitCommEvent for EV_TXEMPTY took 1500 ms (timeout 1500)
comm.c:886: Test failed: WaitCommEvent used 1500 ms for waiting
https://test.winehq.org/data/tests/kernel32:comm.html
These failures are random and have been seen on the following TestBot VM4
configurations:
wxppro
w2003std
w7pro64-32
w1064v1507-32
w1064v1607-32
w1064v1607-64
w1064v1709-64
w1064v1607-64
w1064v1809-32
w1064v1809-32
w1064v1809-64
w1064v1809-2scr-32
w1064v1809-fr-64
w1064v1809-ja-32
w1064v1809-ja-64
So it does not depend on the Windows version, bitness of the test, or locale.
However it only happens on QEmu VMs: it never happened on the fg-win7u64 VMware
VMs or on the real hardware machines, cw-rx460 and cw2-gtx560.
Yet the VMware VMs have two serial COM ports, and, according to dmesg | grep
tty, the real hardware machines do have a serial port too.
QEmu bug?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.