Re: [Freedos-user] FreeDOS install

[Robert Riebisch via Freedos-user]

Hi Norby,

> Thanks to jerome I believe the issue was tryin to install over the old
> copy since i fprmated the drive before the install this time and it
> worked.  I probably should have tried that before sendin out the long
> message.  My gremlin there.

Glad it worked now.

> I cannot use vbox since my pc cannot run it, unless there is an xp
> version.  I prefer connectix virtual pc in xp and have the option to
> share files between xp and the virtual machine.

For the record:
Older VirtualBox versions (<6.0) should still run on Windows XP, but I
didn't try for myself.
https://www.vogons.org/viewtopic.php?t=66264
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2

By the way: Oldest version I have here is
`VirtualBox_1.5.6-1_Win_x86.msi` from 2008. It's only 18 Mbyte in size,
while v5.2.44 is 105 Mbyte.

Cheers,
Robert
-- 
BTTR Software   https://www.bttr-software.de/
DOS ain't dead  https://www.bttr-software.de/forum/


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS install

[Norby Droid via Freedos-user]

Thanks to jerome I believe the issue was tryin to install over the old copy
since i fprmated the drive before the install this time and it worked.  I
probably should have tried that before sendin out the long message.  My
gremlin there.

I cannot use vbox since my pc cannot run it, unless there is an xp
version.  I prefer connectix virtual pc in xp and have the option to share
files between xp and the virtual machine.

Thanls to everyone for their replies and assistance.  Great community.

On Sun, Apr 7, 2024 at 11:27 Paul Dufresne  wrote:

>
> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-LiveCD.zip
> worked for me (in QEMU).
> I have chosen 'Install to hard disk' from the main menu.
>
> Do you install in english?
>
> Have you verified the file with
> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/verify.txt
> ?
> You could use https://www.winmd5.com/ ...
>
> Maybe try with VirtualBox:
> https://download.virtualbox.org/virtualbox/7.0.14/VirtualBox-7.0.14-161095-Win.exe
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS install

[Paul Dufresne via Freedos-user]

https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/FDT2404-LiveCD.zip
worked for me (in QEMU).
I have chosen 'Install to hard disk' from the main menu.

Do you install in english?

Have you verified the file with 
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/verify.txt
 ?
You could use https://www.winmd5.com/ ... 

Maybe try with VirtualBox: 
https://download.virtualbox.org/virtualbox/7.0.14/VirtualBox-7.0.14-161095-Win.exe


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS install

[Norby Droid via Freedos-user]

The install I have wanted to try (in connectix vpc) is the test FreeDOS
FDT2404-Live CD.zip from ibiblio.  The test fails on both options with or
without sources added.  TestDisk is where it will always stop.
‘Util\testdisk’ package. A reboot may help.

On Sun, Apr 7, 2024 at 01:49 Jerome Shidel via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:

> Hi,
>
> > On Apr 6, 2024, at 8:40 PM, Norby Droid via Freedos-user <
> freedos-user@lists.sourceforge.net> wrote:
> >
> > One issue I find alot when tryin to install FreeDos is that it would go
> most of the way through the install then without any reason and no
> explanation as to why, it just stops and says there is a problem so reboot
> or exit.
>
> The installer is batch based. It uses other executable utilities to
> perform the required tasks. This limits the amount of information that is
> passed back to the installer when an error occurs.
>
> However, there are only a couple things that generally cause an install to
> fail after packages have already started to extract successfully.
>
> Corrupted install media.
> Insufficient disk space.
> File conflicts.
>
> Around the time of the 1.3 release, there was a file conflict that would
> occur when Full+Sources was selected. One of the packages contained its
> source files and those of another package. So when selected, it would cause
> a conflict during installation. That conflict was resolved and does not
> occur in the latest test builds.
>
> You could just install BASE with or without sources. Then after rebooting
> from the installed system, put the CD back into the drive and run FDIMPLES.
>
> That will make it easy to install any additional packages that could have
> been installed with FULL or those from the BonusCD.
>
> You could also try the monthly interim test build of FreeDOS. While it is
> not a “release”, it contains many fixes since 1.3 and numerous software
> updates. However, it is a test build and some of the updated software may
> have issues. It is available on ibiblio in the test directory for
> distributions.
>
> >
> > I have FD in three locations.  Second drive in my old desktop, usb
> drive, and in connectix virtual pc in windows xp.  The glitch would happen
> no matter which environment I use.  I decided to use 7zip to test and
> extract all files from the liveCD and all passed and was successful.  As
> another test I went in and tested all the .zip files found in the
> directories and they also all passed the test.  I take from this that if
> the files are good then the issue is with my system?
>
> If your installing Full + Sources, possibly not.
>
> >
> > Is there any way to find out why it crashes?
>
> Not really.
>
> When 1.3 was released, there was no reliable good was to record such
> information during installation.
>
> Since that time, a new utility was created that can efficiently record
> boot messages, program output and other messages. That programs recording
> could be output to a log when needed.
>
> However, no decision has been made to use the program on the install
> media. If it were, support could be added to the installer to record more
> detailed information about the installation process.
>
>
> > I know in the latest version on ibiblio the file “TestDisk” is where it
> would always crash.  Is it possible to just extract all the .zip files into
> separate directories in each folder the zips reside in and still have a
> proper FreeDos install?
>
> Well, mostly yes. But, there are some issues with dying it that way.
>
> Most programs that come with FreeDOS will work fine regardless of what
> directory they are located. However, a few won’t and need configured for
> their location.
>
> Also, the directories in the zip archive are meta-directories. Many paths
> are remapped during the package installation.
>
> :-)
> Jerome
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS install

[Jerome Shidel via Freedos-user]

Hi,

> On Apr 6, 2024, at 8:40 PM, Norby Droid via Freedos-user 
>  wrote:
> 
> One issue I find alot when tryin to install FreeDos is that it would go most 
> of the way through the install then without any reason and no explanation as 
> to why, it just stops and says there is a problem so reboot or exit.

The installer is batch based. It uses other executable utilities to perform the 
required tasks. This limits the amount of information that is passed back to 
the installer when an error occurs. 

However, there are only a couple things that generally cause an install to fail 
after packages have already started to extract successfully.

Corrupted install media.
Insufficient disk space.
File conflicts.

Around the time of the 1.3 release, there was a file conflict that would occur 
when Full+Sources was selected. One of the packages contained its source files 
and those of another package. So when selected, it would cause a conflict 
during installation. That conflict was resolved and does not occur in the 
latest test builds.

You could just install BASE with or without sources. Then after rebooting from 
the installed system, put the CD back into the drive and run FDIMPLES. 

That will make it easy to install any additional packages that could have been 
installed with FULL or those from the BonusCD.

You could also try the monthly interim test build of FreeDOS. While it is not a 
“release”, it contains many fixes since 1.3 and numerous software updates. 
However, it is a test build and some of the updated software may have issues. 
It is available on ibiblio in the test directory for distributions.

> 
> I have FD in three locations.  Second drive in my old desktop, usb drive, and 
> in connectix virtual pc in windows xp.  The glitch would happen no matter 
> which environment I use.  I decided to use 7zip to test and extract all files 
> from the liveCD and all passed and was successful.  As another test I went in 
> and tested all the .zip files found in the directories and they also all 
> passed the test.  I take from this that if the files are good then the issue 
> is with my system?

If your installing Full + Sources, possibly not.

> 
> Is there any way to find out why it crashes? 

Not really. 

When 1.3 was released, there was no reliable good was to record such 
information during installation.

Since that time, a new utility was created that can efficiently record boot 
messages, program output and other messages. That programs recording could be 
output to a log when needed. 

However, no decision has been made to use the program on the install media. If 
it were, support could be added to the installer to record more detailed 
information about the installation process. 


> I know in the latest version on ibiblio the file “TestDisk” is where it would 
> always crash.  Is it possible to just extract all the .zip files into 
> separate directories in each folder the zips reside in and still have a 
> proper FreeDos install?

Well, mostly yes. But, there are some issues with dying it that way.

Most programs that come with FreeDOS will work fine regardless of what 
directory they are located. However, a few won’t and need configured for their 
location.

Also, the directories in the zip archive are meta-directories. Many paths are 
remapped during the package installation.  

:-)
Jerome

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS install

[Norby Droid via Freedos-user]

One issue I find alot when tryin to install FreeDos is that it would go
most of the way through the install then without any reason and no
explanation as to why, it just stops and says there is a problem so reboot
or exit.

I have FD in three locations.  Second drive in my old desktop, usb drive,
and in connectix virtual pc in windows xp.  The glitch would happen no
matter which environment I use.  I decided to use 7zip to test and extract
all files from the liveCD and all passed and was successful.  As another
test I went in and tested all the .zip files found in the directories and
they also all passed the test.  I take from this that if the files are good
then the issue is with my system?

Is there any way to find out why it crashes?  I know in the latest version
on ibiblio the file “TestDisk” is where it would always crash.  Is it
possible to just extract all the .zip files into separate directories in
each folder the zips reside in and still have a proper FreeDos install?

I love FreeDos and use it more than xp for Basic Programming in a couple
different ones (PowerBasic 3.5 and FreeBasic).

Thank You Jim Hall amd all those involved with its development.
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Hello,
I bought a CF card and adapter, so waiting for those to arrive. I tried the
fdisk /bmbr command on both the installed fdisk and the live cd, both of
them give the syntax error… operation terminated. The other fdisk mbr
options work though. When the CF adapter arrives I should be able to get
the files off the computer and send them. I havnt found a command which
copys to cd, probably need to find an application for that eventually, if
my cd drive can write. Not sure if it can.

On Sat, Jun 12, 2021 at 7:40 PM Eric Auer  wrote:

