| -
I think I used that machine when I went to Control Data Institute. They
shared it with SLU. Steve Bromley wrote: **************************************** For List Info or To make _ANY_ changes, including unsubscribing from this list, click -----> //www.freelists.org/list/geocaching Missouri Caches Scheduled to be Archived http://tinyurl.com/87cqw- Nope, but close. It was a CDC3300 (Old Control Data machine with 32K and a Floating Point Unit). It was in the basment of the Pink Building on the SLU campus and wouldn't fit into my current house. It ran off of 220 3-Phase power. ----- Original Message ----- From: "Robert Oelschlaeger" <roelschlaeger@xxxxxxxxx> To: geocaching@xxxxxxxxxxxxx Subject: [GeoStL] Re: [geocache] Re: Branson Caching Date: Fri, 15 Jun 2007 07:22:51 -0500.. must have been a PDP-11; hardly anyone else used octal... Bob (aka roelsch) On 6/14/07, Steve Bromley <bromley@xxxxxxx> wrote:I just absolutely love geek talk. Brings my back to my days of punch cards, wiring boards, and using Octal. Lets code it in machine language.... Steve Bromley bromley@xxxxxxx ------------------------------ *From:* geocaching-bounce@xxxxxxxxxxxxx [mailto: geocaching-bounce@xxxxxxxxxxxxx] *On Behalf Of *Robert Oelschlaeger *Sent:* 14 June 2007 Thursday 9:38 PM *To:* geocaching@xxxxxxxxxxxxx *Subject:* [geocache] [GeoStL] Re: Branson Caching For the entire file, or for each record of say 64 bytes, like a Motorola S-record file? 8-bit, 12-bit 16-bit or 32-bit? Which polynomial? CCITT-16? CCITT-32? preset to all 1's first? complemented at the end? Single-error detecting? Single-error correcting, double-error detecting Hamming code? That would add three bits per byte, I'd guess. Adding just a single parity bit to each character add about 10%, so we would have 4.3860 years. Adding the file checksum would be negligibly different. Adding a 16-bit CRC per line of 64 bytes adds 3.125% Grand total is about 4.5 years. Any other requests? Bob (aka roelsch) On 6/14/07, Enormous Richard <_rnx_@xxxxxxx> wrote:- very nice 8^) what if i wanted to add a redundancy checksum ------ Original Message ------ *Received: *Thu, 14 Jun 2007 10:16:59 PM EDT *From: *"Robert Oelschlaeger" <roelschlaeger@xxxxxxxxx> *To: *geocaching@xxxxxxxxxxxxx *Subject: *[GeoStL] Re: Branson Caching 3.9873 years if you're talking 1M = 1048576 bytes :-) Bob (aka roelsch) On 6/14/07, Robert Oelschlaeger <roelschlaeger@xxxxxxxxx > wrote: I get 3.8026 years, figuring four seconds per bit, 10 bits (start/stop/8 data -- this is serial asynchronous, after all) per byte, and 365.25 days per year: octave:1> rate=0.25 rate = 0.25000 octave:2> bytes=3e6 bytes = 3000000 octave:3> bits=10*bytes bits = 30000000 octave:4> seconds = bits/rate seconds = 120000000 octave:5> hours = seconds/3600 hours = 3.3333e+04 octave:6> days = hours/24 days = 1388.9 octave:7> years = days/365.25 years = 3.8026 octave:8> On 6/14/07, HoosierDaddy <_rnx_@xxxxxxx > wrote:- i wonder how long it would take to send 3Mb via smoke signals ------ Original Message ------ *Received: *Thu, 14 Jun 2007 08:06:39 PM EDT *From: *"Robert Oelschlaeger" <roelschlaeger@xxxxxxxxx> *To: *geocaching@xxxxxxxxxxxxx *Subject: *[GeoStL] Re: Branson Caching Must be all those folks trying to escape the chain of being shackled to their high speed DSL :-) On 6/14/07, Tim and Pam <timpam2mocachers@xxxxxxxxxxxxx > wrote: I wish we could leave our house unlocked. Washington is starting to grow like St.Charles did 20 years ago. It is scary to look around at the changes made in just the last 6 months L Tim www.tueltzen.smugmug.com ------------------------------ *From:* geocaching-bounce@xxxxxxxxxxxxx [mailto:geocaching-bounce@xxxxxxxxxxxxx] *On Behalf Of *HoosierDaddy *Sent:* Thursday, June 14 , 2007 6:38 PM *To:* geocaching@xxxxxxxxxxxxx *Subject:* [GeoStL] Re: Branson Caching we all make choices that have consequences. just keep in mind all the privlidges that living in Washington provides to keep your minds off the |
