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

Any good way to create a bootable DOS CF HDD on a LINUX box?

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

    Any good way to create a bootable DOS CF HDD on a LINUX box?

    Long story short;

    I have an XT class PC with an XT-IDE and a 512mb CF card. No good way at present to use real floppies or a gotek for a few reasons.

    What I would like to do is format that CF card with DOS 5.0 as a bootable drive and if possible define a few partitions, and if possible drop files into them like a full DOS install and other programs.

    I would like to think that by now we would have a linux program to do such a thing with a few tick boxes, but I can't seem to find one. Does such an app exist or even a reasonable process to pull this off?

    #2
    Maybe not as a GUI, but I can probably figure out how to do it from a Linux CLI, given the DOS files, of course.
    Reach me: vcfblackhole _at_ protonmail dot com.

    Comment


      #3
      Maybe I'm a bit askew, but is there a rufus for Linux?

      Comment


        #4
        There are sites that have boot floppy images available for download. What I would do in this situation is to set up some kind of PC emulator and have it boot from a diskette image. Using the emulator, make a bootable DOS volume, then dd the resulting volume image onto your CF card (or find a way for your emulator to write to the CF card directly).

        Comment


          #5
          Just make a virtual machine in VirtualBox and mount the physical media. It requires a bit of putzing around in bash, but if you mount the physical media as a drive for the virtual machine, you can just pull the CF card when done installing DOS and put it in the XT machine.

          https://www.serverwatch.com/server-t...ualbox-vm.html

          Comment


            #6
            The last time I did something like this I started with a DOS 6.22 virtual machine from Winworldpc and used a procedure along these lines:
            1) use the dd command to create a blank 256m(or whatever the size of your physical media is) file: dd status=progress if=/dev/zero of=./dos622.img bs=1024k count=256
            2) Mount the blank image file as a hard drive in the virtualization software
            3) Format the blank drive with DOS and copy all DOS files to the new drive
            4) Shut down the virtual machine
            5) Mount my physical media(in my case a DOM) via USB
            6) Copy the image file to the physical media: dd status=progress if=./dos622.img of=/dev/DEVICE(where DEVICE is the name of your physical media)

            Disclaimer: I can't guarantee that this procedure is 100% accurate as I typed it from memory.
            Once upon a time, the internet sucked because it came through the phone. Now the phone sucks because it comes through the internet.

            Comment


              #7
              Originally posted by GiGaBiTe View Post
              Just make a virtual machine in VirtualBox and mount the physical media...
              I can vouch for this procedure. Years ago I used it to set up a bootable hard disk for an old Dolch Pentium luggable that had a nasty mid-90's BIOS that rendered it incapable of booting most CD-ROM formats. (And I had no floppy disks.) Attached the hard disk via one of those universal USB-to-IDE dongle kits; for a CF card you should be able to just use an apropos universal flash reader.

              QEMU or KVM (via virt-manager or other gui of choice) would probably work just as well as Virtualbox, so far as it goes.
              My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

              Comment


                #8
                So I just did this for my Compaq portable and it booted almost to dos.. getting parity check 2 at the moment but may as well say how I got that far lol.

                This will boot your floppy image and attach a drive located at /dev/sdb (typical name if you only have one main HDD or SSD installed + a USB CF adapter connected) run dmesg just after attaching the USB CF adapter with the disk in it and you'll see where linux recognizes it an gives it a device name in the output.

                qemu-system-i386 -fda Disk1.img -drive fmt=raw,file=/dev/sdb -boot a

                After you boot up partition and format you disk manually as it probably will fail to do it automatically... 2GB is the max it will do this by default for 6.22.

                Then run the setup command to continue... it will begin the install and then ask to switch disks assuming you have the GTK interface version of QEMU you can select the compatmonitor0 device from the dropdown menu and type in change floppy0 Disk2.img to switch to the second image in your floppy set or whatever disk image name in the same folder as your previous floppy image. Now switch back to the VGA output device. Note if you don't have the GTK version of QEMU you can redirect that IO to the terminal but I don't remember how to do that at the moment just google search for it. Note I had to run fdisk /mbr before was able to boot from my drive. From there you have what you need to know to continue the install!

                Also note that I used a cheap $10 CF to SD card adapter for this just now... and was able to access a 16GB SD card.

                Comment


                  #9
                  A problem is that different IDE devices may interpret a CF card's geometry differently. Even different XT IDE BIOS revisions can wind up expecting different CHS values.

                  The CHS values set in the partition table must match whatever values BIOS assigns it on the target machine. For CF cards and other LBA devices, these number just get pulled out of the air. Emulators/Virtualizers also usually just make up numbers to fit an arbitrary sized volume.

                  Sometimes, if BIOS and the partition table don't match, DOS booted from a different drive might still be able to find and read the partition, but it won't boot.

                  So you might get lucky and have a Windows/Linux/Emulator created partition boot DOS, but you might have to futz with the CHS values.

                  Comment

                  Working...
                  X