Hi all,
sorry for the likely trivial question from a FreeDOS newbie.
I'm trying to access a physical 5.25/360KB floppy drive connected to an
old PC whose BIOS does not support that kind of drives (only 5.25/1.2M
or 3.5). I've been suggested to try some DOS utilities, so I'm looking
at FreeDOS
Hi Eric,
thank you very much for your help, really appreciated!
First of all, my drive letter issue has been solved... more or less.
In my first attempt, I picked the "Install to HD" menu item to see the
available options, then chose to "Return to DOS". This way, I got A: as
the main/current
Hi!
In theory, when you boot from a CD containing a virtual boot
floppy image, the BIOS is supposed to move your real floppy
drive to the next drive letter, so it should be B: When you
use a MEMDISK bootable ramdisk, I expect similar effects.
In case of the BIOS method, we could add a tool
On Fri, 20 Aug 2021 at 19:02, Exilas wrote:
>
> In the hope someone could still provide me with additional hints, I'm
> posting here all the information I've found about the involved hardware.
Use the DRIVPARM command in CONFIG.SYS to inform the OS of the real
drive type and parameters?
--
Ok so I tried with FreeDOS booting from the LiveCD. In this way, I can
address the physical 5.25 drive on letter A:, but I always get a "Seek
error" when trying to access to a disk by executing the command "dir
a:". This seems very similar to the "Can't read superblock" error I get
from Linux.
Hello,
> On Aug 20, 2021, at 8:19 AM, Exilas wrote:
>
> Hi Eric,
> thank you very much for your help, really appreciated!
>
> First of all, my drive letter issue has been solved... more or less.
>
> In my first attempt, I picked the "Install to HD" menu item to see the
> available options,
Hi Liam and Exilas,
> Use the DRIVPARM command in CONFIG.SYS to inform the OS of the real
> drive type and parameters?
Both DRIVPARM and DRIVER are related to situations where the BIOS
e.g. fails to report correct (typically floppy) drive properties.
At this used to be only relevant for
Hi Eric, everyone.
I admit to having a challenge picturing the problem.
If this 5.25 drive is physically installed, it should? be shoring up in
your BIOS letting you at least perhaps impact how it is designated.
Otherwise,I do agree with Eric, regardless of your boot location and
sequence,
Hi All,
Just released minor (but nice) update to PGME. Fixed a non-critical (visual
only) bug. Tweaked a couple fonts. And if you use the TIME screen saver, it
will now "remember" what scale it was last left it. You could change scale
before. But, it would always reset. You can download the
There are multiple issues here.
First, if you want to use both floppy drives, your floppy cable must
have both connections on it, since there is rarely more than a single
floppy controller slot on a motherboard.
Second, there needs to be 5 (if I remember correctly) pins reversed
between
Eric,
posting this reply on list, since I am sure writing me privately without
permission was a mistake on your part.
Karen
-- Forwarded message --
Date: Fri, 20 Aug 2021 21:45:35 +0200
From: Eric Auer
To: Karen Lewellen
Subject: Re: Accessing real floppy drive after
On Fri, 20 Aug 2021, Travis Siegel wrote:
There are multiple issues here.
First, if you want to use both floppy drives, your floppy cable must
have both connections on it, since there is rarely more than a single
floppy controller slot on a motherboard.
A quick note on this - if the
Hmm, I was not aware of that, thanks for the info. Always good to know
possible causes of failure. Now there's one more to add to the pile.
On 8/20/2021 3:05 PM, geneb wrote:
On Fri, 20 Aug 2021, Travis Siegel wrote:
There are multiple issues here.
First, if you want to use both floppy
Hi everybody, thank you all for your contributions.
@Karen: Eric is right, my original issue with FreeDOS floppy drive
letter has been solved by executing the boot from CD in "harddisk image"
easter egg mode. Also, later on I managed to install FreeDOS on a HD
partition, and also booting from
14 matches
Mail list logo
