browser

You are currently browsing the archive for the browser category.

If you are trying to connect to an online server in Call of Duty, you have probably noticed that you will wait through “Awaiting Connection” for about 10 or 11 seconds, then the connection times out. This is due to the Activision master server browser having issues (presumably because Call of Duty 4 has been more popular than they thought).

A quick remedy for this connection problem is to set the timeout to be longer in your CoD 4 multiplayer config file, found in the profile folder of your player. For example, mine is: C:\Program Files\Activision\Call of Duty 4 - Modern Warfare\players\profiles\string\config_mp.cfg Yours could be C:\Program Files\Activision\Call of Duty 4 – Modern Warfare\players\profiles\YOURNAME\config_mp.cfg

Open the file up in notepad or any other text editor (I use ConText), and add this line: seta cl_connectionAttempts "30" – this will give the connection 30 seconds, and normally fixes the problem.

Happy Call of Duty 4 playing!

Blandname is currently hosted with DreamHost, and we’ve been here for years. It’s cheap, offers lots of goodies, and one-click installs allow us to easily install and test web-based software. Not to mention that they also support Ruby on Rails, and give you SSH access and the ability to run a Jabber server as well as unlimited MySQL databases.

You’ve also probably gathered that blandname is currently running WordPress. Dreamhost has had a one-click install for WordPress 2 for a while now, and since it was handy at the time, we went for it.

But things change, and one-click installs often are not enough to satisfy most webmasters, which is how we got where we are today. Since my goal with blandname is to create another multiuser blog similar to what has already been running for years at yottabite, but instead of having one big weblog, we’d like to have multiple subdomains like string.blandname.com, which WordPress MU allows you to accomplish, automatically.

Unfortunately DreamHost doesn’t support WordPress MU’s subdomains by default yet (you can always send them an email), but we can still get away with subfolders, which is more than good enough for a test.

This guide will require familiarity with DreamHost’s control panel, as well as common Bash shell commands as we will be using SSH.

The first step is to make a test domain for you WordPress MU install. In my case, I navigated to the “Domains” section of the left-hand menu, then to the “Manage Domains” section of the DreamHost panel, and created the new subdomain test.blandname.com. You’ll want to make sure to select PHP5, and enable extra security. This typically takes about 10 minutes to complete, but we still have the database to add, so let’s get to that at the same time.

In the “goodies” section of the DreamHost control panel, select “Manage MySQL”. The default view is to set up a new MySQL database, which is what we’re going to do. Create a unique database name, the subdomain you would like it to use, as well as the data base username and password. Make sure to keep note of all of these settings as we will need them when installing WPMU.

DreamHost will have by now created a folder in your SSH root that will allow you to place files there and start some of the work while we wait for the subdomain to be created and propagate. Login to your server using SSH (you’ll need to use either your DreamHost hostname here or another web address for now – you can use the WordPress Mu domain later). Now we’ll navigate to the new subdirectory that was created when we setup the new subdomain by typing: cd test.blandname.com Change the folder name to whatever is pertinent in this case.

Now that we’re in the correct folder, we’ll grab the latest using the always-handy WGET. Here’s the code:

wget http://mu.wordpress.org/latest.tar.gz

gunzip latest.tar.gz

tar -xvf latest.tar

cd wordpressmu-1.0 (this will probably change, ls -al will tell you the dirname)

cp -rf * /home/YOURUSERNAME/test.yourdomain.com/

cd ..

rm -rf wordpressmu-1.0/

Now we’ve got a clean directory structure in the root of our test domain, and we’re set to go ahead with the WordPress MU installation.

By now the subdomain has probably propagated because DreamHost is getting faster and faster, so using your web browser, navigate to test.yourdomain.com

Next you’ll want to retrieve the soiled napkin, SubEthaEdit file or whatever else it was that you used to jot down the database settings, and plop them in here. They are very straightforward, and this is typically the most problematic so check them twice but have no fear: if you mess up WP MU will tell you, and you can retrieve the settings from the “Manage MySQL” section in the DreamHost web control panel.

The rest is quite simple: you’ll be met with a typical WordPress installation page, but instead it’s for WorPress MU. The first question that needs to be asked is whether or not WordPress MU users will be using subdomains or subfolders of the root WPMU installation. As previously stated, DreamHost currently does not support subdomains by default (I’ve put in a request, here’s hoping), so we’ll select subfolders here. WP MU will have already placed the domain name you will be using in the yellow textfield, but if you had decided to use subfolders instead of the webroot, you’ll want to specify that here as this will affect all links as well as your RSS feeds.

Lastly, we’ll want to name our multi-user Wordpress MU blog, and specify the email address that you will use for things like spam reports, and replies to your comments on the parent blog.

Click on that small “submit” button, and let’s see what happens!

Hopefully on the next screen you’ll see this message:

Creating Database Config File: DONE
Congrats! Your WPMU site has been set up and you have been sent details of your login and password in an email.

Click on the link provided, and get with customization, as we’re all done.

OK, so everyone is very excited about Firefox 2. I’m excited, your excited, all the social networks are ablaze.

But development does not stop at whole numbers, and the testing must go on – which is how we got here.

So I’m testing Firefox 3 (Minefield). That’s right, I won’t be outdone. I must run the most unstable software. Well at least on the test boxes. So currently the Vista, Leopard, and Edgy boxes are running “firefox-3.0a1″.

The first things you will notice are the graphics – everything has a nice sheen to it (in fact, looks just like Firefox 2!), while remaining true to the normal Firefox UI. Also of note is the fact that favorites are now run using a SQLite3 database. For the full list of features, head on over to the Burning Edge page.

Firefox 3 Minefield Toolbar
Firefox 3.0a1 Toolbar
Firefox 3 Minefield Tabs
New Tabs in Firefox 3.0a1 Minefield

As far as I can tell this is just as stable as Bon Echo was (that’s right – was stable for me), with inline spell-checking and some other fancy goodies.That’s all for now, some more screenshots from other platforms (other than Windows XP of course) and crash reports as they happen

Note: of course this is somewhat tongue-in-cheek. I’m sorry for the Mozilla devs. We all need to stop worrying about the cutting edge and appreciate what we have – fantastic browsers! Opera, Safari, IE7 and Firefox are all great, really.

Now that Internet Explorer 7 has been released in its final form, a lot of people are rushing out to install it as soon as possible. However, some web designers will want to keep a working version of Internet Explorer 6 to make sure their designs for IE7 aren’t broken in IE6. Jon Galloway has a great tool to have both versions of Internet Explorer installed and working at the same time, using a launcher comprised of a batch file and some registry hacks.

I tested the hackish launcher, and had no problems whatsoever.

Another mention: very soon IE7 is going to be a forced (pushed) update, so it’s going to be installed without you noticing, and Microsoft is going to reboot your computer, regardless of what you have left open overnight. To prevent having Internet Explorer 7 from being installed in the fashion, you’ll need to download the IE7 blocking tool from Microsoft.

Finally, if you don’t pass the WGA check to download the blocking tool, SnapFiles is providing a mirror of the IntelliAdmin IE7 Blocking Tool.