Bargeld

You can always sort the process list by name... that way it won't jump around when trying to kill it.

Just another iteratation to show that update windows sucks. Fresh installs are always more stable than updates on top of an existing OS.

Doh, I should play more, nowadays 8(

McAfee is probably the culprit. Disable it as a test to see if it fixes it. For the Router, I suggest holding the reset button for 10 secs to reset it to default settings, then start over with your setup from scratch.

That should be for enemies only, your ping will always show.

Re-install windows (always a last resort, but haven't had anyone come back to say it didn't work).

In-game, hit ESC, so the menu is open. Hit F3 to cycle through the 3 options: Show all nametags Show Other Nametags (not yours) Show No Nametags (if you read the menu when opened with ESC, it tells you to use F3)

Refer to this post... same problem (and it is current): http://www.ssforum.net/index.php?showtopic=10650

here are my directory servers: sscentral.sscuservers.net sscentral.subspacehq.com sscentral.subspace.net sscentral.subspacedownloads.com

Re-install/install the latest DirectX and drivers for your hardware. Go to http://windowsupdate.microsoft.com and get all critical, optional and hardware updates.

check the FAQ: http://www.ssforum.net/index.php?showtopic=10499 If you cannot solve it with those suggestions, post here again.

Might sound silly and too easy, but control-alt-delete and see if you can kill the proccess (it probably won't be in the running programs list.)

You wouldn't get a response from server saying 'wrong password' if it couldn't connect to the zone. It would just time out. Go with SOS's suggestion... that was my first thought.

Closed.

You need to make a new shortcut to the new Continuum039pr1.exe. The shortcut you are trying is pointing to the old Continuum.exe, which is throwing the error.

Your playername (not the profile name) cannot start with special characters, such as ()#$% etc. Make sure your player name starts with a letter or number.

I'm banking on the user account. Usually the "Unable to create file..." means that the zones directory is not writable, due to permissions (the user account hasn't been given access to copy/create files in program files.)

nope, i've seen worse... even worse than that AND negative ploss. The explanation I've been given is that the client will push the same packets (not all packets, but certain required ones, like position) multiple times if they are lost. Not only are you dropping the first packet, but the second and possibly 3rd (I'm not sure how many times it will try to push the packet until it gives up on it). 100% ploss = you drop all your packets on their first trip. 200% ploss = you drop the redundant (2nd) packets as well.

SSCX Servers are gone.

Oh yes, the Alien Autopsy disk. If you lose it (like the owners of the laptops I've worked on) you are basically screwed. They (alienware support) told me that they can't make a copy of the disk because it is custom for each machine, made at the time they put it together. If you lose it, they can't replace it.

It's probably a permissions thing... I've worked with a number of alienware laptops, and I've learn a crapload about Alienware: 1) Their tech support is useless. 2) Standard Drivers usually suck; in many cases, they won't even work. 3) They install additional user accounts when deploying a unit (a common practice for most manufacturers). Sometimes you get the 'new guy' on the production line, and they screw up; hence permission problems. A re-install will work (get used to it, cuz you may need to do it a lot because it's an Alenware). Before you re-install, make sure you have both a CD of the OEM drivers (or most recent versions) as well as an external floppy drive, or a USB device that can be accessed by the bios (you may need custom alienware raid drivers when you reinstall windows, if you need them and don't have them available, then windows will not recognize any drives to use for installation.)

In the advanced options of continuum, toggle the option for 'show default resolutions'. You may want to check out the specs of the monitor (on the box or in the manual) to see if it supports 1280x1024.

I had it laying around

Here is a txt version of the original guide for subspace (circa 1997): http://alpha.bargeld.us/storage/Guide311.txt

http://alpha.bargeld.us/storage/tutorial.gif http://alpha.bargeld.us/storage/Icons.bmp