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

Disk Boot Faulure on good hardware

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

    Disk Boot Faulure on good hardware

    So this machine I built will not boot form floppy. IT will boot from IDE if it wants to but first I need to floppy boot it to install DOS.

    Same as the DOM boot thread, ASUS ISA-486SV2 Rev. 3.1 and ISA combination floppy/IDE controller with the GoldStar PRIME 2 chipset. Both support 720k and 1.44mb floppy formats. Motherboard has a good battery and default CMOS configuration. Have tried two different floppy cables, have tried three other 3.5" floppy drives and I have both a 720K and 1.44mb floppy I have formatted and sys'd on another machine and verified they are bootable. This machine will not boot. It just says DISK BOOT FAILURE as soon as it tries to read from the floppy. That I can tell it's not corrupting or physically damaging the disks. I've also tried a different controller card with the same result. Have also tried with TURBO both turned on and off.
    There's three cards in this machine. The Disk I/O card, the VLB video card and a tape drive controller (which I've removed for testing with no change)

    Edited: As a test of my sanity I recabled the floppy drives and tried booting from a known good 360k 5.25" floppy. No change. I also rejumpered the motherboard as I had originally received and and swapped back in the 40mhz DX-40 I received it with. Still no go.
    Last edited by NeXT; April 25, 2021, 09:48 AM.
    [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
    --------------------------------------------------------------------------------------------
    [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

    = Excellent space heater

    #2
    Man I hate issues like yours. This is when I start trying the things that in my mind couldn't possibly be the issue. Looking at the setup you described I would try a standard ISA video card next. I know, VLB shouldn't cause any issues, but like I said, time to try anything. I would then try playing the binary shuffle by moving the I/O and video cards to different combinations of slots.

    I just refurbished a Micron Pentium 133 system that I installed a 3D Virge 4MB video card into. The video card will *only* fire up in PCI slot #1. Why? Don't know. But it wasn't until I started playing the binary shuffle that I figured that out. The other PCI slots work fine with different cards (NIC, Sound, Etc..) Just weird.

    Comment


      #3
      I'll dig into my board bins today and see if I can find just a generic ISA video card to swap in.
      [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
      --------------------------------------------------------------------------------------------
      [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

      = Excellent space heater

      Comment


        #4
        Originally posted by NeXT View Post
        So this machine I built will not boot form floppy. IT will boot from IDE if it wants to but first I need to floppy boot it to install DOS.

        Same as the DOM boot thread, ASUS ISA-486SV2 Rev. 3.1 and ISA combination floppy/IDE controller with the GoldStar PRIME 2 chipset. Both support 720k and 1.44mb floppy formats. Motherboard has a good battery and default CMOS configuration. Have tried two different floppy cables, have tried three other 3.5" floppy drives and I have both a 720K and 1.44mb floppy I have formatted and sys'd on another machine and verified they are bootable. This machine will not boot. It just says DISK BOOT FAILURE as soon as it tries to read from the floppy. That I can tell it's not corrupting or physically damaging the disks. I've also tried a different controller card with the same result. Have also tried with TURBO both turned on and off.
        There's three cards in this machine. The Disk I/O card, the VLB video card and a tape drive controller (which I've removed for testing with no change)

        Edited: As a test of my sanity I recabled the floppy drives and tried booting from a known good 360k 5.25" floppy. No change. I also rejumpered the motherboard as I had originally received and and swapped back in the 40mhz DX-40 I received it with. Still no go.
        From my experience with 486's of that ilk, I would double check the BIOS settings and make sure the onboard floppy controller is disabled. Other than that maybe swap out the RAM. I know, not much wisdom here but worth mentioning.
        Last edited by Agent Orange; April 25, 2021, 12:14 PM.
        Surely not everyone was Kung-fu fighting

        Comment


          #5
          Have you tried a different FDD controller? had as PS/2 Model 65sx that with a known good disk, FDD and cable, refused to boot. AFAIK the FDD controller is bad. Also check boot sector virus. BTW your youtube is great.
          EISA .cfg Archive | Chip set Encyclopedia

          Comment


            #6
            I'm on my fifth controller, in fact. At this point it is VERY unlikely to be a bad controller, cable, drive or floppy.

            So I switched out the VLB video card for a more generic ISA Trident to no avail, then I replaced the ram with 4mb that I know were tested and switched off the internal and external cache with no success. Time for the nuclear option.



            Different motherboard, same CPU, ram, VLB video card, power supply and the original controller card and it booted the floppy as soon as I had the drive configured. It has to be the motherboard.
            There is three revisions of this board. The 2.4, the 2.5 and the 3.1 that I have and guess which one I cannot find the jumper charts for? (and yes things changed between revisions). This board has no onboard I/O or disk controllers and its your regular AMI BIOS.

            Edited: sorry, the jumper designations for the 3.1 exist but they're really confusing. Since the system presumably was configured as-is when I got it it should already work fine so I'm stumped.
            Last edited by NeXT; April 25, 2021, 12:50 PM.
            [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
            --------------------------------------------------------------------------------------------
            [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

            = Excellent space heater

            Comment


              #7
              Okay here's a hot take.

              So I used this other motherboard to format and install MS-DOS on an IDE DOM, then I swapped that out for the Asus board and booted up using the C: drive.
              MS-DOS reports a Data Error when you try to access either floppy drive but otherwise the system seems to be running fine, so whatever is causing the floppy system specifically to malfunction is not otherwise interfering with the rest of the computer or MS-DOS, but at least now we have a way to load any diagnostic programs anyone can think of that might better answer what is going on.
              [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
              --------------------------------------------------------------------------------------------
              [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

              = Excellent space heater

              Comment


                #8
                I noted a past thread on these forums.
                My recorded summary is, "Thread 42994: Acer VI15G motherboard. SETUP option 'video cacheable option' preventing boot from floppy."
                An example of how odd the relationship between symptom and cause can be.

                (BTW. The recent migration of vBulletin appears to have renumbered the old threads.)

                Comment


                  #9
                  Nope, disabling video BIOS shadow/caching doesn't fix it either. As a shot in the dark I also went through the DOS Benchmark Pack to see if I could make it choke on something like bad cache, a bad CPU or ANYTHING really. All I could determine is that the BIOS has the Y2K bug (but I set it to 1994 so that didn't matter here) and I underestimated the performance of this VLB Trident card.
                  [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
                  --------------------------------------------------------------------------------------------
                  [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

                  = Excellent space heater

                  Comment


                    #10
                    Someone over on VOGONS suggested I verify that we have working DMA by testing to see if both serial ports work. They do.
                    The floppy controller needs DMA 2 in order to use the floppy drive. Sure enough I pulled out the other POST card and I can see IRQ6 when the floppy drive is polled but no DMA.



                    I beeped out and verified that DRQ2 and DACK2 was present on each ISA slot and that looked okay. DACK2 connects to U24 pin 13 (74LS138N) which goes to the chipset while DRQ2 goes to U8 pin 13 (74F151BN) and I could beep all the pins back to the chipset, except for Z̅. It seems to connect to a trace layered in the board but was not connected to the chipset directly. I have no idea if that could be the fault or if it's not important in this case.


                    Edited: Oops, the POST card was not fully seated in the board. We do actually have DMA2.

                    Last edited by NeXT; April 26, 2021, 06:16 PM.
                    [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
                    --------------------------------------------------------------------------------------------
                    [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

                    = Excellent space heater

                    Comment


                      #11
                      Originally posted by NeXT View Post
                      Someone over on VOGONS suggested I verify that we have working DMA by testing to see if both serial ports work.
                      I beg your pardon but IMHO the serial ports don't use DMA. It is another matter using LPT ports in ECP mode. But to be honest, I have no idea to test that.

                      Having read all, my idea is that the FDC chip is broken. If the FDC is part of a bigger IC, then you can have a problem: replacing these ICs is a problem. And you have to find a replacement in the first place.

                      FYI: I have 8086 board that has a broken internal FDC so I know that it is possible.


                      With kind regards / met vriendelijke groet, Ruud Baltissen

                      www.baltissen.org

                      Comment


                        #12
                        Originally posted by Ruud View Post
                        Having read all, my idea is that the FDC chip is broken. If the FDC is part of a bigger IC, then you can have a problem: replacing these ICs is a problem. And you have to find a replacement in the first place.
                        Did you at all see the above post where I booted with no issues using a different motherboard but the same floppy drive, cable AND disk controller, then proceeded to see the fault persist on several other controllers?
                        [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
                        --------------------------------------------------------------------------------------------
                        [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

                        = Excellent space heater

                        Comment


                          #13
                          There are two settings to check in the BIOS:

                          1. Cache mode. If it is set to write-back, change it to write-through. A non-working floppy is one of the side effects when something is not compatible with WB mode (often with AMD CPUs)

                          2. Virus protection. Some Bioses of that time had a built-in virus protection that did strange things when accessing the mbr/boot sector. Disable that.

                          Comment


                            #14
                            It was something way more insane.
                            One of the three SN74F151's that handle DMA multiplexing for the chipset had a broken pin. The floppy controllers could all request DMA channel 2 but it would never reach the chipset. I desoldered it after suspecting it might be bad and swapped it with a neighboring chip, predicting the floppy would come back and the IDE channel would fail. Sure enough, it did.




                            I soldered a new leg onto the chip and it seems to be all good now.
                            [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
                            --------------------------------------------------------------------------------------------
                            [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

                            = Excellent space heater

                            Comment


                              #15
                              How the shiznit did that happen?

                              Awesome troubleshooting by the way.

                              Comment

                              Working...
                              X