Archive for January 6, 2006

Windows Apps, Not Windows OS

While many don’t care what kind of chip is inside a Mac, others wonder what it will take to boot Windows on an Intel Mac. TechWorld has found an interesting intermediate argument, predicting that the big winner will be Windows-emulation products such as VirtualPC. They should allow Windows apps to run at native PC speeds on the new Macs since code translation will no longer be necessary. While only a few geeks like me want both a Mac and a PC on their desks, more may benefit from the ability to run Windows apps on their Macs. I figure that this will be a great opportunity to run Windows apps while eschewing the Windows OS! We will have to see how well the next generation of Windows emulators integrates with the Mac OS.

Data Projector Maintenance and Troubleshooting

When we had just a handful of data projector/Smart Panel installations, I could call one of our two vendors (BBI Engineering and Audio Graphic Systems) to fix problems that arose. Within the last two years, use has gone way up and we have installed an additional dozen units. Downtime is much more sensitive than before. As a result, I have begun to take ownership over basic troubleshooting and maintenance of the devices.

Basic maintenance is mostly about periodically cleaning the air filters. Otherwise, the units overheat prematurely. At their worst, they may not make it through a lesson before needing to reset. Since our projectors are ceiling-mounted, I need to climb up, remove the filters, vacuum or brush them out, and then put them back in place. For computers, we do this sort of work over the summer. We should now add data projectors to the task list.

Since the manufacturer must complete nearly all repair tasks, troubleshooting is mostly about replacing a bulb and then removing the projector to send it away if necessary. In the past, we could only give teachers a mobile replacement projector, which was a hassle to set up in a room equipped for an installed projector. By purchasing universal mounting brackets that fit our mobile projectors, I can now ceiling-mount a projector to stand in for the permanent unit as it is out for service. In this way, the teacher may continue working with no interruption to the usual setup.

Physically installing the mobile projector is not so hard, but if the replacement is a different model than the original, then you must reconfigure the Smart Panel control device. The good news is that SP Controls makes it easy to download both the configuration utility and the settings file for our projector model.

It turns out that the configuration utility is also easy to use. A normal serial cable connects a computer to the Smart Panel, and then the application can upload, back up, and configure the control panel’s buttons and options. I can even copy one configuration to multiple Smart Panels. Piece of cake.

Our iPod Solution (for now)

We are going to begin to distribute iPods with microphones to some students with learning disabilities. Students who have difficulty taking notes quickly enough to keep up with the teacher or who have auditory processing challenges may benefit from being able to replay the day’s lesson, if it involved a fair amount of teacher presentation. I had assumed (erroneously, it turned out) that the new iPods were compatible with the handful of iPod microphones that I had seen out there. Boy, was I wrong. Apple has phased out the control port, rendering unusable existing microphone adapters.

Luckily, there are a sea of castaway iPods from the failed iPod-HP joint venture of 2004. I have purchased three 20GB, fourth generation iPods for about $200 each plus three iTalk microphones to match. This should give us a convenient solution while avoiding technology overkill. Heck, it might even be less tempting to steal!

Unfortunately, this is the cheapest way to get an Apple solution for this use. Xtrememac just introduced what I believe is currently the only microphone adapter that will fit a new iPod: the micromemo. Of course, it only works with the video iPod, the most expensive and largest model Apple makes. At least it attaches via the dock connector, raising the possibility that, one day, someone will make a microphone adapter for the nano, or better yet, how about a USB version for the Shuffle?

This just in: the iTalk has just disappeared from the Griffin web site, suggesting that they are discontinuing the product, perhaps due to lack of stock but also maybe suggesting that they plan to replace it with a new product.

New Macintosh Computers Good for UHS

Timing the purchase of new Macintosh computers is a guessing game. The rhythm of our replacement schedule does not always match the release of new products. This is more of an issue for Macintosh than Windows computers, because Apple tends to keep their innovations secret before release and tend to introduce more changes in their laptops than Windows laptop manufacturers.

This time, we have gotten lucky — the timing is just right. Our “lampshade” iMac computers are in their third year of use and will be able to serve a fourth year in our Mac lab next year. As we expand to the Sacramento St. building, the film program will gain a dedicated computer lab, which photography (adjacent) will share. Not only will we be able to purchase a room full of new iMacs, but hopefully Apple will release a second revision of the model by then. Final Cut Pro on Intel should be stable, although we will have to upgrade from HD.

