Maintenance

Tested new machine in Lab B this PM. It's a dual-boot, with Server 2003/2000 and Sanako apps installed. Went through 3 reboots and a series of logins/outs in both OS's and everything seems to be OK. I'm tentatively calling this a H/W problem.

Martin has suggested that I get a serial port card and try that. I might do it, as long as I can get a half-height card and it comes with it's own drivers, after what WO told me about new OS's and old tech.

Spoke to WO last Firday regarding the flaky desk issue. He suggested that I consider the COM port being poorly supported by the OS. He says that modern machines do not support COM very well and it's possible that we won't resolve the problem with the current OS/hardware. I did a bit of research and discovered that the possibility is certainly there, but as I have no really specific info about the way the COM port talks to the OS in this case I have no simple way of diagnosing the problem.

Wayne's recommendation is to rebuild the older box and see if it has the same problem. I'll get right on that.

If the link for the Lab 300 Client and Server admin tool gets trashed (hrmph), you can get to the GUI by running this command for the Server:
"C:\Program Files\Sanako\Shared Components\NetCommPlatform\RSrv.exe" /UI

and this one for the Client:
"C:\Program Files\Sanako\Shared Components\NetCommPlatform\RCLNT.EXE" /UI

For documentation:
Settings in Lab C look like this

This morning, more joy with Lab B teacher station, which had been running and logged in all night. Attempting to log off proved fruitless -- the system presented the log off dialog box, but just did nothing when I clicked on the button, apart from dismissing the dialog box -- and it was impossible to shut it down either. My guess is that many users are simply giving up on this and leaving it logged on. I had to shut it down with the power button and restart it.

This morning I followed the ELC instructor into the lab to make sure everything was working, and experienced the same problems as before: Starting the teacher program results in an RSRV error. This happens even after confirming that RSRV.exe and RSRVAny.exe are running. The only thing that fixes it is to turn the console off and back on again before starting the teacher program. This suggests it's something to do with the sequence of events; the sequence that works is to start RSRV, then power up the console, then start the teacher station.

The station is also lacking any obvious links to the teaching materials. I was able to navigate easily to them, but it would be hard for a teacher. In the past, we've put a link to the materials folder in the actual directory in which the teacher station always opens up its dialog box (which if I remember rightly is somewhere in its program folder). I'll do that if I get a chance today.

HP came in with her class, and among other things needed to do the telephoning activity. When we started up the Sanako teacher application, we got the same RSRV error as the other day. I was still hitting the same problem after starting RSRV.exe manually several times. Eventually, after confirming that both RSRV.exe and RSRVAny.exe were running, I turned off the console and turned it back on, then restarted the application; that finally did it. My guess is that RSRV.exe has to be running from boot time, not logon, otherwise it has trouble connecting to the console.

Even after everything was running, and we switched Group A to the Telephone activity, we had trouble getting stations to connect to each other; stations which were not connected to anyone were still reporting themselves as Busy when called by another station.

This teacher station is pretty much unusable without one of us physically in the room to get it going, and even then it takes a while and is flaky. I wonder if it might be better to roll it back from Server 2003 to Server 2000, like Lab C, which as far as I know is working OK.

Late yesterday afternoon, HP called me from the ELC about her class today, in Lab B. She wants to show a video. I checked the TV cart in Lab B this morning, and it has no VCR on it (has it been stolen, or was it never there?). I decided I'd move the one from lab C, which is set up and working, but the cart has been padlocked to one of the desks, so that's out. There is another TV+VCR cart in the materials room, so I've rolled that into Lab B in the hope that it will work.

Unplugged everything in Lab C again for tonight's outage, then started on the servers. Shut down Chou by SSH. Couldn't log in to Quince at all, either as root or hcmc, with the given pwds; I tried this both remotely and on the KVM in the server room. Finally I had to shut down the server with the power switch. Shut down Parsnip with no problem on the KVM. When I came to Squash, I discovered that it had actually failed to start properly this morning, and appeared to be locked in a loop going through its memory test. Restarted it a couple of times, eventually skipping the memory test, but when it came up it reported one or more services had failed. Shut it down. This will need looking at tomorrow.

Still waiting to shut down Idaho because I'm doing ColDesp backups at the moment.