>
> Hi Andrew,
>
> > So I did the experiment, simply by using fdisk /mbr in the live cd of
> > freedos. The OS now is not bootable from hdd, and gives read error while
> > reading drive error. So definitely problem is fdisk /mbr command.
>
> Can you send me the MBR in working "Win98" state (from your backup
> made with FDISK /SMBR) and the MBR in broken state (i.e. copy the
> boot.mbr backup to a new name, then run FDISK /SMBR again to write
> the broken MBR to boot.mbr again) so I can compare both? Also, does
> the same problem happen with FDISK /BMBR instead of FDISK /MBR ? In
> both cases, you can use FDISK /AMBR to put the previously backed up
> boot.mbr file back on the MBR, of course after copying the right
> instance of boot.mbr into the working directory of FDISK again.
>
> Thanks!
>
> > gotek sees iso images of formatted floppy drives
>
> There is a problem with choice of wording here. By ISO images
> are files containing ISO9660 filesystems used only on CD/DVD,
> so your floppy disk images cannot be ISO images.
>
> I assume you use the device because your 486 can only boot
> from floppy, not from CD or USB, but I guess you could just
> use IDE devices for booting instead? For example, there are
> simple CF to IDE adapters and you can use a cardreader to
> edit the contents of some CF which you can later use as a
> "harddisk" for the 486 with that kind of adapter. Would be
> less technologically advanced than the floppy simulation.
>
> Regards, Eric
>
> --
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Hello,
So I did the experiment, simply by using fdisk /mbr in the live cd of
freedos. The OS now is not bootable from hdd, and gives read error while
reading drive error. So definitely problem is fdisk /mbr command.

The gotek sees iso images of formatted floppy drives and reads them to a
computer as if it was a floppy drive. It uses the standard floppy
connector, also works on amiga and other non ibm computers. Also almost
everyone who buys one installs custom firmware, that works much better than
default one.

http://www.gotekemulator.com

https://github.com/keirf/FlashFloppy



On Sat, Jun 12, 2021 at 5:44 AM Eric Auer  wrote:

>
> Hi Andrew,
>
> So apart from the floppy cable problem, you say only
> the Win98 MBR boots correctly, but the FreeDOS one
> will not boot? You have re-formatted the partition
> in DOS (by the way, better use SYS, not FORMAT /S),
> but kept the partitions unchanged, so there could be
> a problem with either FDISK partition edits, or the
> MBR code added by the installer (if any, why does it
> do that by default, by the way?) or of course both?
>
> You could do the following: Use FDISK to backup the
> MBR to a file, then write one of the two built-in MBR
> codes of FDISK and see if that breaks booting. If yes,
> a bug exists in the selected boot code. If no, then
> the bug is probably in the partitioning and less in
> the MBR. After the experiment, you can restore the
> Win98 MBR using FDISK.
>
> I hope that is not too much effort for you. Would
> be good to know whether either of the two MBR in
> our FDISK has bugs. Of course you may have to boot
> from (USB or) CD or floppy to run FDISK for repairs.
>
> Thanks! Regards, Eric
>
> PS: Why would the gotek use ISO to emulate floppy?
> You probably mean floppy images, not CD/DVD images?
>
> > I was able to get both systems working correctly. I first formatted the
> > partition and wrote the mbr in Windows 98. Then in freedos I formatted
> the
> > filesystem and setup system files with format c: /s. I then used the
> > advanced installer to install without overriding the mbr, and after
> > restarting the pentium 2 was able to boot normally, straight from hdd.
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Eric Auer]

Hi Andrew,

So apart from the floppy cable problem, you say only
the Win98 MBR boots correctly, but the FreeDOS one
will not boot? You have re-formatted the partition
in DOS (by the way, better use SYS, not FORMAT /S),
but kept the partitions unchanged, so there could be
a problem with either FDISK partition edits, or the
MBR code added by the installer (if any, why does it
do that by default, by the way?) or of course both?

You could do the following: Use FDISK to backup the
MBR to a file, then write one of the two built-in MBR
codes of FDISK and see if that breaks booting. If yes,
a bug exists in the selected boot code. If no, then
the bug is probably in the partitioning and less in
the MBR. After the experiment, you can restore the
Win98 MBR using FDISK.

I hope that is not too much effort for you. Would
be good to know whether either of the two MBR in
our FDISK has bugs. Of course you may have to boot
from (USB or) CD or floppy to run FDISK for repairs.

Thanks! Regards, Eric

PS: Why would the gotek use ISO to emulate floppy?
You probably mean floppy images, not CD/DVD images?

> I was able to get both systems working correctly. I first formatted the
> partition and wrote the mbr in Windows 98. Then in freedos I formatted the
> filesystem and setup system files with format c: /s. I then used the
> advanced installer to install without overriding the mbr, and after
> restarting the pentium 2 was able to boot normally, straight from hdd.



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Hello guys,
I was able to get both systems working correctly. I first formatted the
partition and wrote the mbr in Windows 98. Then in freedos I formatted the
filesystem and setup system files with format c: /s. I then used the
advanced installer to install without overriding the mbr, and after
restarting the pentium 2 was able to boot normally, straight from hdd.

With the compaq 486, first off the floppy drive before gave diskette read
errors in bios. This was because the cord and connectors do not have the
missing pin that normal floppy drive connectors use to tell you
orientation. In addition to this there is master connection flip ( middle
part of cable), and both combined means 1 out of 4 possible cable
orientations work. After finding the correct orientation, the gotek and
floppy drive work correctly. Now I am installing freedos with the gotek
(gotek emulates a floppy drive but instead reads iso files on a usb).
Thanks for the help!

On Thu, Jun 10, 2021 at 8:02 AM Andrew  wrote:

> Gotcha, thanks for the info. Its possible the mobo floppy controller is
> broken. I haven't finished troubleshooting it yet.
>
> On Thu, Jun 10, 2021 at 8:00 AM Liam Proven  wrote:
>
>> On Wed, 9 Jun 2021 at 18:05, Andrew  wrote:
>> >
>> > 3) I havnt worked enough in getting the floppy working on the i386, i
>> think it has to do with a nonstandard ide connection.
>>
>> Standard floppy drives are *not* IDE. They have their own connection
>> (34-way not 40-way) and this is attached to a floppy controller, not
>> an IDE controller.
>>
>> There is no resemblance and no connection between the floppy and IDE
>> controllers. It is just that both use ribbon cables, but of differing
>> widths.
>>
>>
>> N.B. There is a partial exception: "superfloppy" or "floptical" drive
>> use IDE. These take different disks, such as 20MB or 120MB disks, but
>> can read the old style of disks.
>>
>> Some RISC workstations did not have a floppy controller and so if they
>> were fitted with the optional, and rare, floppy drive, these were SCSI
>> floppies that only work on a SCSI card. But no PC-compatible I recall
>> ever used SCSI floppy drives, because they were far too expensive.
>>
>> > The bios doesnt give an error when the connector is upside down, and it
>> sees the drive
>>
>> If a floppy is connected with the cable in the wrong orientation, the
>> classic giveaway is that the floppy drive's access light will be
>> permanently illuminated.
>>
>>
>> --
>> Liam Proven – Profile: https://about.me/liamproven
>> Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com
>> Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
>> UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053
>>
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> --
> Thank you very much,
>
> Andrew Ingram
> Fainman Group
> Graduate Student, UCSD
>
> Phone: (831)-320-3531
> aj1ing...@gmail.com
>
> --
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Gotcha, thanks for the info. Its possible the mobo floppy controller is
broken. I haven't finished troubleshooting it yet.

On Thu, Jun 10, 2021 at 8:00 AM Liam Proven  wrote:

> On Wed, 9 Jun 2021 at 18:05, Andrew  wrote:
> >
> > 3) I havnt worked enough in getting the floppy working on the i386, i
> think it has to do with a nonstandard ide connection.
>
> Standard floppy drives are *not* IDE. They have their own connection
> (34-way not 40-way) and this is attached to a floppy controller, not
> an IDE controller.
>
> There is no resemblance and no connection between the floppy and IDE
> controllers. It is just that both use ribbon cables, but of differing
> widths.
>
>
> N.B. There is a partial exception: "superfloppy" or "floptical" drive
> use IDE. These take different disks, such as 20MB or 120MB disks, but
> can read the old style of disks.
>
> Some RISC workstations did not have a floppy controller and so if they
> were fitted with the optional, and rare, floppy drive, these were SCSI
> floppies that only work on a SCSI card. But no PC-compatible I recall
> ever used SCSI floppy drives, because they were far too expensive.
>
> > The bios doesnt give an error when the connector is upside down, and it
> sees the drive
>
> If a floppy is connected with the cable in the wrong orientation, the
> classic giveaway is that the floppy drive's access light will be
> permanently illuminated.
>
>
> --
> Liam Proven – Profile: https://about.me/liamproven
> Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com
> Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
> UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
-- 
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Liam Proven]

On Wed, 9 Jun 2021 at 18:05, Andrew  wrote:
>
> 3) I havnt worked enough in getting the floppy working on the i386, i think 
> it has to do with a nonstandard ide connection.

Standard floppy drives are *not* IDE. They have their own connection
(34-way not 40-way) and this is attached to a floppy controller, not
an IDE controller.

There is no resemblance and no connection between the floppy and IDE
controllers. It is just that both use ribbon cables, but of differing
widths.


N.B. There is a partial exception: "superfloppy" or "floptical" drive
use IDE. These take different disks, such as 20MB or 120MB disks, but
can read the old style of disks.

Some RISC workstations did not have a floppy controller and so if they
were fitted with the optional, and rare, floppy drive, these were SCSI
floppies that only work on a SCSI card. But no PC-compatible I recall
ever used SCSI floppy drives, because they were far too expensive.

> The bios doesnt give an error when the connector is upside down, and it sees 
> the drive

