ghostrider

It's been a while since I've posted here. Since I've been gone I've been doing a lot of Operating System related programming. All the people above me are mostly correctly. Firstly, be sure to check your drivers. I believe they have to be 64-bit no matter what when running Windows Vista 64-bit edition, however I am not totally sure on that. Secondly, just because you're processor is 64-bit doesn't mean its "pushing twice as much data through". The 64-bit refers to the amount of memory that can be accessed, and also how high your processor can "count". It also does a few other things programming wise, which are beyond the scope of this. You can message me if you want to learn more. Intel 64-bit technology can actually only allocate 2^40 (1 terabyte) bytes due to keeping production costs low. The next step up will allow for 2^56 bytes, and then finally 2^64 (16 exabytes). Applications that are 32-bit will also run slightly slower because of the way the processor handles 32-bit code when working in 64-bit mode. There is no performance increase for 64-bit applications. Windows Vista 64-bit is the only version of Windows that can run any type of 64-bit code, EVEN if you processor supports it. Hopefully this gave you an insight into how this works

Hello All, I've been doing a lot of PHP programming since I last posted here. I've run across two security related things with sessions that you may or may not know about. The first one pertains to the session id, or the id that PHP assigns each computer when a session is created. This id is either stored in a cookie (search for PHPSESSID) or through the URL as GET data. Remember that all session data is stored server side; this ID is the only thing that PHP will use to differentiate your computer from someone else's. While I was programming for Plug Computers, I decided to experiment with logging into the Admin CP I built, copying the session ID from my computer, and putting it as a cookie on the other computer. Sure enough, both computers were recognized as logged into the admin CP. This poses a very serious threat to anyone that knows what they are doing with sessions. However, there is a system that I use to eliminate this from occurring. PHP has a bunch of functions for working with sessions. I utilize the "session_regenerate_id", which will change the session ID every time it is invoked. This way, if someone is able to capture someone's session ID, the next time that function is invoked, the ID will be useless. <?session_start(); // Start the session.session_regenerate_id(); // Give the session a new id.?> I recommend doing that every time your user loads a new page. The second discovery I've made pertains to using local variables and session variables. When I write PHP for people I use PHP version 5.2.2. I believe newer versions have addressed and fixed this issue. But just in case, I'll share what I've found anyway. Firstly, let me tell you what I mean by a local variable. Look at the code below: function some_function($var) {$newvar = $var;++$newvar; // This is not a local variable.return $newvar;}$othervar = 7; // This is a local variable Variables within functions are not considered local variables because when a user-defined function is invoked, PHP will create the variables within that function, and then destroy them once the function has been completed. Other variables outside of functions are considered "local variables", with the exception of superglobals ($_POST, $_GET, $_COOKIE, $_SERVER). I am currently writing some PHP for a tenis coach in Indiana who wants a way to allow his students to keep track of work out routines, keep a blog, keep notes on opponents and other things like that. When working with the Admin CP and creating a "add user" form for the site, I noticed that the key 'username' in the session superglobal would change each time I ran the script. Here is the code in question: $username = $_POST['username']; The value in $_SESSION['username'] was changed to $username. It's a bug that also caused me some difficulty with Plug Computers. I had to change all of my $id's to $id1's to avoid it. Hope this helps someone out.

Its looks like a good monitor to me. For its size however, a maximum of 1440 x 900 is slightly small, but still a decent resolution I think.You might want to make sure from someone else, I am a computer programmer, not a computer designer :XD:.

I worked a couple years ago with the Hayes modem commands, or AT modem commands as some people call them. Check out this reference: https://support.microsoft.com/en-us/kb/164660.

I see what you mean now. Your format for your tables is just fine .Keep in touch, I'd like to hear about how your project is coming along.

Hello Custergrant, Firstly, let me say that you will have no regret switching to Xisto. They are excellent. My name is Chris Feilbach (http://forums.xisto.com/no_longer_exists/) and I am a computer programmer. I have 11 years experience programming (started in 1st grade), and 4 years experience working with PHP and MySQL. Below are my suggestions for your database. Before I give you my opinion, please make sure that all of the tables in your database are right: TABLE Resource (Contains data about what resources are available in your game) ID - Primary Key Name - Name of resource Market Buy Price - Price resource is sold for at market. Market Sell Price - Price resource is bought for at market. TABLE Buildings (Contains data about available buildings in your game) ID - Primary Key Building - Name of building TABLE Cost (Contains data about resources that your buildings use or make) ID - Primary key Cost_type (either cost, input, or output) Resource_Type (Refers to ID in TABLE Resource) Resource_Amount (Amount of resource needed) TABLE Users (stores your user's login and contact information) ID - Primary Key Username - Username of user Password - Password of user Email - Email of user Userlevel - Level user has attained in your game TABLE User_Buildings ID - Primary Key User_ID - (Refers to user ID in TABLE users) Building_ID - (Refers to ID in TABLE buildings) Amount - Number of buildings user owns TABLE User_Resources ID - Primary Key User_ID - (Refers to user ID in TABLE users) Resource_ID - (Refers to ID in TABLE resources). Amount - Number of this resource that the user owns Granted that this information is correct, here are my recommendations. 1. As a general rule of thumb when using MySQL, stay uniform. If you have a table for users and resources and buildings, make sure that their names are either singular (user, resource, building) or plural (users, resources, buildings). TRUST ME, it gets very complicated once you start working with around 10+ tables and some of them end in s, and others do not. I leave all of my table name singular. 2. Make sure also that all of your field names are lowercase (saves your time). You want this to be as easy as possible for yourself to code. 3. Make sure that all of your id fields have auto_increment set (once again, saves time). 4. After reviewing your code, you absolutely NEED to combine the tables Buildings and Cost. If you happen to delete one row from buildings, things will go horribly wrong. 5. Keeping User_Buildings is great, but it offers one major limitation. Let's say someday you grant your user's the opportunity to improve upon their buildings, or even if you want to be able to customize individual buildings, or anything that involves modifying one building. Your current design does not allow for that. Below is a design of how you can address this. TABLE user_building id - Primary key building_id - id of building user_id - id of user who owns the building (any other custom fields may be added) In order to keep a count of the buildings you can use the following code: $query = mysql_query("select count('id) from user_building where user_id='__USER_ID_HERE__' and building_id='__BUILDING_ID_HERE__'");$result = mysql_fetch_array($query, MYSQL_NUM);print $result[0]; // Prints number of buildings. I really hope this helps you. All of my contact information is located in my Profile on this forum.

This reminds me of the time when my family first got our inground pool. It was still being built, and there was a screw at the bottom. My dad told me to go get it, so i got in my swim suit. I believe the water was around 40 or 50 degrees, it was VERY COLD. Its not too bad if you work your way into it very slowly like I did. However this woman accomplished something truly amazing. Go her!

I actually worked with this concept just a couple days ago working for one of my clients. If you have experience with PHP i'll be glad to explain to you how I did.

Domain names are obviously the best that you can have, as long as they aren't to long to remember.I voted for subdomain, but you should only use it if you if thats short, otherwise the address gets to long to remember. You can always use a folder too, and change it later.

Create a PHP script that puts them in a file on your server, and then use your software to read the file. Try that, it should give good results.

After thinking about it, the games that use full screen are most likely going to be using DirectX, since it offers faster access to things like video and audio, and contains a lot of code that makes working with images and sound a lot easier. I don't think that there is an application that can get rid of the way DirectX functions, and even if there was, you would be modifying the core code of DirectX, which could lead to unexpected results. I don't think there is much you can do about this one.

Happy Birthday Xisto

I would use this site. It would be good to keep track of what I've done and be able to look back on it. Let's develop it. I have tons of experience with PHP and mySQL and programming in general.

I believe that the majority of Linux kernels can run in text mode with only 32 megabytes of RAM. My advice to you, create a swap partition and make it huge, like 2 or 3 gigabytes. Virtual memory is over 1000 times slower than RAM, but at least this should work. You can also by more RAM if you need it. Even only doubling your RAM will make a huge difference.