Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

My Latest Buy (5160)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • modem7
    replied
    Originally posted by antiquekid3 View Post
    This must mean my system works, but it just needs a keyboard!
    Yes. That's good news. There might be some nice old software on the hard drive.

    Originally posted by antiquekid3 View Post
    Here's an update: I tried making a 720K boot disk, and my floppy drive wouldn't format it to 720K
    Nor would it take a floppy that had the hole covered.
    Now that you know that an XT keyboard will get your machine going (very high probability), you no longer have a need for a 720K sized boot diskette, because once your machine is booting from C:, you'll be able to create a 5.25" boot diskette.

    If you want to pursue the creation of a 720K boot disk, you'll need to inform us of the technique/sequence you used, and the error messages (or symptoms).

    Originally posted by antiquekid3 View Post
    That means something is messed up with the floppy drive. However, it doesn't always do that. I pulled out the cards and put them back in, and it seems to be working better now.
    Note that something that's common with 5.25" drives is that the lubrication on the slide/carriage rails has deteriorated.

    Leave a comment:


  • antiquekid3
    replied
    Okay, I just tried connecting some random new Dell PS/2 keyboard. It does something DIFFERENT!! Yay!

    Firstly, no 301 error. Secondly, it now goes to this screen:
    "
    C>DATE
    Current date is Tue 01-01-1980
    Enter new date (mm-dd-yy): _
    "

    I guess I went back in time...!

    This must mean my system works, but it just needs a keyboard! Unfortunately, the keyboard I'm using won't type. But at least it tricks it into thinking a real keyboard is connected!

    Kyle

    Leave a comment:


  • antiquekid3
    replied
    Hey guys,

    Here's an update: I tried making a 720K boot disk, and my floppy drive wouldn't format it to 720K. Nor would it take a floppy that had the hole covered.

    Also, I suppose it would help if I told ya'll just what this computer IS doing. After checking RAM, here's what the monitor reads:
    "
    301
    640 KB OK

    ST10 v2.4
    Hard Disc 1: ST251

    ERROR. (RESUME = "F1" KEY)
    _
    "

    The 301 error means the keyboard didn't respond. No duh, I don't have a keyboard connected (and I haven't figured out my Arduino keyboard emulator just yet...drats!). Also, several times upon startup, the computer gave a "601" right before the ERROR line. That means something is messed up with the floppy drive. However, it doesn't always do that. I pulled out the cards and put them back in, and it seems to be working better now.

    Any suggestions?

    Kyle

    Leave a comment:


  • Chuck(G)
    replied
    Originally posted by modem7 View Post
    My statement stands. If you connect a 1.44M drive to the combination of an IBM 5160 motherboard (even the first release/BIOS) with original IBM DD floppy controller, that combination will boot/read a 720K diskette. Note that I did not use the word, "write". For what we're doing here, which is to boot from a pseudo 720K diskette then execute programs on that diskette such DEBUG/FDISK/FORMAT against the C: drive, no writes to the diskette are required.
    And I'll stand with you. I've booted up an original 64K 5150 (with the early BIOS) using a 1.44MB 3.5" and just booted up an XT clone the same way. It works.

    Leave a comment:


  • per
    replied
    Originally posted by modem7 View Post
    When you use the word, "use", I'm sure that you mean at least the ability to read and write.

    My statement stands. If you connect a 1.44M drive to the combination of an IBM 5160 motherboard (even the first release/BIOS) with original IBM DD floppy controller, that combination will boot/read a 720K diskette. Note that I did not use the word, "write". For what we're doing here, which is to boot from a pseudo 720K diskette then execute programs on that diskette such DEBUG/FDISK/FORMAT against the C: drive, no writes to the diskette are required.
    As of I remember, the HD drive didn't even read on the IBM controller.

    Anyways, it may be drive independent. More testing will need to be done in order to say anything for sure.

    Leave a comment:


  • modem7
    replied
    Originally posted by per View Post
    You can not use a 3.5" HD (1440KB) disk drive with the original IBM DD FDC
    When you use the word, "use", I'm sure that you mean at least the ability to read and write.

    My statement stands. If you connect a 1.44M drive to the combination of an IBM 5160 motherboard (even the first release/BIOS) with original IBM DD floppy controller, that combination will boot/read a 720K diskette. Note that I did not use the word, "write". For what we're doing here, which is to boot from a pseudo 720K diskette then execute programs on that diskette such DEBUG/FDISK/FORMAT against the C: drive, no writes to the diskette are required.

    Leave a comment:


  • per
    replied
    Originally posted by modem7 View Post
    Per what Chuck wrote, if you connect a 1.44M drive to the combination of an IBM 5160 motherboard (even the first release) with original floppy controller, that combination will boot/read a 720K diskette.
    Well, I have personally done some investigation at this, and what I found was that:
    • You can use a 3.5" DD (720KB) disk drive with the original IBM DD FDC and XT motherboard (first BIOS)
    • You can use a 3.5" HD (1440KB) disk drive with a one-chip* HD FDC and original IBM XT motherboard (first BIOS)
    • You can not use a 3.5" HD (1440KB) disk drive with the original IBM DD FDC

    In the two first cases, DOS will see and use all 720KB of the disks, but several other programs will see the disks as only 360KB. I don't find this a problem since I usually use DOS when working with files.

    * I haven't tested with anything else than a one-chip HD FDC (GoldStar GM82C765B). I believe all standarized HD FDCs will work as well.
    Last edited by per; June 20, 2010, 03:15 AM.

    Leave a comment:


  • modem7
    replied
    Per what Chuck wrote, if you connect a 1.44M drive to the combination of an IBM 5160 motherboard (even the first release) with original floppy controller, that combination will boot/read a 720K diskette.

    To create a 720K sized boot diskette (with DEBUG/FDISK/FORMAT on it) using a 1.44M diskette with tape over the density hole, you can use the STEP 2 part of the process at http://members.dodo.com.au/~slappane...170_gsetup.htm

    Originally posted by antiquekid3 View Post
    Instead of printing "ST-251-1", it just prints "ST-251." But I assume that is just fine.
    Yes. I used "ST-251-1" because of your earlier, "After that, it tells me there is an ST-251 HDD (more specifically, an ST-251-1)."

    Leave a comment:


  • antiquekid3
    replied
    Thanks for the low level info, modem! I'm about to see about writing an Arduino program to emulate a keyboard so I can get some work done tonight.

    Instead of printing "ST-251-1", it just prints "ST-251." But I assume that is just fine.

    Kyle

    Leave a comment:


  • modem7
    replied
    Having just experimented with my ST-10 (with BIOS version 2.4), I'm expecting that what you presently see on screen is:
    ST10 v2.4
    Hard Disk 1: ST-251-1


    I used an ST-225 instead of an ST-251, but the expectation is similar.

    The "ST-251-1" gets retrieved by the ST-10 from a track on the drive that it reserved for itself.
    So that means that:
    1. The ST-10 is communicating with the ST-251 okay.
    2. The ST-251 has been low-level formatted by the ST-10.

    Good though to go through the low-level process (followed by FDISK and FORMAT) again just to ensure that it all has been done properly.

    Leave a comment:


  • modem7
    replied
    Seagate ST-10 low-level format process:

    1. Boot from boot diskette.
    2. Run DEBUG
    3. Enter G=C800:5
    4. Enter 1
    5. Enter Y
    6. Enter 3 (selects ST251)
    7. Enter Y
    8. Enter 3
    9. Enter N (split question)
    10. Enter N
    11. Enter Y
    12. Enter Y
    13. Enter F

    After that, you FDISK and FORMAT per usual.

    Leave a comment:


  • antiquekid3
    replied
    Okay, I'm about to try and make a boot disk. I found some online instructions...hopefully they are right!

    I have a Seagate hard drive controller. It has a Seagate ST-10 BIOS in it, version 005 2.4. Any more info needed?

    Kyle

    Leave a comment:


  • linuxlove
    replied
    To low-level format a drive, you'll need:

    * MS-DOS bootdisk with DEBUG
    * Knowledge of where the low-level formatter is on the hard drive's controller so you can call it using DEBUG.

    Post your hard drive controller model, someone should be able to help.

    Leave a comment:


  • antiquekid3
    replied
    How do I low level format a drive? I presume I will need to boot into DOS to do this?

    I'm going to try to connect my 3.5" drive tonight. Will the floppy controller work with it just fine?

    Thanks for the tips!

    Kyle

    Leave a comment:


  • Chuckster_in_Jax
    replied
    You may have to try a low-level format of the drive. If the drive is bad, I wouldn't recommend replacing it with another MFM drive. The XT-IDE project was in response to the problem of failing MFM drives. Consider one of those boards if you determine the drive can't be salvaged.

    Chuck

    Leave a comment:

Working...
X