I’m posting this here mostly so I can refer back to it later if I ever have the need to. I recently had to setup a Windows server running IIS 5.0 at work. It will be hosting a web application that will be used to verify all orders.
Anyway, I had IIS up and running but couldn’t get it to execute pages with a .aspx extension. It would just offer up the .aspx file for download instead of executing it and displaying in the browser. Turns out this is due to the ASP.NET ISAPI extension not being registered with IIS. To register the extension with IIS, open a command prompt and issue the following commands:
cd C:\winnt\Microsoft.Net\Framework\v2.0.50727
aspnet_regiis -i
In that example, I registered the ASP.NET 2.0 framework with IIS. If you want to use a different version of .NET, replace v2.0.50727 with whatever version you want to use. The various versions installed will be listed in the C:\winnt\Microsoft.Net\Framework\ folder.
After running the apsnet_regiis command, my .aspx files loaded right away. I discovered all this at the Channel9 MSDN forums.
Take note of this graphic. Notice there’s been 3,775,826 queries processed by that MySQL server in a little more than 5 days. Nothing too impressive right? Right.
We know MySQL can handle many more queries than that in a much shorter period of time. What amazes me is how well MySQL performs on the server it’s running on. The box hosting that MySQL server is an old HP. It’s got 1 Pentium II 400mhz processor with 128Mb of RAM. And it serves data to anywhere between 10 and 14 seperate PC’s at any given point in time. In addition to that, this MySQL server also provides data to a web interface that is used by 50 or so people. The MySQL server pumps out about 500Mb worth of data every day.
MySQL never ceases to amaze me in what it can do on less than optimal hardware.
Sorry for the lack of posting lately. We started moving our office over the weekend. Being the tech guy I had a ton of work to doy. So, I spent basically the entire weekend getting all setup in the new office.
We’re moved in now and are still getting situated. I’ve got a few pictures I’ll post when the whole thing is complete. I ducked out a little bit early today just because I got the chance to do so. Don’t expect many posts for the rest of the week unless I see something at night that really deserves attention.
Ashley and I are goin to Cedar Rapids in like 3 minutes. Only about a 2.5 hour drive. Not too bad of a drive. Goin up there for a “house-warming” party. I’ll be back blogging tomorrow, cuz, well, I gotta go into work for a few hours. Bah!
Slackware 10.2 has been released. I will probably upgrade to 10.2 sometime this weekend. I know the Dropline guys are hard at work prepping their Gnome 2.12 release for Slackware 10.2. They were expecting Slackware 10.2 to be released right about now. Below is taken straight from the Slackware homepage:
Slackware 10.2 includes the Linux 2.4.31 kernel, with Linux 2.6.13 available in the /testing directory. For the first time, a 2.6 kernel with support for SCSI, RAID, and SATA is offered as a boot option in the installer (called “test26.s”). Slackware 10.2 also sports a new revision of glibc (2.3.5) with NPTL support for improved thread performance when using a kernel with NPTL support, the latest KDE 3.4.2 and XFce 4.2.2 desktop environments, updated development tools, and new additions like SASL support in sendmail, the Subversion version control system, the Firefox browser, and the Thunderbird email and news client. For a complete list of changes since Slackware 10.1, check out the Slackware 10.2 ChangeLog.
A list of mirrors that are likely to be among the first offering the 10.2 release may be found here.
I’m excited. I love new Slackware releases, nothing more exciting. Azmeen at HTNet has word of the new Slackware too. I bet he’s just as excited as I am.