If a floppy is connected with the cable in the wrong orientation, the
classic giveaway is that the floppy drive's access light will be
permanently illuminated.


-- 
Liam Proven – Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com
Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Carsten Strotmann]

Hi Andrew,

On 9 Jun 2021, at 19:20, Eric Auer wrote:


9) I will also try the FDISK /INFO command for both situations


Enjoy. You could also use XFDISK, which is more user friendly,
but shows fewer details. Note that both also have pretty long
config files which let you (mis-) configure lots of settings.
Maybe some of those have bad defaults in our current package!


XFDISK also can install a boot manager (XFDISK own) on the hard-disk 
that can boot DOS, OS/2, Windows, Linux and other systems. I've used 
XFDISK almost exclusively for older machines for the last 30 years with 
no issues. Give it a try. It has a relatively user friendly text UI.


Greetings

Carsten


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[ZB]

Maybe let's start with this: how is your HDD partitioned and do you use any
boot-loader utility to load FreeDOS? If so - how its FreeDOS section looks like?
-- 
regards,
Zbigniew


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Jerome Shidel]

An additional fact to be aware of…

All the normal install media for FreeDOS 1.3-RC4 uses and always installs the 
386 kernel with large file system support. Thats the CD media, USB media and CD 
Boot Floppy. 

However, the alternate x86 installer uses the 8086 kernel. The current version 
of this kernel is compiled without support for large file systems. But 
depending on the detected hardware, either the 8086 or 386 version of the 
kernel may be installed.  The x86 installer is the one used on all of the 
Floppy Diskette Sets (720k, 1.44m and 1.2m) and in the Easter Egg on the 
LiveCD. 

It is probably not relevant in this case. However, it may still be beneficial 
to know which of the two installers is being used. If it is the x86 installer 
it may be helpful to identify which kernel is being installed.

On a side note…

The Easter Egg launches the x86 installer in advanced mode. You could try 
taking your working Win/DOS install and try this installer. Tell it not to 
update your MBR and possibly not to update your system files. However if you 
choose not to update your system files, you will need to do it manually. 
Otherwise, the FreeDOS kernel and shell won’t be configured to boot and you 
will still be attempting to boot your previous OS.

:-)






___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Gotcha thank you guys for the support, I have to work till the end of this
week but will try the recommendations after that. If I get it to work ill
let you know what the problem was. Cheers!

On Wed, Jun 9, 2021 at 10:22 AM Eric Auer  wrote:

>
> Hi!
>
> > Ive been using the freedos wiki as a guide, are there any better
> > docs available? Particularly about MBR and SYS with freedos?
>
> In general, I recommend using /? such as SYS /? and FDISK /?
> as a starting point. Both also come with documentation text.
>
> By the way, you can also use GRUB4DOS as boot manager if you
> think a different boot loader would work better, for example
> regarding the MBR step.
>
> And instead of doing everything by hand, just run the advanced
> mode of the installer :-) Jerome can give advice about that.
>
> Eric
>
> --
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Eric Auer]

Hi Andrew,

> 1) The pentium 2 has LBA support, it sees even a 32gb windows 98 partition
> no problem. i486 has no LBA support, so I keep the partition below 2gb. It
> is fine seeing the 2gb DOS partition and booting from it.

It is possible that you end up getting a LBA-only boot sector when
you use the Pentium2 to install on FAT32 and then run the installed
system on the i486. For FAT16, the boot sector can automatically
detect whether LBA is available. In both cases, you can use special
SYS options to force installation/boot in either CHS or LBA style.
You can also use SYS CONFIG to patch flags in the kernel binary to
force either CHS or LBA mode instead of the default autodetection.

While LBA is only necessary when you would have more than 1024 CHS
cylinders afterwards (with or without translation) it CAN be used
for disks of any size. So if the i486 BIOS announces that LBA is
available, but in fact it is buggy, you have a problem. Also, if
SYS sees that the Pentium2 has LBA, it can chose to install a LBA
only boot sector (if you use FAT32) which will then fail after you
put the disk in the 486 if the 486 BIOS supports no LBA etc.

> 2) the wording is read error while reading drive

This does not seem to be one of the error messages in our various
boot sector versions, so I would expect it to be produced by your
MBR, possibly because of some problem with the partitioning.
Otherwise, I would expect our kernel to show at least some other
boot messages before it gets to "error while reading drive", which,
however, is not a common error message for our kernel either. It
could have been "Error reading partition table drive" ... instead?

I do not know enough about your floppy emulator and real floppy
to give advice here. Maybe the emulator is not meant to be used
at the same time as a real floppy? Or you have to change jumpers
or settings on the emulator or the floppy drive?

> 5) I am not sure about the LBA support in the kernel

As said, the default is that the kernel uses LBA when it can,
but you can use SYS CONFIG to patch flags in the kernel binary.

> 6) Yes essentially you boot first into a boot CD, and then instead
> of booting to the CD OS you tell it to boot to hdd it works fine

That is interesting and I remember no similar cases of that, but
maybe half-booting the CD inits some data structures which the
harddisk boot sector took for granted and which are somehow not
properly setup by your BIOS itself. Just guessing there. This
can also include CPU registers and stack location for example.

> 7) I could try partitioning and formatting in DOS first, then
> installing freedos onto that.

My suggestion was the inverse: Use the already proven to work
partitioning and filesystem (formatted drive letter) of your
Windows or MS DOS installation without re-partitioning and
without formatting again. The most basic way of installing
FreeDOS would be to just SYS C: to create a boot sector and
copy the kernel - do not forget to also copy command.com and
some other files as necessary, of course, if you want a full
manual install. A much easier suggestion would be to use the
advanced mode of the installer and simply skip fdisk and format
before proceeding to install the packages using the installer.

> 8) For the MBR, should I use /SMBR after partitioning in DOS then again
> after partitioning in freedos? And then reply with the files?

I suggest that you use /SMBR to collect some evidence about
what is going wrong, at any moment which seems to represent
an interesting state of your system. But please do not send
files to the list. Either quote relevant parts of hexdumps
or upload the files somewhere or send them manually to those
who would like to get a copy. I am happy to receive a few
MBRs and boot sectors myself. No full disk images please.

And as said, you could use /MBR or /BMBR to let FDISK write
a suitable MBR to your disk in case the pre-existing one is
really not okay. But again, I suggest to skip the step of
"partitioning in freedos" if we assume that this causes the
boot problems for you.

> 9) I will also try the FDISK /INFO command for both situations

Enjoy. You could also use XFDISK, which is more user friendly,
but shows fewer details. Note that both also have pretty long
config files which let you (mis-) configure lots of settings.
Maybe some of those have bad defaults in our current package!

Regards, Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Gotcha, Ill need to learn more about this, perhaps try a manual install. Is
there any up to date guides for a manual installation?

Ive been using the freedos wiki as a guide, are there any better docs
available? Particularly about MBR and SYS with freedos?

On Wed, Jun 9, 2021 at 9:59 AM Eric Auer  wrote:

>
> Hi!
>
> > Perhaps just a simple bootloader would fix the problem? I only know of
> > modern linux ones, perhaps systemd-boot would work from arch?
>
> You can load DOS with many boot loaders including GRUB,
> but that still usually relies on a working boot sector.
>
> If the MBR has a problem (as said, FDISK lets you install
> one of the built-in templates if the one which was on your
> harddisk before has a problem) then it may indeed help to
> install a boot menu. Given that Win98 works for you, you
> could simply keep the MBR from that.
>
> As said, you may have a problem with LBA, SYS or the MBR
> contents. Even if your disk is not large enough to NEED
> LBA, FreeDOS may still PREFER it unless you disable it.
>
> Our boot sectors are organized into "FAT12 or FAT16
> with automatic choice from CHS or LBA", "FAT32 with
> CHS" and "FAT32 with LBA", as well as "OEMBOOT" which
> is a configurable boot sector to boot different brands
> of DOS kernels:
>
> https://github.com/FDOS/kernel/tree/master/boot
>
> As the docs explain, you can use SYS /OEM:FD to use the
> OEM boot sector with FreeDOS settings. You can also use
> various /FORCE options in case automatic choices would
> be wrong, for example between CHS or LBA. See
>
> https://github.com/FDOS/kernel/blob/master/docs/sys.txt
>
> No, you should not compile your own SYS, I am just
> sharing the source code links as a way of explaining
> the features of the SYS binary you already have :-)
>
> It is unusual that you are experiencing systematic boot
> problems with FreeDOS, so it would help to get more fine
> details of the issue in case a relevant bug causes that.
>
> Regards, Eric
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
-- 
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Eric Auer]

Hi!

> Perhaps just a simple bootloader would fix the problem? I only know of
> modern linux ones, perhaps systemd-boot would work from arch?

You can load DOS with many boot loaders including GRUB,
but that still usually relies on a working boot sector.

If the MBR has a problem (as said, FDISK lets you install
one of the built-in templates if the one which was on your
harddisk before has a problem) then it may indeed help to
install a boot menu. Given that Win98 works for you, you
could simply keep the MBR from that.

As said, you may have a problem with LBA, SYS or the MBR
contents. Even if your disk is not large enough to NEED
LBA, FreeDOS may still PREFER it unless you disable it.

Our boot sectors are organized into "FAT12 or FAT16
with automatic choice from CHS or LBA", "FAT32 with
CHS" and "FAT32 with LBA", as well as "OEMBOOT" which
is a configurable boot sector to boot different brands
of DOS kernels:

https://github.com/FDOS/kernel/tree/master/boot

As the docs explain, you can use SYS /OEM:FD to use the
OEM boot sector with FreeDOS settings. You can also use
various /FORCE options in case automatic choices would
be wrong, for example between CHS or LBA. See

https://github.com/FDOS/kernel/blob/master/docs/sys.txt

