http://bugs.winehq.org/show_bug.cgi?id=8980
------- Additional Comments From daimengchen(a)gmail.com 2007-16-07 22:19 -------
I got the same bug at the exact same time and server [BT]BrothersTrust. Mine
also freezes and crashes at "retrieving server info." All the servers are now
doing the same thing. At random intervals I may actually be able to connect to a
server, but within 1 second, I am disconnected and receive the message
"Disconnect: Client timed out." I am able to host my own server without
crashing. But the tutorial function does not work. Deleting the HL2 .gcf files
solves the problem temporarily for me too, but requires too much time. I do not
have any such problems with other mods.
I am running Ubuntu Feisty with wine 0.9.41.
--
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=8980
harrisonchen(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Half Life 2 mod The Hidden |Half Life 2 mod The Hidden
|crashes after |crashes after
------- Additional Comments From harrisonchen(a)gmail.com 2007-16-07 22:12 -------
The bug seems to only apply to this specific mod.
--
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=8980
Summary: Half Life 2 mod The Hidden crashes after
Product: Wine
Version: 0.9.41.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: harrisonchen(a)gmail.com
I've been playing the half-life 2 mod "The Hidden" (beta 4) (url:
http://www.hidden-source.com/) for awhile and I haven't had any problems. Then
I tried joining a server ([BT]BrothersTrust :Hidden Source Beta4a) and The
Hidden would stop at "retrieving server info" and then the game would crash. I
am not sure if the problem is limited to that server. After this initial crash,
every subsequent attempt to join any server has resulted in the same exact crash.
We found a workaround which is to delete all the half life 2 .gcf files, but
this requires redownloading half life 2 and this takes a long time.
I am running Gentoo.
If any more info is needed I would gladly give it.
--
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=8971
------- Additional Comments From wbednarzyk(a)charter.net 2007-16-07 21:58 -------
Vitaliy, I am simply offering what I have managed to find on the MSDN in an
effort to assist with resolving this bug. I haven't re-opened the bug report,
as I figure I am not really worthy of your assistance. Oh great one.
And James, no, I am not satisfied.
You both really need to get a better hobby. You don't seem to like the
interaction, and, don't have the patience to assist self proclaimed NOOBS.
Maybe you all should go eat a hotdog bun on a Friday or something.
Peace
--
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=8979
------- Additional Comments From brian(a)brianvuyk.com 2007-16-07 21:40 -------
A native dinput.dll helped the problem, though it still exists to some extent.
Also, it doesn't seem to be quite a duplicate of the bugs you've mentioned
above, since they all describe behavior very far removed from what I am
experiencing. The only connection between the bugs being that they are with the
mouse.
At any rate, it is playable now, though hardly perfect, with the native dinput.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=8971
------- Additional Comments From truiken(a)gmail.com 2007-16-07 21:18 -------
> Maybe this will help. Don't know what it means, but, it describes the error I
recieve exactly.
No it doesn't help because we already know exactly what the problem is.
manifests are a part of sxs assemblies, which we don't support, which is what
bug 6591 is all about. Are you satisfied now? That's a rhetorical question you
can answer by not reopening this bug.
--
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=8971
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From vitaliy(a)kievinfo.com 2007-16-07 21:15 -------
This is the last time this bug is closed. If you reopen it, it will be simple
ignored. And not a single person will be touching it until you personally
resolve it.
--
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=8971
vitaliy(a)kievinfo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From vitaliy(a)kievinfo.com 2007-16-07 21:14 -------
Bill, again this is bugzilla - the place Wine collects bugs. Bug is an
unresolved issue!
What this place is not:
- It's not a user support forum
- It's not a place ask for help
- It's not a place to seek for workarounds.
--
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=8971
wbednarzyk(a)charter.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |UNCONFIRMED
Resolution|DUPLICATE |
------- Additional Comments From wbednarzyk(a)charter.net 2007-16-07 21:09 -------
Maybe this will help. Don't know what it means, but, it describes the error I
recieve exactly.
http://msdn2.microsoft.com/en-us/library/ms235560(vs.80).aspx
C Run-Time Error R6034 (C++)
This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0
Other versions are also available for the following:
# .NET Framework 3.0
# Microsoft Visual Studio Codename Orcas
Visual C++ Concepts: Building a C/C++ Program
C Run-Time Error R6034
Error Message
An application has made an attempt to load the C runtime library without using a
manifest. This is an unsupported way to load Visual C++ DLLs. You need to modify
your application to build with a manifest. For more information, see the "Visual
C++ Libraries as Shared Side-by-Side Assemblies" topic in the product documentation.
Applications must use a manifest to load the C runtime library. For more
information, see Visual C++ Libraries as Shared Side-by-Side Assemblies and
Manifest Generation in Visual Studio.
In release builds, the diagnostic message reads: "An application has made an
attempt to load the C runtime library incorrectly. Please contact the
application's support team for more information."
To correct this error
*
Rebuild your application with a manifest. Building an application with
Visual Studio automatically puts the manifest into the resulting EXE or DLL
file. If you are building at the command line, use the mt.exe tool to add the
manifest as a resource. Use resource ID 1 if building an EXE, 2 if building a
DLL. For more information, see How to: Embed a Manifest Inside a C/C++ Application.
--
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.