Hi,
I had some more time to spend on this project today. I reinstalled Freedos
on a 2 GB disk-on-module. Again after installation I had to do a sys from
2031 bootdisk and then copy kernel.sys to get a bootable freedos 1.2
system. I can use my CDROM connected to the IDE interface on the Sound
Blaster card. So all is fine here apart from past 2031 bootdisks requiring
the workaround to boot from hard drive.
The issue I am facing now is that the mechanical drives I connected to the
secondary IDE channel of my Vesa Local Bus controller are not detected.
Windows 98 SE bootdisk does not detect them either, The BIOS of my system
only supports 2 hard drives. Last time I had this setup working with Linux,
so I will try to dig some old bootdisk to see if Linux can detect the
secondary IDE hard drives. Is there anything I can try from FreeDOS?
Best regards,
Dimitris
On Wed, Jul 20, 2016 at 11:31 PM, Dimitris Zilaskos <dimitr...@gmail.com>
wrote:
> Hi Eric,
>
> I have tried the /FORCE:CHS and it did not help.
>
> Cheers,
>
> Dimitris
>
> On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer <e.a...@jpberlin.de> wrote:
>
>>
>> Hi Dimitris,
>>
>> > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging
>> at
>> > Loading FreeDOS, hard drive working like mad, I rebooted with the same
>> > floppy, did the same thing, and it booted. Tried again with sys 3.6e,
>> > hang again, tried again with sys 2.6, was able to boot again.
>>
>> This is a bit confusing but it sounds like a problem with the way
>> that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you
>> should be able to boot with /FORCE:CHS (explicitly selecting the
>> CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version).
>>
>> This will probably work with various, including newer (and better)
>> versions of the kernel.sys file: In earlier tests, you mentioned
>> that using SYS CONFIG to require pure LBA or pure CHS mode from a
>> kernel did not affect the ability of the kernel to use the drive.
>>
>> Regards, Eric
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning
>> reports.http://sdm.link/zohodev2dev
>> _______________________________________________
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
