Multimonitor not working

[Splurgle]

Hi,

I'm trying to use multimonitor and it's not working. I'm following the instructions from the FAQ and previous postings on this message board, e.g.:

1) Start Uplink on both machines which are networked together, know each other by name and have no firewalling between them

2) On main machine (w2k) start server. At which point I see a Uplink.exe open port 31337 and listen for connections.

3) On 2nd machine (xp) go into the network settings, and all I see is localhost. The main machine is not listed.

Use an IP packet sniffer I can see that not a single packet passes between the two machines.

Is there anything I can do to get Uplink to tell me what the problem is? How is the 2nd machine meant to discover the main one? By a broadcast packet?

Any help gratefully received.
Sp.

[Iris]

without loading uplink, try sharing files between the 2 units. if this doesn't work, there must be something wrong with your lan connection. check your network settings and see if they're configured correctly. some ofthe guys in these forums will surely jump in, wait for their suggestions.

[Splurgle]

Thanks for your suggestions Iris.
File sharing works fine.
Ping on both machines works fine.

It seems as though Uplink client just isn't trying to broadcast out to find servers. Perhaps there's a way of telling the client the IP address of the server?

Another thing I've noticed that is wrong with the Uplink server side is that multiple listener sockets are created if you "start a server" and then "stop server" and then "start a server" again. Minor issue but shows that the code isn't tidying up after itself.

[Stewsburntmonkey]

The multimonitor deal is a bit of a kludge.  It was not meant as a serious feature really, just something for fun.  You might try switching the client and server, you can also try fooling with the server name.  :)

[Splurgle]

It's the same deal both ways round. Are you suggesting I change the name of my machines - or is there something within Uplink I can do? I'm not going to change the name of the two machines, they are established machines and the networking between the pair of them works just fine.

[Stewsburntmonkey]

No when you set up a server (in game) and connect to a server you can enter the name manually.  I had to fiddle with that before I could get it working.  :)

[Splurgle]

Thank you Stewsburntmonkey that was it. I'd missed the fact that I could edit the line that said localhost on the client side. Doh.

So it started to work. Populating the stats and I could see half of the windows filled in before the uplink client crashed. I guess that's what I should have expected from what I've been reading. Tried a couple of times and it happens each time. It seems to be something to do with the hugely powerful machine I own in Uplink - check the error in debug.log below

NEW GAME     18:14, 3/5/2003
===============================================
Version : 1.31
RELEASE
Win32 Build
Version 1.31 (RELEASE)
Compiled on Sep  9 2002 at 16:53:38
(code-C)(code-M)(code-T)
Loading uplink options from C:\Program Files\Uplink\users/options...success

Successfully loaded data archive data.dat
Successfully loaded data archive graphics.dat
Successfully loaded data archive loading.dat
Successfully loaded data archive sounds.dat
Successfully loaded data archive music.dat
Successfully loaded data archive fonts.dat
Successfully loaded data archive patch.dat
Client type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not setClient type not set
An Uplink Assertion Failure has occured
=======================================
Condition : strlen(newhw) < sizeof(hardware)
Location  : C:\Development\Uplink\source\Network\interfaces\clientstatusinterface.cpp, line 175
============== B E G I N  C O R E  D U M P =================
retAddress = 004CCCD3
retAddress = 646F4D0A
============== E N D  C O R E  D U M P =====================

[Stewsburntmonkey]

Yea, big gateways become unstable fairly easily.  :)

[Iris]

you got that right. by the time i was able to rig my Nano gateway with its 31st processor, the whole game collapsed!