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

optromloader: IBM PC/Clone 8086+ floppy-loading of option roms.

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

    optromloader: IBM PC/Clone 8086+ floppy-loading of option roms.

    A few days ago, I burned the wrong image into my last EPROM, and was left unable to get XTIDE Universal BIOS working on my 486. At least until I get an eprom eraser or more roms.

    I looked for ways to load the option rom into memory instead, and the solutions I found were not great.

    So I wrote my own: https://github.com/rvalles/optromloader

    It works great on the 486, and also works great in emulated PC/AT/XT and clones. This includes PCem's 5150.

    But I have no real <32 bit hardware to try it on. There's hope somebody here will.
    Last edited by dmac; September 26, 2021, 08:31 PM. Reason: <32 bit
    Got an Amiga and a null-modem cable? Try amigaXfer today!

    #2
    Interesting.
    With kind regards / met vriendelijke groet, Ruud Baltissen

    www.baltissen.org

    Comment


      #3
      I tried to use this but I am a noob and missing some information. So for windows whats needed to make this?
      I have fasm , I installed make, but I get

      >make

      fasm -d bios_drive=0 -d build_date="`date -u +%Y%m%d%H%MZ`" -d readblock_retries=7 -d sectors_per_track=18 optromloader.asm optromloader18
      flat assembler version 1.73.28
      usage: fasm <source> [output]
      optional settings:
      -m <limit> set the limit in kilobytes for the available memory
      -p <limit> set the maximum allowed number of passes
      -d <name>=<value> define symbolic variable
      -s <file> dump symbolic information for debugging
      make: *** [Makefile:15: optromloader18] Error 1

      Comment


        #4
        Originally posted by Theoryboy View Post
        I tried to use this but I am a noob and missing some information. So for windows whats needed to make this?
        I have fasm , I installed make, but I get

        >make

        fasm -d bios_drive=0 -d build_date="`date -u +%Y%m%d%H%MZ`" -d readblock_retries=7 -d sectors_per_track=18 optromloader.asm optromloader18
        flat assembler version 1.73.28
        usage: fasm <source> [output]
        optional settings:
        -m <limit> set the limit in kilobytes for the available memory
        -p <limit> set the maximum allowed number of passes
        -d <name>=<value> define symbolic variable
        -s <file> dump symbolic information for debugging
        make: *** [Makefile:15: optromloader18] Error 1
        I've never tried to build it on Windows (I mainly use Linux).

        My guess is that the build date part doesn't become a date (on linux, it would get replaced by the output of the command that's `wrapped like this`) . You can just hardcode that parameter.

        I ran that date command now, it did output 202109261717Z, so you can just edit the makefile, and replace the date= line in that format, like this:

        Code:
        date = \"202109261717Z\"
        Else, you can just put any text there really, as long as it is the same length or shorter.

        Worst case scenario, you can use the binary build and just concatenate optromloader18 (or whatever appropriate) with the optrom image and pad to floppy image size.

        I'll try and boot windows sometime soon, to see if I can improve the process without breaking the Linux build.
        Last edited by dmac; September 26, 2021, 10:14 AM. Reason: makefile
        Got an Amiga and a null-modem cable? Try amigaXfer today!

        Comment


          #5

          Perfect thats what I needed. I just ran this command
          for a 360K floppy

          fasm -d bios_drive=0 -d build_date="202109261717Z" -d readblock_retries=7 -d sectors_per_track=9 -d pad_to_bytes=368640 -d include_optrom="optrom.bin" optromloader.asm fd360.img


          Thanks for this, it will be very useful
          You do not have permission to view this gallery.
          This gallery has 1 photos.

          Comment


            #6
            Originally posted by Theoryboy View Post
            Perfect thats what I needed. I just ran this command
            for a 360K floppy

            fasm -d bios_drive=0 -d build_date="202109261717Z" -d readblock_retries=7 -d sectors_per_track=9 -d pad_to_bytes=368640 -d include_optrom="optrom.bin" optromloader.asm fd360.img


            Thanks for this, it will be very useful
            Good to hear! I will try and make the build JustWork on Windows too.

            Note your screenshot shows 1.44M drives. You'll probably want to try with an emulated 5.25" drive and the 360K floppy, too

            I also do try a bunch of PCem targets before each release, to ensure nothing is broken. It does even work on emulated IBM PC (5150), as long as it's the 360K floppy.
            Last edited by dmac; September 26, 2021, 10:17 AM. Reason: IBM PC
            Got an Amiga and a null-modem cable? Try amigaXfer today!

            Comment


              #7
              Here its working on real hardware on my Tandy, I took the eeprom out of my card and it booted XTIDE and CF fine from 720K floppy.
              DISK COPY FAST would not write the floppy as it through it was a virus.
              rawrite3.com wrote the image to floppy perfectly.
              You do not have permission to view this gallery.
              This gallery has 1 photos.

              Comment


                #8
                Originally posted by Theoryboy View Post
                Here its working on real hardware on my Tandy, I took the eeprom out of my card and it booted XTIDE and CF fine from 720K floppy.
                DISK COPY FAST would not write the floppy as it through it was a virus.
                rawrite3.com wrote the image to floppy perfectly.
                Very nice! Date isn't YYYY-MM-DD (ISO, pet peeve...), but great otherwise.

                Interesting re: DISK COPY FAST. I suppose it would with anything that has a non-standard DOS bootblock . I use FDIMAGE by Robert Nordier, which is included in most i386 FreeBSD install media, in the tools directory. Find version 1.5 attached to this post.
                Attached Files
                Last edited by dmac; September 26, 2021, 05:09 PM. Reason: whitespace
                Got an Amiga and a null-modem cable? Try amigaXfer today!

                Comment


                  #9
                  As promised, I rebooted and fixed Windows build.

                  Make should work now.
                  Last edited by dmac; September 26, 2021, 08:29 PM. Reason: grammar
                  Got an Amiga and a null-modem cable? Try amigaXfer today!

                  Comment


                    #10
                    This is darned handy for testing new optroms. Thanks for the work, dmac!

                    - Alex

                    Comment

                    Working...
                    X