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

Speeding Up the ADP-50L Boot

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

    Speeding Up the ADP-50L Boot

    I have an ADP-50L card with 2.18T BIOS. That card displays a splash screen showing the contact information of the maker, Silicon Valley Computer, for several seconds. That is no longer necessary and I assume that the wait time has nothing to do with the card's internal operations. I do not know how to modify the BIOS to remove the wait, I have attached it as a link so someone else may be able to cut that whole screen out. Perhaps this can be a first step to enabling Universal XT-IDE BIOS support.

    http://www.mediafire.com/download.php?zrarlb16lshakor
    My Retro Computing and Vintage Gaming Blog : http://nerdlypleasures.blogspot.com/

    #2
    I can't help with the bios but just a thought have you tried replacing the bios chip with an XTIDE Bios chip, I have a silicon valey adp-60/70 in my old Zenith and replaced the original bios chip with the XTIDE and it works great, gets rid of the splash screen and it seem's to be a lot faster on boot up too.

    Regards
    Malc

    Comment


      #3
      I doubt it would work, the ADP 60/70 has a standard 16-bit IDE port and uses port mapping. The 50L is an 16-bit to 8-bit translating IDE interface and uses memory mapping to speed data transfers. If I had an EPROM programmer I would try it.
      My Retro Computing and Vintage Gaming Blog : http://nerdlypleasures.blogspot.com/

      Comment


        #4
        Patch location 097a in the ROM with C3 (RET) and then recompute the ROM checksum. Recompute the checksum for 0-17FE and put it into location 17FF (only the first 1800h locations of the ROM are used).

        If you have trouble figuring this out, I can do it and post the result.

        Comment


          #5
          Here is what I did :

          I deleted the bytes from 17FF to 19FF, including 17FF. I saved the result as a new file, ORIGINAL.ROM. I ran a program called CHECK8.EXE to calculate the resulting checksums. The checksum was FD. Using my hex editor, I changed the value at the location specified and saved it as a different file, MODIFIED.ROM. The checksum was 70.

          The original value at 1FFF of the dumped file (ADP50L218T.ROM before any deletions) was 03. So if that was the checksum of the original 0-17FE, I must have done something wrong, but what?
          My Retro Computing and Vintage Gaming Blog : http://nerdlypleasures.blogspot.com/

          Comment


            #6
            Did you truncate the file to 6,144 bytes before generating the checksum?

            Comment


              #7
              Originally posted by pearce_jj View Post
              Did you truncate the file to 6,144 bytes before generating the checksum?
              I truncated the file to 6,143 bytes, because I thought the 6,144th byte stores the checksum for the previous 6,413 bytes.
              My Retro Computing and Vintage Gaming Blog : http://nerdlypleasures.blogspot.com/

              Comment


                #8
                BIOS ROM checksums work by having the lowest 8 bits of the sum work out to 0. So, modified as I mentioned, the sum of the first 17FF bytes is 70H, to make this come out to XX00, you need to add 90H.

                Attached is the modified ROM. Let me know how it works.
                Attached Files

                Comment


                  #9
                  Originally posted by Chuck(G) View Post
                  Attached is the modified ROM. Let me know how it works.
                  Works great. I'm able to boot to a DOS command prompt on a 286/10MHz system in just under four seconds. Thanks, Chuck!

                  Comment


                    #10
                    ...and I only had to wait 8 years for the report!

                    Comment


                      #11
                      Originally posted by Cloudschatze View Post
                      Works great. I'm able to boot to a DOS command prompt on a 286/10MHz system in just under four seconds. Thanks, Chuck!
                      You're not happy with XUB running on that?
                      Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                      Comment


                        #12
                        Originally posted by Krille View Post
                        You're not happy with XUB running on that?
                        I still need to test with that. I've been unable to get any XUB builds to work with an "XT-IDE Deluxe" card in this persnickety system, so when I was able to get the ADP50L to boot with its standard BIOS (albeit, requiring both master and slave "drives" to be present), I decided to take a pause.

                        Comment

                        Working...
                        X