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

5150 Compact flash formatting

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

    #16
    Originally posted by Blaze8088 View Post
    QEMU/KVM from libvirt under Manjaro Linux, probably a weird choice, but I already knew how to pass the CF as an HDD under it and wasn't sure how to do that when we tried PCEM.
    I would swear that I was able to do this using QEMU on a MacOS machine, IE, creating a bootable disk image from complete scratch. It was months ago so my memory is a tad sketchy but I think the one thing that may have differed from your procedure is I didn't try mapping the media (in my case an SD card because I'm using an SD->IDE adapter) directly to QEMU but instead made a "raw format" disk image file roughly the size of the SD and then dd-ing it to the SD after I'd done all the needful in the VM. (IE, booting from a floppy image, FDISK-ing, format /s-ing, etc.) I probably have a spare SD card lying around, I guess I could try re-doing it and make sure I'm not forgetting having to boot from the gotek to do the initial partitioning or whatever.
    My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

    Comment


      #17
      where are you located? Are you lacking in floppy media? Floppy drives? which?

      Comment


        #18
        Originally posted by erikarn View Post
        where are you located? Are you lacking in floppy media? Floppy drives? which?
        Media, but I don't want to have to use floppies as a crutch.

        Comment


          #19
          You know what would make this whole process easier? If we just patched XT-IDE BIOS to print out the damned geometry that it detects, so we have a hope in heck of faking it.

          Who is the XT-IDE maintainer these days? I can submit a patch for it to print out CHS at boot, and then it's super trivial at that point to craft up the partition table to populate to make it boot. I used to have to do this back in the day when it came to LILO (linux bootloader) and various BIOSes idea of LBA versus CHS addressing modes..

          Comment


            #20
            Originally posted by Blaze8088 View Post

            Media, but I don't want to have to use floppies as a crutch.
            ok, so as I just posted about - the problem here is that you don't know the geometry that XT-IDE is detecting the flash drive as, so you can't easily craft up a suitable partition table layout that DOS is happy with in order for all the boot stages to be happy.

            The trick is knowing the geometry in advance.

            Now, the UNFUN part of this is that sometimes the BIOS will quite happily use a /different/ geometry than what the CF card reports - it could speak LBA to the drive, and decide upon its /own/ CHS layout for MS-DOS and legacy boot applications. This quite frequently tripped up things in yesteryear. In fact, I re-discovered (and then remembered!) this when I installed a CF adapter in my 386 here rather than a whole XT-IDE setup - the geometry that the BIOS detects the drive as? Is not the same that's listed for that drive in the datasheet. Either the drive lied, or the data sheet is wrong, or the BIOS is recent enough to know about LBA and is making it "easier" for DOS to use the larger disk.

            In any case, the solution is to either know the precise geometry being presented by the drive -> XT-IDE (or general BIOS) -> BIOS -> MS-DOS boot blocks, and then craft up a suitable partition table in a virtual machine or other setup to match said geometry, OR you boot DOS on the drive yourself.

            Also note - MS-DOS 3.1 doesn't know about the DOS 6.2 FAT16 partition table, and it won't let you delete unknown drives. So, I ended up having to boot a DOS-6.22 boot disk on 360k media with fdisk to delete the partition, then boot MS-DOS 3.1 from a second/third 360k disk to partition and install the OS.

            With all that said - if you're in the bay area, I'm happy to provide you boot media to work around this nonsense. It really will be easier doing this on the 5150 itself rather than trying to guess drive geometry.

            Comment


              #21
              Originally posted by erikarn View Post
              You know what would make this whole process easier? If we just patched XT-IDE BIOS to print out the damned geometry that it detects, so we have a hope in heck of faking it.
              No need, The XUB issues the " Identify Device " command, There is a tool on the XUB binaries website called "Biosdrvs.com". Run it and it will report the results. Or one could look up the Manufacture data sheet for the CF card if available.

              Comment


                #22
                Originally posted by Blaze8088 View Post
                Media, but I don't want to have to use floppies as a crutch.
                Then you're in for a lot of fun and games, As already mentioned a Gotek sounds like a good alternative though i've never had / used one.

                Comment


                  #23
                  The CHS geometry for the OP's CF card is in the datasheet for it:


                  cap | cyl | heads | sectors | model
                  256MB | 978 | 16 | 32 | THNCF256MMA

                  Presumably that's what the XUB BIOS is detecting, so for QEMU you'd presumably use something like:

                  qemu-system-i386 -boot acd -m 16 -cpu 486 -fda "Tandy MS-DOS 3.3.IMA" \
                  -device ide-hd,drive=ide0,cyls=978,heads=16,secs=32 -drive file="256MB.dsk",format=raw,if=none,id=ide0

                  (I just tested the above and was able to boot dos, FDISK the image file, and make it bootable with a format. Unfortunately the ZIP'ed version of the resulting file is about 310k, just a teeny bit over the forum's size limit. But it should be easy enough to recreate.)

                  Thinking about the time I had it "just work" when I DD'ed a partition from QEMU onto an SD card the card I was using in the SD->IDE adapter was over 8GB (yes, a waste for an XT but it's what I had lying around), I'm thinking that may have worked without specifying a geometry because with a card that big it'd have to use LBA natively at the BIOS level and, presumably, QEMU and XUB had compatible translation algorythms?
                  My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

                  Comment

                  Working...
                  X