Announcement

Collapse

Forum Rules and 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.


Rule 1: 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.


Rule 2: 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.



Rule 3: 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.


Rule 4: "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.

Rule 5: 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

IBM Enhanced Corvette (SCSI) on a Model 55SX

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

    IBM Enhanced Corvette (SCSI) on a Model 55SX

    Hi there - looking for guidance on whether its possible to get an IBM "Enhanced Corvette" (Differential SCSI Fast/Wide Adapter) to work in a Model 55SX. I've read ambiguous things online, and some futzing around with reference and options disk has got me to the point that I do now have it at least registered with the system, it now appearing in the View Configuration page of the ref disk, and the system boots (to floppy) with no errors. I should mention the weird proprietary original IBM hard disk is long dead.

    Things that concern me are that -
    View Config indicates the SCSI card's BIOS is not loaded
    Running through Set Configuration errors, indicating that "An error occurred during the installation of the initialisation program"
    Running Set and View SCSI devices indicates that "An error occurred while saving the SCSI data."

    I currently have no way of attaching a SCSI disk (or expensive SCSI2SD gadget) currently so I don't know if that's the cause of some or all of these errors, but before I waste money on a hopeless cause maybe someone could give me a steer?

    Cheers!


    #2
    I'm afraid that's not a valid option (adapter) for a 55SX.

    Comment


      #3
      You want an adapter like the adaptec AHA-1640 or a future domain adapter with a built in scsi boot rom.

      the tribble, Spock, cheetah, corvette etc. will not work in a 55sx unfortunately.

      Comment


        #4
        Originally posted by pinkdonut666 View Post
        You want an adapter like the adaptec AHA-1640 or a future domain adapter with a built in scsi boot rom.

        the tribble, Spock, cheetah, corvette etc. will not work in a 55sx unfortunately.
        I'm afraid that's not quite correct.
        The technical requirements, Reference Diskette updates needed and systems supported vary:
        https://www.ardent-tool.com/IBM_SCSI/IBM_SCSI.html
        https://www.ardent-tool.com/SCSI/SCSI_Adapters.html
        https://www.ardent-tool.com/storage_adapters.html
        But it is the 8KB NVRAM requirement for the Corvette and Corvette "Turbo" which exclude support of the Model 55SX.
        Almost all others are possible. Current draw is more crucial for the 55SX as well.

        Comment


          #5
          Guys, I am having the same problem. Upgraded my 55SX with a Corvette SCSI Card and a SCSI2SD card. It only works, when the original legacy DBA disk is connected as well. If I disconnect the legacy Hard drive, I get the same errors as Jamie_S.

          The funny thing is that it works like a charme with the legacy disk in place. When I do FDISK I get the ESDI-DBA drive as DISK1 and the SCSI2SD Card as DISK2. Any solution yet ? THanks Christian

          Comment


            #6
            Originally posted by chrispl1974 View Post
            Guys, I am having the same problem. Upgraded my 55SX with a Corvette SCSI Card and a SCSI2SD card. It only works, when the original legacy DBA disk is connected as well. If I disconnect the legacy Hard drive, I get the same errors as Jamie_S.

            The funny thing is that it works like a charme with the legacy disk in place. When I do FDISK I get the ESDI-DBA drive as DISK1 and the SCSI2SD Card as DISK2. Any solution yet ? THanks Christian
            It's because the DBA-ESDI BIOS support is integrated into the system BIOS.Thus, it is impossible to either disable that or ensure the SCSI adapter's BIOS precedes it in memory, to swap drive orders.

            Comment


              #7
              Originally posted by WBST View Post

              It's because the DBA-ESDI BIOS support is integrated into the system BIOS.Thus, it is impossible to either disable that or ensure the SCSI adapter's BIOS precedes it in memory, to swap drive orders.
              Thanks for the feedback. I still think it ought to be possible to change at least the drive sequence, getting a chance to boot from a SCSI drive.

              Apparently Peter W. one of the PS2 Gurus from Germany changed the ESDI Adf file
              However, the original link with the modified file is not available anymore.

              Any thoughts ? Check the Modified ADF for ESDI and SCSI Coexistence paragraph

              IBM SCSI /A (ardent-tool.com)

              Comment


                #8
                Originally posted by chrispl1974 View Post

                Thanks for the feedback. I still think it ought to be possible to change at least the drive sequence, getting a chance to boot from a SCSI drive.

                Apparently Peter W. one of the PS2 Gurus from Germany changed the ESDI Adf file
                However, the original link with the modified file is not available anymore.

                Any thoughts ? Check the Modified ADF for ESDI and SCSI Coexistence paragraph

                IBM SCSI /A (ardent-tool.com)
                I'm afraid you're misunderstanding the difference between the DBA-ESDI controller and drive (@DF9F.ADF) with system BIOS, and the separate ESDI controller adapter (and drives) used in the Model 60 and 80 (@DDFF.ADF plus CDDFF.ADF) which has an on-adapter BIOS chip.
                http://www.mcamafia.de/mcapage0/adflist5.htm

                Comment


                  #9
                  Originally posted by WBST View Post

                  I'm afraid you're misunderstanding the difference between the DBA-ESDI controller and drive (@DF9F.ADF) with system BIOS, and the separate ESDI controller adapter (and drives) used in the Model 60 and 80 (@DDFF.ADF plus CDDFF.ADF) which has an on-adapter BIOS chip.
                  http://www.mcamafia.de/mcapage0/adflist5.htm
                  Thanks . I think you are right. I did not consider this difference. So bottom line is that there is no chance to >
                  a) Run the 55sx with SCSI only
                  b) run at least the SCSI drive as the primary hard drive while coexisting with the ESDI DBA native disk setup

                  The native disk is failing and I wanted to install OS/2 1.3 on the SCSI drive.

                  Comment


                    #10
                    By the way, would this mean that I face the same problem when trying to upgrade my Portable IBM P70 ?

                    Comment


                      #11
                      Originally posted by chrispl1974 View Post

                      Thanks . I think you are right. I did not consider this difference. So bottom line is that there is no chance to >
                      a) Run the 55sx with SCSI only
                      b) run at least the SCSI drive as the primary hard drive while coexisting with the ESDI DBA native disk setup

                      The native disk is failing and I wanted to install OS/2 1.3 on the SCSI drive.
                      For a 55SX:
                      A) isn't possible, it seems. The System BIOS wasn't designed to recognise a failed or absent DBA-ESDI drive. It was a limited low cost design.
                      B) isn't strictly possible, but could be achieved with a Boot Manager resident on the primary DBA-ESDI drive.

                      Comment


                        #12
                        Originally posted by chrispl1974 View Post
                        By the way, would this mean that I face the same problem when trying to upgrade my Portable IBM P70 ?
                        I haven't tested this out, but the following seems to imply that it is possible:
                        https://www.ardent-tool.com/8573/8573-P70.html#SCSI

                        Comment


                          #13
                          Originally posted by WBST View Post

                          For a 55SX:
                          A) isn't possible, it seems. The System BIOS wasn't designed to recognise a failed or absent DBA-ESDI drive. It was a limited low cost design.
                          B) isn't strictly possible, but could be achieved with a Boot Manager resident on the primary DBA-ESDI drive.
                          i bump this tread

                          another option should be to use the 65sx bios in the 55sx. this is something i'm gonna try soon.
                          i see no particular reason it wouldn't work. as the V1.05 of the reference diskette is shared between both models.

                          i tried to make work a "corvette turbo" in the 55, but i guess this one is really a no go. it can't even load the adf, saying there's an error.
                          edit : in fact i'm doubtful on the exact model, seems it's an enhanced corvette turbo. FRU is 93H7896.

                          edit bis : of course there's a reason
                          65sx use 128KB eprom, 55sx use 64KB...

                          yet another edit : ardent tool say 65sx also use 27512 eprom, so, let's try anyway.

                          and another... don't know what i did, but yes, they definely use the same eprom.
                          i probably did something wrong when checking files size... they all do 64KB each, for both machine.
                          really don't know how i get confused.
                          Last edited by whaka; November 25, 2021, 02:31 AM.

                          Comment


                            #14
                            well, i think i can say i was young and innocent with PS/2's...
                            of course, bioses of the 65 or 55ls don't want to work like that in the 55sx, would be too easy

                            Comment

                            Working...
                            X