Ag62 Projector
-The projector in Ag62 has begun shutting itself off after approximately 1 hour of use. It has happened 2 times that I have confirmed in the last week, but I am not sure when the problem began. My first guess would be overheating problems, but I leave actual diagnosis to the experts.

 
GRIPLite on your Desktop
-Ok, recently I have had a few questions from those who want to know how to get Grip to show up on your desktop as a shortcut. The following is a quick and easy step-by-step walkthru on how to dig through your computer and get a Grip shortcut onto your desktop.
1) Open "My Computer".
2) Open the main hard drive on your computer (almost always the "C" drive).
3) Open the "Program Files" directory.
4) Open the "SVS" file.
5) Open the "GRIP" file.
6) Now you should be looking at a number of files and a few executables. There should be an executable file in here that will start-up GRIPLite. Do NOT drag this file out to your desktop. Instead, do the following:
A) Right click on the icon and select "Create Shortcut".
B) Drag the shortcut you just created out to the desktop.

-By following these steps you should now have access to GRIPLite from your normal desktop. As always, if you have problems, feel free to call me at any time.

 
MCU Protocol
-A good practice to keep in mind is to use MCU ports 2 & 3 before you use MCU port 1. Daryl and I have been trying to create classes from the bottom up in the MCU (meaning you use 3 first, then 2, and 1 last). By doing it this way MCU 1 will stay open longest and can be used for testing and in case of emergencies...like what happened last night with the connection to ISU.
-I will start setting a reminder alarm for myself on days that we have to register our MCU to WSU's gatekeeper so that I remember to double-check that we re-register to our own gatekeeper when all WSU events are completed. Please try to remember to reset the MCU to our own gatekeeper if your event is the last one scheduled with WSU and there is not another conference running. The reason we had so many problems with ISU last night is likely because our MCU was still registered to WSU.

 
9/11/06, MCU - PLSC 334, Ag 323 and TF stayed connected on the MCU for 6 hours yesterday.
I kept noticing it but did not investigate, I thought if it's in the MCU it must have been a scheduled event. As we are going in and out of the MCU let's try to be aware of what supposed to be in there and if a meeting or class hasn't disconnected we can catch it. I've been putting a time frame in each class I'm connecting into the MCU, just in case Murphy's Law decides to get me.

MCU connection with Pocatello did not work so well last night, Mike said in previous weeks we could call them fine. The MCU was registered to the WSU Gate Keeper. Sam and I worked together to figure it out with Pocatello. The final solution was I moved the ED Ad Class to MCU 3 and connected the CNR14, If, ISU Poc class into MCU 1 so that ISU could dial into us.

 
TF A-21
-More problems with Twin this morning. 10 minutes after I connected, my point-to-point connection with A-21 died on me. I immediately tried to re-establish the call, but was unable to connect. Then I tried to reach the TF Tandberg through the web, but could not establish a connection. Finally I called Amanda and had her restart the unit in Twin, and once that happened I was able to connect again.
-I have never before seen a unit stop a connection and need a restart in the middle of a conference. I have had to restart between conferences, but it is highly unusual that the unit would allow me to connect for a few minutes, then stop working while the conference was connected. This is the second or third time I have had problems with the TF A-21 Tandberg unit.