No, you should not compile your own SYS, I am just
sharing the source code links as a way of explaining
the features of the SYS binary you already have :-)

It is unusual that you are experiencing systematic boot
problems with FreeDOS, so it would help to get more fine
details of the issue in case a relevant bug causes that.

Regards, Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Perhaps just a simple bootloader would fix the problem? I only know of
modern linux ones, perhaps systemd-boot would work from arch?

On Wed, Jun 9, 2021 at 9:01 AM ZB  wrote:

> On Wed, Jun 09, 2021 at 08:40:25AM -0700, Andrew wrote:
>
> > Ive installed different operating systems on the two hdds I have, over 15
> > times in total between them all. Every time DOS and 98 installs fine,
> > freedos always gives the same error. And if I boot from bios to cd to
> hdd,
> > freedos also works, but I cant do that on i486 computer because it doesnt
> > have cd or floppy drive working. So I know it isnt random/ hardware
> > problem, like faulty hard drive. The OSes work fine.
>
> You wrote in your initial post about "warnings" FreeDOS is giving you; so
> it's clear to me: you've got hardware-related problem. System reported it
> has trouble while trying to access your disk. Maybe something wrong with
> your LBA settings (Normal/Large/LBA in BIOS)?
>
> Anyway I would try a different drive/cable pair first
> --
> regards,
> Zbigniew
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
-- 
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

I dont see how it can he hardware related if both DOS 6 and 98 dont have
the problem, but freedos, all on the same hdd and same computer, using a
2Gb partition which shouldnt have LBA problems. Also two computers have
this same problem. Ive tried multiple drives and multiple cables.

On Wed, Jun 9, 2021 at 9:01 AM ZB  wrote:

> On Wed, Jun 09, 2021 at 08:40:25AM -0700, Andrew wrote:
>
> > Ive installed different operating systems on the two hdds I have, over 15
> > times in total between them all. Every time DOS and 98 installs fine,
> > freedos always gives the same error. And if I boot from bios to cd to
> hdd,
> > freedos also works, but I cant do that on i486 computer because it doesnt
> > have cd or floppy drive working. So I know it isnt random/ hardware
> > problem, like faulty hard drive. The OSes work fine.
>
> You wrote in your initial post about "warnings" FreeDOS is giving you; so
> it's clear to me: you've got hardware-related problem. System reported it
> has trouble while trying to access your disk. Maybe something wrong with
> your LBA settings (Normal/Large/LBA in BIOS)?
>
> Anyway I would try a different drive/cable pair first
> --
> regards,
> Zbigniew
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
-- 
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

1) The pentium 2 has LBA support, it sees even a 32gb windows 98 partition
no problem. i486 has no LBA support, so I keep the partition below 2gb. It
is fine seeing the 2gb DOS partition and booting from it.

2) the wording is read error while reading drive
This normally shows up when a hdd is broken, but when I install DOS or 98
to the same drive, it boots correctly and no errors apear.

3) I havnt worked enough in getting the floppy working on the i386, i think
it has to do with a nonstandard ide connection. The bios doesnt give an
error when the connector is upside down, and it sees the drive, but then
the gotek gives an error, funny enough. Might have to do some manual
wiring, but I need to do further testing.

4) Gotek is a floppy drive emulator which reads iso files from a usb, and
has ide connection. Works great in pentium 2, and should work even with a
ibm p/s2 apparently.

5) I am not sure about the LBA support in the kernel, that may fix the
problem. I have tried both the floppy and live CD installs, both dont work.
So I suppose whatever SYS file they use is the one I am using.

6) Yes essentially you boot first into a boot CD, and then instead of
booting to the CD OS you tell it to boot to hdd it works fine, and freedos
boots completely on the pentium 2. I think the CD loads part of the OS,
either freedos or 98, which is able to see the freedos hdd partition and
boot files and boot to it. But the bios isnt able to do that directly to
the hdd. Pritty weird problem.

7) I could try partitioning and formatting in DOS first, then installing
freedos onto that. Im not sure if I tried that, so that might be a good
option.

8) For the MBR, should I use /SMBR after partitioning in DOS then again
after partitioning in freedos? And then reply with the files?

9) I will also try the FDISK /INFO command for both situations, Ill see
what it says. Im not as familiar with dos commands, so any commands  I can
run to inspect the problem will be helpful.


On Wed, Jun 9, 2021 at 8:14 AM Eric Auer  wrote:

>
> Hi Andrew,
>
> > 1) Both use IDE connectors, no sata.
> >
> > 2) The error simply says disk read error in the pentium 2. The i486
> simply
> > has a black screen, like it is trying to load the OS but cannot. Both
> > computer see the hard drive in the bios ( no hard drive post errors).
>
> At which point, using which exact wording? Could
> it be that your BIOS has a bug in LBA support?
>
> > 3) I installed DOS 6 on the pentium 2 on a hdd, moved the hdd to the
> i486,
> > and it boots up every time, and works correctly. Currently the i486 does
> > not see any floppy drive or the gotek I have, but it sees the hdd
>
> What is a gotek? Does the floppy work with another OS?
> Proper wiring, proper jumpers, proper BIOS CMOS setup?
>
> I assume you mean MS DOS 6 by DOS 6? And you had to use
> the Pentium2 to install it for the 486 because even MS
> DOS cannot use the floppy on the 486? Note that MS DOS
> 6 never uses LBA, so if your LBA BIOS has a bug, this
> would not affect MS DOS, but this also limits it to at
> most 8 GB usable disk size. You can also use a special
> feature of our SYS command to modify a flag in your
> FreeDOS kernel file to either disable or force LBA,
> in case LBA or CHS is broken. Depending on whether you
> use FAT16 or FAT32 partitions, you can use different
> boot sectors to prefer CHS or LBA, but I am not sure
> how to access this via SYS command line options. This
> depends on the specific version of our SYS you use.
>
> This may also depend on your BIOS CMOS setup choices.
>
> > 4) it does not get far enough to offer the JEMMEX option on either
> computer.
>
> How far exactly does it get?
>
> > 5) When you load either a Windows 98 CD, or a freedos CD in the pentium
> 2,
> > both give an option to boot from hdd. When I do this freedos boots.
>
> You say FreeDOS boots okay from harddisk when you first start to
> boot from a Win98 or FreeDOS CD and then abort that to continue
> booting from harddisk, on the Pentium2?
>
> > 6) I tried formatting it on 98 then installing freedos to the partition,
> > but it still gives the same error. However this is with automated
> > installer, perhaps with manual installation the problem can be fixed.
>
> That sounds like a question for Jerome. But as said, if you can,
> skip partitioning (and maybe even formatting) the disk in case you
> ran into a bug of FDISK (which that recent update may have fixed).
>
> It is indeed possible that the MBR itself causes troubles with
> booting. Our FDISK has some options to overwrite the boot code
> with one of the built-in templates of FDISK, but you could also
> just keep the boot code left behind by Win98. Our FDISK has he
> options /MBR and /BMBR and you can also use the /SMBR to copy
> the MBR to a file and /AMBR to copy a file to the MBR etc.
>
> > When DOS or 98 sees the freedos partiton, with it installed,
> > it calls it a non-dos partition. Not sure why.
>
> You would have to be more specific about that, 

Re: [Freedos-user] Freedos Install Problem

[ZB]

On Wed, Jun 09, 2021 at 08:40:25AM -0700, Andrew wrote:

> Ive installed different operating systems on the two hdds I have, over 15
> times in total between them all. Every time DOS and 98 installs fine,
> freedos always gives the same error. And if I boot from bios to cd to hdd,
> freedos also works, but I cant do that on i486 computer because it doesnt
> have cd or floppy drive working. So I know it isnt random/ hardware
> problem, like faulty hard drive. The OSes work fine.

You wrote in your initial post about "warnings" FreeDOS is giving you; so
it's clear to me: you've got hardware-related problem. System reported it
has trouble while trying to access your disk. Maybe something wrong with
your LBA settings (Normal/Large/LBA in BIOS)?

Anyway I would try a different drive/cable pair first
-- 
regards,
Zbigniew


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Ive installed different operating systems on the two hdds I have, over 15
times in total between them all. Every time DOS and 98 installs fine,
freedos always gives the same error. And if I boot from bios to cd to hdd,
freedos also works, but I cant do that on i486 computer because it doesnt
have cd or floppy drive working. So I know it isnt random/ hardware
problem, like faulty hard drive. The OSes work fine.

On Wed, Jun 9, 2021 at 7:57 AM ZB  wrote:

> On Wed, Jun 09, 2021 at 07:37:30AM -0700, Andrew wrote:
>
> > 2) The error simply says disk read error in the pentium 2.
>
> Isn't it clear enough? You've got some sort of hardware problem. Try
> different cables, different HDD etc.
> --
> regards,
> Zbigniew
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
-- 
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Eric Auer]

Hi Andrew,

> 1) Both use IDE connectors, no sata.
> 
> 2) The error simply says disk read error in the pentium 2. The i486 simply
> has a black screen, like it is trying to load the OS but cannot. Both
> computer see the hard drive in the bios ( no hard drive post errors).

At which point, using which exact wording? Could
it be that your BIOS has a bug in LBA support?

> 3) I installed DOS 6 on the pentium 2 on a hdd, moved the hdd to the i486,
> and it boots up every time, and works correctly. Currently the i486 does
> not see any floppy drive or the gotek I have, but it sees the hdd

What is a gotek? Does the floppy work with another OS?
Proper wiring, proper jumpers, proper BIOS CMOS setup?

