Re: New Server Set Up guide.
i would greatly appreciate something like this and think its a wonderful idea, you've got my support bob! <3
Re: New Server Set Up guide.
Well that's two.
But I still have no responses from those who provide support here as to which file set, and especially server executable, they would rather provide support for.
Nor any indication as to how far into set up such a guide should go.
I think my preference would be to get a server working for LAN without user registration, clans and SoD... then others could build Clan and SoD and Registration guides referring to mine as a base.
Re: New Server Set Up guide.
that will be hard to get together b4 a month for example, the best things is to make a whole tuto (complete) from the start to the end with sod, clans and web working in a comprehensive order and the right files sets (im tired of trying to explain not every file work with the others) so better have a complete set of fully working files.
Re: New Server Set Up guide.
That is a fair point.
I was actually thinking of maintainability. Because as separate sections, the Student (person reading the tutorial) can pick and choose the parts they want to use for their server, and segmented, you can replace sections with newer versions to take advantage of newer ways of working.
It could also limit query threads to queries about a specific section of the process. Which keeps the forum cleaner and information easier to find.
If the tutorial is split into discreet sections, as individual threads building one upon another... provided you don't jump into the tutorial part way through there should be no problems. Of course, aside from posting disclaimers there isn't any way we (as a community) can enforce new members to work that way.
Re: New Server Set Up guide.
Its a damn good idea in my eyes.
Most of the files are old now and they arent clear all the time.
Go ahead!
Unzubaru!
Re: New Server Set Up guide.
I've actually started getting this together on a Wiki. As SoyEdu says it will take some time to get together and get right, so I figured some way of making it before posting would be really good, and I can set up a free Wiki without too much difficulty.
It's not really for public consumption, but it's an effective way to collect and document my thoughts on the process. It's also open enough for me to be able to link others to it who may have input they'd like to offer, and has a means of logging who suggested what for accreditation purposes.
So if you have a little free time and are interested, please PM me, and I'll send you a link and password. Please don't spread it too wide however, because I really don't want to detract from the core community here at RZ.
Re: New Server Set Up guide.
Maybe once unzubaru and his mates finish the release of the server files, which would be awesome, somehow if you had the time to make a guide, use his files as a base? I think because they are new files and many things are resolved from previous files that it would be an ok idea. But it is entirely up to you bob.
Re: New Server Set Up guide.
Yes... I'm happy to use Unzubarus' files, if people are happy that they are stable enough for beginners.
After all, one tends to find that the more features a server set has, the less stable it runs.
At the moment, a few people have reported issues connecting to Unzus server, but that's kind of expected for a beta release... what would be more helpful to him (I'm sure) is reports of what people did that does work... again, I'm going to try this.
Re: New Server Set Up guide.
well possibly if he is going to release a final you could use that? I suppose it won't hurt to wait a few months for a new guide unless you desperately are wanting to right it now. You could always update the files in your guide aswell I suppose. Up to you, but it sounds like a great idea.
Re: New Server Set Up guide.
well atm its just me XD. Others have buggered off with.... a Life? Yeh well i have a side project working with Ille but thats it. I'm getting stuck on the cap and in the next release i will make it BloodPT not Quantums. Man i dunno whats wrong with people's client and things it has to be with them cause i explained the hotUK.ini and everything O_O.
Meh lemme look over it.
Thanks,
Unzubaru!
Re: New Server Set Up guide.
Okay... well the guide is up to ODBC. When I get to file set, I will try to work it from your beta, that way I can maybe help you with your files as well.
I think peoples problems with you edit of the quantum client is their system security not your client... because (if we are thinking of the same person) he suggested that the alternate client he could connect with was a pure qf 1873 client he modified. And I really don't think you've changed anything that should stop it connecting.
Re: New Server Set Up guide.
haha no i havent. Just a couple of backdoors for you so i can DDoS some n00bs via your PC when we meet on IRC >:-D XD. <--- Hope you got the joke there.
Well i think the BloodPT client should stop it anyway cause it requires no IP. Its interesting cause it worked for the people who tried it.
Also guys, has anyone got this working? I mean i've heard problems but no feedback about if they work? Just gimme a heads up so i can fix stuff.
Thanks,
Unzubaru!
Re: New Server Set Up guide.
You know I've trawled your files for common errors.
And yah, I get the joke. I've seen far more nasties on MSN than IRC TBH, and I think I know what I'm doing well enough to keep your Trojans and skript kiddy antics off my PC. :wink:
Actually, the IP was put into the client to make things easier... I believe. Even Quantums' client doesn't need to be hexed if you set it to 127.0.0.1 because that is only server1, you can still add server2 and server3 to your registry, or ptreg.rgx and connect via them... it's not a big problem.
What is a big problem, is if XP firewalls this "UnZiped" not "Installed" executable that is trying to access the internet, and your PT client blocks window changes during execution... which will happen if people have XTrap or NProtect in their client install folder, or just run full screen.
Let alone Vista users running it from "C:\Program Files" or "C:\Program Files (x86)" without elevating their token, so that all it's configurations (and their hex editing) is virtualised off into a separate instance in their profile never to be actually used.
For my money, even the official clients need some considerable work put into making them comply with modern Microsoft security restrictions, or running on XP, Vista and Win7 is always going to be problematic.
The official installs work with XP... mostly, just be careful with the System Restore feature. But that's only because the install and patch program registers a firewall exception. They work with Vista, but you have to fight UAC to run the game, or install to a custom location. (as Suba do by default) They would never pass the XP logo program... they wouldn't even get a waiver on some of the requirements that many XP logo software got that couldn't get away with it for Vista.
I've been signed up to the logo programs for many years... though I never submit anything for testing.
I was used to following the Amiga Style Guide like a bible, because the slightest deviation would mean you get no support if future OS patches break your program. You follow the rules or put up with your users complaints that your program sux and doesn't work on their computer. I think that's fair...
I think if you don't make your software follow the rules and regulations of development for your target platform, you should not be surprised when your hacks don't work on someone elses machine, and I think it's fair that badly written programs don't work right on Vista, and we, as users, should blame the software developers and not Microsoft, because anything (software wise) that complied fully with the Windows XP logo program will work on Vista just fine. Anything that got a waiver, has had MS ACT compatibility patches built into Vista.
So if it doesn't work, it was badly written to begin with... I have had absolutely nothing that I rely on fail to work flawlessly on Vista x64 since I switched shortly after the release... because I refuse to use anything that didn't comply with the logo program documentation I received back on XP... or I patched my copy back then to make it more compliant.
If we had the full source code of the client, I could fix (at least most of) it's compatibility issues in a day.
1) Don't store information in "C:\Program Files" or "C:\Windows" that you are going to modify after the initial setup. (This causes Virtual Storage to kick in as an automatic compatibility protection in Vista, but was bad practice on XP.)
2) Don't store information in the system registry under HKey Local Machine which you want to use after the user logs on... this is for drivers and software that runs under the SYSTEM account credentials only. (This also virtualises calls in Vista, but even Read access to what the setup.exe wrote will be blocked. It was bad coding practice on ME/2K, and was only green for global, across all users, settings for 95/NT4)
3) Include a correct XML manifest in your resource section which declares the resources and access rights the program needs. (This causes UAC warnings as well as warnings that "The program is from an unknown source." even in XP, and can stop XP applications getting internet access.)
4) Ensure no executable section is writeable, do not use self modifying code, and do not execute late allocated memory. (This causes conflicts with any 2003 / 2008 system which has DEP active, this is also a common security and stability strengthening method on XP SP2+ performed by system security and lock down tools and... me! This has been a style guide requirement from iNTEL since the 486... and they introduced the hardware DEP in the P4 chips to allow the OS to flag an exception on it. Originally it caused L1 and L2 caching faults which could crash the whole machine, later it has been used in Root Kits, SpyWare and DDoS to bring whole servers down.)
These guidelines where released circa 2002 for the Whistler RCs. They aren't hard to comply with, and are there for very good reasons.
Most "players" aren't even aware that there are so many issues with this program, that are only worked around by the installer. When we give someone a Zip file with a custom client in it, they expect it to just work... I know from my beta testers, that if they don't understand how to administer the securities in their own PC without a setup.exe to do it for them, it isn't that simple at all.
I have spent hours trying to explain to one friend in particular how to get my game.exe to work for her. She uses many Private PT clients, but has only Beta tested for me. She knows the game inside out, and is no "Digital Dunce".
In sheer frustration (there is a language barrier as well, IDK what menu options, buttons and icons are labelled in the Flemish versions of Windows) I gave her the exact same files, with a setup.exe, and everything was fine... It's as simple as that.
Re: New Server Set Up guide.
Quote:
Originally Posted by
Kagome1
i would greatly appreciate something like this and think its a wonderful idea, you've got my support bob! <3
I'm resurrecting this thread, only to point out that I have given thanks to this post, not because it is, or is not helpful (it spurred the release of PPT and the guide to use it with other releases here.) but more because Kagome deserves thanks for her contribution to this leaked server which she has chosen not to comment on... and I don't blame her.
I advise people to study this excellent work, and to learn from it. Please do not use or "borrow" files directly from this release in your later releases, or active public servers. I would consider doing so "trafficking in stolen goods". But I cannot vouch for the morals of others.:(:
Thanks Kagome.
