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.
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.
http://bugs.winehq.org/show_bug.cgi?id=10051
Summary: Parallax SX Key IDE cannot detect serial port under WINE
Product: Wine
Version: 0.9.46.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-setupapi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ultimatedevr(a)yahoo.com
Created an attachment (id=8599)
--> (http://bugs.winehq.org/attachment.cgi?id=8599)
Result of running SXKey.exe in wine with the +setupapi debug flag.
I am trying to run the Parallax SX Key IDE through WINE, however the IDE does
not detect any of my serial ports. I have symlinked them to ~/.wine/dosdevices/
and added them to my registry, however the IDE still cannot detect my serial
ports.
I am currently running WINE v.0.9.46 (the same problem exists in the CVS
version as well).
(BTW, I have heard of others getting this to work, yet others who couldn't:
http://forums.parallax.com/forums/default.aspx?f=15&m=217429&g=221692)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=23326
Summary: Cannot change printer settings, Family Tree 7
Product: Wine
Version: 1.2-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jamesl(a)bestweb.net
Created an attachment (id=29072)
--> (http://bugs.winehq.org/attachment.cgi?id=29072)
FTW7 print dialogue, compare Wine to XP
Cannot select printer/change print settings with Family Tree Maker 7. Dialogue
box comes up, drop-down boxes are working, but radio buttons for switching
between "default printer" and an alternate printer are not selectable. Have
compared the print dialogue between Wine vs a native install under Windows XP
(SP3) and notice some text from the Windows install does not show up under
Wine.
Also tried the same thing with the "free" version of FTM2005se available at
http://past.familytreemaker.com/download/starter.aspx and found it's behavior
is the same. So I will describe steps from there, since it would be eaier for
someone to get that to test against.
STEPS TO RECREATE:
1: Set up wine profile with "WINEPREFIX=/home/jelabarre/wine-apps/ftw2005
winecfg"; set winver to "Windows XP", point the Documents directory under
Desktop Integration to my own Documents directory
2: install FTW2005 by running
"WINEPREFIX=/home/jelabaWINEPREFIX=/home/jelabarre/wine-apps/ftw2005 wine
./FamilyTreeMaker2005se.exe", accept all defaults.
3: open FTW 2005 from "Wine" menu entry on Gnome menu. Selected "Buy Later"
from popup window (does not affect outcome, as same print problem occurrs in a
regular retail version of FTM7)
4: create new file, or use existing file (same result either way)
5: select "File | Print Setup", then try to select radio button for either
"Default Printer" or "Specific Printer". Neither can be selected
6: try selecting a "specific printer" from drop-down box. Printer can be
selected, but radio buttons still not functional.
7: after selecting a printer other than the default (such as print-to-PDF) and
then try printing. Output will still go to the Linux default printer, no edits
of the print settings will take effect.
The "Family Archive Viewer v6.0" at
http://familytreemaker.genealogy.com/abtffiv.html and "Family Archive Viewer
v11.0" at http://www.genealogy.com/abtffiv.html are other variants that
exhibits this behavior.
Have attached sample screenshots of Wine vs WinXP versions of the print
dialogue.
--
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=9378
Summary: CM: Shock Force 'Could not initialize graphics display'
Product: Wine
Version: 0.9.43.
Platform: PC
URL: http://www.battlefront.com/products/cmsf/downloads.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mailing_list(a)orange.nl
After starting Combat Mission: Shock Force Demo it stops with the message:
'Could not initialize graphics display. REQUIRED 1024x768, 32-bit
color'.
The terminal output doesn't provide any clues:
wine 'CM Shock Force DEMO.exe'
ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0
ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file
or directory
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=18889
Summary: Live Messenger 2008 fails to load - possible actctx
problem
Product: Wine
Version: 1.1.16
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andras(a)csevego.net
Created an attachment (id=21730)
--> (http://bugs.winehq.org/attachment.cgi?id=21730)
+actctx,+relay log
Starting of installed (on windows) Msn 2009 wil result:
err:module:import_dll Library MSVCR80.dll (which is needed by
L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe") not
found
err:module:LdrInitializeThunk Main exe initialization for
L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe" failed,
status c0000135
Same load failure, when I manually install with wine (from msi packages)
MSVCRT 8.0 is installed, as shown attached +actctx,+relay log
I suspect here an Activation Context failure.
--
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=24614
Summary: Medieval Total War crashes on startup
Product: Wine
Version: 1.2
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx9
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: th.seltsam(a)gmail.com
CC: wine-bugs(a)winehq.org
Running the game just shows a black window, no crash dialog, and an infinite
console output
err:d3dx:assemble-shader Asm reading failed
err:d3dx:assemble-shader Asm reading failed
err:d3dx:assemble-shader Asm reading failed
err:d3dx:assemble-shader Asm reading failed
Using d3dx9-36 did not solve the problem.
--
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=11436
Summary: Pepakura viewer: err:wgl:X11DRV_wglShareLists Could not
share display lists, context already created !
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://www.tamasoft.co.jp/pepakura-
en/download/viewer.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: x11-driver
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fabio.capela(a)yahoo.com
Created an attachment (id=10567)
--> (http://bugs.winehq.org/attachment.cgi?id=10567)
Trace until the error.
I'm trying to run the Pepakura viewer, but it's giving an strange error on
startup (error: no error) and is having some graphical glitches, as well as
being extremely slow.
The grafical glitches are a flickering 3D model and no textures on the 2D
model.
The bug seems to be the same one affecting Pepakura Designer 2.
The console shows an error with X11DRV_wglShareLists
(err:wgl:X11DRV_wglShareLists Could not share display lists, context already
created !). I've attached a wgl trace up to the moment the error dialog
appears. Seems like the workaround to handle the different way to share OpenGL
contexts in Windows and Linux can't handle this specific software.
The software is freeware and can be downloaded from
http://www.tamasoft.co.jp/pepakura-en/download/viewer.html
--
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=21983
Summary: Buttons come on each other in Proteus
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ssserkkk(a)yahoo.com
hi!
The buttons in ISIS and ARES come on each other. The ones that create this
problem are "subcircuit mode ile terminals mode",
"virtual instruments mode and 2D graphics line mode" in ISIS program;
"connectivity highlight mode and round through-hole pad mode", "padstack mode
and 2D graphics line mode" in ARES.
--
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.