I assume you mean MS DOS 6 by DOS 6? And you had to use
the Pentium2 to install it for the 486 because even MS
DOS cannot use the floppy on the 486? Note that MS DOS
6 never uses LBA, so if your LBA BIOS has a bug, this
would not affect MS DOS, but this also limits it to at
most 8 GB usable disk size. You can also use a special
feature of our SYS command to modify a flag in your
FreeDOS kernel file to either disable or force LBA,
in case LBA or CHS is broken. Depending on whether you
use FAT16 or FAT32 partitions, you can use different
boot sectors to prefer CHS or LBA, but I am not sure
how to access this via SYS command line options. This
depends on the specific version of our SYS you use.

This may also depend on your BIOS CMOS setup choices.

> 4) it does not get far enough to offer the JEMMEX option on either computer.

How far exactly does it get?

> 5) When you load either a Windows 98 CD, or a freedos CD in the pentium 2,
> both give an option to boot from hdd. When I do this freedos boots.

You say FreeDOS boots okay from harddisk when you first start to
boot from a Win98 or FreeDOS CD and then abort that to continue
booting from harddisk, on the Pentium2?

> 6) I tried formatting it on 98 then installing freedos to the partition,
> but it still gives the same error. However this is with automated
> installer, perhaps with manual installation the problem can be fixed.

That sounds like a question for Jerome. But as said, if you can,
skip partitioning (and maybe even formatting) the disk in case you
ran into a bug of FDISK (which that recent update may have fixed).

It is indeed possible that the MBR itself causes troubles with
booting. Our FDISK has some options to overwrite the boot code
with one of the built-in templates of FDISK, but you could also
just keep the boot code left behind by Win98. Our FDISK has he
options /MBR and /BMBR and you can also use the /SMBR to copy
the MBR to a file and /AMBR to copy a file to the MBR etc.

> When DOS or 98 sees the freedos partiton, with it installed,
> it calls it a non-dos partition. Not sure why.

You would have to be more specific about that, for example using
FDISK /INFO /TECH or /STATUS or /DUMP or similar, although for
my taste, those are still not verbose enough, so maybe simply
show hexdumps of the right MBR after copying it to a file ;-)

> 7) I downloaded freedos last week, if should be up to date. I did see some
> old forums from 2002 or so with similar, but not exactly the same problem,
> that were fixed however.

I meant the FDISK update by Japheth and Tom, see:

https://www.bttr-software.de/forum/board_entry.php?id=17440

Given that this was about 1.3.1 while GITHUB as 1.3.4:

https://gitlab.com/FDOS/base/fdisk/-/tree/master/BIN

While the 1.3rc4 boot CD has 1.3.4a, it should be up to date:

http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/previews/1.3-rc4/report.html

> 8) Could the bios not be able to compensate for the cylinder problem,
> causing it not to boot? Which is why it can boot from bios to cd to hdd,
> but not bios to hdd?

It could be that the BIOS and DOS disagree about the geometry,
but given that both agree about sector and head, just not about
the cylinder, I would rather expect this to be a problem with
FDISK or a bogus warning from the kernel in case it has a bug
regarding the decision when to show the message. But unlikely.

Regards, Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[ZB]

On Wed, Jun 09, 2021 at 07:37:30AM -0700, Andrew wrote:

> 2) The error simply says disk read error in the pentium 2.

Isn't it clear enough? You've got some sort of hardware problem. Try
different cables, different HDD etc.
-- 
regards,
Zbigniew


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Andrew]

Thank you for replying.

1) Both use IDE connectors, no sata.

2) The error simply says disk read error in the pentium 2. The i486 simply
has a black screen, like it is trying to load the OS but cannot. Both
computer see the hard drive in the bios ( no hard drive post errors).

3) I installed DOS 6 on the pentium 2 on a hdd, moved the hdd to the i486,
and it boots up every time, and works correctly. Currently the i486 does
not see any floppy drive or the gotek I have, but it sees the hdd
correctly.

4) it does not get far enough to offer the JEMMEX option on either computer.

5) When you load either a Windows 98 CD, or a freedos CD in the pentium 2,
both give an option to boot from hdd. When I do this freedos boots. However
it gives the previous error when going from bios directly to boot hdd. It
seems like the bios cant see the boot partition, although it is set to
active.

6) I tried formatting it on 98 then installing freedos to the partition,
but it still gives the same error. However this is with automated
installer, perhaps with manual installation the problem can be fixed. Im
not sure if the problem is with the filesystem or with the mbr or with the
partition. When DOS or 98 sees the freedos partiton, with it installed, it
calls it a non-dos partition. Not sure why.

7) I downloaded freedos last week, if should be up to date. I did see some
old forums from 2002 or so with similar, but not exactly the same problem,
that were fixed however.

8) Could the bios not be able to compensate for the cylinder problem,
causing it not to boot? Which is why it can boot from bios to cd to hdd,
but not bios to hdd?

On Wed, Jun 9, 2021 at 7:18 AM Eric Auer  wrote:

>
> Hi Andrew,
>
> I assume your 486 and your Pentium2 both use ATAPI
> CD drives and IDE harddisks, not SATA? Can you be
> more specific about the (harddisk?) read errors on
> the Pentium 2 after install? What does the BIOS and
> CMOS setup say about your i486 which does not boot?
>
> In general, I recommend the following: When asked
> at boot, do NOT select the option with JEMMEX or
> JEMM386. The default config sys uses options for
> those two which require some level of compatibility
> from your hardware and firmware. We should use more
> humble defaults for that! As said, the easiest way
> to avoid this is to select one of the other boot
> menu options which simply load no EMM386 at all.
>
> What do you mean by the following?
>
> > However in the pentium 2 when I boot to any CD then boot
> > to the hdd, it is able to read the hdd and boot to freedos.
>
> > However the i486 I have not been able to get the cd/
> > floppy drive to work, but it can run dos off the hdd,
> > and the pentium 2 can run dos or windows 98.
>
> So the 486 does actually boot? Or not? How have you
> installed DOS to the harddisk without using the CD?
>
> By using a boot USB (unlikely for 486)? Or floppy?
> Or by installing while the harddisk of the 486 was
> in a more modern computer for easier installation?
>
> You say you have used different partitioning schemes,
> but all had some (?) problems with FreeDOS? Have you
> tried to keep the partitions from Win98 and just put
> FreeDOS on them, optionally after formatting them?
>
> If your problem is specific to FreeDOS FDISK, there
> has been an update recently which may fix it, but as
> said, if you already have a bootable FAT32 partition
> from Win98, you could simply recycle that as-is.
>
> Which warning does FreeDOS produce when booting from CD?
>
> > if I have freedos installed on the hdd: initdisk warning using
> > suspect partition pri:1 FS 06: with calculated values 260-254-63
> > instead of 261-254-63 cant get drive parameters for drive 01.
>
> Apparently this describes a 2 GB partition and the last
> cylinder of the partition mismatches by 1 between CHS
> and LBA values. The last head and sector both do match.
>
> Regards, Eric
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
-- 
Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos Install Problem

[Eric Auer]

Hi Andrew,

I assume your 486 and your Pentium2 both use ATAPI
CD drives and IDE harddisks, not SATA? Can you be
more specific about the (harddisk?) read errors on
the Pentium 2 after install? What does the BIOS and
CMOS setup say about your i486 which does not boot?

In general, I recommend the following: When asked
at boot, do NOT select the option with JEMMEX or
JEMM386. The default config sys uses options for
those two which require some level of compatibility
from your hardware and firmware. We should use more
humble defaults for that! As said, the easiest way
to avoid this is to select one of the other boot
menu options which simply load no EMM386 at all.

What do you mean by the following?

> However in the pentium 2 when I boot to any CD then boot
> to the hdd, it is able to read the hdd and boot to freedos.

> However the i486 I have not been able to get the cd/
> floppy drive to work, but it can run dos off the hdd,
> and the pentium 2 can run dos or windows 98.

So the 486 does actually boot? Or not? How have you
installed DOS to the harddisk without using the CD?

By using a boot USB (unlikely for 486)? Or floppy?
Or by installing while the harddisk of the 486 was
in a more modern computer for easier installation?

You say you have used different partitioning schemes,
but all had some (?) problems with FreeDOS? Have you
tried to keep the partitions from Win98 and just put
FreeDOS on them, optionally after formatting them?

If your problem is specific to FreeDOS FDISK, there
has been an update recently which may fix it, but as
said, if you already have a bootable FAT32 partition
from Win98, you could simply recycle that as-is.

Which warning does FreeDOS produce when booting from CD?

> if I have freedos installed on the hdd: initdisk warning using
> suspect partition pri:1 FS 06: with calculated values 260-254-63
> instead of 261-254-63 cant get drive parameters for drive 01.

Apparently this describes a 2 GB partition and the last
cylinder of the partition mismatches by 1 between CHS
and LBA values. The last head and sector both do match.

Regards, Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Freedos Install Problem

[Andrew]

Hello Guys,
I am new to the mailing list and retro computers in general, (mostly work
on linux), but I've been having some problems with installation. I have a
Pentium 2 233mhz, 128mb ram, and a compaq presario i486, 8mb of ram ive
been trying to install freedos to. After the install and booting from hdd
freedos, the pentium 2 gives disk read errors, and the i486 simply stays on
black screen and never boots. However in the pentium 2 when I boot to any
CD then boot to the hdd, it is able to read the hdd and boot to freedos.
However the i486 I have not been able to get the cd/ floppy drive to work,
but it can run dos off the hdd, and the pentium 2 can run dos or windows 98.

 On the pentium 2, I use the same hdd and remake the partition, (delete
partition, fdisk /mbr, new partition), I am able to install and boot
directly from hdd windows 98 or dos.  I have tried letting freedos use its
own partition scheme, tried 2gb fat16 only, and tried 2gb fat32 only. All
of them have the same problem. When freedos boots from cd, it also gives a
warning if I have freedos installed on the hdd: initdisk warning using
suspect partition pri:1 FS 06: with calculated values 260-254-63 instead of
261-254-63 cant get drive parameters for drive 01. I am guessing this
is the cause of the boot error. I have also tried multiple drives, the
current one I am using is is seagate barracuda 7200 at 200gb, width ide
interface.

