Doom in Linux HOWTO

Hello.

I really think that playing doom on the same machine the tunnel is running, is rather rare requirement, so you can write that section omitting that detail. I also still think that it is nothing more than your bridging software limitation. See what the main page says:
---
For those who wanna play in Windows, *with more than 2 LANs connected*, try GIT
---
And I also think that tunelling to dsn will work. I tried 2 dosemu sessions:
first with $_vnet=(on) and the second with $_vnet=(off) (as acting from outside) and the dooms see each other.

Well, I don't agree it is a third-party patch:) Furthermore it will be a part of dosemu eventually, so this part of the doc is nothing more than a "temporary hack".

No, this is whatever CPU you want to be emulated (actually just reported to the dos prog with some other minor differences).

Doom might not requre neither XMS nor EMS but still setting them to 0 is not recommended as many other progs may start complaining.

Is it really necessary to do that packets conversion? I was playing network doom only on dsn and it works also without a novell_hack, so I am not sure what problems does it solve exactly. So why is this important?

OK, I think you have to also describe a $_vnet possibility. Btw, if $_vnet is enabled, $_netdev is ignored, which must be noted.

How does this feet with your suggestion of setting $_hogthreshold to 0? It must eat 100% of your cpu if $_hogthreshold is not enabled.
Even with $_hogthreshold set to 1 doom eats 75% of CPU under X and 60% under console on my Athlon700. Two instances of doom (connected via vnet) are not playable:(
So I would say doom is extremely CPU-hungry under dosemu, at least on my system.

* At 2002-12-08T17:35+0300, Stas Sergeev wrote:
:

| I really think that playing doom on the same machine the tunnel is
| running, is rather rare requirement, so you can write that section
| omitting that detail.

I find this to be a very strange opinion. Most people wanting to play Doom on the 'net won't have an extra machine on which to run a tunnel.

| I also still think that it is nothing more than your bridging software
| limitation.  See what the main page says:
| ---
| For those who wanna play in Windows, *with more than 2 LANs
| connected*, try GIT
| ---
| And I also think that tunelling to dsn will work. I tried 2 dosemu
| sessions: first with $_vnet=(on) and the second with $_vnet=(off) (as
| acting from outside) and the dooms see each other.

Mm, I still have some testing to do...

| Well, I don't agree it is a third-party patch:) Furthermore it will be
| a part of dosemu eventually, so this part of the doc is nothing more
| than a "temporary hack".

I'm aware. On the other hand, it's been supplied as a patch for quite some time now. :)

| No, this is whatever CPU you want to be emulated (actually just | reported to the dos prog with some other minor differences).

Ok, I guess it's rather irrelevant in Doom's case, then?

| Doom might not requre neither XMS nor EMS but still setting them to 0 | is not recommended as many other progs may start complaining.

That's sort of outside scope of the HOWTO, however I believe there was some particular reason for setting 0 EMS, but I don't remember what it was, now.

| Is it really necessary to do that packets conversion? I was playing
| network doom only on dsn and it works also without a novell_hack, so I
| am not sure what problems does it solve exactly. So why is this
| important?

Hm. Looks like it does convert them to 802.3 regardless of whether it's on or off?

| OK, I think you have to also describe a $_vnet possibility. Btw, if | $_vnet is enabled, $_netdev is ignored, which must be noted.

Yes, I will expand this part when Section 4.2 is written.

| How does this feet with your suggestion of setting $_hogthreshold to | 0? It must eat 100% of your cpu if $_hogthreshold is not enabled.

You're right. This was an error. It DOES eat alot of CPU. :)

Thanks for your feedback.

Stian Sletner

sorry i'm late getting into this but why can't you run either:

lxdoom-svga 1.4.4-7
Svgalib binary for lxdoom
or
lxdoom-x11 1.4.4-7
X binary for LxDoom

do they not have needed features?

Oh, I have slipped the surly bonds of DOS,
and danced the skies on Linux silvered wings.
http://pfrostie.freeservers.com/cad-tastrafy/
http://www.freelists.org/list/cad-linux

because he wanted to detail doom under dosemu. :) sometimes this kind of reason is simply enough when you're talking about linux.

btw, lxdoom is totally outdated. that project has merged with 2 other doom port projects and has formed prboom.

i think doom legacy is the best; you have mouse look up and down (like quake) and can jump.

pete

begin phrostie <[email protected]>

Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D