LinuxQuestions.org - Starting Win32 hlds via wine problem

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Starting Win32 hlds via wine problem (https://www.linuxquestions.org/questions/slackware-14/starting-win32-hlds-via-wine-problem-302594/)

Starting Win32 hlds via wine problem

I went through this a while ago, but I could not find the old threads so forgive me for starting this topic again. Once again, I have time to continue this task.

I have Slackware 10.0 running, and have used for quite a while. I run the Windows Half-Life server using wine. I do it because there are no linux binaries for Opposing Force, the mod I run.

To start this, I have to start either the Norton Commander for Windows, or the Total Commander for Windows, both windows file manager type of programs. From there, I start hlds.exe, and it runs just fine. Both of these file managers see ONLY C:\, the windows fake drive, and Z:\, which appears to be mapped to my linux root (this is not my doing). They see them as if they were windows drives, not linux drivers. So, I navigate to z:\fat-d\hlserver\gearbox, where hlds.exe is located, and start it with appropriate switches. I've been doing this for about a year, and it works well.

If I try to start if from konqueror, it fails to start:

fixme:font:WineEngCreateFontInstance just using first face for now
err:mmio:MMIO_ParseExtA No . in szFileName: ""
err:mmio:MMIO_ParseExtA No . in szFileName: "Z:\\fat-d\\hlserver\\gearbox\\"
wine: Unhandled exception (thread 003e), starting debugger...
WineDbg starting on pid 0x3d
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x01408d68).
In 32 bit mode.
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:1007 GS:0000
EIP:01408d68 ESP:4068fb14 EBP:42ec0944 EFLAGS:00210246( - 00 -RIZP1)
EAX:00000000 EBX:42ec0900 ECX:00000001 EDX:42ec0944
ESI:415d5d30 EDI:42ecc310
Stack dump:
0x4068fb14: 42ecc7d8 415d5d30 00000000 42ec09b4
0x4068fb24: 00000100 00000000 00000000 00000000
0x4068fb34: 00000136 00000000 0140cba5 42ff1130
0x4068fb44: 0140cbb6 42ff1130 00000000 00000001
0x4068fb54: 0003004c 42ff1130 00000000 00000000
0x4068fb64: 00000136 0000015e 42ea0fe7 00000001
0200: sel=1007 base=40016000 limit=00001f97 32-bit rw-
Backtrace:
=>1 0x01408d68 in hlds.exe -port 27014 (+0x8d68) (0x42ec0944)
2 0x42e9c550 in vgui2 (+0xc550) (0x42e9c230)
0x01408d68: movl 0x0(%eax),%edx
Wine-dbg>parse error
Wine-dbg>

I'm not quite sure what is is telling me. Any ideas how to trouble shoot this, or where to go from here? Or why it works from the windows file manager programs, but not from konqueror?

It's probably being supplied with unexpected arguments from Konq.

But more to the point: OpFor can be run from the linux hlds without any problem. In fact, if running with Steam, it's a matter of a couple of install commands to get OpFor, just like it is for CS. I promise, it can be done. :)

The last time I installed linux Steam, it installed OP4 but installed the win32 dll only. It did not run because there were not any linux binaries. Have you actually run linux hlds OP4?

I've been running the win32 Steam OP4 via wine for quite a while, and it works very well. The only problem is the startup issue I mentioned. Linux binaries for hlds tend to blow chunks as Valve doesn't seem to know how to make them run stably and without memory leaks. I'll take the win32 binaries any day.

I wonder if it throws the error because Z:\\fat-d\\hlserver\\gearbox\\ does not exist when launched from Konq? Being a win32 app, it expects Z:\\fat-d\\hlserver\\gearbox\\, not /fat-d/hellserver/gearbox.

I would rather not run the binaries than run them through wine. And I've never seen any memory leak for my CS server. In answer to your question: no, I haven't run OP4, but I know people who have, using linux binaries.

Can you refer me to one of them? The last I heard, there were no linux OP4 binaries, so I would very much like to talk to someone who is doing this.

Are you on the hlds mailing lists? They rant and rave all the time about the problems with the linux binaries, and we just don't seem to have those problems with the win32 binaries.

Quote:

[i]I would rather not run the binaries than run them through wine. [/B]

I've done this for more then a year, and it works very very well. Half-Life OP4 Win32 server running under Linux via Wine is very stable and performs very well.

Back to the original question. How can I start hlds.exe so that it thinks it's starting form z:\fat-d\hellserver\gearbox? As I mentioned above, I can start it from Total Commander, but not fro Konq.

Anyone? How to start hlds.exe from Konq without errors?