Thank you very much,

Andrew Ingram
Fainman Group
Graduate Student, UCSD

Phone: (831)-320-3531
aj1ing...@gmail.com
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS install

[Lawrence Dionne]

Pardon my late reply.  I was able to install it via the legacy installer.
I don't know why I missed that.

I am not much of a gamer, but I do play some games, even in DOS.

My main use for FreeDOS is to create text-based programs and some graphical
prorgams.

I also run an old word processor with speech output.  Haven't tested that
yet though.

Thank you for the assistance.
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install

[James Collins]

Hey guys I just bought soft pic 1.3 unopened in a box with the plastic still on 
it.

What do you think of that ira?

Sent from my iPhone

> On Jan 10, 2017, at 5:41 PM, Jerome Shidel  wrote:
> 
> Also, try to just install BASE and not FULL. You can install the other 
> packages after the install completes. 
> 
> 
>> On Jan 10, 2017, at 4:59 PM, Ira Minor  wrote:
>> 
>> Try using the Legacy Installer CD rather than the Standard one.
>> 
>> Ira
>> 
>> irami...@gmail.com  805-212-0588
>> 
>>> On Tue, Jan 10, 2017 at 1:10 PM, Lawrence Dionne  
>>> wrote:
>>> I have an old Dell computer: Intel Celeron processor 700Mhz CPU 320MB RAM
>>> 
>>> I thought it would make a nice machine for installin and runnin FreeDOS, 
>>> but here is the issue:
>>> 
>>> "freedos invalid opcode at 0FAE 1068 0046 0001 0002  0200   
>>> 0183  4200 0001"
>>> 
>>> I boot the CD, choose "Install to hard drive" and after some text I get a 
>>> constantly scrollin message.
>>> 
>>> I was able to get it to install, at least partially by the following 
>>> procedure:
>>> 
>>> Start the CD then after choosing install to hard drive, I press F8 to 
>>> choose the config.sys settings.
>>> 
>>> Once I skip the "himemx.sys" item, it will install, at least partially.  I 
>>> stops at the 4DOS packages.
>>> 
>>> Does anyone know of a fix for this?  Is the computer too 'Old' for FreeDOS?
>>> 
>>> 
>>> 
>>> --
>>> Developer Access Program for Intel Xeon Phi Processors
>>> Access to Intel Xeon Phi processor-based developer platforms.
>>> With one year of Intel Parallel Studio XE.
>>> Training and support from Colfax.
>>> Order your platform today. http://sdm.link/xeonphi
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>> 
>> 
>> --
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install

[Jerome Shidel]

Also, try to just install BASE and not FULL. You can install the other packages 
after the install completes. 


> On Jan 10, 2017, at 4:59 PM, Ira Minor  wrote:
> 
> Try using the Legacy Installer CD rather than the Standard one.
> 
> Ira
> 
> irami...@gmail.com  805-212-0588
> 
>> On Tue, Jan 10, 2017 at 1:10 PM, Lawrence Dionne  
>> wrote:
>> I have an old Dell computer: Intel Celeron processor 700Mhz CPU 320MB RAM
>> 
>> I thought it would make a nice machine for installin and runnin FreeDOS, but 
>> here is the issue:
>> 
>> "freedos invalid opcode at 0FAE 1068 0046 0001 0002  0200   0183 
>>  4200 0001"
>> 
>> I boot the CD, choose "Install to hard drive" and after some text I get a 
>> constantly scrollin message.
>> 
>> I was able to get it to install, at least partially by the following 
>> procedure:
>> 
>> Start the CD then after choosing install to hard drive, I press F8 to choose 
>> the config.sys settings.
>> 
>> Once I skip the "himemx.sys" item, it will install, at least partially.  I 
>> stops at the 4DOS packages.
>> 
>> Does anyone know of a fix for this?  Is the computer too 'Old' for FreeDOS?
>> 
>> 
>> 
>> --
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
> 
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install

[Ira Minor]

Try using the Legacy Installer CD rather than the Standard one.

Ira

irami...@gmail.com  805-212-0588

On Tue, Jan 10, 2017 at 1:10 PM, Lawrence Dionne 
wrote:

> I have an old Dell computer: Intel Celeron processor 700Mhz CPU 320MB RAM
>
> I thought it would make a nice machine for installin and runnin FreeDOS,
> but here is the issue:
>
> "freedos invalid opcode at 0FAE 1068 0046 0001 0002  0200  
> 0183  4200 0001"
>
> I boot the CD, choose "Install to hard drive" and after some text I get a
> constantly scrollin message.
>
> I was able to get it to install, at least partially by the following
> procedure:
>
> Start the CD then after choosing install to hard drive, I press F8 to
> choose the config.sys settings.
>
> Once I skip the "himemx.sys" item, it will install, at least partially.  I
> stops at the 4DOS packages.
>
> Does anyone know of a fix for this?  Is the computer too 'Old' for FreeDOS?
>
>
>
> 
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS Install

[Lawrence Dionne]

I have an old Dell computer: Intel Celeron processor 700Mhz CPU 320MB RAM

I thought it would make a nice machine for installin and runnin FreeDOS,
but here is the issue:

"freedos invalid opcode at 0FAE 1068 0046 0001 0002  0200  
0183  4200 0001"

I boot the CD, choose "Install to hard drive" and after some text I get a
constantly scrollin message.

I was able to get it to install, at least partially by the following
procedure:

Start the CD then after choosing install to hard drive, I press F8 to
choose the config.sys settings.

Once I skip the "himemx.sys" item, it will install, at least partially.  I
stops at the 4DOS packages.

Does anyone know of a fix for this?  Is the computer too 'Old' for FreeDOS?
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS install aborted into VirtualBox - Help please

[Eric Auer]

Hi Knute,

 Can you help, please?... I finally installed FreeDOS into VirtualBox,
 except at the very end of the install instead of the window where the
 instructions say Now we boot FreeDOS in our virtual machine (select
 1)... instead of that the DOS window says Bad or missing Command
 Interpreter: C:\FDOS\BIN\command.com ...

Have you tried to boot with fewer drivers? Use the F5 or F8 hotkeys
when the kernel loads to skip all or selected drivers. Or, if that
works as expected, just use the menu provided by FreeDOS config sys:

It is possible that your EMS/UMB/XMS/HMA memory driver or disk cache
get confused which could make DOS disconnect from your virtual disk.

Of course it is also possible that you just have some failure in
installing all necessary boot files. Boot from the install CD or
ISO and look if you have command.com in c:\fdos\bin\ as expected.

Which version of FreeDOS were you installing from? One of the CD
ISO images, I assume? By making the ISO visible as a virtualbox
virtual CD? Or by burning it to real CD or DVD first? The latter
should not be necessary, I am just trying to gather more details.

Regards, Eric


--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS install aborted into VirtualBox - Help please

[Knute Myhrvold]

Can you help, please?... I finally installed FreeDOS into VirtualBox, except at 
the very end of the install instead of the window where the instructions say 
Now we boot FreeDOS in our virtual machine (select 1)...
instead of that the DOS window says Bad or missing Command Interpreter: 
C:\FDOS\BIN\command.com C:\FDOS\BIN /E:1024/P=C:\Autoexec.batEnter the full 
shell command line:_ ... and then it freezes.

I've been struggling with this for quite some time, and just when I thought I'd 
made it to the end it gives me this Bad... message and dies.  Any suggestions 
on how to correct this?  Or must I uninstall everything and begin over?

Thanks for any help you can give!
~Knute

---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install HOWTO does not take you to HOWTO

[Jim Hall]

Oops. Thanks for pointing that out. We moved the wiki to
www.freedos.org/wiki and I did not remember to update this link.

I'll do this tomorrow when I'm home from vacation.
On Jul 29, 2014 2:54 PM, Jaroslav Beran jaroslav.be...@gmail.com wrote:

 Hello,

 FreeDOS Install HOWTO link on main page http://www.freedos.org/ does
 not take you to HOWTO.

 Jarda


 --
 Infragistics Professional
 Build stunning WinForms apps today!
 Reboot your WinForms applications with our WinForms controls.
 Build a bridge from your legacy apps to the future.

 http://pubads.g.doubleclick.net/gampad/clk?id=153845071iu=/4140/ostg.clktrk
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user


--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS Install HOWTO does not take you to HOWTO

[Jaroslav Beran]

Hello,

FreeDOS Install HOWTO link on main page http://www.freedos.org/ does not
take you to HOWTO.

Jarda
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071iu=/4140/ostg.clktrk___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Rugxulo]

Hi,
   BTW, this isn't directly related to this guy (and haven't heard any
feedback from him lately), but I'll continue in this thread here
anyways since the topic is still valid.

Seems there is a bug in VirtualBox (4.1.8, at least, doubtful fixed in
4.1.10) that causes implicit file renaming to fail in FreeDOS. So
things like UPX and sed -i don't work correctly, it keeps the
garbled temporary name instead and doesn't work. It's not the fault of
the shell (4DOS, FreeCOM), and it's not DOSLFN. I even upgraded the
kernel to 2041 (from 2040), skeptically, but that didn't fix it
either.

It turns out that the bug isn't there when VT-X is enabled, only when
it's off (blech!). So I saw it on my laptop but not desktop. Very
annoying, it's almost unusable with such a bug (and was already kinda
painfully slow without VT-X).

I have no idea how to even describe such a bug for their bugtracker,
much less have any hope that they actually care or could fix it. Just
mentioning it here in case someone cares. (Perhaps now would be a good
time for me to test some other VMs.)


