My thanks to all who responded. With your help I managed to
recover the installed Fedora 39 KDE Workstation OS and to install a
modified GRUB2 bootloader that gives me the option of booting Fedora
or FreeDOS. I made a number of discoveries along the way and for
use by anyone who might find themse
Thank you all for your responses. Apparently my responses have been over
the 40k limit; I'm not familiar with the site so pardon my delay in
responding.
There is only one active partition; it is sda1. it got moved to sda3 where
DOS was installed when I used the fdisk that was part of the FreeDOS
On a Lenovo R400 laptop with an existing Fedora 39 KDE system, booted by
GRUB2, I decided to add a new partition and install FreeDOS 1.3.
The Intel Core2 DUO processor lacks VM extensions so I decided to install
on the SSD. I resized the BRTFS partition to create a new 3 GiB FAT32
partition, label
On 11/24/2010 4:32 PM, userbeit...@abwesend.de wrote:
> charles wrote on Wednesday 24th of November 2010:
>> I have recently installed freedos 1.0 on my 486sx laptop. I am now
>> looking for a math coprocessor emulator that won't kill emm386. Any
>> suggestions?
>
>
I have recently installed freedos 1.0 on my 486sx laptop. I am now
looking for a math coprocessor emulator that won't kill emm386. Any
suggestions?
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500
basudeb gupta wrote:
> Hi All,
>
> Is there an ASPI driver for FreeDOS? Where can I get it?
>
> Also, where can I get the specs of that driver so that I can write a
> program and access a SCSI hard disk?
>
> Thanks
> Basudeb
>
>
I've had the same problem with FreeDOS not accessing hard drive
ed by something else.
Question:
Does the kernel handle int 13H itself without bothering to use BIOS
functions? But if that was the case why can't loading the proper device
driver remove control of int 13H from it.
Charles
Kenneth J. Davis wrote:
> charles wrote:
> ...
>> FreeDOS completely blows this off and refuses to access the drives
>> installed using fdisk (Unless using the before mentioned set option)
>> or xfdisk or format. Since aspi8dos.sys should have taken the BIOS
>>
--- Begin Message ---
Kenneth J. Davis wrote:
charles wrote:
Been trying to install freedos V1.0 onto a SCSI HD. The fdisk program
is giving me Invalid Drive Designation but will see the SCSI drives
when I issue "set FFD_VERSION=6" at the command prompt. That doesn't
do me
bled
SCSI Devices:
SCSI ID 0 = Quantum QM318200TD (18GB)
SCSI ID 1 = Quantum QM318200TD (18GB)
From these settings FreeDOS should see the drives a ordinary fixed
disks. But it doesn't. Any help on this would be greatly appreciated.
Charles
P.S. Linux can access
Hello to everyone ,and thank you to all developers.
I have a problem with my cdrom .
My install went fine but now it doesn't work.
Problem is I don't have a floppy drive or network attached ,just a
cdrom.
I just installed freedos and I cant get the drivers working.
Here is the line in my config sys
workstations).
Has anyone else run across this? I did a search on Bugzilla but couldn't
find any reference to it. Thanks!
Charles Hamby
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?
, and hangs. I'm not sure
whether I have himem.sys and emm386.exe configured wrong, or if it is
something else, so I have included my himem and emm386 lines below.
My Himem.sys line:
device=\bin\himem.exe /testmem:off
My emm386.exe line:
device=\bin\emm386.exe noems X=TEST
Thanks,
Charles
--
If you send me the comments/the file with the comments, I will try to
translate them, but I only know Spanish, not Portugese. And even
then, I might not get much, because of the different vocab often used
with computers. Send it to me and I'll try though.
-Charles
On 11/24/05, Blair Cam
> I can't confirm nor deny, but I think I saw a sentence or two in one of
> my many readings describing PROTMAN (no version mentioned if I recall
> correctly) makes some very specific assumptions about kernel/memory
> layout, which I do not believe the FD kernel attempts to mimic.
> Unfortunately n
INT19h… Has anyone else had any problems with the
Int19h bios interrupt?
16 matches
Mail list logo
