Lan game failure

Search these posts first and if your question hasn't already been asked, ask it here!

Smatthew
Posts:6
Joined:Tue Oct 16, 2007 2:39 pm
Lan game failure

Postby Smatthew » Mon Nov 03, 2008 11:46 pm

Hello. I've been trying to run a lan game with two computers run from a router. I'm getting an error message within the dosbox status window..

serial1: warning: tried to activate FIFO

Anyone know what is causing the connection failure?

Thanks.

User avatar
Cabman
Posts:235
Joined:Fri Jul 29, 2005 5:58 pm
Location:Zabrze, Poland

Postby Cabman » Tue Nov 04, 2008 3:36 am

Follow the steps from the Dosbox guide. Then, in section 8A you have to add the LAN IP of the host.

Smatthew
Posts:6
Joined:Tue Oct 16, 2007 2:39 pm

Lan game failure

Postby Smatthew » Wed Nov 05, 2008 2:29 am

i have the dobox config file set up just as the guide suggests and have been using the lan ip(cmd\ipconfig). the router runs four machines and i have been just trying to run moo2 between two of them. i installed moo2 and dosbox just as i did on the other machines on another computer on the lan to do a round robin test to see if it was a particular computer that was causing the problem. im getting the same failure... starting game through multiplayer-network moo2 ui... game loads but on the non host computer there isnt any available games on network. thought it might be a firewall problem, still pretty sure it could be, so set up a port forward on my router(linksys-g) and made exceptions for any firewall running(dosbox,moo2,port 213)... no available connection.

at a bit of a loss to what i should try next.. thanks again cabman.

c'g~
Posts:80
Joined:Wed Jan 16, 2008 3:26 pm
Location:Ukraine

Try Hamachi

Postby c'g~ » Thu Nov 06, 2008 6:22 am

Hi there.

Try to establish the connection through Hamachi (tunneling program) first. Then do as always: run dosbox with config, etc.

Smatthew
Posts:6
Joined:Tue Oct 16, 2007 2:39 pm

hamachi

Postby Smatthew » Thu Nov 06, 2008 9:25 pm

i downloaded hamachi on 2 of the 3 computers i have on my network. the tunneling is definately working between them. however still no moo2 connection once i ran dosbox... multiplayer option starts up on the host but no game visable on the join menu.

the 3rd computer which is actually the one i usually play from that runs my linksys-g network couldnt get hamachi running for some reason, getting "mediation server has rejected your login request".

perhaps there is something funny with my dosbox config so ill have it at the bottom of this post. maybe something i dont have right, currently set up to act as host.. think i got it from siron last year. really thought this last idea would resolve what i thought was a firewall issue, arg.

[sdl]
# fullscreen -- Start dosbox directly in fullscreen.
# fulldouble -- Use double buffering in fullscreen.
# fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# windowresolution -- Scale the window to this size IF the output device supports hardware scaling.
# output -- What to use for output: surface,overlay,opengl,openglnb,ddraw.
# autolock -- Mouse will automatically lock, if you click on the screen.
# sensitiviy -- Mouse sensitivity.
# waitonerror -- Wait before closing the console if dosbox has an error.
# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest.
# Second entry behind the comma is for when dosbox is not focused/minimized.
# mapperfile -- File used to load/save the key/event mappings from.
# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.

fullscreen=true
fulldouble=false
fullresolution=original
windowresolution=original
output=overlay
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language -- Select another language file.
# memsize -- Amount of memory dosbox has in megabytes.
# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
# captures -- Directory where things like wave,midi,screenshot get captured.

language=
machine=vga
captures=capture
memsize=16

[render]
# frameskip -- How many frames dosbox skips before drawing one.
# aspect -- Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler -- Scaler used to enlarge/enhance low resolution modes.
# Supported are none,normal2x,normal3x,advmame2x,advmame3x,advinterp2x,advinterp3x,tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.

frameskip=1
aspect=false
scaler=normal2x