On Fri, Mar 2, 2012 at 2:59 PM, nweissma nweis...@verizon.net wrote:

 I am using solaris 11 11/11 (64-bit; latest) as the VirtualBox host; VB
 version is 4.1.8 (the latest) https://www.virtualbox.org/wiki/Downloads;
  and I am using fd11src.iso (although I am in possession of fdfullcd [152
 MB]and fdfullws [241MB])

 I mention that the hardware = AMD Athlon II x2 250 .. I will mine sysbo data
 if you request it

 From: Rugxulo
 Sent: Friday, March 02, 2012 12:47 AM
 To: freedos-user@lists.sourceforge.net
 Subject: Re: [Freedos-user] FreeDOS Install on VirtualBox

 BTW, what host OS and which version of VirtualBox are you using? And I
 assume you're using fd11src.iso?

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Jim Hall]

 On Thu, Mar 1, 2012 at 10:34 PM, Neal Weissman nweis...@gmail.com wrote:
 i will attempt another install and do as you say:
...

 and report back to you.

 but i don't understand your instruction try running without UIDE --
how do
 i do that (it seems to be a procedure different from leaving the REM in
 front of UIDE)?

You don't have to reinstall. You can put the REM back (which comments out
the line, it stands for remark) or you can step through as Rugxulo
suggested and tell FreeDOS not to run the UIDE line.
--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Mark Brown]

also rewriting the reboot alias in autoexec.bat/fdauto.bat
so a cold reboot is performed might maybe reboot the machine
better.

.
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
eufdp...@yahoo.com
..--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Bernd Blaauw]

Op 1-3-2012 23:41, nweissma schreef:

 your instructions don't say how to 'reboot' .. being a noob, i tried
 entering reboot -- and it seemed to work -- mentioned something about
 warm reboot -- and then /hung/. how can i get passed this point?

There are various ways to reboot:
* press powerswitch on your machine, twice I guess :)
* press reset button on your machine
* press control, alt and delete keys on keyboard simultaneously
* use some software to reboot the machine.

There are many programs that can perform reboots. FreeDOS by default 
provides FDISK and FDAPM for this:
* FDISK /REBOOT
* FDAPM WARMBOOT

Most convenient would be if the shell or a memory driver would provide a 
reboot/restart/reset command, but alas.

You might be able to fix this issue permanently on an installed FreeDOS 
on your machine by replacing

ALIAS restart  = fdapm warmboot

by

ALIAS restart = fdisk /reboot

hope that helps.

Other issues were with the keyboard driver, requiring /NOHI as well as 
an issue with HIMEM/EMM386 combined with DEVLOAD /H , which as 
workaround can be fixed by removing the (first) /H part in 
autoexec.bat's DEVLOAD line (used for UIDE if I remember correctly).

Bernd

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Bernd Blaauw]

Op 2-3-2012 0:31, Rugxulo schreef:
 I don't know why Bernd disabled it. I guess it didn't work well for
 him under VMware. But it works fine in VirtualBox for me.

It will work fine, but the generated loading of 
AMD/PCNET/VMware/Virtualbox packet driver would be for everyone who 
installed FreeDOS 1.1, instead of only those with the relevant (virtual) 
hardware.

In other words, there's no generic network adapter selection yet, nor 
were the big collection of packet drivers bundled in FreeDOS 1.1


--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Bernd Blaauw]

Op 2-3-2012 16:13, Mark Brown schreef:
 also rewriting the reboot alias in autoexec.bat/fdauto.bat
 so a cold reboot is performed might maybe reboot the machine
 better.

Likely, I'll implement it for FreeDOS 1.2, thanks for your suggestion.
Actually I'd prefer the HOTBOOT (from JEMMEX, mimicking good old QEMM 
there) but that's still quite unstable due to FreeDOS kernel-specific 
issues.

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[nweissma]

I am using solaris 11 11/11 (64-bit; latest) as the VirtualBox host; VB version 
is 4.1.8 (the latest) https://www.virtualbox.org/wiki/Downloads;  and I am 
using fd11src.iso (although I am in possession of fdfullcd [152 MB]and fdfullws 
[241MB])

I mention that the hardware = AMD Athlon II x2 250 .. I will mine sysbo data if 
you request it


From: Rugxulo 
Sent: Friday, March 02, 2012 12:47 AM
To: freedos-user@lists.sourceforge.net 
Subject: Re: [Freedos-user] FreeDOS Install on VirtualBox



BTW, what host OS and which version of VirtualBox are you using? And I
assume you're using fd11src.iso?

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FreeDOS Install on VirtualBox

[nweissma]

PROLEGOMENA: i'm a noob.


kudos: your instructions are understandable, unlike others that i've grappled 
with (and lost). Many Thanks for Your Efforts.

i was successfully following your instructions until 
http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_6

where it reads:


a.. Type auto to edit AUTOEXEC.BAT again. 
a.. Remove the REM before the line DHCP. 
  That means the mTCP DHCP client is started at every boot to update your 
clients network settings. 

a.. Reboot 
a.. You should see boot messages like this one: 

your instructions don't say how to 'reboot' .. being a noob, i tried entering 
reboot -- and it seemed to work  -- mentioned something about warm reboot 
-- and then hung. how can i get passed this point?


i suspect that chapter 8 also has relevance because i recall seeing the 
white-on-black screen shown in the instructions.--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Rugxulo]

Hi,

On Thu, Mar 1, 2012 at 4:41 PM, nweissma nweis...@verizon.net wrote:

 kudos: your instructions are understandable, unlike others that i've
 grappled with (and lost). Many Thanks for Your Efforts.

 i was successfully following your instructions until
 http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_6

 where it reads:

 Type auto to edit AUTOEXEC.BAT again.

That is just a shell alias. Type alias to see what is set by
default. Or just manually edit c:\autoexec.bat.

 Remove the REM before the line DHCP.

 That means the mTCP DHCP client is started at every boot to update your
 clients network settings.

I don't know why Bernd disabled it. I guess it didn't work well for
him under VMware. But it works fine in VirtualBox for me.

 Reboot

 You should see boot messages like this one:

 your instructions don't say how to 'reboot' .. being a noob, i tried
 entering reboot -- and it seemed to work  -- mentioned something about
 warm reboot -- and then hung. how can i get passed this point?

Normally, Ctrl-Alt-Del would work, but for a virtual machine, that may
not do what you want (as the host OS may misinterpret it).

Again, I believe reboot is just a shell alias to fdapm warmboot or similar.

 i suspect that chapter 8 also has relevance because i recall seeing the
 white-on-black screen shown in the instructions.

... dunno ...

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Jim Hall]

On Thu, Mar 1, 2012 at 4:41 PM, nweissma nweis...@verizon.net wrote:
 PROLEGOMENA: i'm a noob.


 kudos: your instructions are understandable, unlike others that i've
 grappled with (and lost). Many Thanks for Your Efforts.

 i was successfully following your instructions until
 http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_6

 where it reads:

 Type auto to edit AUTOEXEC.BAT again.

 Remove the REM before the line DHCP.

 That means the mTCP DHCP client is started at every boot to update your
 clients network settings.

 Reboot

 You should see boot messages like this one:


 your instructions don't say how to 'reboot' .. being a noob, i tried
 entering reboot -- and it seemed to work  -- mentioned something about
 warm reboot -- and then hung. how can i get passed this point?


 i suspect that chapter 8 also has relevance because i recall seeing the
 white-on-black screen shown in the instructions.


You describe 2 problems, which I'll tackle separately:


1. How to reboot?

Oops, we don't actually describe how to reboot, do we? Entering the
'REBOOT' command will do the job, so that's good. You can also just go
into the VirtualBox controls and manually reboot the virtual machine
there. DOS is a very simple operating system, so rebooting by doing a
reset or power off/on is fine.


2. Why does FreeDOS hang during reboot?

The answer to this depends on what FreeDOS is trying to do when it hangs:

If FreeDOS hangs when it's trying to load UIDE support, then the
problem is likely with the chipset setting in VirtualBox. This is
described in chapter 8.

If FreeDOS hangs when it is trying to load the packet driver, and
gives a Device not found message, then unfortunately this is the
*other* chipset setting in VirtualBox. This is also described in
chapter 8.

Which error message do you see when it hangs? What is the last line of
text in the boot sequence before things stop?

As a debugging step, try booting FreeDOS without drivers (using the
boot menu.) FreeDOS should at least bring up a C:\ prompt. If that
works, try commenting out the UIDE line in the AUTOEXEC.BAT file.
Reboot - if FreeDOS boots normally this time, then the problem is with
the first chipset setting in VirtualBox. Or, just try running without
UIDE, and see if networking comes up.



-jh

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Jim Hall]

I'll also add this: Do you really need to have networking to run FreeDOS?


Chapter 6 of the installation instructions
(http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_6)
describe how to set up networking in FreeDOS, when using VirtualBox.
The reasons to do networking under DOS are usually:

* to run a program that requires the network (a client server program,
or a network game, etc.)

* to browse the web using a DOS-based web browser, such as Dillo

* to or to transfer files between your FreeDOS virtual machine and
another system (usually your host PC)



If you don't need to do these things, you can safely skip the section
in the installation instructions about how to set up networking.


-jh

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Neal Weissman]

i will attempt another install and do as you say:


 Which error message do you see when it hangs? What is the last line of
 text in the boot sequence before things stop?

 As a debugging step, try booting FreeDOS without drivers (using the
 boot menu.) FreeDOS should at least bring up a C:\ prompt. If that
 works, try commenting out the UIDE line in the AUTOEXEC.BAT file.
 Reboot - if FreeDOS boots normally this time, then the problem is with
 the first chipset setting in VirtualBox. Or, just try running without
 UIDE, and see if networking comes up.


and report back to you.

