http://bugs.winehq.org/show_bug.cgi?id=4053
------- Additional Comments From blacktiger(a)covers.de 2005-24-12 08:47 -------
Well when i pressed c it worked a bit further but then stopped again ... I tried
pressing c again but didn't change anything
So the game didn't really start at all ...
Again a screenie to see what I see ;):
http://img358.imageshack.us/img358/1164/winedbgwargh4hr.jpg
Shall I post the whole text output winedbg gave me? ... But as I said I didn't
come that far to reproduce the "closing the game error" ...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4053
------- Additional Comments From blacktiger(a)covers.de 2005-24-12 08:26 -------
Hmm I think here went something wrong ;)
Look at the screen please:
http://img469.imageshack.us/img469/4672/winedbg0vo.jpg
Did I do something wrong, or should I do something else? Let me know :o
Ah and btw - Merry Christmas ^_^"
All I get (as you can see on the picture) is the following text and an empty
windowed wine box:
WineDbg starting on pid 0xa
In 32 bit mode.
start_process () at
/home/blacktiger/wine-0.9.3/dlls/kernel/../../include/winternl.h:1692
0x7fc7580c start_process+0xfc
[/home/blacktiger/wine-0.9.3/dlls/kernel/../../include/winternl.h:1692] in
kernel32: jmp 0x7fc757fb start_process+0xeb
[/home/blacktiger/wine-0.9.3/dlls/kernel/process.c:994] in kernel32
1692 static inline void WINAPI DbgBreakPoint(void) { __asm__
__volatile__("int3"); }
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4053
------- Additional Comments From reif(a)earthlink.net 2005-24-12 08:03 -------
Yes, that's the type of info we need. Unfortunately the program catches the
crash rather than wine so the info is useless. I never tried this so I don't
know if it will work but can you try running the program in the wine debugger to
see if it catches the exception first. Use winedbg rather than wine to run your
program.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4147
Summary: Regression: steam crashes on wine 0.9.4/cvs from
24.12.2005
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: leon_fraitak(a)mail.ru
Steam started crashing with wine 0.9.4 with following message:
wine: Unhandled page fault on read access to 0x0000000c at address 0x524c0b6c
(thread 001b), starting debugger...
[...]
1 0x524c0b6c DllMain+0x1cc(hinstDLL=0x524a0000, fdwReason=0x3,
lpvReserved=0x0)
[/home/leon/Downloads/tarballs/wine/wine/dlls/msvcrt/../../include/winbase.h:2250]
in msvcrt (0x524c0b6c)
2 0x524d1a28 __wine_spec_dll_entry(inst=0x524a0000, reason=0x3,
reserved=0x0) [dll_entry.c:42] in msvcrt (0x524d1a28)
[...]
With 0.9.3 it worked fine.
Maybe that has something to do with msvcrt, since Bug 4128 also describes a
msvcrt regression, but I'm not sure (I didn't test without the patch)
The patch which may have broken it, is this one:
http://www.winehq.org/pipermail/wine-cvs/2005-December/019940.html
This was the last msvcrt patch committed, but I didn't test without it yet
(that's why I'm not sure if it's msvcrt)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4131
------- Additional Comments From leon_fraitak(a)mail.ru 2005-24-12 07:14 -------
Today I tried Steam with Wine 0.9.3 and it works fine. Make sure you don't use
ALSA driver, because Steam freezes with it for me. With 0.9.4 and today's CVS
it crashes however.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4146
------- Additional Comments From winebugger(a)piments.com 2005-24-12 07:11 -------
from http://www.winehq.org/site/docs/wine-faq/index
wine sol or wine sol.exe (using the search path to locate the file).
wine c:\\windows\\sol.exe (using a DOS file name).
wine /usr/windows/sol.exe (using a UNIX file name).
wine "c:\windows\sol.exe" (using quoted DOS file name).
unix file name may be best left out here for brevity and since sol is a special
case that is likely to be confusing.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4146
Summary: first run usability
Product: Wine
Version: unspecified
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: wine-help
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winebugger(a)piments.com
Suggestions to make wine work for users who are not linux developers.
Starting from the point where the wine package has been installed. What would a
typical user do and what will happen. Remembering we're catering for windows
user mentality here not seasoned linux system maintainers.
At this stage you can be damn sure he/she has not found man wine ; man winecfg;
or winehq.com. He naively thinks he has installed a software package and it will
do something if he runs it, so let's see what happens.
1a. He will look for it on the "start" menu
1b. He will try to run wine from console.
1a. next idea please...
Consider 1b in detail.
First thing wine does it create a default setup if one is not found.
There's a fair chance he had to be root to install it and he still is root.
This is a big no-no but he does not know that yet. Wine does, but carries on
regardless installing /root/.wine and does not even warn the user this is a BAD
idea.
Suggested fix: trap the error and warn. Possibly add --root switch just in case
someone had a real need to do this for some unseen reason. The error should be a
dlg as well as console output.
Maybe now he wants some help:
prof@linbox ~ $ wine -?
wine: cannot open (null)
WHAT?? OK, try again:
prof@linbox ~ $ wine -h
wine: cannot find '-h'
DUHH! forget it just try running wine:
prof@linbox ~ $ wine
Wine 0.9.1
Usage: wine PROGRAM [ARGUMENTS...] Run the specified program
wine --help Display this help and exit
wine --version Output version information and exit
prof@linbox ~ $
So that's it ?! My cry for help gets me "wine PROGRAM [ARGUMENTS...]" what are
arguements? What do I do ??
Critism: this is near useless. it's technical ; version I already got , so what;
"display this page" by this stage is likely to be taken as a bad joke if the guy
is still in a good mood.
Suggestions : -h should equal --help ; so should -? ;don't assume everyone is
used to reading UNIX documentation. One more line with an eg. would speak a
thousand words.
eg wine explorer , wine notepad , wine notepad.exe , wine "c:/Program Files/
installed software/windows-program-name.exe"
ABOVE ALL; he called for help and you've got his attention. HERE is where you
put hooks to more info so he does not have to start using google to find what
doc there is. Refer the user to man wine , man winecfg , www...wine-beginners-
guide.html
So at the first hurdle we fall flat, face-down in the mud.
All our new user gets is "wine PROGRAM". Over and out.
If he did not know before he wont be any wiser.
I'll cut this off here since that much is self-contained , trivial to put in
place and at least a big step forward.
best regards.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.