Rick Osterberg '96, coordinator of residential computing at HASCS, said his organization had decided not to allow shuttleboy onto their servers because they didn't want the hassle of maintaining and supporting the program.

"We have a limited staff and budget, and our primary duties are keeping systems up and running, keeping e-mail flowing. That's a task in itself," he said.

Osterberg said that the program requires someone to update information in the program manually every time the shuttle schedule changes, in addition to any other support issues that might arise.

However, Malan said that the work involved in supporting the program would not be an issue, for both he and the Harvard Computer Society (HCS) have agreed to support the program themselves.

"Both I and HCS explicitly expressed willingness to maintain and support the program ourselves," Malan wrote in an e-mail message, "provided HASCS simply installed the program on the public systems."

Malan said the process "would take only seconds."

Another alternative would be to shift the shuttleboy program to another student's account. But Malan said each time the program changes hands, each shuttleboy user would have to reconfigure their account--making this option impractical.