Image Map Image Map
Results 1 to 5 of 5

Thread: Franklin DOS 2 (FDOS2)

  1. #1

    Default Franklin DOS 2 (FDOS2)

    Hello group, I am looking for disk images of Franklin DOS 2 (FDOS2). The one that I find on Asimov doesn't seem to work.
    Any other disk images related to Franklin ACE 500, 1200, and 2200 would also be welcome.
    Thanks!

  2. #2

    Default Disk Image of Franklin DOS2

    Quote Originally Posted by retrobecanes View Post
    Hello group, I am looking for disk images of Franklin DOS 2 (FDOS2). The one that I find on Asimov doesn't seem to work.
    Any other disk images related to Franklin ACE 500, 1200, and 2200 would also be welcome.
    Thanks!
    I have a copy of Franklin Dos2 and the Expanded Memory Utility Disk that I found a while back. I am working on getting a 5.25 drive up and running so I can get an image of it and quite a few otherdisk. Nice I have I will let you know!

    8B64E841-FE14-4978-9F3F-D0BCCB944282.jpg
    Attached Images Attached Images

  3. #3

    Default

    FDOS was a very nice DOS written almost entirely by a fellow named Dave McWherter, who was VP of Engineering for a while at Franklin. I know I've got the progrmmer's guide for it someplace in my collection and can look to see if I've got the boot disk too. We (Engineering) always seemed to have disks with exactly what we wanted and official released disks were very uncommon.

    BTW, one of the plain DOS disks released in 1982 has my name as a comment in the HELLO program. I was one of the people who put the files on the disk used to deliver to Production.

    Bob

  4. #4
    Join Date
    Dec 2008
    Location
    libtard capital, California
    Posts
    1,070

    Default

    Hi Bob, was software always done in house or were they farmed out near the end like the 2000s and 500s?
    (I still have a CX in the garage somewhere.)

  5. #5

    Default

    Sorry, I missed reading this post until now.

    There were a lot of legal issues dealing with Apple, so two outside consulting houses were hired to write new versions of some sections of the code that were causing us legal problems. Us "old timers" were considered "tainted" and could write requirements for code and evaluate what was coming back from the consulting houses, but couldn't write any code that could be issues with Apple.

    In-house people wrote a lot of stuff, just not much in the EPROMs. McWherter wrote FDOS and pulled in a lot of stuff that was written in engineering.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •