http://bugs.winehq.org/show_bug.cgi?id=3586
------- Additional Comments From akohlsmith-wine(a)mixdown.ca 2005-14-10 15:04 -------
I forgot to mention that the individual helping on IRC has no issues running
the setup.exe with SuSE 9.3, which is why we believe it is something specific
to my install, but aren't sure what or how to next approach this.
--
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=3586
------- Additional Comments From akohlsmith-wine(a)mixdown.ca 2005-14-10 15:02 -------
Created an attachment (id=1173)
--> (http://bugs.winehq.org/attachment.cgi?id=1173&action=view)
non-stripped backtrace with native comctl32.dll
This is the same backtrace after a make install-dev and a rm -rf ~/.wine and
forcing the windows version to win2k through winecfg. It is using the native
comctl32.dll from my win2k machine.
--
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=3584
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From vitaliy(a)kievinfo.com 2005-14-10 15:01 -------
Author resubmited more readable bug report
--
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=3586
------- Additional Comments From akohlsmith-wine(a)mixdown.ca 2005-14-10 15:00 -------
Created an attachment (id=1172)
--> (http://bugs.winehq.org/attachment.cgi?id=1172&action=view)
non-stripped backtrace with builtin comctl32.dll
This is the backtrace after a make install-dev and a rm -rf ~/.wine and forcing
the windows version to win2k through winecfg. It is using the builtin
comctl32.dll.
--
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=3586
Summary: All apps (various installshield setup.exes) seem to
crash
Product: Wine
Version: CVS
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-binary
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: akohlsmith-wine(a)mixdown.ca
Working with some very bright individuals in #winehq we've come to the
conclusion that there is something unusual about my setup. It is a stock
Slackware 10.1 system, stock kernel.org kernel 2.6.13 SMP (HT) on a P4 system
with 768MB of RAM. I was running with the kernel default of CONFIG_NOHIGHMEM
but it was suggested I use CONFIG_HIGHMEM4G to get the 2G/2G split instead of
the default 3G/1G... no change.
Wine is compiled clean from CVS HEAD (as of 20051014), rm -rf ~/.wine before
make install. Running as a normal user. Also tried forcing windows version
to Win2k and copying comctl32.dll over (and forcing native instead of builtin
use of comctl32).
Almost all apps fail immediately and with a very very similar backtrace. Some
will get the InstallShield "initializing" progressbar, some just crash right
away without putting anything on the screen.
I'm running xorg 6.8.1 on an ATI Radeon Mobility M7 LW (Mobility 7500) -- this
is an IBM Thinkpad T30.
An example backtrace from a failed setup.exe attempt is at the bottom of this
bug report (palm desktop 4.14), but two different versions of Agendus also
fail pretty much the same way. Please note that there are libraries loaded
above 0x7fffffff, which I was told is unusual.
Hopefully someone can assist.
--
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=3584
------- Additional Comments From akohlsmith-wine(a)mixdown.ca 2005-14-10 14:56 -------
Created an attachment (id=1171)
--> (http://bugs.winehq.org/attachment.cgi?id=1171&action=view)
non-stripped backtrace with builtin comctl32.dll
Sorry about posting the crash inline instead of attaching. Especially since it
appears to be a stripped install. This is the same backtrace after a make
install-dev and a rm -rf ~/.wine and forcing the windows version to win2k
through winecfg. It is using the builtin comctl32.dll.
--
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=3585
Summary: Wiki mentions 'quickstart' document which has
disappeared
Product: WineHQ.com
Version: unspecified
Platform: Other
URL: http://wiki.winehq.org/Debugging_Reason_3
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: misc-web
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: akohlsmith-wine(a)mixdown.ca
The wiki link
http://wiki.winehq.org/Debugging_Reason_3
Mentions a quickstart document which appears to be very useful for determining
WHERE a crash occurs. I have, however, been unable to locate this document to
try and help with my own debugging.
The text in question is as follows: "Here code e06d7363 is, as you can see
from the quickstart document, a MSVC++ exception. So it hasn't crashed,
instead the program has thrown an internal exception using "throw foo::bar"
syntax."
--
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=1429
------- Additional Comments From gareth.tpc(a)gmail.com 2005-14-10 14:32 -------
dxdiag still failes with a number of fixmes. It procues a dialog that asks if
you want to check your drivers against MS's dirver database. I clicked "no" and
got the following output:
gareth@linux-box:/mnt/c/windows/system$ wine dxdiag.exe
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),1,3,(nil),0,(nil)) - stub!
fixme:dxdiag:IDxDiagContainerImpl_AddProp (0x403da338, L"dwDirectXVersionMajor",
0x407df9c4)
fixme:dxdiag:IDxDiagContainerImpl_AddProp (0x403da338, L"dwDirectXVersionMinor",
0x407df9c4)
fixme:dxdiag:IDxDiagContainerImpl_AddProp (0x403da338,
L"szDirectXVersionLetter", 0x407df9c4)
fixme:dxdiag:IDxDiagContainerImpl_AddChildContainer (0x403da318,
L"DxDiag_SystemInfo", 0x403da338)
gareth@linux-box:/mnt/c/windows/system$ wine --version
Wine 20050930
And a dialog that says "Error: DXDIAGN.DLL is out of date". NB: I simply rand
dxdial from my windows partition rather than installing a fresh copy, in case it
matters.
--
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.