We don' need no stiinkin' Kodachrome. We got jets, man, we got jets.

Discussion in '35mm Cameras' started by Nicholas O. Lindan, Apr 25, 2007.

  1. .......And they did. ......And they still are.........
    William Graham, Apr 29, 2007
    1. Advertisements

  2. Back in the 40's my orthodontist had a television set that had a 4" by 4"
    green on black screen.....It was about as big as a clothes washing
    machine....I can still remember seeing tiny pictures of Milton Berle on that
    tiny green screen........
    William Graham, Apr 29, 2007
    1. Advertisements

  3. Lots of snipping...
    The first computer I had to deal with was
    Hewlett-Packard's version of the PDP-8, I no longer remember
    the model number. Anyone who had to use one carried a "basic
    binary bootstrap" in the form of a loop of punched paper
    tape around wtih them. This also required waking up with
    hand set switches on the front, about 5 commands, at the
    time I had them memorized. The machines I worked with spoke
    Basic. It required an interpreter to work with Fortran. -hp-
    had drum and high speed tape memories for these guys but I
    never worked with anything other than paper tape.
    Richard Knoppow, Apr 29, 2007
  4. Nicholas O. Lindan

    Matthew Winn Guest

    There's information about the computers used on the Voyager missions
    at <http://voyager.jpl.nasa.gov/faq.html>. The section begins around
    two thirds of the way down the page. The first part reads:

    There are three different computer types on the Voyager spacecraft
    and there are two of each kind. Total number of words among the
    six computers is about 32K.

    Computer Command System (CCS) - 18-bit word, interrupt type
    processors (2) with 4096 words each of plated wire, non-volatile

    Flight Data System (FDS) - 16-bit word machine (2) with modular
    memories and 8198 words each

    Attitude and Articulation Control System (AACS) - 16-bit word
    machines (2) with 4096 words each.
    Matthew Winn, Apr 29, 2007
  5. Thanks for that, Matthew. It's what I was looking for before I posted, but
    could not seem to locate. I did eventually find this, though:


    Powerful enough to explore the Solar System -- and interstellar space
    beyond -- but orders of magnitude too weak to run Windoze...

    Ken Nadvornick, Apr 29, 2007
  6. Nicholas O. Lindan

    Alan Browne Guest

    The 1802 "Cosmac" was touted as the first integrated microprocessor. I
    did some assembler code maintenance on realtime nav software using this
    little beastie. I confess that I never really grok'd its bizarre
    architecture and instruction set... Nonetheless we produced Doppler
    navigation sensors using this thing. Imagine it seeking and tuning
    Doppler freq. peaks and executing an Euler matrice computation,
    formatting and outputting the velocity set, continuos BITE ... all 20X
    per second...

    Win-dohs? We certainly had no OS of any kind, just burned the code into
    the EPROM and that was it.

    Alan Browne, Apr 29, 2007
  7. Nicholas O. Lindan

    Alan Browne Guest

    If you're talking about the HP-2100, HP-21MX, HP-1000, etc. I don't
    believe they derived anything from DEC.

    Occasionally we had to hand load the bootstrap and had the list of
    opcodes right by the 2100.

    We had a navigation computer based on that architecture. 3 boards of
    about 8 x 11 inches for a mere 32 Kwords of memory (of which 28 was
    EPROM). One cool thing was flight testing. We replaced the EPROM with
    battery backed up RAM. In flight, without halting the processor we
    could insert new instructions in free memory and then simply punch in a
    JMP to that code and then a JMP back to the following address to test
    changes in flight. Saved a lot of flight test hours and frustration.

    When I first started on that machine we actually "wrote" edit scripts
    and punched them on paper tape. Then ran the paper tape to edit from
    one v of source code to the next. The nav program was 70,000 lines of
    assembler (inc. comments) in 8 files. When we migrated that to the
    HP-1000 we broke that up into about 25 files for better manageability.
    For Y2K, because the file index system was 2 digit date dependant, we
    closed down the HP-1000 and had a contractor write a X-assembler on PC.
    That took him a few days ... 0 bugs.
    Alan Browne, Apr 29, 2007
  8. Nicholas O. Lindan

    Alan Browne Guest

    Or design a program with 100,000 interrupts per second to synthesize a
    complex signal in two channels for real time stimulation of radar IF
    channels. Did that back in the early 90's, in assembler in less than
    400 lines of code. (TMS320C25).

    The "obese" code comes from code reusage where it's easier to link a
    module for a function or two and also get dozens of unused functions. A
    good linker will remove the unused code, but that's not always done.

    Object programming speeds development which is a lot more expensive than
    mere memory.
    Alan Browne, Apr 29, 2007
  9. Nicholas O. Lindan

    Ken Hart Guest

    Nonetheless, if programmers followed Mr Nebenzahl's advice (which is
    generally a good thing, based on his past posts!), you would have room to
    store dozens, perhaps hundreds more photographs on your hard drive.

    BTW, if you're storing all those images on your hard drive, I'm guessing you
    never had a hard drive failure. It's not a day at the beach!
    Ken Hart, May 2, 2007
  10. But then I wouldn't have all the software I have now, as the programmers
    would still be making version 0.1's, year after another.
    Who said I store them _only_ on my hard drive?
    Toni Nikkanen, May 2, 2007
  11. Nicholas O. Lindan

    Pudentame Guest

    Never had a simultaneous failure of the hard drive AND *both* backups.
    Pudentame, May 3, 2007
  12. Pudentame spake thus:
    You have *backups*? What a novel idea ...

    Any system of knowledge that is capable of listing films in order
    of use of the word "****" is incapable of writing a good summary
    and analysis of the Philippine-American War. And vice-versa.
    This is an inviolable rule.

    - Matthew White, referring to Wikipedia on his WikiWatch site
    David Nebenzahl, May 3, 2007
  13. Nicholas O. Lindan

    Pudentame Guest

    Actually, I think it was a Novel idea ... William Gibson IIRC. ;-D
    Pudentame, May 4, 2007
  14. First of all, just like conventional silver gelatin prints,
    not all inkjet B&W prints are created equal. In particular, the choice
    of inkset and media is critical; there are quite a few aftermarket
    inksets available, mostly for Epson printers, which produce extremely
    good results. These inksets use multiple black-pigmented inks at
    varying density levels to produce monochrome prints.

    In fact, Epson heard loud and clear and has introduced a number of
    printers which feature an "Advanced B&W" (ABW) mode. ABW mode uses
    primarily black-pigmented inks at three density levels (Ultrachrome K3)
    with very small amounts of yellow and cyan for tone control. I have an
    Epson Stylus Photo R2400 and the results are truly outstanding and,
    if you believe the Wilhelm numbers, archival for well over 100 years.

    Some folks also produce negatives using inkjet output, too.

    An excellent mailing list on this topic - the production of high-quality
    B&W prints from digital images - is the Yahoo Group:


    For the uninitiated, it's amazing eye-opener to what's happened
    in the world of digital B&W printing.

    Dana H. Myers, May 5, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.