BobS

Normally I don't recommend the simple cut and paste, but you can give it a try. It's typically the app data that messes things up. All MySQL data is stored in \usr\local\mysql\data. Caveat: MyISAM tables will transfer properly, but InnoDB tables are all combined in the ibdata and ib_logfile. They don't transfer as well. Instead you should do an export/import of the SQL using phpMyAdmin. You'll also get a chance to scan for path strings in the data, which would make your app fail (even though the DB worked fine). Even if you're changing between MySQL versions, the copy/paste will still work, since I don't think that the structure has been modified much. Example: the application plugins made for 5.6-Nano work properly with 7-Orion versions, and they're all MyISAM-based. Regards, BobS

Not really, although you may luck out. There are many apps that put path-related info in the DB, such as WordPress. While these can often be repaired with phpMyAdmin edits, it's still not the "right" way. There are two much more portable methods. Since version 5.3-Nano there is a Database Backup function built in to The Uniform Server. Look at the Wiki page http://wiki.uniformserver.com/index.php/5....Database_Backup for details. It create a text-based SQL file. You can also use phpMyAdmin to do a DB Extract to create the same type of SQL file. Both methods have the option to compress this text file in order to save space (as I recall). Since the output is a text file, you have the option to edit the text fields of the problem records as required. This can also allow you to change from InnoDB structure to MyISAM, if need be. Regards, BobS

The Uniform Server stopped using disk W: as a default action with version 5-Nano. SlimFTPd was designed to work with 3.5-Apollo and 4-Mona. Since then, the FileZilla Server is the preferred solution. Look at http://sourceforge.net/projects/miniserver...Zilla%20Server/ and select the 1.2 version. While it needs a bit of an update, it functions well. For detailed information on setting up FileZilla Server, look at the Wiki pages starting with http://wiki.uniformserver.com/index.php/Fi...3:_Introduction. If you still want to make use of disk W:, look at your \UniServer\alternative_control directory for run_on_drive_w.txt, which tells how. Regards, BobS

Great reply! The problem and the solution are in the www\.htaccess file. Change the first few lines to be like this: #------------------------------------------------------------------------------ # Server root folder www .htaccess # This file provides server security limiting access to the localhost only. # Comment next four lines to deactivate. (Allows external access) #------------------------------------------------------------------------------ #Order Deny,Allow #Deny from all #Allow from 127.0.0.1 #Allow from ::1 See these Wiki articles (and others) for more info: http://wiki.uniformserver.com/index.php/Ba...and_redirection http://wiki.uniformserver.com/index.php/Ht...s:_Introduction One more point: See the edit to your post. Win98 is NOT secure enough to act as a server exposed to the Internet. When your site is hacked, I hope you have a recent backup Regards, BobS

@hotelf, You're doing just fine with this procedure, so long as you keep the path the same. but skip the (unneeded) \tmp stuff in step c), which is just session data. Note that this works with most apps, but there are some that store location-specific in their databases. WordPress is one of those, but it can be resolved by using phpMyAdmin to fix the entries. Specifically, there are two path entries in wp_options that should be updated: siteurl and home. Also, Jerod is right about the user info, since it's in another db. Regards, BobS

Well, it's your browser that's adding the www. to the URL. The reason it does it is that it can't find the names in DNS. Specifically, it needs to find either *.mydomain.com or newsite1.mydomain.com. The alternative to updating the DNS server is to update your Hosts file with the names and point them to 127.0.0.1. Regards, BobS

Whoa, wait! @Glenleslie, This thread is about a different environment. @ausdev indicates he's running WinXP. You seem to be referring to problems involved with running the servers as a service under Windows 7. @ausdev, Just as a clarification, The Uniform Server does not use, nor need, cygwin. ALL its operations are Windows-native.

Seems like you missed telling us a lot of the basic info we need in order to offer you any help. What version of UniServer? Have you followed the Security recommendations (aside from being on Win98, which is totally unsecure!)? Are you trying to view this from the Internet? I. e., why should the router be of importance? Can you get to Apanel? What do your error.log and access.log show? Is Win98 the server or the client OS? Do you see the UniServer splash page? Have you tried to view a simple html page? Etc., Etc. Regards, BobS

There MAY be a bug related to it being on a different drive. After all, it's trying to create a directory on C: (why?). Regards, BobS

You'll probably find this information useful: http://wiki.uniformserver.com/index.php/PH...I:_Introduction. Note that while it talks about 5-Nano, almost all of this applies to 7-Orion series as well. Also, if you look at httpd.conf around lines 562-612, you'll see the alias and script directory redirects. I believe you need to add BOTH a ScriptAlias and an Alias directive pointing to the external directory, but it MUST be on the same machine. The path should be like "D:/Otherserver/htdocs/cgi-bin/scripts". Caveat: I've never tried this, but that's the way I see it working. Try it and post back your results. Regards, BobS

FIRST question: Why doesn't it say "C:\UniServer\user\local\php"? Also, the PEAR installation path should be "C:\UniServer\home\admin\www\plugins\pear\PEAR", which is already set for The Uniform Server. Mine ran without problems on Win7-64. I started the install from the Apanel Plugin Manager (left nav panel). Also, at the top of the Go-PEAR Installer page it says: Installation in progress ... (If the page stops loading before the end of the installation, then just reload it) Assuming the paths are correct, did you follow what it says there? You could have had a timeout error. Regards, BobS

My first thought is "Why are you using that old version?" We're not really into supporting old code, and it's likely that any bugs have been resolved in later versions. Secondly, I would suggest that you edit the httpd.conf file DIRECTLY to get around the problem. Regards, BobS