but i don't understand your instruction try running without UIDE -- how
do i do that (it seems to be a procedure different from leaving the REM in
front of UIDE)?

i breathe a sigh of relief: i met someone who's not of the Rabble
mediocrity.

btw, how do i 'reply' to a forum post (yours, for example; thus, if i
wanted the contents of this instant email to immediately follow your post,
then how is that done)?

On Thu, Mar 1, 2012 at 11:02 PM, Jim Hall jh...@freedos.org wrote:

 On Thu, Mar 1, 2012 at 4:41 PM, nweissma nweis...@verizon.net wrote:
  PROLEGOMENA: i'm a noob.
 
 
  kudos: your instructions are understandable, unlike others that i've
  grappled with (and lost). Many Thanks for Your Efforts.
 
  i was successfully following your instructions until
 
 http://sourceforge.net/apps/mediawiki/freedos/index.php?title=VirtualBox_-_Chapter_6
 
  where it reads:
 
  Type auto to edit AUTOEXEC.BAT again.
 
  Remove the REM before the line DHCP.
 
  That means the mTCP DHCP client is started at every boot to update your
  clients network settings.
 
  Reboot
 
  You should see boot messages like this one:
 
 
  your instructions don't say how to 'reboot' .. being a noob, i tried
  entering reboot -- and it seemed to work  -- mentioned something about
  warm reboot -- and then hung. how can i get passed this point?
 
 
  i suspect that chapter 8 also has relevance because i recall seeing the
  white-on-black screen shown in the instructions.
 

 You describe 2 problems, which I'll tackle separately:


 1. How to reboot?

 Oops, we don't actually describe how to reboot, do we? Entering the
 'REBOOT' command will do the job, so that's good. You can also just go
 into the VirtualBox controls and manually reboot the virtual machine
 there. DOS is a very simple operating system, so rebooting by doing a
 reset or power off/on is fine.


 2. Why does FreeDOS hang during reboot?

 The answer to this depends on what FreeDOS is trying to do when it hangs:

 If FreeDOS hangs when it's trying to load UIDE support, then the
 problem is likely with the chipset setting in VirtualBox. This is
 described in chapter 8.

 If FreeDOS hangs when it is trying to load the packet driver, and
 gives a Device not found message, then unfortunately this is the
 *other* chipset setting in VirtualBox. This is also described in
 chapter 8.

 Which error message do you see when it hangs? What is the last line of
 text in the boot sequence before things stop?

 As a debugging step, try booting FreeDOS without drivers (using the
 boot menu.) FreeDOS should at least bring up a C:\ prompt. If that
 works, try commenting out the UIDE line in the AUTOEXEC.BAT file.
 Reboot - if FreeDOS boots normally this time, then the problem is with
 the first chipset setting in VirtualBox. Or, just try running without
 UIDE, and see if networking comes up.



 -jh


 --
 Virtualization  Cloud Management Using Capacity Planning
 Cloud computing makes use of virtualization - but cloud computing
 also focuses on allowing computing to be delivered as a service.
 http://www.accelacomm.com/jaw/sfnl/114/51521223/
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user




-- 

/s/ Neal Weissman
--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FreeDOS Install on VirtualBox

[Rugxulo]

Hi,

On Thu, Mar 1, 2012 at 10:34 PM, Neal Weissman nweis...@gmail.com wrote:
 i will attempt another install and do as you say:

 Which error message do you see when it hangs? What is the last line of
 text in the boot sequence before things stop?

 As a debugging step, try booting FreeDOS without drivers (using the
 boot menu.) FreeDOS should at least bring up a C:\ prompt. If that
 works, try commenting out the UIDE line in the AUTOEXEC.BAT file.
 Reboot - if FreeDOS boots normally this time, then the problem is with
 the first chipset setting in VirtualBox. Or, just try running without
 UIDE, and see if networking comes up.


 and report back to you.

 but i don't understand your instruction try running without UIDE -- how do
 i do that (it seems to be a procedure different from leaving the REM in
 front of UIDE)?

F8 will step-by-step through the CONFIG.SYS (and AUTOEXEC.BAT),
letting you manually load (or not) various drivers, including UIDE.

BTW, what host OS and which version of VirtualBox are you using? And I
assume you're using fd11src.iso?

 i breathe a sigh of relief: i met someone who's not of the Rabble
 mediocrity.

 btw, how do i 'reply' to a forum post (yours, for example; thus, if i wanted
 the contents of this instant email to immediately follow your post, then how
 is that done)?

Looks like you did so just fine.

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Freedos Install Options

[Larry]

I have an old W95 era Dell Laptop that I still find useful. I managed to 
install Linux Etch in it by installing w/o Xwindows, then adding that later so 
I could control what all that was installed. I use either Ratpoison or Fluxbox 
for my windows manager.

I have Freedos installed two ways on the Laptop. I can run it in dosemu, or I 
have the option to boot to it directly for any apps that won't run in dosemu. 
Booting directly to Freedos lets me be up and running very quickly, and I can 
get to the Freedos directory later from Linux, so I have access to work from 
either platform.

If I only knew how to get networking to work with Freedos via my pcmcia network 
wirless card, I'd likely boot to Freedos more often than to Linux. But for now, 
I only know how to get the wireless working through Linux.

I'm not a gamer, so I don't really have need for any version of Windows. I do 
use a USB Quickcam Express webcam for astrophotography, and for a time the only 
package I knew that drove the webcam was the Windows software it came with. Now 
I can use Linux and a program called camstream.  

Even better would be some dos compatible webcam program, but I must learn to be 
happy with the nice things Freedos does supply, making an old laptop still a 
valuable asset.

--- On Sun, 6/21/09, Eric Auer e.a...@jpberlin.de wrote:

 From: Eric Auer e.a...@jpberlin.de
 Subject: Re: [Freedos-user] Peace and Quiet!
 To: freedos-user@lists.sourceforge.net
 Date: Sunday, June 21, 2009, 9:32 AM
 
 Hi!
 
  needed to support some.  If Dos based Windows is
  used, Freedos is possibly being run on a computer
  that has 128+ megs of RAM.  There are a LOT of
  old computers that have this much RAM.
 
 And several operating systems that can run there ;-)
 
  Freedos can ask, Are you on a Pentium, 486, 386,
 286,
  or 8088, at install time.  Based off of that
 info...
 
 You typically install from CD today, so you can assume
 a 386 or better, often Pentium or better CPU. Many apps
 run on 8086, but to have decent memory management, you
 typically want HIMEMX and a 386. Several drivers also
 require that. There are also floppy distros for 8086.
 I would not put too much extra 8086 fiddling inside a
 CD distro installer if you ask me. Almost no apps need
 a more modern CPU than 386, or would gain from a FPU.
 Well, probably Arachne would... I also think FreeBASIC
 had issues with 486sx and older CPU which lack a FPU.
 
  is possible to decide whether or not certain programs
  like Firefox for example make any sense.  I
 seriously 
  doubt that anyone wants to run Arachne on anything
 less 
  than a 486 with at least 2 megs of RAM for example.
 
 On any PC which is too old to run NT or Linux, you
 probably want Dillo and not Firefox anyway... ;-)
 
 Interestingly, Firefox depends mostly on GTK, Python
 and Cairo. Python 2.4 already exists for DOS DJGPP.
 Cairo has backends for GTK and Win32, but Nokia did
 help with some QPainter backend for QT. It makes me
 wonder how hard writing a VESA framebuffer backend
 for DOS might be. On the other hand, I really wonder
 how far HX is from running older Firefox for Win32.
 
 Note that while DOS runs on modern hardware, it
 does not necessarily make use of it. There is
 no surround sound, multi-core, more-than-4-GB-
 of-RAM or similar support, but it does not hurt
 to have that hardware while running DOS either.
 
  of Linux that installs to a FAT directory and
  exits to Freedos when you are done would be fine
 
 On the other hand, switching THAT way would not
 be much faster than rebooting to DOS either ;-)
 
  In short, the state of Freedos's Arachne poses a
  security problem for anyone who needs to make sure
  that a graphical web browser has a local filter
 
 You cannot install censorship in any DOS browser
 because in DOS, every user always is the admin.
 
  Sure you might filter at the router to the net
 
 That would be morer secure indeed.
 
 Eric
 
 
 
 --
 Are you an open source citizen? Join us for the Open Source
 Bridge conference!
 Portland, OR, June 17-19. Two days of sessions, one day of
 unconference: $250.
 Need another reason to go? 24-hour hacker lounge. Register
 today!
 http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user
 


  


--
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org
___
Freedos-user mailing list

Re: [Freedos-user] FreeDOS install on 2nd hard drive

[Eric Auer]

Hi Eric ;-)

 I'd like to put FreeDOS on HDB1,
 but wanted to know if that was possible.

Yes but this will change the drive letters for the
other FAT partitions on HDB, I guess. Unless you
ask Grub / ... to hide the DOS partition before it
boots Windows.

 boot using a DOS bootable floppy, HDA1 shows up as C:, HDB8 shows
 up as D:.  If I install FreeDOS, will it be able to use C:?

Yes but HDB8 will become E: and booting from HDB1 might mean that
drive letters will be different anyway? It might call HDB1 C: then,
HDB8 D: or E:, and HDA1 D: or E:...?

 Also, will FreeDOS mess up my drive lettering in XP?

I think in XP you can tell which drive letters are where,
to make a fixed setup instead of the automatic numbering
which would indeed change when you make HDB1 a FAT disk.
Or, as said, you can tell Grub to dynamically hide DOS.

The NTFS drives of XP (those called C: and D: by XP) will
keep their drive letters anyway afair :-). Note that DOS
will not give the NTFS drives a drive letter at all.

 FreeDOS with Grub, so I think I should be OK.

Eric



-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user