[RESOLVED] Need ms-dos 1.0
Results 1 to 9 of 9

Thread: [RESOLVED] Need ms-dos 1.0

  1. #1
    melee5
    Guest

    Post Need ms-dos 1.0

    Hi, I need to boot up Ms-dos 1.0 and look at the drive parameter table that goes with that 160k single sided relic. I can trade 1.1 or 3.1 for it? Or you could just post the table? Thanks.

  2. #2
    Registered User AlienDyne's Avatar
    Join Date
    May 1999
    Location
    Athens, GREECE
    Posts
    3,772

    Exclamation

    What exactly do you mean?

  3. #3
    Geezer confus-ed's Avatar
    Join Date
    Jul 1999
    Location
    In front of my PC....
    Posts
    13,087

    Post

    [quote]Originally posted by AlienDyne:
    <strong>What exactly do you mean?</strong><hr></blockquote>

    I dunno either, but I think he might want a boot disk so...<a href="http://www.bootdisk.com/" target="_blank">Bootdisks - various</a>.

    Or does he need a 160k verion floppy? and he wants to know all the parameters so "format /?"

    DOS 1? What's somebody's slogan - "DOS isn't dead it just smells funny"...?

    Or are we talking something from the 80's we must be..

  4. #4
    Registered User AlienDyne's Avatar
    Join Date
    May 1999
    Location
    Athens, GREECE
    Posts
    3,772

    Post

    Let's just hope this thread is not about software trade..

  5. #5
    melee5
    Guest

    Post

    Yes we are talking 80s, early 81 to be precise. MS-DOS 1.0 or IBMDOS 1.0 which ever you care to call it. The very first DOS to run on IBM PC, its also known as the ripped off re-coded QDOS which was a rip off of CP/M and got Gates going with IBM. Up till then, MS only did BASIC. Enough history.

    The Drive Parameter table informs DOS of how to format a disk, it holds head load time, unload time, sector count, default filler byte and the count of intergap data that seperates sectors, amoung other things.

    To see it, run debug. Then Type
    D0000:0078

    That will give you a pointer, in win98se, you get as the first two bytes shown

    22 05

    That's the address where DOS thinks the parameter table is. Type

    D0000:0522

    and the first 11 bytes shown are the Paramter table that I need to see - only in MS-DOS 1.0 flavor. I'm trying to collect an 'average' value of bytes that are stored in each type of 5.25" format so that I can work on creating a different format on a different system altogether and have the count of intergap data close enough to allow reading and writting to the 'new' unique format.

    Like having 26 sectors of 128 bytes, instead of the normal 9 with 512 bytes.

    26 x 128 =3328
    9 x 512 =4608

    Looks like I need some extra filler intergap data don't it?
    So if I can get that info it would help me find a working average to shoot for. Thanks.

  6. #6
    Geezer confus-ed's Avatar
    Join Date
    Jul 1999
    Location
    In front of my PC....
    Posts
    13,087

    Post

    [quote] I'm trying to collect an 'average' value of bytes that are stored in each type of 5.25" format so that I can work on creating a different format on a different system altogether and have the count of intergap data close enough to allow reading and writting to the 'new' unique format <hr></blockquote>

    Still clear as mud , why pray tell for 5.25" disks??? & not 3 1/2?

    Is this technical enough for you Alien!!??

    If you hold your fire a while I may have some DOS 2 mannuals in a box somewhere, but before I do any searching convince me....

  7. #7
    Registered User
    Join Date
    Oct 1999
    Location
    Clackamas, OR USA
    Posts
    5,422

    Post

    The original DOS upon which Gates built MS was called Seattle DOS 1.0. He bought the company and turned it into something bigger--gee, that sounds awful familiar...I've seen original copies but never booted anything with it....(just a historical note)

  8. #8
    Intel Mod Platypus's Avatar
    Join Date
    Jan 2001
    Location
    Australia
    Posts
    5,783

    Post

    The Drive Parameter Table melee is looking at is shown here:

    <a href="http://www.xs4all.nl/~matrix/fdd_pt.html" target="_blank">http://www.xs4all.nl/~matrix/fdd_pt.html</a>

    & he's after typical figures used under DOS 1.0

    Like others I'm not clear on the significance of DOS 1.0, but it looks like he's using it to establish workable figures for an alternative formatting system.

    melee, if any of the shareware authors who wrote alternative DOS formatting programs, like Chris Hochstatter, are still contactable, they may have some clues. Chris for example suggests no less than 40 for gap on DD drives, so 28 gaps of 40 almost fills the figures you used above. If you're actually using a SD drive the figure may be larger. Waste of capacity is one reason not to use the smaller sector sizes.

    I've only got old contact details for Chris & Ciriaco Garcia who wrote 2M, I can post them if you like?

  9. #9
    melee5
    Guest

    Post

    Thanks, Platypus, old contact data not needed. But you gave me some more ideas. I could compare how the numbers line up for 3.5" amound the various alternative DOSes and see if my 'method' holds true on that disk platform.

    I do need 5.25" data though and the only one I don't have yet is 160k single side which is what DOS 1.0 is. Can anybody suggest an earlier DOS or alternative DOS on 5.25"?

    Thanks for all the posts everybody, I didn't think there was that much activity in here.

    Seattle DOS was the name before Gates got it, and it was also known as Quick and Dirty DOS shortened to QDOS. Still, so close to CP/M, that Digital Research sued over it.

    What we are doing is trying to reprogram the system to write out boot disks on the PC that will boot the old Atari 8 bit. It almost works too! So now we need to tweak things a bit and I just want a solid base of tables that do work so that we can get the fiddling done with in a hurry. Further complications are 288 RPM on Atari drive and sector size limited to 128 bytes. So I'm actually trying to build a table for 130k disks from 180k and 160k tables. The more 5.25" tables I can get, the better idea of just what is optimum values for total head write time per track. Adjust that for RPM and we should really be close. Thanks.

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
  •