First off, is the "latest version" you're using 7.1.7 Orion? Second, what IP is returned for "localhost"? Third, what do you get when you try to access the admin menu? Regards, BobS

Let's start from the beginning. I assume you're running Win XP. First, where did you install UniServer? Second, did you run "Start.exe"? That would have made the use of 2_apache_program.bat unnecessary. Also, look at this: http://wiki.uniformserver.com/index.php/5....Install_and_Run Regards, BobS

Coral is right on! For some more details on msmtp, see this Wiki article: http://wiki.uniformserver.com/index.php/5.3-Nano:_msmtp Regards, BobS

What OS are you running? If it's Vista or Win7, did you run Start.exe as administrator? My copy of US works fine when I do that. Regards, BobS

The IMPORTANT part here is the word "Vista". This implies UAC and other restrictions. Have you ever tried to run Start.exe with "Run as Administrator"? Check out the info at http://wiki.uniformserver.com/index.php/5....Vista_and_W7.29, which tells just how to do what you want. Regards, BobS

This really isn't a fault with The Uniform Server, but rather with how Windows works. If you look at the properties for a web document (.html), you should see the name of some browser, like Firefox or IE. When UniServer starts the servers, it also looks at the startup flag to see if it should also display the splash redirect page. It does this by executing a "start" command with the name and path of redirect.html (UniServer\home\admin\www\redirect.html). That is the file you copied above. You can do the same at a command prompt. Just type (depending on the location of UniServer) start c:\UniServer\home\admin\www\redirect.html and your default browser should open up. If it doesn't, that's not because UniServer has done anything wrong, but rather the OS. You can fix this by changing what program opens a .html file. This is done in the Properties page. Regards, BobS

I guess that depends on what you need to do with UniServer. For example, PHP4 is no longer officially supported, but you may need to set up a development server to help port some old PHP code. That would be a reason for installing the PHP4 plugin. The caveat is that you really need to have the rest of the components match. You might try downloading an earlier UniServer version that has PHP4 already available. Regards, BobS

And this has to do with PHP.... how? This actually belongs under Programming & Web Design. It's NOT a Uniform Server-related problem, so I'm moving the topic. Remember, Javascript runs on the client's browser, not on the server. There is no browser associated with UniServer. It seems to me that you need to build a chart that shows just where and when the elements are created, transferred, and then acted upon. Regards, BobS

Heinz, It looks like you have gotten too far ahead of yourself here. First, I suggest you set up a new, separate install of US, like D:\basic\UniServer. Then DON'T CHANGE ANYTHING in it. Use this ONLY to look over all the code, especially www\index.php. Study how it works, and solutions to several of your problems will become obvious. You can then make a COPY of that server directory, changing the name and then make whatever changes you wish, step-by-step. Look at the application plug-ins for examples of fully configured apps. Install one, like WordPress, and look over the MySQL connection information. There's a LOT of information in the Wiki you really must read. Secondly, one of the features of The Uniform Server is to switch between development and production PHP configs. Do a left-click on the tray icon, then choose Advanced. You'll see "php.ini switch to Development", which will copy php.ini_development_nano to php.ini. After restarting Apache, this will display all errors to the screen. This is all covered in excruciating detail in the Wiki. Finally, it's not The Uniform Server's charter to be a tutorial system. Rather it is a straight-forward and compact implementation of EXISTING components, namely Apache, MySQL, PHP and some glue to hold them together. It is a great base for all sorts of testing, but there are no lesson plans included. Regards, BobS

PHP files are intended to be read by the Apache server, and the resultant output sent as a reply to the requester. This means they all go in the www directory. Regards, BobS

$result=msql_query("SELECT Code,Item,Description,Href,Src FROM silver")or die(mysql_error( )); Is that call supposed to be mysql_query() instead? This might be your problem. You can use root/root if that's what you still have configured, but that also means you're wide open to attack, because it's NOT secure. You should set up a restricted user (through phpMyAdmin), and assign that user to the specific database. The user should have select, insert, update, and delete at a minimum. Regards, BobS

Heinz, The virtual drive W: was a standard part of The Uniform Server ONLY in 4-Mona series and earlier. While you can still set it up as an option, it is NOT germane to this problem. Borszczuk, The real difficulty is with service installation. While this is rather trivial in WinXP, it's much more complex in Vista and Win7, and even more so with 64 bit systems. The key problem seems to be WAITING for the sysWOW and winsxs procedures to complete. These are all done "transparently" by the OS, but it isn't instantaneous. Thus, the built-in delay times aren't long enough the first run, and users may also interfere before everything is ready. I found this to be especially true for MySQL. However, once you get the processes properly installed, everything works just fine. In any case, I have found that it will install the services properly with only one change. For \UniServer\Start.exe, in Properties>Compatibility, click on "Change settings for all users", and then ONLY check the "Run this program as an administrator" box. No more fiddling needed. Regards, BobS

The "right" way to do this is to: 1. Rename your UniServer directory to UniOld (for example). 2. Install the new version of The Uniform Server, which will create a new UniServer directory. 3. Copy the application contents from UniOld\www to UniServer\www. 4. Copy the application databases from UniOld\usr\local\mysql\data to UniServer\usr\local\mysql\data. 5. Start the new version and test the apps. NOTE: Moving the databases assumes you're using only MyISAM. If you have activated innoDB, then you'll have to do a data export and import for that application database. If you have MANY apps running on US, then it might make sense to upgrade US. Check out this post http://forum.uniformserver.com/index.php?s...mp;p=8798 Regards, BobS