TCH-Tim

I can see the site fine. Ping, tracert, http.

If you have an FTP program like FileZilla, you can highlight a bunch of files, right-click, and choose Properties just like you would in Windows Explorer.

This is an important note that should probably be added to the install instructions. Your firewall/security/spyware programs might take issue with you running a web server on your machine and they should be configured accordingly. If your firewall doesn't take issue with it, you should probably get something else.

Awesome.

Which part of that is the error message? Just "Busy"? Did you install Apache as a service? If you did, you could try stopping/starting the service with the Windows service manager. Does xampp start up with Windows? If so, try disabling that and starting it up yourself after Windows loads.

You could go into cPanel --> MySQL Databases --> phpMyAdmin (at the bottom). In phpMyAdmin select the database you want to work with. Click the 'SQL' button (top menu bar) and you will be brought to a page where you can copy/paste the commands or upload the .sql file.

If you have a Standard or Deluxe plan, custom nameservers are included. Which is nice to make it look like you are hosting sites on your own servers instead of TCH's. Other than that, as far as I know, disk space and bandwidth.

I've got 72. Suppose I could spare a few degrees for those less fortunate.

technically you can put an include anywhere you want, just make sure your paths are correct.

I guess I should say "shouldn't" be applicable at work, with quotes and a rolling eyes smiley guy. My first job as a network admin flunky was at a credit union where every now and then I'd come across a user that had to use some program and it required local admin privelages. Like you said, interesting trouble calls. (On yet another unrelated note, when I first got there I found that the local admin password on every workstation was empty. At a bank. Ah the memories.) Anyway, the article makes the case that software developers especially should be in the habit of working as Users so they become aware of the security issues their software creates and help avoid the admin-rights-necessary workarounds we've all had to deal with.

Yes, when your inc folder is a subfolder of site1, etc. Did you try the /inc/header.php with the common inc folder? I'm confused as to why that won't work for you.

I use Pest Patrol and it works well. On a related note, I found this article last week discussing why we should all be logged in as Users, not Admins or Power Users. If we don't have access to mess up our systems, then most spyware won't either. Started doing it myself last week on my laptop. Takes some getting used to, but it seems to work. Instead of relying on some application to clean up after the fact, change your habits to try to prevent the junk in the first place. Shouldn't be applicable at work, as everyone should be a User, but home users might want to give it a try.

You could set up a forwarder to send that email address to :fail:. That sends a bounce message back to the sender though, and you're still processing the mail, so that might not be the best option.

Everything is relative to htdocs, which is /. If you have two sites, let's call them site1, site2, etc. They each live in their own folder: /site1/, /site2/, etc. Each site has an index.php: /site1/index.php, /site2/index.php, etc. Each index.php references the same include file, let's call it header.php, which lives in the includes folder /inc/. You should be able to write the include in each index.php as: ><?php include("/inc/header.php"); ?> This tells it to start at htdocs, or /, and work it's way up. If each site was to have it's own include folder, such as: /site1/inc/, /site2/inc/, etc., then you could write the include as: ><?php include("inc/header.php"); ?> This tells it to start in the folder that index.php is in (/site1/, /site2/, etc.) and work up from there. You could also do: ><?php include("/site1/inc/header.php"); ?> which tells it to start in htdocs, or /, and work its way up from there. Maybe you should post the include line that is giving you problems, and we can compare that with your directory structure.

Your index.php file is looking in /inc/, should it maybe be looking in /php/inc?

So then it works? Keep in mind that firewall/security stuff may restrict loopback connections.

I happened to format my laptop the other day and I am in the process of reinstalling everything. I figured I'd write down the steps I took to install Xampp (not Xampp Lite) on WinXP SP2. Follow this step-by-step and it should work. If it would be useful to have screenshots of each step, I'm more than happy to do so. Go: 1. Download the Xampp 1.5.1 for Windows installer (the 29MB exe, not the zip file) here. 2. Double click xampp-win32-1.5.1-installer.exe to start the installation process. 3. Choose English as my language. 4. Choose D:\ as my installation location (you can put it anywhere, including a USB drive or Program Files if you prefer). It will create a xampp folder in your specified location. 5. Watch it do it's thing. 6. Click Finish. 7. It asks if I would like to install Apache, MySQL, or FileZilla Server as services. I decline. 8. Congratulations, the install was successful. Start Xampp Control Panel Now? I say sure. 9. In the Xamp control panel, click the Start button next to Apache to start the Apache web server, and it starts. The control panel is also where you go to start MySQL, FileZilla Server, or Mercury. It is accessible from your Start Menu ((Start --> Programs --> apachefriends --> xampp --> control xampp server panel). 10. Open up my favorite web browser and go to http://localhost (or http://127.0.0.1). I am redirected to http://localhost/xampp/splash.php, which is a listing of languages. I click on English and am sent to /xampp/index.php, which has all kinds of info about my installation. From now on, http://127.0.0.1 redirects to /xampp/index.php. I like to leave this in place as it's a handy place to look at server status info, get to phpMyAdmin, read the instructions for switching from PHP 5 to 4, and other junk. 11. Copy my websites into the htdocs folder. For me, D:\xampp\htdocs\site1 and D:\xampp\htdocs\site2. In the Start Menu program group that is created during the installation there is a shortcut to the htdocs folder, just in case you can't find it. 12. I can now access my sites individually by navigating to http://127.0.0.1/site1 and http://127.0.0.1/site2. I can see images and CSS, and PHP includes work just fine. Just have to make sure relative paths are correct. Remember that your site is in a folder, not the root directory. If you only want to work on one site, remove the redirect to /xampp/index.php and dump your files directly into the htdocs folder. 13. When I'm done working, I click on the Xampp Control Center icon in my system tray to bring up the control panel. I click Stop next to Apache to stop the server, and I click Exit to exit the control panel. (Clicking the X just minimizes it to the system tray.) That should do it.

We're all getting leg lamps? Awesome.

It shouldn't screw up your computer. Uninstall is very clean. And like Don said, you could even run it off a USB drive if you wanted to.

Haven't used the apache2triad setup, but that's what it looks like. That's what I use xampp for anyway.

And if you didn't have directory indexing off or you didn't remove the install scripts, you might be in trouble. They're just fishing. Be vigilant, but don't lose too much sleep over it.

You might want to check out Xampp. It's got Apache, PHP, mySQL, etc. so you can test everything on your PC before you upload. And you won't have to mess with your include paths.

If you go to the Scripts Library in cPanel you will find phpBB there.

Unless you're in Europe, in which case you will have 01:02:03 04/05/06 on May 4th.

dressing