For those of you wondering how it doesn't crash, it is all pretty much logic control. Also, in the event of any kind of failure (on any roller coaster), all the brakes default to the on position (stopping the ride as fast as possible).
The best part about TTD would be a rollback (I've never gotten one, in 30+ rides), or the ultimate (when a train got stuck at the top for 20 mins loaded). For more info check www.pointbuzz.com
When I was a student 3 years ago at my local junior high school, I was on the student tech team helping set up all the computers around the school. Pretty much every new computer we got was a Dell, (minus the imac/g4s for the art department). We had a simple system to keep track of all software on each system.
1) Unpack computer, hook up, power on. Enter in the Windows Key on the shrinkwrapped package. Computer ID (room/letter) goes on the shrinkwrapped package and goes into a box, which are in a secure storage facility.
2) Novell User System Login installed, confirmed that it worked.
3) Microsoft Office 2000 Installed on EVERY MACHINE! This kept it simple, every system had all of the same software installed (minus a few "special" labs). That made keeping the software on each machine indentical, and records slightly easier.
4) Microsoft Photo Editor installed. Same reason as above.
5) Network printers set up. No big deal here.
6) Foolproof security installed. This was a "decent" piece of software that kept students (minus me and a few others) from doing almost anything. All saving had to be done on the network server, and nothing could be isntalled.
6a) Now we use a system called Fortress. This is much better, because we can integrate access with Novell user names, meaning if I log in as techsup (techsupport) I have full access very easily.
Anyways, the moral of the story is to keep solid records from the beginning. Our tech admin kept very good records, and anytime an audit might occur, I have no doubt that everything would work with no problems whatsoever.
Slashdot Mirror
For those of you wondering how it doesn't crash, it is all pretty much logic control. Also, in the event of any kind of failure (on any roller coaster), all the brakes default to the on position (stopping the ride as fast as possible). The best part about TTD would be a rollback (I've never gotten one, in 30+ rides), or the ultimate (when a train got stuck at the top for 20 mins loaded). For more info check www.pointbuzz.com
When I was a student 3 years ago at my local junior high school, I was on the student tech team helping set up all the computers around the school. Pretty much every new computer we got was a Dell, (minus the imac/g4s for the art department). We had a simple system to keep track of all software on each system.
1) Unpack computer, hook up, power on. Enter in the Windows Key on the shrinkwrapped package. Computer ID (room/letter) goes on the shrinkwrapped package and goes into a box, which are in a secure storage facility.
2) Novell User System Login installed, confirmed that it worked.
3) Microsoft Office 2000 Installed on EVERY MACHINE! This kept it simple, every system had all of the same software installed (minus a few "special" labs). That made keeping the software on each machine indentical, and records slightly easier.
4) Microsoft Photo Editor installed. Same reason as above.
5) Network printers set up. No big deal here.
6) Foolproof security installed. This was a "decent" piece of software that kept students (minus me and a few others) from doing almost anything. All saving had to be done on the network server, and nothing could be isntalled.
6a) Now we use a system called Fortress. This is much better, because we can integrate access with Novell user names, meaning if I log in as techsup (techsupport) I have full access very easily.
Anyways, the moral of the story is to keep solid records from the beginning. Our tech admin kept very good records, and anytime an audit might occur, I have no doubt that everything would work with no problems whatsoever.
And you that getting a few SETI Work Units for your small fleet, imagine trying to run 5000+ processes at once.