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

how to dump BIOS to a file?

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

    how to dump BIOS to a file?

    Is there a utility available to dump the BIOS of a PC or XT
    to a file on diskette ? I have a couple of clone XT's that I'd
    like to backup the BIOS just in case I ever need to reburn.
    I imagine there might be a way to do this using DEBUG with the correct
    address. Ideally it would be an image that was ready to burn
    with an EEPROM burner in case the current BIOS chip died.

    I would prefer not to pull the chips from the mb to copy.
    Last edited by mikey99; May 31, 2008, 07:35 PM.

    #2
    Mbbrutman wrote a utility named 'PCjrcart', available at http://www.brutman.com/PCjr/pcjr_downloads.html

    The DEBUG method:
    If you know the address at which the BIOS starts and you know the BIOS size, you can suitably modify the following (saves 32K starting at F000 to file MYF000.BIN).

    Code:
    C:\> DEBUG
    
        -N MYF000.BIN          (resulting file will be named MYF000.BIN)
    
        -R BX                  (set BX=0000H/CX=8000H as count of bytes to write,  00008000H = 32K)
        BX 0000
        :0000
        -R CX
        CX 0000
        :8000
    
        -M F000:0 8000 0100    (copy 32K bytes from F000:0 to offset 0100 in local segment)
    
        -W 0100                (write from offset 0100 in local segment)
        Writing 8000 bytes
    
        -Q

    Comment


      #3
      Thanks - I didn't want to self promote.

      Debug gives you a pure dump.. PCjrcart can do that too, but it can also scan the BIOS area for extensions. This is useful for dumping the BIOS on cards like SCSI adapters, VGA cards, etc.

      Comment


        #4
        Thanks for the info. I ran pcjrcart using the rom dump option
        and it generated a 64KB file SYS_ROM.BIN. I edited the file
        using a binary editor and there is header info like PCJRCART
        date, time, filename ,etc.

        If I had an EPROM burner, could I burn this file directly to
        an EPROM, plug into my machine and it would work ?
        Or would I be better off making a 'pure' dump using DEBUG?

        Comment


          #5
          Your ROM is probably not 64K. It is for a Jr, but on the PC and XT it is much smaller. (The PCjr has Diagnostics and other stuff in ROM.) You need to know the size of the ROM for your machine. There are options on pcjrcart for getting particular memory regions. You can do the same thing with debug, but it might be easier with pcjrcart.

          I think that there is an option on PCjrcart to suppress the header .. you definitely don't want the header showing up.

          Comment


            #6
            For some reason, when I dump my model 25's BIOS, it comes out as 37KB.. wtf?

            thats when using an EEPROM programmer..
            IBM PS/2 Model 25, NEC V30 8MHz, 640KB RAM, ATI VGA Wonder XL, 2GB SSD, Ethernet, DR DOS 6/GeOS, Xircom PE3 Ethernet

            Comment


              #7
              If you run MSD (Microsoft Diagnostics), it will tell you what address region your system ROM occupies, and also for any option ROMs (video, hard drive controller, etc.) you have installed.

              Generally if you dump more address space than your ROM actually occupies, the unused space will show up as a stream of 00 or FF hex.

              Comment


                #8
                Originally posted by vwestlife View Post
                Generally if you dump more address space than your ROM actually occupies, the unused space will show up as a stream of 00 or FF hex.
                Or, if the address lines aren't completely decoded, additional copies of the ROM.

                Comment


                  #9
                  Originally posted by modem7 View Post
                  Code:
                  C:\> DEBUG
                  
                      -N MYF000.BIN          (resulting file will be named MYF000.BIN)
                  
                      -R BX                  (set BX=0000H/CX=8000H as count of bytes to write,  00008000H = 32K)
                      BX 0000
                      :0000
                      -R CX
                      CX 0000
                      :8000
                  
                      -M F000:0 8000 0100    (copy 32K bytes from F000:0 to offset 0100 in local segment)
                  
                      -W 0100                (write from offset 0100 in local segment)
                      Writing 8000 bytes
                  
                      -Q
                  If you got a REALLY slow computer, you might change -M F000:0 8000 0100 to -M F000:0 7FFF 0100, saving you some nanoseconds :P

                  You can repeat the process with -N MYF800.BIN and -M F800:0 FFFF 0100 instead if you want the other half of the BIOS.
                  Last edited by per; June 3, 2008, 02:36 AM.
                  Current systems owned by me:
                  Vintage:IBM PC/XT submodel 087 ( 1983 ), [Kon]tiki-100 rev. C (1983), Compaq Portable I ( 1984 ), IBM PC/XT submodel 078 ( 1985 ), IBM PC/XT286 ( ~1986 ), 3x Nintendo Entertainement Systems ( 1987 ).
                  Obsolete:Commodore A500 ( ~1990 ), IBM PS/2 model 70/386 type 8570-161 ( 1991 ), Atari Lynx II ( ~1992 ), Generic Intel 486SX PC ( ~1993 ), AT/T Globalyst Pentium w/FDIV bug MB ( 1994 ), Compaq 486DX4 laptop ( ~1995 ).

                  Comment


                    #10
                    If you got a REALLY slow computer, you might change -M F000:0 8000 0100 to -M F000:0 7FFF 0100, saving you some nanoseconds :P
                    Are confusing 'number of bytes to move' with 'last address'?

                    Comment


                      #11
                      I wrote a utility to save the BIOS ROM a few years ago (aimed at Apricot PCs, but it should work on genuine IBMs and compatibles as well.

                      http://www.seasip.demon.co.uk/Misc/saverom.zip

                      It's a bit more convenient than fiddling with DEBUG.

                      Comment


                        #12
                        Originally posted by modem7 View Post
                        Are confusing 'number of bytes to move' with 'last address'?
                        Look at this:
                        http://mirror.href.com/thestarman/as...g/debug2.htm#M

                        But it is only a minor detail nobody needs to care about anyways. Both ways work so use the one you prefere.
                        Current systems owned by me:
                        Vintage:IBM PC/XT submodel 087 ( 1983 ), [Kon]tiki-100 rev. C (1983), Compaq Portable I ( 1984 ), IBM PC/XT submodel 078 ( 1985 ), IBM PC/XT286 ( ~1986 ), 3x Nintendo Entertainement Systems ( 1987 ).
                        Obsolete:Commodore A500 ( ~1990 ), IBM PS/2 model 70/386 type 8570-161 ( 1991 ), Atari Lynx II ( ~1992 ), Generic Intel 486SX PC ( ~1993 ), AT/T Globalyst Pentium w/FDIV bug MB ( 1994 ), Compaq 486DX4 laptop ( ~1995 ).

                        Comment

                        Working...
                        X