On Tue, Sep 20, 2022 at 2:02 PM tauro via Freedos-user
wrote:
> Quoting the website:
>
> > Rudolph Loew (Rudy) passed away on September 11th, 2019.
> > This site is maintained by his family to archive his work and make it
> > available to anyone who is interested in pursuing further endeavors.
>
On 20/9/22 04:35, Eric Auer wrote:
You could use AHCICD, which got open sourced after the author
Rudolph Loew passed away, but unfortunately, he has not been
able to update all documentation after his death, so the way
in which AHCICD and his other software became open source was
not accepted by
On 9/20/22 02:35, Eric Auer wrote:
>>> There's a script that gets called from FDAUTO that tries several drivers
>>> -- why wouldn't that work? And why did it work during install?
>
> Because only the open source ones actually got installed automatically?
That seems backwards to me. The installer
Hi!
There's a script that gets called from FDAUTO that tries several drivers
-- why wouldn't that work? And why did it work during install?
Because only the open source ones actually got installed automatically?
There CD also has an ELTORITO.SYS driver it will try to use.
El Torito
Make sure you have the CD/DVD-ROM driver and a MSCDEX equivalent loaded
on startup. This might be happening during the installer, but might be
missing out of config.sys and autoexec.bat in your installed version...
There's a script that gets called from FDAUTO that tries several drivers
--
Hallo Herr Glenn Holmer via Freedos-user,
am Sonntag, 18. September 2022 um 19:30 schrieben Sie:
> I installed FreeDOS 1.3 on a machine about ten years old. It
> successfully read the DVD during installation, but doesn't recognize it
> afterward when booted.
> How can I diagnose this?
you have
> On Sep 18, 2022, at 2:53 PM, Glenn Holmer via Freedos-user
> wrote:
>
> [..]
> There's a script that gets called from FDAUTO that tries several drivers
> -- why wouldn't that work? And why did it work during install?
There CD also has an ELTORITO.SYS driver it will try to use. For several,
OK, so the cat is now awake, and I have installed a fresh copy of FreeDOS
1.3 on VirtualBox. The DVD is visible. This is weird.
Can you copy and paste the contents of your fdauto.bat file into an email,
to help with further diagnosis?
On Sun, 18 Sept 2022 at 20:44, John Vella wrote:
> As I
As I understand it, (and I'm not in front of a computer so I can't check
right now) fdauto on the install disk can access the optical drive, but the
files required to access the optical drive are not copied during install,
and the lines are not in the fdauto file on the hard drive.
I may be
On 9/18/22 14:12, John Vella wrote:
> You should look at fdauto.bat, copy and paste the relevant lines into
> the copy on your hard drive and copy the files it calls into the dos folder.
Are you suggesting that the installer wrote config files that point to
drivers that don't exist? That doesn't
You should look at fdauto.bat, copy and paste the relevant lines into the
copy on your hard drive and copy the files it calls into the dos folder.
I think that'll work. :)
On Sun, 18 Sep 2022, 19:56 Glenn Holmer via Freedos-user, <
freedos-user@lists.sourceforge.net> wrote:
> On 9/18/22 12:58,
On 9/18/22 12:58, Ralf Quint wrote:
> On 9/18/2022 10:30 AM, Glenn Holmer via Freedos-user wrote:
>> I installed FreeDOS 1.3 on a machine about ten years old. It
>> successfully read the DVD during installation, but doesn't recognize it
>> afterward when booted.
>>
>> How can I diagnose this?
>
>
On 9/18/2022 10:30 AM, Glenn Holmer via Freedos-user wrote:
I installed FreeDOS 1.3 on a machine about ten years old. It
successfully read the DVD during installation, but doesn't recognize it
afterward when booted.
How can I diagnose this?
Make sure you have the CD/DVD-ROM driver and a
13 matches
Mail list logo
