On 12/26/2021 12:29 PM, Louis Santillan wrote:
There seems to be some population of newer or obscure BIOSes that will
misreport IDE drives and BIOS booted HDD formatted USB drives as being
non fixed disks which FD FDISK requires to be able to interact with them.
This isn't "obscure" at all
I was able to test and MS DOS 6.22 is able to see and format the IDE DOM
drive much like MS DOS 7. So, I haven't looked at what FD FDISK is doing
differently, and it's likely a relatively small population that is affected
by this.
There seems to be some population of newer or obscure BIOSes that
Apologies for the zombie thread revival.
I recently bought 3 of these Wyse SX0 thin clients and I can confirm that
FreeDOS 1.3-RC5 (and worse!) and FDISK are buggy on it. I think the
reality is that BIOS and USB boot code is only partially complete and just
enough to boot into a more modern OS
Hi! As said, I can imagine that the BIOS of your
system has problems if the USB stick and DOM both
count as harddisks. But you already have bootable
DOS installed from floppy now, so I suggest ways
which are easier:
You can connect the DOM instead of the normal disk
to a "bigger" PC with CD-ROM
It was partitioned, with an MBR, accessible to Windows when connected to a USB
to IDE adapter.
Currently it's bootable to a DOS prompt. I used the "China DOS Union" DOS 7.1
boot floppy with a USB floppy drive to fdisk and format the DOM installed in
the thin client. I could go ahead and put
>"Missing Operating System" is usually issued by the master boot
>record, when no active partition is found.
I have a Compaq Presario that issues that statement apparently from the
BIOS, as I switch among about 4 hard drives and sometimes the drive is not
fully inserted in the connector..
On
> I used CloneDisk to rip a RAW image of the booting DOM with
> FreeDOS. Mounted that with Qemu. Booted Qemu with the FreeDOS
> install image and installed FreeDOS to the image copied from the
> DOM. Then I used CloneDisk to write that image back to the DOM. "Missing
> Operating System".
I just
I'm going to try using RMPrepUSB to put the FreeDOS USB install image onto a
USB stick. Why? Because it's supposed to be able to be selected to emulate an
A: floppy drive (or as C: or D:) instead of presenting itself as C: like the
FreeDOS image does. Recall that the FreeDOS installer initially
> I used CloneDisk to rip a RAW image of the booting DOM with
> FreeDOS. Mounted that with Qemu. Booted Qemu with the FreeDOS
> install image and installed FreeDOS to the image copied from the
> DOM. Then I used CloneDisk to write that image back to the DOM. "Missing
> Operating System".
forget
Hi again,
I used CloneDisk to rip a RAW image of the booting DOM with FreeDOS.
Mounted that with Qemu. Booted Qemu with the FreeDOS install image and
installed FreeDOS to the image copied from the DOM. Then I used
CloneDisk to write that image back to the DOM. "Missing Operating
System".
I used CloneDisk to rip a RAW image of the booting DOM with FreeDOS. Mounted
that with Qemu. Booted Qemu with the FreeDOS install image and installed
FreeDOS to the image copied from the DOM. Then I used CloneDisk to write that
image back to the DOM. "Missing Operating System".
On
Hi,
On Fri, Jan 5, 2018 at 5:13 PM, E. Auer wrote:
>
> Possible explanation: The FreeDOS USB boot thing has a harddisk-
> style bootable disk image and the BIOS of your computer has some
> compatibility issue with the drive-renumbering caused by booting
> from USB and/or from
Possible explanation: The FreeDOS USB boot thing has a harddisk-
style bootable disk image and the BIOS of your computer has some
compatibility issue with the drive-renumbering caused by booting
from USB and/or from using a "harddisk" boot image. A possible
solution would be to use a FreeDOS
13 matches
Mail list logo