BobS

Ahhh, explains your userID LOL I'm getting rusty as well, and fully appreciate your comments! Now, back to reality. If you're going to use a dedicated machine, and it's going to be Windows, then I'd still suggest not going whole hog on a Win 7 Ultimate. Only one reason is the cost of a license (I assume you'll have a legitimate copy). The other reason is that there would be many more bells and whistles added on, and for what purpose? To create more code vulnerabilities? Use the most stripped-down OS that you can get away with. Uninstall as many "features" as possible. I exhort you to look at the article that Yoni just made available concerning REAL security. You can read about it here: http://forum.uniformserver.com/index.php?s...post&p=9875 Regards, BobS

This is actually a question for Ric (who is away for the moment). I would guess that libmysql was put where it is so that it facilitated the MySQL version updates. When a MySQL update occurs, most all the changes happen only in the MySQL folder,and often are limited to just the bin subfolder at that. However, your security argument tops that reasoning, as long as we can be sure it doesn't get forgotten during an update cycle. Mismatched dlls are a real nightmare to resolve. Regards, BobS

I noticed that you had SyncToy dat files. You might want to look at TreeComp for comparing and synchronizing directories. I've stopped using SyncToy in favor of it. See http://lploeger.home.xs4all.nl/TreeComp3.htm I use it extensively for checking what Ric has fixed from version to version. Regards, BobS

OKAY! The PRIMARY problem was that the UniServer\uni_con\config_tracker.ini file was out of sync with reality. It had your .exes still marked as installed as services (which was obviously false for my system). I suppose I could have run the batch files to install them as services, and then the Start_as_service.exe would have been in sync. I also reverted your change in UniServer\uni_con\includes\core_config_inc.vbs on line 124. I don't know if this actually was a problem, but why not keep it the same as the "standard"? With just these changes, the system came up with no problem. "Cute!" Regards, BobS PS. You probably should delete your 4shared copy. And change your MySQL password to something SECURE!! What you have is no better than "root".

The reality is that that's beyond where we specialize. You will know much more about how you use the servers than we will. We then take what you tell us and attempt to figure out how to make it work. You'll always be pushing the limits, whereas we're just trying to keep it from breaking. So MAYBE you can adjust the priorities and it will help, but my experience tells me that it's more fruitfull to adjust the many different parameters in Apache, MySQL and PHP. Far too may combinations for us to validate or qualify. It's "left as an exercise for the student." Regards, BobS

As the phrase goes, "Some assembly required." BTW, Perishable Press is reputable and been around a while. It looks like you need to implement ths very carefully, since it can have seriously adverse effects, which would be hard to debug if done all at once. So, no, don't just cut and paste. Better to snip and glue small, incremental parts. Regards, BobS

Thanks for the clarification. I'll go there and correct that little nugget of nonsense. Next thing, someone will say it even runs on DOS. Regards, BobS

Yep, Wonder what other special characters don't work? We'll put it on the list for RC2. Regards, BobS

AO, Yes, but exactly for what type of access? If you use the tool in The Uniform Server to create the vhosts, it will add an entry to your HOSTS file to the route for your vhost site. Example: vhost1.mysite.org 127.0.0.1 This will be rather unhelpful if you want to use it for external access to that vhost, because it doesn't go far enough. You can follow the information in the Wiki about DtDNS, which is a dynamic DNS service. The result will be a DNS name that will convert to your (current) WAN IP, the one presented to you by your ISP. Then you'll need to set your router to forward port 80 TCP to the INTERNAL address of the machine on which your server is running (like 192.168.1.22). And you need to pin that address to the machine, so that DHCP doesn't move it around. That gets the requests to your web server. The vhosts entries also set up the target directory for your web server. You need to have at least an "index.html" file or similar, so that you have something to serve to the requests. This would be the location to put up, say, WordPress, or other app. Hope that helps, and be sure to look in the Wiki. Regards, BobS

Sorry, DrLeadro, that's NOT the solution for this problem. What you have specified is to open the entire directory to the Internet (the lines are all commented out). Also, the .htaccess files are not referred to as "firewalls," but rather Apache config files. See this location: http://httpd.apache.org/docs/2.2/configuring.html#htaccess . What you got right was the "Allow from ::1" which will pass requests from localhost IPv6 (::1). You can also add Allow from 192.168 which will open up your server to the entire intranet, i.e., your private network. Regards, BobS

The fact that you have BOTH port 80 and port 3306 tied up tells me you may have another WAMP running. If it were only port 80, then I'd suggest other choices. Use netstat -anbp tcp to find out more. Regards, BobS

I'm not sure I understand your exact intent. Let me see if I decode this right: All computers are on the same net, e.g, 192.168.20.xxx Link on machine A points to file on machine B, which in turn executes a URI (http://example.com/whatever.html) So what you're asking is how to create a link on a web page that does this? Not clear.... Regards, BobS

DrLeandro is on the right track. He did assume you're using 8-Coral and not an earlier version. You'll likely want to change the FireFox line to start Chrome instead. The same basic stuff applies to 7-Orion. Only the names have been changed ("to protect the innocent" or confuse the guilty). Look under alternative_control for the Start_server.bat, which starts both Apache and MySQL. Regards, BobS

When you made the virtual host on your home machine, it created an entry in your HOSTS file. The entry is seen before the DNS, so anytime you type in www.iris3d.tk on your machine, it returns 127.0.0.1 (localhost). This is GREAT for testing, but stinks when you want to go to the actual site. You can only have it one way or the other. To quickly fix the problem, you can edit the HOSTS file ( in Windows\System32\drivers\etc) and put a # in front of that line. Regards, BobS

Thanks Yoni! You've reminded me of why I don't normally run Web servers from my home machine! We'll have to add this type of material to the Wiki, and do a lot more research to come up with a list of "things to do and NOT do" when opening up to the Internet. Regards, BobS

Concerning the Wiki: I searched for that reference. It's NOT in the Wiki (I used a text edit search of the SQL dump!). Sorry. Might have been somewhere else I don't normally look at. Wherever you saw it, it probably should have a "NOT" stuck in front.... If you'd like to make some edits to the Wiki, however, I'd be happy to activate a login for you Regards, BobS

Yeah, there's lots more. Since you're using Coral 8, I suggest you use the Server Configuration > General > Root phpMyAdmin Change access type and General > Root www Change passwords and access These will resolve most all your access problems. FYI, there are several .htaccess files and you will want to look at these: -UniServer\Home\us_phpmyadmin This guards phpMyAdmin -UniServer\Home\us_splash This restricts the CSS for non-localhost access. Use this to see the splash page on locations other than localhost. Now, you COULD read the included docs that describe all of this. When you say it "doesn't serve php via Internet," what do you really mean? If you see a splash page, then PHP is working. Regards, BobS

I agree that a server-oriented version is a good choice. Again, though, it depends on the reason you want to run a web server on your home machine. Here are three reasons NOT to open it up to the WorldWildWeb : 1. How well do you maintain your software? Do you install updates promptly? Do you have a good antivirus program running? Is your firewall as tight as possible? 2. Who is the intended audience for your server? Anyone? How much traffic will your visitors create? Will that amount freak out your ISP? If it's over, say 200GB/month, you could have a problem. 3. What's your backup plan when someone compromises your web server and gets into your system? Can you wipe and reload, or will you have stuff that's irreplaceable on the server? How long will this take? While I have had servers open to the net from some of my home machines at various times, I'm not attempting to do "web hosting" for a production site. It sounds to me like this is your intent. Now, if you only want to have a tiny portal for friends, and you can keep it secure (don't use port 80, for example), then it really won't matter what OS you use. I might even suggest, though, that Win 7 Home Ultimate would be a reasonable choice. No reason to waste a Win 7 Pro license on this. Win XP would also work for a server that you'll upgrade in the next 2 years. Oh, and you really should dedicate the machine to being just a web server. Regards, BobS

Actually, we HAVE noticed, but it was something that changed AFTER we checked it out! PEAR worked perfectly before they changed the links. It's on the list to be fixed for the next release. I tested out the fix specified above, which will properly install PEAR using go-pear.phar. The difficulty is that it isn't applicable to the go-pear.php included in Coral 8.0.0. That package has not yet been updated (they have a bug ticket open). Regards, BobS

I think you may have "overcharged" the form. For a test, start with a clean Apache Virtual Host form. Fill in ONLY the following Document Root: C:\UniServer\vhosts\v1 Server Name: v1.xyz Press "Confirm" ALL the fields are then properly filled in, and "Create Vhost" should be available. When you create the vhost (and restart Apache), you should be able to access the new host as http://v1.xyz , but you must put some content in the new root directory. I make up a simple index.html that tells me it's being served from V1, the ID of my vhost, which is at http://v1.xyz. Since The Uniform Server puts an entry in the HOSTS file for this, it resolves to 127.0.0.1, but then Apache filters the request for "v1.xyz" to go to the proper virtual host. This DOES work. I just used it on a test version of Coral 8.0.0, and then installed a WordPress instance. Regards, BobS

See this reply: http://forum.uniformserver.com/index.php?s...post&p=9870 Regards, BobS

The short answer: No. Microsoft dropped official extended support for Win2000 in July, 2010, and so did we. Your best bet is to see if those dlls mentioned in MSDN will function for you. There may be many more issues, though.I'm not sure whether Apache, MySQL, PHP and the rest of the components work under Win2000. Please tell me that you don't have this server exposed to the Internet, because here's the real problem. Even if you get ALL the pieces needed to get The Uniform Server running (whatever version), there's always the worry about malware attacks. Remember that Microsoft is not plugging any more security holes in Win2000. My best advice in this case is to find a copy of Win Server 2008 R2 or Win Server 2003 R2 (if you can) and get that running instead. Regards, BobS

Short answer: there's no automated way to do this. Kris_fr maintains a site where you can get a differential for updating to the next revision. See this entry, and you can also check out the full thread. http://forum.uniformserver.com/index.php?s...post&p=9573 The only problem I've had using these is that they don't handle deletion of unwanted files, so the garbage will continue to grow. Secondly, even though this next thread mentions older versions, it has the best general recipe for upgrading: http://forum.uniformserver.com/index.php?s...post&p=9573 Updating the application code is far easier than updating the databases. While InnoDB may port directly, it's NOT designed to do that. Yo really should do a DB export and import to keep it all intact. It's far too easy to lose your whole database with any copy-paste method. MyISAM, on the other hand, is all self-contained, even though it's not as robust. A Wiki article covering this is on my project list. Regards, BobS

The EASIEST way is to change home.html to index.html. Apache uses a list of file names to determine what file to start with, known as Directory Index Files list. If it doesn't find one on the list, it goes to the next action, which in The Uniform Server's configuration is to display the directory. Alternatively, you can add "home.html" to the Directory Index Files list. Finally, you can create a 301 redirect in the .htaccess file that sends a request for "index.html" to "home.html". In 8-Coral's Unicontroller panel, you can easily access the Directory Index Files list through the Server Configuration > Apache > Edit Basic Configuration sequence. Regards, BobS

Right, That article is a good start (but needs to be updated), and we're in the process of developing more info along the lines of "going live". NAT (Network Address Translation) is what your little home router is doing to get you private addresses like 192.168.x.x. I would suggest you NOT tell Google about this page, since that would create far too much traffic for your home connection. Your local ISP would frown on that much traffic. That's why there are hosting services instead. The ideal way to use The Uniform Server is as an off-line test and development environment. Then the site info can be ftp'd to the live location. You can use The Uniform Server in a live test, but don't tell the world about it. Think of it like learning to drive in a protected large parking lot or quiet residential street, and not on the expressway. Regards, BobS