The timing of the new Powerbook is not bad, either. Though we only have three on campus, two are due for replacement next fall, one on the desk of yours truly! I am curious to see whether integrated video chat holds any real value for me. Having invested almost exclusively in asynchronous communication up to this point, I’m not sure how much I will like direct video communication once it’s built in to my device.

Urban School Laptop Mini-Conference

I am currently attending the Urban School Laptop Mini-Conference. Attendance is most impressive. There are about 80 people in the room, and Howard (Urban’s tech director) has taken the innovative step of requiring each school to bring one lead administrator. I have to believe that part of this new wave of enthusiasm for 1:1 laptop programs is the accelerating popularity of Web 2.0 technologies.

The content is not new to me, having heard Howard and other laptop evangelists speak before. However, I am pleased to hear directly from Saul Rockman, who has conducted a series of laptop program evaluations, and a member of the Lausanne School in Tennessee, which hosts the leading annual laptop conference in the United States.

Both Saul and the teacher panel provided me with some nuggets for my most present concern: how to convince non-teachers (e.g., board members) of the quality of classroom transformation that takes place with a laptop program. A teacher’s personal theory of effective instruction is (usually) complex and deeply held, and each teacher will selectively adopt aspects of a laptop program to suit his/her objectives. This reality does not sit well with individuals who are being asked to approve or reject a program that will cost families thousands of dollars.

Our strategy is to answer the trustee’s questions as well as we can. Let us describe the ways in which classroom instruction will likely change as a result of laptop implementation, stressing the long-term timetable for this change. My Dean of Faculty has added a good idea to this plan, which is to first describe what powerful activities we already do with technology before addressing how a laptop program will amplify and expand these.

Power Surge Casualties

For the first time in three and a half years, we lost some equipment to a power surge here on campus. On today, the first day of second semester classes, we found that two printer network cards had stopped working. The weather had been bad over break and we know that we lost power a couple of times, so a power surge seems the likely culprit. We consider ourselves lucky that no other equipment was affected

Planned Obsolescence?

Are laptop computers designed to fall apart after three years? Three and a half years ago, we purchased a set of Dell Latitude c840 laptops for our science teachers and laboratories. Over the course of three years, some were used heavily and some lightly, as is the case with most laptop installations. This fall, we replaced the computers with newer laptops, as per our customary three-year replacement schedule for laptops. They were experiencing typical third-year hardware faults, and the extended warranties we had purchased had expired. The c840s were migrated into our loaner pool, where they were distributed as needed to students and teachers.

The surprise was how quickly the laptops fell apart in their fourth year. Each time we attempted to use the laptops for a training, most of them had problems. We discarded half the remaining inventory within three months. The problems had nothing to do with the processor speed (1.6GHz P4) or disk size (20-40GB). They were always related to a hardware fault, such as a motherboard failure. Fortunately, we received an in-kind donation of a number of laptops from parents who work at HP and IBM, so we are now able to replace the loaner pool without incurring additional cost to our operating budget. However, our plan to use laptops retired from primary duty as loaners seems unsupported by our experiences.

The three-year problem is a major issue for our proposed student laptop program. If families only had to buy one computer over a student’s high school years, it would be a lot easier to launch a student laptop program. Currently, we face the prospect of charging an annual fee that allows us to purchase two laptops during a student’s career.

Hide Your PHP Scripts

In the process of reviewing the security of our web server, I found a significant problem with Win2k server. The web and FTP servers use the same directory permissions, so it is not so easy to restrict read permissions on public web directories in the site. This isn’t a problem for HTML documents, which are the same whether viewed in a web browser or downloaded via FTP. It is also not a problem for PERL scripts, which reside in a virtual directory outside of the FTP space. It is a big problem for PHP scripts, which produce HTML when viewed in a web browser but reveal the PHP code when downloaded via FTP!

The source code for open source PHP scripts is already published, so why is this a problem? Most PHP web applications have a config file that contains database login information, and an unscrupulous network user could acquire this information and attempt to modify the database directly. How real is this risk to us? Because of other user limitations, not significant, but it is good practice to close such security holes anyway.

