|
|
Post by tmeitner on Oct 22, 2019 14:45:05 GMT -5
Hi everybody,
Long-time user of TNM, looking to get back into it now that I got my old codes from Oliver.
I run a Chromebook (a Pixelbook, actually) with Crostini installed. In other words, I can run Linux apps. I do run some apps, like Steam, through WINE. I was warned that Linux wouldn't be able to support the Windows-based plugins, which is fine. But I've taken a couple of different routes to install TNM 7 SE with DOSBox, and no matter which route I take, launching the game simply hangs at the DOSBox window where the "TNM" command is entered. Nothing happens beyond that.
Does anyone know why this would be? I know there's no official support for Linux, but I was thinking since I can get WINE to run things like Steam and some other apps, there must be a way to get whatever dependencies are needed in order for me to run TNM.
Any thoughts or ideas are appreciated. Cheers!
Tom
|
|
|
|
Post by tnmlyger on Oct 22, 2019 15:27:42 GMT -5
It's probably trying to initialize the Windows server component and failing. What I mentioned in my e-mail was just an example off the top of my head but not an all-encompassing answer.
If I find some time, I'll install a Linux VM later this week. If you install DOSBOX on Linux, most of TNM will work without WINE. But I will need to change some of the source code if it's hanging for you.
|
|
|
|
Post by tmeitner on Oct 22, 2019 15:44:33 GMT -5
Man, you're all over this! I was hoping to not saddle you with support needs. :-)
I installed the TNM package that included DOSBox through WINE, so I'll see what happens if I install DOSBox on Linux straight-up and then install TNM from there. I'll report back!
|
|
|
|
Post by tnmlyger on Oct 22, 2019 17:02:47 GMT -5
The installer won't work in straight Linux as it's a Win32 program.
I'll go the manual route in a few days and see where we end up.
|
|
|
|
Post by tnmlyger on Oct 23, 2019 4:06:00 GMT -5
So... since others might profit from this:
Native Linux DOSBOX doesn't do the trick. In its standard configuration, the arrow keys on the keyboard don't work. You can remap the cursor right and cursor up but left and down return an "unknown_key" error.
To fix this, you have to activate the "usescancodes" configuration option in DOSBOX --- but that prevents about half the keyboard from working properly otherwise when polled through DOS interrupts (which TNM does). So something as simple as entering the name of a card you just created will be close to impossible unless you're looking to call your card "E RA" or "E MADN" ;-)
So... don't get your hopes up.
If you're using UNIX, I recommend getting an actual Windows VM up... not WINE. DOSBOX over WINE will have similar issues as what I described above.
|
|
|
|
Post by tmeitner on Oct 23, 2019 21:59:22 GMT -5
Thanks Oliver!
Tonight, I was able to play around a little bit. I installed the Linux version of DOSBox, and then installed Build 6 of TNM7SE. The current build wouldn't install (I don't remember the error I was getting, but I just went back to Build 6 to give it a shot).
It installed perfectly. I noticed the same situation with the arrow keys, and did go into the config file and change "usescancodes" to "false". This fixed the arrow problem and I could use TNM normally. Interestingly, I didn't have any other keyboard problems - my full keyboard worked. I named one card "WWF Just Testing This Out 2009" and "WWF One Match Only", just to make sure keys were working and everything did.
There are a few screen transitions that hang for 15-20 seconds, but everything else of the default installation seems to work. I imported some wrestlers, ran a couple cards just to put it through its paces, and it worked!
I tried to install the Ladder Plus plugin, but got a message that the INF file was corrupt. But I know with Build 6 and not running in Windows that the plugin situation would probably not work.
So, to recap, the default installation of Build 6 through the native Linux version of DOXBox was a win for me, keyboard and all. My hopes are up at least to be able to use the base program again. A few delays here and there, but even the ring introductions worked. I'm impressed that it goes as smoothly as it did!
And to clarify for anyone - I'm using Debian Linux through Crostini on a Pixelbook Chromebook.
|
|
|
|
Post by tnmlyger on Oct 24, 2019 1:47:34 GMT -5
Thanks for the update, Tom!
I have a suspicion what's happening here. Without having verified it yet, I suspect the missing ingredient that ties all this together is that you're on a US keyboard and I'm on a German one. DOSBOX may be stumbling over the fact that I'm using Fedora in English but with a German keyboard layout.
I'll let you know when I know more.
The installation thing you encountered is explainable.
Build 9 comes with a Windows-based installer which also puts it in your start menu and puts an icon on your desktop. It's streamlined to be installed and run in Windows.
Build 6 was the final straight DOS-based release with a DOS installer and zero Windows integration or DOSBOX for that matter.
|
|
|
|
Post by tmeitner on Oct 24, 2019 8:14:07 GMT -5
Ha! That keyboard explanation makes sense. And yeah,that's what I figured happened with the builds. Either way, after like 20 years without it, having base TNM 7 back is still pretty doggone cool! Now to just find exports of wrestlers from the 80s and 90s. Too many current wrestlers out there! ;-) Hope this thread helps anybody else.
|
|
|
|
Post by tnmlyger on Oct 25, 2019 12:35:41 GMT -5
So... my suspicions have been confirmed. TNM can only run in Linux DOSBOX without error if you're using an English OS with an English keyboard. Since over half of TNM's users are international, I don't think it makes sense to provide and support a pre-built version for Linux.
It's really too big of a headache compared to the number of people who are going to use TNM on Linux.
Sorry for that!
|
|
|
|
Post by tmeitner on Oct 25, 2019 13:19:11 GMT -5
Oh that's okay. I appreciate you even taking the time to look into that. I didn't expect it to be supported, and definitely not if those are the numbers you're working with. Either way, I've got it running on my end!
|
|
|
|
Post by tnmlyger on Oct 26, 2019 2:15:17 GMT -5
That's awesome!
What I will look to do for Build 10 is make it possible for the user to tell the program via a config option if it is being run in Linux, in which case it would forego any Windows integration and behave like Build 6 did.
This way you could take advantage of the general improvements since Build 6 without having to switch away from Linux.
|
|
|
|
Post by tmeitner on Oct 26, 2019 19:59:27 GMT -5
You're the man.
|
|
