On Sat, Sep 19, 2020 at 07:36:04PM -0400, dmccunney wrote:
> > http://www.malinov.com/Home/sergeys-projects/xt-cf-lite
>
> Not a solution for me. The XT clone is an *XT* clone. That's an IDE
> CF Adaptor card, and the old XT clone doesn't have IDE slots. It
> predates IDE.
It's just its
On Sat, Sep 19, 2020 at 12:34 PM ZB wrote:
> On Sat, Sep 19, 2020 at 12:15:04PM -0400, dmccunney wrote:
>
> > My old 32 bit desktop has a half height combo 3.5"/5.25" floppy drive.
> > It was originally seen as drives A: and B:, and which was seen as
> > which was controlled by a jumper setting
On Sat, Sep 19, 2020 at 04:28:00PM +0200, Eric Auer wrote:
> About your missing 10 kB: That might be extra driver
> data, extra BIOS data, a virus, depends. Just telling
> DOS to use them anyway will not be the solution. You
> could use DEBUG to see what is in those 10 kB.
I browsed memory using
On Sat, Sep 19, 2020 at 07:19:46PM +0200, Eric Auer wrote:
>
> Hi again :-)
>
> >>>
> >>> https://retrocomputing.stackexchange.com/questions/1452/only-drive-a-detected-with-two-floppy-disk-drives
> >>
> >> It says controllers after 2003 tend to no longer support
> >> more than one drive at
Hi again :-)
>>>
>>> https://retrocomputing.stackexchange.com/questions/1452/only-drive-a-detected-with-two-floppy-disk-drives
>>
>> It says controllers after 2003 tend to no longer support
>> more than one drive at the same time. From when is yours?
>> The computer mentioned on stackexchange
On Sat, Sep 19, 2020 at 05:04:10PM +0200, Eric Auer wrote:
> Any memory allocated BEFORE DOS starts will be shown as
> "there is less than 640k of memory". For example extra
> data used by BIOS extensions, a bootable MEMDISK, some
> tools which load before DOS to provide LBA support on
>
On Sat, Sep 19, 2020 at 12:15:04PM -0400, dmccunney wrote:
> My old 32 bit desktop has a half height combo 3.5"/5.25" floppy drive.
> It was originally seen as drives A: and B:, and which was seen as
> which was controlled by a jumper setting on the drive. That went away
> in an emergency
On Sat, Sep 19, 2020 at 9:26 AM ZB wrote:
>
> completed lately my DOS machine with additional 1.2 MB 5,25" FDD for
> occasional use of my old diskettes. So I have 3,5" FDD as drive A: and
> 5,25" FDD as drive B: now.
>
> But there is a problem: I can only access the drive A: - never both drives
>
Hi!
> You mean "extra driver data" not shown by "mem"? Or BIOS data within 640 KB?
Any memory allocated BEFORE DOS starts will be shown as
"there is less than 640k of memory". For example extra
data used by BIOS extensions, a bootable MEMDISK, some
tools which load before DOS to provide LBA
On Sat, Sep 19, 2020 at 04:28:00PM +0200, Eric Auer wrote:
> About your missing 10 kB: That might be extra driver
> data, extra BIOS data, a virus, depends. Just telling
> DOS to use them anyway will not be the solution. You
> could use DEBUG to see what is in those 10 kB.
You mean "extra driver
Hi! If you can only access the 1.2 or 1.44 MB drive,
but not both at the same time, you may have to use
a different cable or different jumper settings on
the drives themselves. It is also possible that you
have a mainboard which supports only one driver, but
that would probably only happen with
And another riddle: "mem /c/p" on the motherboard I use (Asrock K7S8XE)
shows just 630K of "Conventional memory"; of course it has consequence
in "Largest available program size".
Is it possible to somehow recover that "lost" 10 KB?
--
regards,
Zbigniew
Hello,
completed lately my DOS machine with additional 1.2 MB 5,25" FDD for
occasional use of my old diskettes. So I have 3,5" FDD as drive A: and
5,25" FDD as drive B: now.
But there is a problem: I can only access the drive A: - never both drives
on a whim. So to access 5,25" drive I have to
13 matches
Mail list logo
