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 M24 XP1050 can't get it to boot from HD

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

    #16
    I was aware of the use of DEBUG.COM to access BIOS routines, but I thought the controller supplied with the M24 had no onboard BIOS, in fact the BIOS EPROM is missing. I think it's under direct control of the M24 BIOS.
    I found the LLF utility for the AT&T6300 that Trixter uploaded some time ago and it did the job. Then FDISK and FORMAT from Olivetti MSDOS 3.30, a bit of SYS C: and the M24 is back online, shiny & new (well... almost )
    __________________________
    http://www.museopc.it
    - 300 computers and counting -

    Comment


      #17
      Olivetti's own notes say tha there could be several extension BIOSes or none for the WX1. So even they weren't sure. My own 6300 has an 80MB hard card, so while the 6300 BIOS reports the presence of a hard disk, it stops short of reporting the capacity. Just a message like "Hard disk is" and then nothing. It all works, just a little curious.

      Comment


        #18
        Originally posted by Gabriele72 View Post
        Thanks everyone for the answers. I had no idea different MFM controllers weren't compatible at low level format.
        I have the original DOS 3.30 diskettes and the M24 Customer Test disk but I seem to miss the HD utilities.
        Will the debug command work to format the HD or do I need something else, if not could someone send me a disk image with the necessary setup utilities?
        Thanks in advance.
        Hi Gabriele, would it be possible for you to make a disk image of that Customer Test disk?

        Comment


          #19
          Originally posted by Chuck(G) View Post
          Why is anyone even arguing about this? The link I gave has complete documentation, right down to Olivetti's documentation for the WX1, service manual (which covers installation of a hard disk), and operations guide. The software has all of the original software images--and a program to write those images to disk. Heck, somewhere on the site, there's a schematic of the system.

          Would that other old systems be as well documented!
          Some people just love to argue lol

          Comment


            #20
            Hi,

            I am trying to restore the HDD of an Olivetti M24.
            The BIOS chip on the DTC (Digital Data Corporation) 5150BX4 disk controller is missing.

            1) Is that a problem? Is there another HDD ROM on the motherboard from Olivetti ?

            2) Where is the low level format utility LLF? Is it in "AT&T PC6300 (M24) Customer Diagnostics Disk Image 360K" on the http://www.olivettim24.hadesnet.org/download.html website ?

            Thanks
            Last edited by tonata; April 25, 2020, 12:21 PM.

            Comment


              #21
              This is what you're looking for: ftp://ftp.oldskool.org/pub/drivers/A...s/A6_LLFUT.ZIP
              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


                #22
                Originally posted by tonata View Post
                Hi,

                I am trying to restore the HDD of an Olivetti M24.
                The BIOS chip on the DTC (Digital Data Corporation) 5150BX4 disk controller is missing.

                1) Is that a problem? Is there another HDD ROM on the motherboard from Olivetti ?

                2) Where is the low level format utility LLF? Is it in "AT&T PC6300 (M24) Customer Diagnostics Disk Image 360K" on the http://www.olivettim24.hadesnet.org/download.html website ?

                Thanks
                1) It depends on the dip switches on the mainboard to decide if that is a problem or not. With controllers without BIOS, like this one, you select the harddisk parameters by DIP switches on the mainboard and it is using M24 BIOS inside HDU funcrion. But you can disable that and use controllers with own BIOS. The 2nd makes sens if you have a very intelligent controller where you can input other values like those from the DIP switches.

                2) With HDU support by M24 BIOS you have to use the tool on the customer test disk. When using controller's own BIOS, then start the LLF with the debug command of that specific controller.

                m24sp.jpg m240ll.jpghdubios.jpg
                Last edited by 1ST1; April 26, 2020, 06:40 AM.
                <album>

                Comment


                  #23
                  Thanks a lot!!!

                  It is DSW1/3 and now the computer sees the fixed drive, which is a great! For XT-IDE I think it should be off (yes because it is an external ROM).

                  Unfortunately my rather contemporary computer with 5.25 floppy is gone (motherboard is burnt). I will appreciate if you know how to write the image (.img) from a 8086 clone?
                  Last edited by tonata; April 27, 2020, 03:26 AM.

                  Comment


                    #24
                    There are many ways to write disk images directly from DOS; I use IMG2DSK (one copy is at ftp://ftp.oldskool.org/pub/misc/Soft...skDumps/progs/ ) but there are others too, such as http://www.brutman.com/PCjr/downloads/DskImage.zip . But how will you get the disk image over to you 8086 to write it?
                    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


                      #25
                      Hi,

                      Thank you all!!!!

                      It worked with the AT&T low level format tool lowform.exe. I could not write the image of the Olivetti diagnostic disk on a floppy disk though.

                      Anyway I am quite happy

                      Maybe the only small thing is how to enter a defect from the back of the hard drive:
                      TRK HD byte_count **** (bits)
                      152 02 05772 04

                      into the lowform.exe which expects: CYL HEAD SECTOR CODE

                      So it should be: 152 02 and then ?????

                      My hard drive is 306 cylinders and 4 heads, 10 MB.

                      Comment


                        #26
                        I think you can not enter the sector. Just tracks.
                        <album>

                        Comment

                        Working...
                        X