Hello. Stian Sletner wrote:
Section 4.2 is still unwritten because of my tunnelling problems, I'm still not quite sure how to go about it.
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.
if you want sound to work (and who wouldn't), you need to get a third-party patch
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".
Set $_cpu to whatever fits your iron.
No, this is whatever CPU you want to be emulated (actually just reported to the dos prog with some other minor differences).
Set $_xms to some value you see fitting, I use 8192. Set $_ems to 0, Doom doesn't use it.
Doom might not requre neither XMS nor EMS but still setting them to 0 is not recommended as many other progs may start complaining.
$_novell_hack to on.
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?
$_netdev to "eth0", if that is your LAN device.
OK, I think you have to also describe a $_vnet possibility. Btw, if $_vnet is enabled, $_netdev is ignored, which must be noted.
DOSEMU and Doom do not use very much CPU
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. - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
