Several months ago the naming scheme of several files that LFS uses was altered. It's likely that the files you have downloaded do not conform to this naming scheme.
Sorry, but you're not being very clear with what you're trying to achieve. You appear to want to run an online server, but you're also implying that you can't play online normally. Can you clarify? If you're running a very old version of LFS you will need to update for various reasons.
mickyc30 the image is pointing at the attachment in the lfs forum. If the attachment is removed the image will not show.
It's also considered very bad manners to include/link to images not hosted on your own webpage (this is known as hot linking). The reason for this is that if your site gets hit by a lot of traffic it will also affect the site the image is hosted at.
Also the original hoster could replace the image with something rude
It's in the works (apologies for my tardy-ness), I'm shuffling work and personal commitments a lot at the moment, hence it not being done. I have every intention of doing so, however (just bear with me, if you can )
At the end of the day it's not just what you drive, what you do for a living (which does affect it), or the risk of what you may hit, but also the risk of the vehicle sketching out and causing an accident in itself.
Insurance is nuts at the end of the day, but it's a necessary evil unfortunately
I'll give you that on first glance Vi(m) is complicated to use. I won't deny it, however once you get used to it the handy things you can do all from the keyboard outweigh the simplicity of alternatives like nano, pico, etc. I spend a lot of my time remotely connected to servers, both Windows and unix-like, both with very fast connections and very slow connections. Apps like Vi(m) just work perfectly regardless at the end of the day, hence why I had put time into it.
The sad thing I occasionally find myself trying to save things by using the various shortcuts, in other programs
I'm with you on Emacs though. Whilst similiarly complicated as Vi(m) I don't see any benefit for the massive number of plugins to it. It strikes me much like eclipse - just too much.
I shall check it out
Now it's funny you say that. Many years ago I used to use very early versions of PHPed and swore by it. Fantastic little application in it's day, but the whole integrate IDE thing started getting on my tits.. Do you feel it's still worth using in this day?
Furthest down I can ask anyone about would be about mid-Devon, I'm afraid Fordie If it's of any use I can poke them and see what they say, but I fear that may not be far enough into pirate territory...
I will point out that a lot of the social networking gumpft has already been disabled As for the bookmarks and tags.. meh I think other things were being concentrated on at the time.
C (and C++, which is just an extension to C at the end of the day) isn't memory managed (as such - I'm not going to get into the complicated argument of user malloc'ed memory, and stuff that the compiler will magically free in certain situations as its a bit complicated), which means you have a fair bit of control over how everything gets allocated, etc.
Character arrays (also known as NULL terminated strings - this is why you tend to write to length of string - 1, so that you can terminate the string with a \0 - InSim isn't fussy in most cases, however it's still good practise tbh) are pretty much your basic string. It's effectively an area of contiguous memory which you write to. In this case it's 64 bytes all sat next to each other. What strncpy and it's cousin memcpy do is take one string (or item of memory) and copy it verbatim into your destination area of memory (in this case a 64 byte area of memory, which is your character array).
Since your dealing with memory you don't need to assign the return value to your Msg variable, as you've just written the location to which it is actually stored in.
strncpy returns pointer to the location of the memory of which it's written to. So (if you're still following), when you assign the output of strncpy to your Msg variable you're trying to assign a pointer to a character array, and that pointer is pointing to the location you've just written to. So ineffect you're trying to overwrite the memory you're pointing to by telling something that you're pointing to that memory (I've tried really hard to make that easy to understand, but I may have lost some people here, I fear). This is daft for obvious reasons, although perfectly "valid" if the datatypes all matched up (which they don't in this case). In the compiler's eyes this is invalid because a pointer to a character array and a character array are fundamentally 2 different data types. It doesn't care too much that you're doing something potentially a little silly
Now that may be a little confusing, but I think that's about as clear as I can make it without turning into a whole tutorial on C and memory Hopefully it's relatively understandable?
Edit: If not gimme a buzz via pm and we'll figure out a way of getting in touch if you like. I can't spare a lot of time in the evenings, but we can figure something out...
A char * is a pointer to the location of a character array in the memory (think of it as an address). Depending on how pedantic your compiler is setup to be, will depend on whether or not it'll allow you to do the code that was given as an example originally.
EDIT: Whoa, I've just noticed what you're doing in the code above (I need to start reading more carefully today).
Dont' assign the output of strncpy to your message. What you want to be doing is something like this;
You're more in the realm of C, rather than what may normally be considered the ++ parts of C++
You'll notice I use strncpy, rather than strcpy. The reason for this is that if you try and copy something too large for the character array, you'll end up out of bounds. strncpy allows you to state the max length to copy into the memory destination (your Msg, in this instance). If someone can push too far you can end up with usable exploits, etc. It's a bit out of the realm of discussion, but basically treat everything with care at this sort of level. There is no "real" bounds checking when you're this far in the dirty stuff
Edit 2: I think you might need to a quick read over of what pointers and references are dougie..
Unless something has changed since I last looked at InSim, you should always get multiple MCI packets if there are more than 8 players (it would be stupid if you didn't). You never need to request any MCI packets, if you've enabled then, and even then if you did you get the same behaviour.
Edit: Sorry, I've re-read the post by Stigpt, he doesn't make it very clear that he was explaining things again. I've ammended this post as appropriate.
I didn't say it wasn't a good idea. I was trying to point something out if you weren't aware of this simple fact, as you failed to say if you were or not.
Look dude, I wasn't rude, I didn't say your idea was shit. I was offering friendly advice incase you weren't aware of something. If you think you're being hard done by I can change my tune so that you really are.
If you want to go and have a strop like a 4 year old, then please feel free. It's no skin off my nose. I just don't understand what the problem is.