I don't know why you have those user and group ids but uplink doesn't need them to run properly. I went back and extracted some of the files from the Linux tarball on the CD and they didn't end up with those IDs. I'm not sure what to make of that. I would recommend changing the user and group ids t...

Wow, that's different. As an administrator of your own system, you may want to find out how that actually works. If random groups can make directories etc... that could be insecure. It looks like UNIX/BSD/Linux has several pre-defined users and groups. The bottom of this page at Hillsborough Commun...

Out of curiosity, did you upgrade? If so did you install it as the same user as the original install? AFAIK, software should always be installed as root for security. What are the names of the groups / users corresponding to the UIDs/GIDs you listed for your system. I re-installed it from the CD I ...

lunchlady55 wrote:If the chmod command doesn't help, it may be a different problem.

Changing the permissions on loading.dat to match the other files doesn't seem to cause any problems and does appear to solve the problem.

The problem is really with the loading.dat file. loading.dat gives read and write permissions to user 990, and no permissions to group 1150 and everyone else. All the other .dat files give read and write permissions to user 990, and read only permissions to group 1150 and other users. Is there a re...

Uplink v1.54 crashes on Ubuntu v6.10 at the agent log-in screen ... =============================================== NEW GAME 14:44, 2/3/2007 =============================================== Version : 1.54 RELEASE Linux Build Version 1.54 (RELEASE) Compiled on Nov 16 2006 at 20:46:23 (code...

Hammerheart wrote:Ok after I did some basic debugging, I found the problem. The .dat files location aren't being included in the LD_LIBRARY_PATH. The easiest way to fix it is to just move them all into the lib directory where you have uplink installed.

Thanks for the help. Uplink works now.

KingAl wrote:... it's better to post them where people will actually see them ... and ... the main thread on a new patch is not the place people generally look for solutions to specific problems.

I apologize if I caused any confusion. I posted to this thread because I thought the problem might be the patch.

On Linux, if you hit a crash please report the relevant part of the ~/uplink/debug.log file, please also report the distro you are using. All testing was done on Ubuntu 6.06 I downloaded the Linux installer script, uplink-patch-1.54.sh, and ran it on v1.31 of Uplink, which I had installed in /usr/l...