[cpu]
# core -- CPU Core used in emulation: simple,normal,full,dynamic.
# cycles -- Amount of instructions dosbox tries to emulate each millisecond.
# Setting this higher than your machine can handle is bad!
# You can also let DOSBox guess the correct value by setting it to auto.
# Please note that this guessing feature is still experimental.
# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.

core=auto
cycles=auto
cycleup=500
cycledown=20

[mixer]
# nosound -- Enable silent mode, sound is still emulated though.
# rate -- Mixer sample rate, setting any devices higher than this will
# probably lower their sound quality.
# blocksize -- Mixer block size, larger blocks might help sound stuttering
# but sound will also be more lagged.
# prebuffer -- How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=22050
blocksize=2048
prebuffer=10

[midi]
# mpu401 -- Type of MPU-401 to emulate: none, uart or intelligent.
# device -- Device that will receive the MIDI data from MPU-401.
# This can be default,alsa,oss,win32,coreaudio,none.
# config -- Special configuration options for the device. In Windows put
# the id of the device you want to use. See README for details.

mpu401=intelligent
device=default
config=

[sblaster]
# sbtype -- Type of sblaster to emulate:none,sb1,sb2,sbpro1,sbpro2,sb16.
# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.
# mixer -- Allow the soundblaster mixer to modify the dosbox mixer.
# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.
# On auto the mode is determined by sblaster type.
# All OPL modes are 'Adlib', except for CMS.
# oplrate -- Sample rate of OPL music emulation.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=22050

[gus]
# gus -- Enable the Gravis Ultrasound emulation.
# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the
# Gravis Ultrasound. (Same IRQ's and DMA's are OK.)
# gusrate -- Sample rate of Ultrasound emulation.
# ultradir -- Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=false
gusrate=22050
gusbase=240
irq1=5
irq2=5
dma1=3
dma2=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker -- Enable PC-Speaker emulation.
# pcrate -- Sample rate of the PC-Speaker sound generation.
# tandy -- Enable Tandy Sound System emulation (off,on,auto).
# For auto Tandysound emulation is present only if machine is set to tandy.
# tandyrate -- Sample rate of the Tandy 3-Voice generation.
# disney -- Enable Disney Sound Source emulation.

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true

[bios]
# joysticktype -- Type of joystick to emulate: none, 2axis, 4axis,
# fcs (Thrustmaster) ,ch (CH Flightstick).
# none disables joystick emulation.
# 2axis is the default and supports two joysticks.

joysticktype=none

[serial]
# serial1-4 -- set type of device connected to com port.
# Can be disabled, dummy, modem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameters for all types are irq, startbps, bytesize,
# stopbits, parity (all optional).
# for directserial: realport (required).
# for modem: listenport (optional).
# Example: serial1=modem listenport:5000

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms -- Enable XMS support.
# ems -- Enable EMS support.
# umb -- Enable UMB support (false,true,max).

xms=true
ems=true
umb=true

[ipx]
# ipx -- Enable ipx over UDP/IP emulation.

ipx=true

[autoexec]
# Lines in this section will be run at startup.

mount c c:\PROGRA~1\MICROP~1\Orion2
c:

ipxnet startserver

#ipx connect 69.144.1.21
#ipx connect 192.168.1.104
#ipx connect

orion2~1 /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport

#Several MOO2 Mods
#oriondr2 /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport
#oriondr3 /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport
#orange /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport
#oriondc /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport
#oriondd /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport
#goodmap2 /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport
#goodMap3 /skipintro /minstart /planets=4 /nosplint /nowh /nobh /noorion /noreport

Smatthew
Posts:6
Joined:Tue Oct 16, 2007 2:39 pm

Lan game failure

Postby Smatthew » Thu Nov 06, 2008 10:06 pm

also im not sure if i ever set up the netbios thing or the autoexec.nt thing... i run windows xp... maybe this is the problem. if thats a possibility does anyone know where the guide to that particular issue resides?


Return to “Support”

Who is online

Users browsing this forum: No registered users and 93 guests