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

(Olivetti M24SP) WD1002S-WX2 recognizes hard drive sometimes as D instead of C

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

    (Olivetti M24SP) WD1002S-WX2 recognizes hard drive sometimes as D instead of C

    Hi guys,

    I have a strange issue with my Olivetti M24SP. Its WD1002S-WX2 Hard Disk/Floppy Controller sometimes recognizes the hard drive as drive D instead of C, causing problems during startup of DOS. Besides of the incorrect drive letter, everything else works fine.
    I already replaced the BIOS battery with a new 3,6V NiCD cell because I noticed that date/time were incorrect after a while of not turing it on, but this didn't help. Any idea whats wrong?
    I believe the jumpers are correct according to https://stason.org/TULARC/pc/hard-di...-driv-222.html although I didn't touch them so they should be still factory-set by Olivetti - the previous owner was a woman which didn't use the machine that often and had other interests than IT and playing around with jumpers.

    Last edited by freakedenough; August 15, 2020, 11:46 PM.

    First own PC in 2003: AMD K6-2 500MHz, 320MB RAM, 40GB IBM HDD, 50x CD-ROM, 8x4x24 CD/RW, 100MBit LAN, 32MB ATi Rage 128 Pro, Windows XP

    #2
    Originally posted by freakedenough View Post
    Its WD1002S-WX2 Hard Disk/Floppy Controller sometimes recognizes the hard drive as drive D instead of C
    An example of when I have seen the only hard drive become D: rather than C: is:

    (In the following, I have left out the BIOS interface. It does not contribute to this particular discussion.)

    At the hardware/physical layer:
    - The floppy disk controller presents the first attached floppy drive as floppy drive 0 (floppy drive 1 for the second drive, etc.)
    - The hard disk controller presents the first attached hard drive as hard drive 0 (hard drive 1 for the second drive).

    When DOS boots, it assigns logical drives (A:, B:, C:, etc.) to the physical drives/partitions.

    Early versions of DOS did the assignment differently to later versions. I think it may have been DOS 4 when the change was made.

    In a system with three floppy drives in the system (the motherboard BIOS thinks there are three), and one hard drive, the assignment is:
    Early DOS: Floppy drive 0 becomes A:, floppy drive 1 becomes B:, floppy drive 2 becomes C:, hard drive 0 becomes D:
    Later DOS: Floppy drive 0 becomes A:, floppy drive 1 becomes B:, floppy drive 2 becomes D:, hard drive 0 becomes C:

    Just now, on my IBM 5160, I got the one and only hard drive (DOS 3.3 installed) booting as D: by changing the floppy count switches on the motherboard from 2 to 3. (It is one of the reasons why when I attach a third floppy drive, an external one, I leave the floppy count switches set to 2, and load DRIVER.SYS for the third floppy drive.)

    When I tried to access C: drive, I got a "Not ready error ..." message, not the "General Failure ..." message that you see. That suggests that 'motherboard BIOS sometimes thinks that there are three floppy drives' is not the situation that you are in. But, if you are in that situation, tools like CheckIt are expected to show three floppy drives (CheckIt 2.1 displayed "Floppy Drive(s): A:Present, B:Present, C:Present"). Also, in the fault condition, you could try a floppy boot from say, DOS 6.

    Comment


      #3
      The 24(SP) battery is only for clock, nothing else.

      Did you disabled onboard HDU support? Otherwise the onboard HDU bios may detects the drive first, and then the WD bios again...

      m24hdu.jpg
      <album>

      Comment


        #4
        Turning this switch off just gave me error1.jpg
        error1.jpg

        But in reverse and according to https://stason.org/TULARC/pc/hard-di...-driv-222.html I removed the jumper from W3 (card BIOS OFF) on the WD card but turned the switch on the motherboard back on, which then gave me error2.jpg
        error2.jpg

        until I placed the WD card into slot 1 instead of 3 (from right), now it boots as regular and I can access both C and A.


        Lets see how this turns out on a long term, I will update the thread later.

        Thanks for your tip!

        First own PC in 2003: AMD K6-2 500MHz, 320MB RAM, 40GB IBM HDD, 50x CD-ROM, 8x4x24 CD/RW, 100MBit LAN, 32MB ATi Rage 128 Pro, Windows XP

        Comment


          #5
          What kind of software do you have on that M24SP? That screen logo looks good and would also be nice on my two M24SP...
          <album>

          Comment


            #6
            thanks! its just dos 3. i made the logo on my own as an echo output in autoexec.bat, which i am glad to share:
            AUTOEXEC.zip

            First own PC in 2003: AMD K6-2 500MHz, 320MB RAM, 40GB IBM HDD, 50x CD-ROM, 8x4x24 CD/RW, 100MBit LAN, 32MB ATi Rage 128 Pro, Windows XP

            Comment


              #7
              Nice, thanks!
              <album>

              Comment


                #8
                Okay, the issue just popped up again. Any other explanations? :\

                First own PC in 2003: AMD K6-2 500MHz, 320MB RAM, 40GB IBM HDD, 50x CD-ROM, 8x4x24 CD/RW, 100MBit LAN, 32MB ATi Rage 128 Pro, Windows XP

                Comment


                  #9
                  Checked again that thing. You have selected the dip switches to use the M24 internal HDU BIOS and not the one on the controller. When looking at the controller closely this is right, as the ciontroller has an empty ROM socket.

                  M24 BIOS is 1.43, that is the latest which is usually found. Currently I have no idea how that behaviour could happen. Maybe using some of system information tools to see what kind/size it detects for 1st drive? Maybe that gives an idea.

                  Anyhow, I have a 2nd idea to try. Get a WD 1002WX2 BIOS chip, plug it on the controller, enable it by controller jumper, and disable M24 HDU BIOS via mainboard dip switch. But maybe you have to lowlevel format and reinstall the harddisk. Maybe that fixes the issue by using different controller BIOS.
                  <album>

                  Comment


                    #10
                    The M24SP BIOS source code is online, IIRC; it might be worth checking the HD init routine there to see what could make it think there are two drives.
                    Offering a bounty for:
                    - A working Sanyo MBC-775 or Logabax 1600
                    - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                    Comment


                      #11
                      If anyone can read the assembler code, would be interesting. However, I meanwhile migrated to a self-soldered XTIDErev3 and will turn on the original hard disk only from time to time.

                      First own PC in 2003: AMD K6-2 500MHz, 320MB RAM, 40GB IBM HDD, 50x CD-ROM, 8x4x24 CD/RW, 100MBit LAN, 32MB ATi Rage 128 Pro, Windows XP

                      Comment


                        #12
                        XTIDE will perform better anyway, so no need to pursue it further. Remember to select the correct BIOS options for compatibility+speed. http://www.vcfed.org/forum/showthrea...012#post575012 has some more info on the M24, I don't know if the M24SP has the same bus issues (it likely doesn't, but the speed comparisons are still interesting.)
                        Offering a bounty for:
                        - A working Sanyo MBC-775 or Logabax 1600
                        - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                        Comment


                          #13
                          M24SP is 99% the same as M24. Only difference is that it runs at 10 MHz.
                          <album>

                          Comment


                            #14
                            But does it have the same bus order/swap problem? (16-bit port reads return swapped bytes)
                            Offering a bounty for:
                            - A working Sanyo MBC-775 or Logabax 1600
                            - Music Construction Set, IBM Music Feature edition (has red sticker on front stating IBM Music Feature)

                            Comment


                              #15
                              It's the same mainboard, just different clock speed. So why it should be different in bus order?
                              <album>

                              Comment

                              Working...
                              X