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

XTIDE V4 troubleshooting IBM 5155

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

    XTIDE V4 troubleshooting IBM 5155

    I recently built an XT-IDE kit V4 from glitchworks... the EPROM did not appear to be programmed so I burned v 1.1.5 of the Universal XT-IDE bios (XT version).

    I've tried various dip switch combinations and the closest I've gotten is I see the following when I boot with no harddrives attached:

    ROM D000
    ERROR PRESS [F1] TO CONTINUE

    I figured I should see some sort of Bios message from the XT-IDE telling me no drives are attached.

    Anyone have any ideas? I can't seem to find any instructions for the board, or the dip switch positions.


    Thanks

    #2
    Originally posted by mykrowyre View Post
    I recently built an XT-IDE kit V4 from glitchworks... the EPROM did not appear to be programmed so I burned v 1.1.5 of the Universal XT-IDE bios (XT version).

    I've tried various dip switch combinations and the closest I've gotten is I see the following when I boot with no harddrives attached:

    ROM D000
    ERROR PRESS [F1] TO CONTINUE
    I think Glitch pre-programs the EEPROM with XUB v1.1.5 for the Kits, When you flashed the EEPROM did you configure the XUB first before flashing ?, If you didn't i would expect to see that error, You must configure first and then flash.

    I figured I should see some sort of Bios message from the XT-IDE telling me no drives are attached.
    A fully working and properly configured XT-IDE / XUB will show " Not Found ", for later revisions of the XUB but can't remember if it's the same for v1.1.5 However you must have drives attached when Auto configuring when using the newer XUB & XTIDECFG.COM.

    Anyone have any ideas? I can't seem to find any instructions for the board, or the dip switch positions.
    Modem7 has info on Jumper / Switch settings on his website http://minuszerodegrees.net/xtide/re...%20general.htm

    Comment


      #3
      Code:
      ROM D000
      ERROR PRESS [F1] TO CONTINUE
      This usually means you didn't generate the checksum byte at the end of the ROM. The BIN images of the XUB don't have a checksum byte at the end by default (not sure why this is). The XTIDECFG program will generate it for you.

      Originally posted by Malc View Post
      I think Glitch pre-programs the EEPROM with XUB v1.1.5 for the Kits, When you flashed the EEPROM did you configure the XUB first before flashing ?, If you didn't i would expect to see that error, You must configure first and then flash.
      That's correct, they all get pre-programmed in an old prototype rev 3 board with a ZIF socket, to ensure they meet spec on the actual ISA bus. I was having problems with defective EEPROMs from a previous supplier so I started pre-programming all of them. The current supplier (Mouser) hasn't given a single defective EEPROM, but people seem to like having them pre-programmed, so that's what I do!
      Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

      Comment


        #4
        Originally posted by glitch View Post
        Code:
        ROM D000
        ERROR PRESS [F1] TO CONTINUE
        This usually means you didn't generate the checksum byte at the end of the ROM. The BIN images of the XUB don't have a checksum byte at the end by default (not sure why this is). The XTIDECFG program will generate it for you.



        That's correct, they all get pre-programmed in an old prototype rev 3 board with a ZIF socket, to ensure they meet spec on the actual ISA bus. I was having problems with defective EEPROMs from a previous supplier so I started pre-programming all of them. The current supplier (Mouser) hasn't given a single defective EEPROM, but people seem to like having them pre-programmed, so that's what I do!
        Thanks yeah I was the one on ebay who had the defective TL866 wipe my eprom. I purchased a new one and it works but I didnt know about the checksum when i reprogrammed the eprom.. Problem is, I dont have a way to get the XTIDECFG program to the PC short of typing the hex manually and unhexing it with a basic program.

        Any chance you could send me the 1.1.5 rom image with checksum, or tell me the checksum value assuming rom version is the same? I guess I could also look at the code and see how the checksum is calculated and add it manually but that is less fun.

        Thanks
        Tom
        electronictreasure

        Comment


          #5
          I can get you a ROM image if necessary; however, you can run XTIDECFG on any DOS PC, it should even run in DOSBOX on Linux/Mac/Windows/whatever.
          Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

          Comment


            #6
            I'd use a more recent revision and jumper the XT-IDE for Hi Speed mode, r591 works fine on my r4 cards as does the new r601. I often use my XP PC to configure the XUB and burn to Eproms.
            Last edited by Malc; February 24, 2019, 03:04 PM.

            Comment


              #7
              Yeah, you can certainly use a newer XUB revision -- I ship v1.15 simply because, in my experience, it's easier for folks to figure out if their kit-built board is working. We've had several cases where v1.15 worked fine but newer revisions had issues.
              Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

              Comment


                #8
                Ah ok I see xtidecfg will save a new rom image. Ok i'll try it thanks.

                Comment


                  #9
                  Thanks guys! I used the XTIDECFG on a 486 laptop, and saved the modified bios. That generated the correct checksum, which worked once burned to the eprom.

                  Cool!

                  Comment


                    #10
                    Excellent, glad you got it going! I need to actually finish writing up a proper manual covering all of this...!
                    Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                    Comment


                      #11
                      Originally posted by glitch View Post
                      Yeah, you can certainly use a newer XUB revision -- I ship v1.15 simply because, in my experience, it's easier for folks to figure out if their kit-built board is working. We've had several cases where v1.15 worked fine but newer revisions had issues.
                      Yep i understand why, I used v1.1.5 for a long time and found it very stable, IIRC around early beta 2 or 3 it got a bit buggy but improved and has come a long way since v1.1.5 (r70). I suspect a lot of people are using an older revision as it does the job and works for them, " If it ain't broke don't fix it " sort of thing.

                      Comment


                        #12
                        It does seem that a fair number of people upgrade to 2.x for high-speed mode, though. It does make a *significant* difference in speed. Of course, even COMPAT mode with v1.15 is faster than my old MFM drive setup

                        It would probably help if there were binary images available for 2.x that are 8K *and* have the full boot menu instead of the hotkeys menu.
                        Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                        Comment


                          #13
                          Originally posted by glitch View Post
                          ...It would probably help if there were binary images available for 2.x that are 8K *and* have the full boot menu instead of the hotkeys menu.
                          I've no idea what that would involve setting it up server side, Though you can always build from source which is what i do, There's really little difference between the HotKey Bar and Boot Menu except of course the Boot Menu display's more info and more recently more colour schemes have been added which requires the BootMenu Module. I can see the attraction to the BootMenu though.

                          Comment


                            #14
                            Originally posted by glitch View Post
                            The BIN images of the XUB don't have a checksum byte at the end by default (not sure why this is).
                            Probably because it's an extra step in the build process that wasn't even possible until GregLi added an option to the makefile that invokes a perl script to calculate the checksum. NASM can't do it on its own.

                            So the only other option would be to use the configurator (XTIDECFG) and create the checksum manually but that would almost certainly be a waste of time since 99 times out of 100 the user need to configure the BIOS for his or her machine anyway. I'm actually amazed that the concept of a ROM that needs to be configured is so strange to people. I have on more than one occasion seen videos on youtube (or images elsewhere) where people boot their vintage machines and something like this is clearly visible;
                            Code:
                            Master at 1F0h: Generic 1234
                            Slave  at 1F0h: not found
                            Master at 0h: not found
                            Slave  at 0h: not found
                            Looking for a cache card for the "ICL ErgoPRO C4/66d V"

                            Comment


                              #15
                              Yeah, I need to finish writing a manual, complete with screenshots of the XUB configuration/flashing process...

                              I wrote a little C program to calculate the checksum and print it, or optionally stick it in the last byte of the ROM. This was back when Hargle's BIOS was the thing to hack on.

                              I'd think a "default options with checksum" build for the base XUB images would be equally sensible, but it's not my project I'll probably start building my own 8K ROM images at some point, with the full menu included. Another project for another day, though.
                              Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

                              Comment

                              Working...
                              X