Other prongs of our security structure help keep hackers out. For example, only current network users have FTP access to the web directories. In addition, students only have write access in their personal directories, and they do not have execute permissions there. So, they cannot run scripts from their user directories anyway. Finally, I create a separate mySQL user for each PHP application I install, so that a compromised database login/password will only affect one application (e.g., bulletin board).

The solution to the specific problem of PHP scripts in FTP directories is to move the scripts, much as is done with the PERL cgi-bin. Store the PHP scripts outside of the web directory, for example in a “scripts” folder elsewhere on the web server. Map a corresponding virtual directory in the web site for each PHP script to the appropriate script folder. Then create a separate FTP site for access to that folder. Windows does not allow you to limit FTP access to that folder by user, but it does allow you to restrict by IP address. So I have locked down the scripts folder to my IP addresses only. This does require opening additional firewall ports if you want off-campus access to the FTP site.

Occasionally, I have students who study a scripting language with me as an independent study. I cannot give them any script access on our production web server, because then they would be able to perform read/write operations about anywhere on the drive using their own scripts. The only option, time-consuming as it may be, is to set up a separate web server in the DMZ, so that it only has access to the internet and not to the other servers on the network. Then the student has full access to an unprivileged machine.

That’s pretty good security, as far as I am concerned. Comments are welcome, of course! I love to deepen my knowledge of web server security.

Sanako Lab 100 Format Issues

I spent some time this week resolving an issue with our Sanako Lab 100 (formerly Elice) language lab software. One of our language teachers digitized about 300 audio files this summer for use in our language lab. When I dropped those files onto the lab’s storage server, they would not play properly, returning an “unsupported file type” error. Then I found our that you must use the Lab 100′s Move command (in the Menu button) to convert files to a compatible format. The specific format is not immediately apparent, but it may be a codec specific to the Lab 100 software. The file format is WAV — I don’t know why, since the files are five times larger than the comparable MP3! All of the above is well-documented, albeit a hassle, because the Move command will only operate on one folder at a time.

What is less well-documented is that the source files must be on the teacher PC, not the MSU, in order to convert properly! If you use the Move command to convert a file that is already located on the MSU, the files will still not play properly. After much trial and error, I found that saving the files to the teacher PC and then using the Move command works.

Some of this problem is due to the two-computer setup in the Sanako language lab. One computer is a Windows teacher PC, which houses the lab software and student recordings. The other is a Linux-based storage server, directly connected to the teacher PC by crossover Ethernet cable. The Linux-Windows communication periodically results in file transfer issues. Why Linux? Perhaps to save cost. Why WAV? I’m not sure — perhaps MP3 royalty issues (more about that).

It appears that the Lab 100 software is best suited for automatically storing the current lesson’s source material on the MSU, and less well-suited to importing a large number of previously digitized files. The good news is that we should only have to perform such an operation annually, at most. Other than these software quirks, we love our language lab!

On an unrelated note, I copied most of these audio files to our web server last semester, so teachers can make them available to students for study outside of lab time. Students with iPods can even take these files to go!

New Library Web Site

Our interim librarian Nicole was recently inspired by the blog-driven web site of the Ann Arbor District Library. She asked me whether we could convert ourLibrary web page into a blog, and I said “of course!” A couple of hours later, we had produced most of the new site. The software will allow her to easily post announcements about new items and links of interest, in addition to the usual task of maintaining links to research databases and subject area sources. For the latter, the blog software functions as a simple CMS by providing links directly to old blog items and removing the date so that they appear to be static pages.

The biggest apparent transformation is the look and feel. Historically, it was difficult to create a high-quality, original look and feel for the static library site. I have always found it challenging to produce good graphic design, so I appreciated finding the Laila skin. Since it already came in UHS web red, all the skin required was one good photo to be ready for production use.

I introduced one advanced wrinkle into this project. Until now, our entire library site was public to the world. In the interest of enabling comments on the new library blog, I moved the site into our private (authenticated) space. Students are automatically logged into the site and can leave comments under their school user names. However, we still wanted to keep the library front page public, in order to maintain visibility with our peer school libraries and to stay consistent with our other school program links on the insideUHS home page. To accomplish this, I wrote a small CGI that sends an authenticated HTTP request to our private site, rewrites some of the links, and returns this code to the browser. Since the request is authenticated but the actual user is not, the user still needs to log in to view any of the links.

UHS community members who would like to subscribe to the RSS feed must use news reader software that supports authentication.