Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[R Moog]

What hypervisor?

śr., 25 wrz 2019, 05:16 użytkownik  napisał:

> I have tried multiple times to install FreeDOS on Raspberry Pi3.
>
>
>
> I have created a 100M and 200M raw disk image.
>
>
>
> Mounted the Standard and then tried with the Legacy ISO.
>
>
>
> Both will boot the ISO, partition and format the hard disk. But when I
> reboot and select the Install to Harddisk after it goes to gathering
> settings a couple of minutes go by and I get:
>
>
>
> I have also tried to mount the floppy.img as well as the ISO and boot from
> floppy with the same results.
>
>
>
> Has anyone seen this and been able to resolve it?
>
>
>
> Thank you,
>
>
>
> Chris
>
>
> ___
> 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] Issue installing FreeDOS on Raspberry Pi 3

[Eric Auer]

Hi Jim,

> When you are finally able to start the installation, be prepared for
> the install process to take a looong time. This is because
> installing all the FreeDOS packages requires a lot of disk I/O to the
> virtual freedos.img drive.

Blasphemic idea: Use symlinks to move the disk image to a RAMDISK
of Linux during DOS install, then close QEMU, move the disk image
back to real (SD or MMC) disk and start using DOS the normal way?
A 200 MB disk image is not much compared to Raspberry RAM sizes.

By the way, which cache and buffers settings does the installer use?
Would it help if FreeDOS had a FASTOPEN to cache directory entries?

SD cards indeed often have very low "I/O per second" because they
are rather optimized to write a few big files, like pics or video,
not many small file modifications in a short period of time.

Regards, Eric



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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Jim Hall]

> From: shift83...@gmail.com
>
> The work-around I have found is to set the image up on my Linux Ubunto 18.04 
> box then transfer the image file over to the raspberry pi.
>
>
>
> I even tried using the FreeDOS 1.3 RC1 installer with the same results on the 
> Raspberry Pi 3.  Both installer ISO’s worked with no issue on the Ubuntu.
>
>  [..]

On Wed, Sep 25, 2019 at 6:56 PM Jon Brase  wrote:
>
> I take it that your Ubuntu box is an x86 PC?
>
> If that is the case, the issue is very likely with QEMU's x86 emulation. On 
> an x86, QEMU is able to use the host CPU to execute x86 instructions, so the 
> emulation layer is only needed for a few instructions that do things that 
> might allow the guest OS to inadvertently or deliberately mess with the host 
> OS's data. On ARM, or any other non-x86 architecture, QEMU has to emulate the 
> full instruction set. This is likely why you're seeing a difference between 
> your Ubuntu box and your Pi. As such, it might be good to file a bug with 
> QEMU.
>


Agree. This seems like there's a bug in QEMU on Raspberry Pi.

I haven't run FreeDOS on my Raspberry Pi since I set it up as a Fedora
30 server (in-home web server, print server, and backup server). So if
there's a bug in QEMU on Raspberry Pi, I haven't had an opportunity to
hit it in the recent builds.

I mentioned in my other email that I thought someone suggested I
should update my OpenSource article with a workaround for installing
FreeDOS on QEMU on RasPi. I am pulling from bad memory here, but I
think the other problem was similar to this.

Jim


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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Jon Brase]

I take it that your Ubuntu box is an x86 PC?
If that is the case, the issue is very likely with QEMU's x86 emulation. On an 
x86, QEMU is able to use the host CPU to execute x86 instructions, so the 
emulation layer is only needed for a few instructions that do things that might 
allow the guest OS to inadvertently or deliberately mess with the host OS's 
data. On ARM, or any other non-x86 architecture, QEMU has to emulate the full 
instruction set. This is likely why you're seeing a difference between your 
Ubuntu box and your Pi. As such, it might be good to file a bug with QEMU.

 Original message 
From: shift83...@gmail.com 
Date: 9/25/2019  18:15  (GMT-06:00) 
To: "'Discussion and general questions about FreeDOS.'" 
 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

The work-around I have found is to set the image up on my Linux Ubunto 18.04 
box then transfer the image file over to the raspberry pi. I even tried using 
the FreeDOS 1.3 RC1 installer with the same results on the Raspberry Pi 3.  
Both installer ISO’s worked with no issue on the Ubuntu. Next I will be trying 
a different SD card. From: Jon Brase  
Sent: Wednesday, September 25, 2019 12:29 AM
To: Discussion and general questions about FreeDOS. 

Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 I 
managed to get the installer to pull packages off the CD, but one thing you may 
be running into is that QEMU de-assigns ISO images from the emulated CD drive 
when the OS sends a disk eject command. On a physical machine, if the CD drive 
ejects a disk you're still using, you notice it and just push the tray back in, 
but in a VM it's a rather annoying behavior for the ISO to be completely 
unassigned, as you don't see that happen, and on reboot it causes the disk to 
no longer be in the drive. When you start the VM fresh with the CD image and 
freshly formatted HDD image specified, do you get the same error?

 Original message 
From: Jon Brase  
Date: 9/25/2019 00:02 (GMT-06:00) 
To: "Discussion and general questions about FreeDOS." 
 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

Interesting, I did have a similar issue on real hardware recently, though the 
situation was enough different that I'm not sure whether they match up, and I 
didn't so much resolve it as work around it. I generally use virt-manager 
rather than the command line to set up QEMU VMs. I'm not sure what QEMU 
defaults to on the command line for things that aren't specified (details of 
how the emulated hardware is presented to the guest OS and such). I may try 
installing FreeDOS in a VM on my machine to see if I can duplicate the issue 
there. 

 Original message 
From: shift83...@gmail.com 
Date: 9/24/2019 23:21 (GMT-06:00) 
To: "'Discussion and general questions about FreeDOS.'" 
 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 Sorry 
for the confusion.  I’m new to QEMU.   So… I created the image with the below 
command: qemu-img create dos.img 200M This is my command line to execute QEMU 
and mount the drives and emulate devices is below: qemu-system-i386 -m 16 -k 
en-us -rtc base=localtime -device cirrus-vga -fda FLOPPY.img -hda freedos.img 
-cdrom FD12CD.iso -boot order=d I have also tried to minimize the command to 
just: qemu-system-i386 -fda FLOPPY.img -had freedos.img -cdrom FD12CD.iso -boot 
order=d I believe the issue is that after it reboots from partitioning and 
formatting the C drive it no longer sees the CDROM when trying to access the 
source packages.  I issues trying to list the directory on the D drive when I 
exit from the installer.   From: Jon Brase  
Sent: Tuesday, September 24, 2019 11:09 PM
To: Discussion and general questions about FreeDOS. 

Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 FreeDOS 
(x86 software) won't boot (natively) on the Raspberry Pi 3 (ARM hardware), so 
if you got as far as to be able to select "install to hard disk", you must be 
using an x86 emulator, and, indeed, your screenshot shows that you're using 
QEMU. To minimize confusion, you should lead with the information that you're 
using QEMU, and follow it up with the fact that you're on a non x86 platform, 
as there are differences in how QEMU handles guest code for the same 
architecture that it's running on and how it handles code for other 
architectures. I myself haven't run FreeDOS on any platform other than x86 PCs, 
so I'm not sure how much help I can be, but can you say what emulated 
peripherals you set up for your FreeDOS  VM in QEMU?

 Original message 
From: shift83...@gmail.com 
Date: 9/24/2019 22:15 (GMT-06:00) 
To: freedos-user@lists.sourceforge.net 
Subject: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 I have tried 
multiple times to install FreeDOS on Raspberry Pi3. I have created a 100M and 
200M raw disk im

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[shift838cs]

The work-around I have found is to set the image up on my Linux Ubunto 18.04 
box then transfer the image file over to the raspberry pi.

 

I even tried using the FreeDOS 1.3 RC1 installer with the same results on the 
Raspberry Pi 3.  Both installer ISO’s worked with no issue on the Ubuntu.

 

Next I will be trying a different SD card.

 

From: Jon Brase  
Sent: Wednesday, September 25, 2019 12:29 AM
To: Discussion and general questions about FreeDOS. 

Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

 

I managed to get the installer to pull packages off the CD, but one thing you 
may be running into is that QEMU de-assigns ISO images from the emulated CD 
drive when the OS sends a disk eject command. On a physical machine, if the CD 
drive ejects a disk you're still using, you notice it and just push the tray 
back in, but in a VM it's a rather annoying behavior for the ISO to be 
completely unassigned, as you don't see that happen, and on reboot it causes 
the disk to no longer be in the drive.

 

When you start the VM fresh with the CD image and freshly formatted HDD image 
specified, do you get the same error?



 Original message 
From: Jon Brase mailto:jon.br...@gmail.com> > 
Date: 9/25/2019 00:02 (GMT-06:00) 
To: "Discussion and general questions about FreeDOS." 
mailto:freedos-user@lists.sourceforge.net> 
> 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

Interesting, I did have a similar issue on real hardware recently, though the 
situation was enough different that I'm not sure whether they match up, and I 
didn't so much resolve it as work around it.

 

I generally use virt-manager rather than the command line to set up QEMU VMs. 
I'm not sure what QEMU defaults to on the command line for things that aren't 
specified (details of how the emulated hardware is presented to the guest OS 
and such).

 

I may try installing FreeDOS in a VM on my machine to see if I can duplicate 
the issue there. 



 Original message 
From: shift83...@gmail.com <mailto:shift83...@gmail.com>  
Date: 9/24/2019 23:21 (GMT-06:00) 
To: "'Discussion and general questions about FreeDOS.'" 
mailto:freedos-user@lists.sourceforge.net> 
> 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

Sorry for the confusion.  I’m new to QEMU.  

 

So…

 

I created the image with the below command:

 

qemu-img create dos.img 200M

 

This is my command line to execute QEMU and mount the drives and emulate 
devices is below:

 

qemu-system-i386 -m 16 -k en-us -rtc base=localtime -device cirrus-vga -fda 
FLOPPY.img -hda freedos.img -cdrom FD12CD.iso -boot order=d

 

I have also tried to minimize the command to just:

 

qemu-system-i386 -fda FLOPPY.img -had freedos.img -cdrom FD12CD.iso -boot 
order=d

 

I believe the issue is that after it reboots from partitioning and formatting 
the C drive it no longer sees the CDROM when trying to access the source 
packages.  I issues trying to list the directory on the D drive when I exit 
from the installer.

 

 

 

From: Jon Brase mailto:jon.br...@gmail.com> > 
Sent: Tuesday, September 24, 2019 11:09 PM
To: Discussion and general questions about FreeDOS. 
mailto:freedos-user@lists.sourceforge.net> 
>
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

 

FreeDOS (x86 software) won't boot (natively) on the Raspberry Pi 3 (ARM 
hardware), so if you got as far as to be able to select "install to hard disk", 
you must be using an x86 emulator, and, indeed, your screenshot shows that 
you're using QEMU. To minimize confusion, you should lead with the information 
that you're using QEMU, and follow it up with the fact that you're on a non x86 
platform, as there are differences in how QEMU handles guest code for the same 
architecture that it's running on and how it handles code for other 
architectures.

 

I myself haven't run FreeDOS on any platform other than x86 PCs, so I'm not 
sure how much help I can be, but can you say what emulated peripherals you set 
up for your FreeDOS  VM in QEMU?



 Original message 
From: shift83...@gmail.com <mailto:shift83...@gmail.com>  
Date: 9/24/2019 22:15 (GMT-06:00) 
To: freedos-user@lists.sourceforge.net 
<mailto:freedos-user@lists.sourceforge.net>  
Subject: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

I have tried multiple times to install FreeDOS on Raspberry Pi3.

 

I have created a 100M and 200M raw disk image.

 

Mounted the Standard and then tried with the Legacy ISO.

 

Both will boot the ISO, partition and format the hard disk. But when I reboot 
and select the Install to Harddisk after it goes to gathering settings a couple 
of minutes go by and I get:

 

I have also tried to mount the floppy.img as well as the ISO and boot from 
floppy with the same results.

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Regan Russell]

> Actually Current CP/M-86 and MP/M were CP/M versions that were
> multi-user and networkable (though no Internet existed those days,
> fortunately)...

I very vaguely remember those days. I almost did a Novell Netware certificate. 
You could make a living with DBASE-II or Turbo Pascal or C with ISAM, writing 
simple software for real estate agents or booking systems for car mechanics. I 
even had nutter post-grad office partner on campus who could route between 
token ring and thick coax ethernet.

There was also this thing called concurrent DOS but I don't remember anything 
good about it, maybe it was the people I was working with at the time.

The source code to CP/M is available on the internet, I have it somewhere, I 
wonder if anyone would be nuts enough to either port it or use it, if it was 
ported.

You can run CP/M under emulation on a RPI...
https://hackaday.com/2016/10/12/raspberry-pi-boots-cpm/
[https://www.bing.com/th?id=OVP.-DtlO7b2K4HjBhbrlbWnJgEsCo=Api]<https://hackaday.com/2016/10/12/raspberry-pi-boots-cpm/>
Raspberry Pi Boots CP/M<https://hackaday.com/2016/10/12/raspberry-pi-boots-cpm/>
Retrocomputing is an enjoyable and educational pursuit and — of course — there 
are a variety of emulators that can let you use and program a slew of old 
computers. However, there’…
hackaday.com


From: Ralf Quint 
Sent: Thursday, 26 September 2019 4:06 AM
To: freedos-user@lists.sourceforge.net 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

On 9/25/2019 9:23 AM, dmccunney wrote:
> Why would they do that? To create much simpler OS for RPI than Linux. Who
> needs that whole complexity on such little SBC? CP/M would do just fine.
> No, it wouldn't.  Digital Research developed CP/M as an OS for 8 bit
> micros like the Intel 8080 and Zilog Z80.  They were single tasking
> CPUs supporting a whopping *64K* of address space.  OS, applications,
> and data all had to fit into 64K.
DR offered CP/M not only for the 8080/8085/Z80 8 bit processors, but
also for Intel 8086 (x86), Motorola 680x0 and Zilog Z8000 CPUs, and at
least the last two don't have a 64K address space limitation...
>
> The Raspberry Pi uses an ARM Cortex CPU, with a 32bit address space
> and a multi-core design.  It can run a full multi-user, multitasking
> OS like Linux, and does.  And ARM CPUs are often used in Internet of
> Things devices.  The critical point is the the CPU can run a full
> TCP-IP networking stack, and become a node *on* the Internet.  A
> second critical point is the the costs of such CPUs have dropped to
> the point where you *can* affordably use something like a a 32bit ARM
> CPU in an embedded device.

Actually Current CP/M-86 and MP/M were CP/M versions that were
multi-user and networkable (though no Internet existed those days,
fortunately)...

Ralf



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
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] Issue installing FreeDOS on Raspberry Pi 3

[Ralf Quint]

On 9/25/2019 9:23 AM, dmccunney wrote:

Why would they do that? To create much simpler OS for RPI than Linux. Who
needs that whole complexity on such little SBC? CP/M would do just fine.
No, it wouldn't.  Digital Research developed CP/M as an OS for 8 bit
micros like the Intel 8080 and Zilog Z80.  They were single tasking
CPUs supporting a whopping *64K* of address space.  OS, applications,
and data all had to fit into 64K.
DR offered CP/M not only for the 8080/8085/Z80 8 bit processors, but 
also for Intel 8086 (x86), Motorola 680x0 and Zilog Z8000 CPUs, and at 
least the last two don't have a 64K address space limitation...


The Raspberry Pi uses an ARM Cortex CPU, with a 32bit address space
and a multi-core design.  It can run a full multi-user, multitasking
OS like Linux, and does.  And ARM CPUs are often used in Internet of
Things devices.  The critical point is the the CPU can run a full
TCP-IP networking stack, and become a node *on* the Internet.  A
second critical point is the the costs of such CPUs have dropped to
the point where you *can* affordably use something like a a 32bit ARM
CPU in an embedded device.


Actually Current CP/M-86 and MP/M were CP/M versions that were 
multi-user and networkable (though no Internet existed those days, 
fortunately)...


Ralf



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Ralf Quint]

On 9/25/2019 7:59 AM, ZB wrote:

On Wed, Sep 25, 2019 at 12:05:04AM -0700, Ralf Quint wrote:


These are two totally different worlds! The only way you could get FreeDOS
to run on a RPi is after installing one of the default Linux versions to
install QEMU, which is an x86 emulator and install FreeDOS within that
virtual machine. Again, FreeDOS can NEVER run natively on a RPi...

With DOS it would mean too much work - but I believe a group of determined
coders could be able to port, say, CP/M. Of course it would be "CP/M-like"
OS for RPi rather than "strict port"
Well, there used to be CP/M 68K (running on the Motorola 680x0 family of 
CPUs) and I think there was a Zilog Z8000 port as well (not to mention 
the original port from 8080/8085/Z80 to x86), but I honestly have never 
bothered how that was accomplished. Beside a bit of "looking around", I 
have never really used CP/M-86, though I did used CP/M-80 extensively 
before the IBM-PC (and similar ones) came out...

Why would they do that? To create much simpler OS for RPI than Linux. Who
needs that whole complexity on such little SBC? CP/M would do just fine.

Well, there is always RiscOS... :P

As Chuck Moore (Forth creator) once said: "most computer operating systems
devolving to caveman interfaces ("point at the pretty pictures and grunt")"


Now comparing Forth to other OS is a bit of heresy... LOL

Ralf ;-)



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Ralf Quint]

On 9/25/2019 7:50 AM, Jim Hall wrote:


Yes, but from the screenshot in his original post, he is installing
FreeDOS in a QEMU virtual machine.


Sorry, didn't see that screenshot (it somehow was blocked by 
Thunderbird) and was going by his description. And that sounded as if 
was trying to install "natively"... :(


Ralf



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Chris Schneider]

I pasted the wrong command.  The freedos.img does exist and I use it in the
command.  The FLOPPY.img also exist and I downloaded it from the freedos.org
site.

My raspberry is a 3+ With a PNY Elite CLass 10 64gb sd  card.

I think the thread you may be referencing may be the one where the user
receives a lot of ‘opcode’ errors and he added ‘raw’ at the end of the
command after boot by pressing tab to fix.

I have tried it with the same results.

On Wed, Sep 25, 2019 at 10:20 AM Jim Hall  wrote:

> On Wed, Sep 25, 2019 at 10:09 AM Jim Hall  wrote:
> >
> [..]
> > I have two suggestions for you:
> >
> > (1)
> > Your "hda" image file is different in the two commands. You created a
> hard disk image named dos.img but you tried to reference a hard disk image
> named freedos.img. Does the freedos.img image file exist? Try re-running
> the qemu-system-i386 command with the dos.img image file you created in
> your earlier qemu-img command.
> >
> > (2)
> > You have an extra parameter to define a floppy disk image named
> FLOPPY.img. Does this image file exist? How did you create it? Try
> re-running the qemu-system-i386 command without the floppy drive defined.
> You don't need it anyway for the install.
> >
> >
> > However, neither of my two suggestions would point to the installer
> being unable to find the installation packages. But I'd try these steps
> anyway to see if that fixes it. If it's still broken after that, we can try
> to debug further.
> >
>
>
>
> I have two other quick thoughts that I'll add as (3) and (4)
>
>
> (3)
> I remember something that another user had reported problems
> installing FreeDOS on the new Raspberry Pi (model 4?) using the same
> QEMU command line I wrote about in the article. Sounds like there's a
> difference in the new Raspberry Pi that needed a new QEMU option? I
> can't remember the details, and a quick search in the freedos-user
> email list archives didn't locate the discussion thread I remembered.
> But maybe someone else here will remember and be able to point to the
> right discussion thread. [However, you said you are doing this on
> Raspberry Pi model 3, and that's the same model I have. I have the
> Raspberry Pi model 3+.]
>
> (4)
> When you are finally able to start the installation, be prepared for
> the install process to take a looong time. This is because
> installing all the FreeDOS packages requires a lot of disk I/O to the
> virtual freedos.img drive. And unless you bought a top-of-the-line SD
> card for your Raspberry Pi, the SD card's I/O speed isn't very fast.
> The installation takes a very *very* long time. But once you install
> FreeDOS, things are mostly fine after that. I think only a few games
> were noticeably slow to start after that. Booting and running FreeDOS,
> and running most DOS applications, was fine.
>
>
> Jim
>
>
> ___
> 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] Issue installing FreeDOS on Raspberry Pi 3

[dmccunney]

On Wed, Sep 25, 2019 at 8:02 AM ZB  wrote:
> On Wed, Sep 25, 2019 at 12:05:04AM -0700, Ralf Quint wrote:
>
> > These are two totally different worlds! The only way you could get FreeDOS
> > to run on a RPi is after installing one of the default Linux versions to
> > install QEMU, which is an x86 emulator and install FreeDOS within that
> > virtual machine. Again, FreeDOS can NEVER run natively on a RPi...
>
> With DOS it would mean too much work - but I believe a group of determined
> coders could be able to port, say, CP/M. Of course it would be "CP/M-like"
> OS for RPi rather than "strict port"

And who, precisely, would do this?

This is another instance of stuff that has come up before, with a
desire for support for things that didn't exist when DOS was still
sold and supported.  It might be theoretically *possible* to do it,
but the folks with that level of skill will be professional developers
who get *paid* for writing code.  I don't see folks who *can* do it
investing the time and effort for free, when the time and effort could
be applied to work they got paid for.

> Why would they do that? To create much simpler OS for RPI than Linux. Who
> needs that whole complexity on such little SBC? CP/M would do just fine.

No, it wouldn't.  Digital Research developed CP/M as an OS for 8 bit
micros like the Intel 8080 and Zilog Z80.  They were single tasking
CPUs supporting a whopping *64K* of address space.  OS, applications,
and data all had to fit into 64K.

The Raspberry Pi uses an ARM Cortex CPU, with a 32bit address space
and a multi-core design.  It can run a full multi-user, multitasking
OS like Linux, and does.  And ARM CPUs are often used in Internet of
Things devices.  The critical point is the the CPU can run a full
TCP-IP networking stack, and become a node *on* the Internet.  A
second critical point is the the costs of such CPUs have dropped to
the point where you *can* affordably use something like a a 32bit ARM
CPU in an embedded device.

Who needs that complexity on such a little SBC?  We do.  You can
actually run a full Linux distro and Linux apps on a form factor the
size of a cigarette pack, and people are.  Everything gets smaller,
faster, and cheaper, and what can be done expands in consequence.

CP/M is *too* simple, designed to work on vastly less powerful
hardware.  As an example, early  versions of DOS supported Ctrl-Z as
an EOF marker.  This was inherited from CP/M, because up till CP/M
3.0, the *size* of a file was not specified in a directory entry.  The
OS needed a marker to indicate where the file *ended* when it was
being loaded from disk.  IIRC, it wasn't till MSDOS 5 that that
"feature" was deprecated and I could stop trying to tell things like
editors that an embedded ^Z was *not* an EOF marker.

And even if $DEITY works a miracle and someone appears to port CP/M to
the ARM architecture, then what do you do?  What will run under it?
Who will port existing CP/M applications to ARM as well, or write new
ones?

If you are savvy enough to try to get FreeDOS running under an
emulator like QEMU on a Raspbery Pi, that "simplicity" of CP/M doesn't
buy you anything.

> As Chuck Moore (Forth creator) once said: "most computer operating systems
> devolving to caveman interfaces ("point at the pretty pictures and grunt")"

And there are folks who want to do precisely that.  Those aren't *my*
use cases, but so what? Computers are tools people use to do work or
play.  I don't get to decide whether their uses are acceptable, and
wouldn't want to if I could.

> regards,
> Zbigniew
__
Dennis


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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Jim Hall]

On Wed, Sep 25, 2019 at 10:09 AM Jim Hall  wrote:
>
[..]
> I have two suggestions for you:
>
> (1)
> Your "hda" image file is different in the two commands. You created a hard 
> disk image named dos.img but you tried to reference a hard disk image named 
> freedos.img. Does the freedos.img image file exist? Try re-running the 
> qemu-system-i386 command with the dos.img image file you created in your 
> earlier qemu-img command.
>
> (2)
> You have an extra parameter to define a floppy disk image named FLOPPY.img. 
> Does this image file exist? How did you create it? Try re-running the 
> qemu-system-i386 command without the floppy drive defined. You don't need it 
> anyway for the install.
>
>
> However, neither of my two suggestions would point to the installer being 
> unable to find the installation packages. But I'd try these steps anyway to 
> see if that fixes it. If it's still broken after that, we can try to debug 
> further.
>



I have two other quick thoughts that I'll add as (3) and (4)


(3)
I remember something that another user had reported problems
installing FreeDOS on the new Raspberry Pi (model 4?) using the same
QEMU command line I wrote about in the article. Sounds like there's a
difference in the new Raspberry Pi that needed a new QEMU option? I
can't remember the details, and a quick search in the freedos-user
email list archives didn't locate the discussion thread I remembered.
But maybe someone else here will remember and be able to point to the
right discussion thread. [However, you said you are doing this on
Raspberry Pi model 3, and that's the same model I have. I have the
Raspberry Pi model 3+.]

(4)
When you are finally able to start the installation, be prepared for
the install process to take a looong time. This is because
installing all the FreeDOS packages requires a lot of disk I/O to the
virtual freedos.img drive. And unless you bought a top-of-the-line SD
card for your Raspberry Pi, the SD card's I/O speed isn't very fast.
The installation takes a very *very* long time. But once you install
FreeDOS, things are mostly fine after that. I think only a few games
were noticeably slow to start after that. Booting and running FreeDOS,
and running most DOS applications, was fine.


Jim


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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Jim Hall]

On 9/24/2019 8:15 PM, shift83...@gmail.com wrote:
>>
>> I have tried multiple times to install FreeDOS on Raspberry Pi3.
>>
>>  *[*..*]*
>>
>> Has anyone seen this and been able to resolve it?
>>
>> On Wed, Sep 25, 2019 at 2:07 AM Ralf Quint  wrote:

> There is no way to resolve this!
>>
>> The RPi (any model!) is based on an ARM RISC CPU, while FreeDOS (any DOS
>> actually) expects to run on an Intel x86 (compatible) CPU.
>>
>> These are two totally different worlds! The only way you could get
>> FreeDOS to run on a RPi is after installing one of the default Linux
>> versions to install QEMU, which is an x86 emulator and install FreeDOS
>> within that virtual machine. Again, FreeDOS can NEVER run natively on a
>> RPi...
>>
>
On Wed, Sep 25, 2019 at 9:46 AM Chris Schneider 
wrote:

> That’s what I’m trying to do.  I have Raspian loaded and qemu loaded.
> Launching qemu with the freedos installation and I’m getting errors after
> the reboot from partitioning the image file.  It seems my cdrom iso can not
> be read.
>
>

Earlier, you mentioned you created your virtual disk with this:

*qemu-img* create dos.img 200M



And that's the correct command. Good so far.


And you ran QEMU with this command:

*qemu-system-i386* -m 16 -k en-us -rtc base=localtime -device cirrus-vga
> -fda FLOPPY.img -hda freedos.img -cdrom FD12CD.iso -boot order=d




This is very similar to the command line I gave in my article on
OpenSource.com about running FreeDOS on the Raspberry Pi
 (using
QEMU). The command line I used was:

*qemu-system-i386* -m 16 -k en-us -rtc base=localtime -soundhw
sb16,adlib -device
> cirrus-vga -hda freedos.img -cdrom FD12CD.iso -boot order=d



I highlighted to show the similarities in those commands.


My OpenSource article provides a full breakdown of the command line, but
the *qemu-img* command creates a virtual hard drive image file
*dos.img* of size
200MB.

The *qemu-system-i386* command defines a virtual machine with these
parameters:

   - 16MB memory
   - US/English keyboard
   - Real-time clock set to host system's local time
   - Cirrus Logic VGA card (very common)
   - Hard drive image named *freedos.img*
   - CDROM ISO image named *FD12CD.iso*
   - Boot the virtual machine from the bootable CDROM first


That should work. You don't need to have a sound card defined in order to
install FreeDOS (that's extra).


*I have two suggestions for you:*

*(*1*)*
Your "hda" image file is different in the two commands. You created a hard
disk image named dos.img but you tried to reference a hard disk image
named freedos.img. Does the freedos.img image file exist? Try re-running
the *qemu-system-i386* command with the *dos.img* image file you created in
your earlier *qemu-img* command.

(2)
You have an extra parameter to define a floppy disk image named *FLOPPY.img*.
Does this image file exist? How did you create it? Try re-running the
*qemu-system-i386* command without the floppy drive defined. You don't need
it anyway for the install.


However, neither of my two suggestions would point to the installer being
unable to find the installation packages. But I'd try these steps anyway to
see if that fixes it. If it's still broken after that, we can try to debug
further.

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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[ZB]

On Wed, Sep 25, 2019 at 12:05:04AM -0700, Ralf Quint wrote:

> These are two totally different worlds! The only way you could get FreeDOS
> to run on a RPi is after installing one of the default Linux versions to
> install QEMU, which is an x86 emulator and install FreeDOS within that
> virtual machine. Again, FreeDOS can NEVER run natively on a RPi...

With DOS it would mean too much work - but I believe a group of determined
coders could be able to port, say, CP/M. Of course it would be "CP/M-like"
OS for RPi rather than "strict port"

Why would they do that? To create much simpler OS for RPI than Linux. Who
needs that whole complexity on such little SBC? CP/M would do just fine.

As Chuck Moore (Forth creator) once said: "most computer operating systems
devolving to caveman interfaces ("point at the pretty pictures and grunt")"
-- 
regards,
Zbigniew


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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Jim Hall]

On Wed, Sep 25, 2019 at 2:07 AM Ralf Quint  wrote:
>
> On 9/24/2019 8:15 PM, shift83...@gmail.com wrote:
>
> I have tried multiple times to install FreeDOS on Raspberry Pi3.
>[...]
>
> Has anyone seen this and been able to resolve it?
>
> There is no way to resolve this!
>
> The RPi (any model!) is based on an ARM RISC CPU, while FreeDOS (any DOS 
> actually) expects to run on an Intel x86 (compatible) CPU.
>
> These are two totally different worlds! The only way you could get FreeDOS to 
> run on a RPi is after installing one of the default Linux versions to install 
> QEMU, which is an x86 emulator and install FreeDOS within that virtual 
> machine. Again, FreeDOS can NEVER run natively on a RPi...
>


Yes, but from the screenshot in his original post, he is installing
FreeDOS in a QEMU virtual machine.


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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Chris Schneider]

That’s what I’m trying to do.  I have Raspian loaded and qemu loaded.
Launching qemu with the freedos installation and I’m getting errors after
the reboot from partitioning the image file.  It seems my cdrom iso can not
be read.

On Wed, Sep 25, 2019 at 2:07 AM Ralf Quint  wrote:

> On 9/24/2019 8:15 PM, shift83...@gmail.com wrote:
>
> I have tried multiple times to install FreeDOS on Raspberry Pi3.
>
>
>
> I have created a 100M and 200M raw disk image.
>
>
>
> Mounted the Standard and then tried with the Legacy ISO.
>
>
>
> Both will boot the ISO, partition and format the hard disk. But when I
> reboot and select the Install to Harddisk after it goes to gathering
> settings a couple of minutes go by and I get:
>
>
>
> I have also tried to mount the floppy.img as well as the ISO and boot from
> floppy with the same results.
>
>
>
> Has anyone seen this and been able to resolve it?
>
> There is no way to resolve this!
>
> The RPi (any model!) is based on an ARM RISC CPU, while FreeDOS (any DOS
> actually) expects to run on an Intel x86 (compatible) CPU.
>
> These are two totally different worlds! The only way you could get FreeDOS
> to run on a RPi is after installing one of the default Linux versions to
> install QEMU, which is an x86 emulator and install FreeDOS within that
> virtual machine. Again, FreeDOS can NEVER run natively on a RPi...
>
> Ralf
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_6225151766977900922_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> ___
> 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] Issue installing FreeDOS on Raspberry Pi 3

[Ralf Quint]

On 9/24/2019 8:15 PM, shift83...@gmail.com wrote:


I have tried multiple times to install FreeDOS on Raspberry Pi3.

I have created a 100M and 200M raw disk image.

Mounted the Standard and then tried with the Legacy ISO.

Both will boot the ISO, partition and format the hard disk. But when I 
reboot and select the Install to Harddisk after it goes to gathering 
settings a couple of minutes go by and I get:


I have also tried to mount the floppy.img as well as the ISO and boot 
from floppy with the same results.


Has anyone seen this and been able to resolve it?


There is no way to resolve this!

The RPi (any model!) is based on an ARM RISC CPU, while FreeDOS (any DOS 
actually) expects to run on an Intel x86 (compatible) CPU.


These are two totally different worlds! The only way you could get 
FreeDOS to run on a RPi is after installing one of the default Linux 
versions to install QEMU, which is an x86 emulator and install FreeDOS 
within that virtual machine. Again, FreeDOS can NEVER run natively on a 
RPi...


Ralf



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Chris Schneider]

Yes I see the same behavior with a fresh formatted c Drive image and
mounted the iso.

On Wed, Sep 25, 2019 at 12:30 AM Jon Brase  wrote:

> I managed to get the installer to pull packages off the CD, but one thing
> you may be running into is that QEMU de-assigns ISO images from the
> emulated CD drive when the OS sends a disk eject command. On a physical
> machine, if the CD drive ejects a disk you're still using, you notice it
> and just push the tray back in, but in a VM it's a rather annoying behavior
> for the ISO to be completely unassigned, as you don't see that happen, and
> on reboot it causes the disk to no longer be in the drive.
>
> When you start the VM fresh with the CD image and freshly formatted HDD
> image specified, do you get the same error?
>
>
>  Original message 
> From: Jon Brase 
> Date: 9/25/2019 00:02 (GMT-06:00)
> To: "Discussion and general questions about FreeDOS." <
> freedos-user@lists.sourceforge.net>
> Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3
>
> Interesting, I did have a similar issue on real hardware recently, though
> the situation was enough different that I'm not sure whether they match up,
> and I didn't so much resolve it as work around it.
>
> I generally use virt-manager rather than the command line to set up QEMU
> VMs. I'm not sure what QEMU defaults to on the command line for things that
> aren't specified (details of how the emulated hardware is presented to the
> guest OS and such).
>
> I may try installing FreeDOS in a VM on my machine to see if I can
> duplicate the issue there.
>
>
>  Original message 
> From: shift83...@gmail.com
> Date: 9/24/2019 23:21 (GMT-06:00)
> To: "'Discussion and general questions about FreeDOS.'" <
> freedos-user@lists.sourceforge.net>
> Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3
>
> Sorry for the confusion.  I’m new to QEMU.
>
>
>
> So…
>
>
>
> I created the image with the below command:
>
>
>
> *qemu-img create dos.img 200M*
>
>
>
> This is my command line to execute QEMU and mount the drives and emulate
> devices is below:
>
>
>
> *qemu-system-i386 -m 16 -k en-us -rtc base=localtime -device cirrus-vga
> -fda FLOPPY.img -hda freedos.img -cdrom FD12CD.iso -boot order=d*
>
>
>
> I have also tried to minimize the command to just:
>
>
>
> qemu-system-i386 -fda FLOPPY.img -had freedos.img -cdrom FD12CD.iso -boot
> order=d
>
>
>
> I believe the issue is that after it reboots from partitioning and
> formatting the C drive it no longer sees the CDROM when trying to access
> the source packages.  I issues trying to list the directory on the D drive
> when I exit from the installer.
>
>
>
>
>
>
>
> *From:* Jon Brase 
> *Sent:* Tuesday, September 24, 2019 11:09 PM
> *To:* Discussion and general questions about FreeDOS. <
> freedos-user@lists.sourceforge.net>
> *Subject:* Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3
>
>
>
> FreeDOS (x86 software) won't boot (natively) on the Raspberry Pi 3 (ARM
> hardware), so if you got as far as to be able to select "install to hard
> disk", you must be using an x86 emulator, and, indeed, your screenshot
> shows that you're using QEMU. To minimize confusion, you should lead with
> the information that you're using QEMU, and follow it up with the fact that
> you're on a non x86 platform, as there are differences in how QEMU handles
> guest code for the same architecture that it's running on and how it
> handles code for other architectures.
>
>
>
> I myself haven't run FreeDOS on any platform other than x86 PCs, so I'm
> not sure how much help I can be, but can you say what emulated peripherals
> you set up for your FreeDOS  VM in QEMU?
>
>
>
>  Original message 
> From: shift83...@gmail.com
> Date: 9/24/2019 22:15 (GMT-06:00)
> To: freedos-user@lists.sourceforge.net
> Subject: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3
>
> I have tried multiple times to install FreeDOS on Raspberry Pi3.
>
>
>
> I have created a 100M and 200M raw disk image.
>
>
>
> Mounted the Standard and then tried with the Legacy ISO.
>
>
>
> Both will boot the ISO, partition and format the hard disk. But when I
> reboot and select the Install to Harddisk after it goes to gathering
> settings a couple of minutes go by and I get:
>
>
>
> I have also tried to mount the floppy.img as well as the ISO and boot from
> floppy with the same results.
>
>
>
> Has anyone seen this and been able to resolve it?
>
>
>
> Thank you,
>
>
>
> Chris
>
>
> ___
> 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] Issue installing FreeDOS on Raspberry Pi 3

[Jon Brase]

I managed to get the installer to pull packages off the CD, but one thing you 
may be running into is that QEMU de-assigns ISO images from the emulated CD 
drive when the OS sends a disk eject command. On a physical machine, if the CD 
drive ejects a disk you're still using, you notice it and just push the tray 
back in, but in a VM it's a rather annoying behavior for the ISO to be 
completely unassigned, as you don't see that happen, and on reboot it causes 
the disk to no longer be in the drive.
When you start the VM fresh with the CD image and freshly formatted HDD image 
specified, do you get the same error?

 Original message 
From: Jon Brase  
Date: 9/25/2019  00:02  (GMT-06:00) 
To: "Discussion and general questions about FreeDOS." 
 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

Interesting, I did have a similar issue on real hardware recently, though the 
situation was enough different that I'm not sure whether they match up, and I 
didn't so much resolve it as work around it.
I generally use virt-manager rather than the command line to set up QEMU VMs. 
I'm not sure what QEMU defaults to on the command line for things that aren't 
specified (details of how the emulated hardware is presented to the guest OS 
and such).
I may try installing FreeDOS in a VM on my machine to see if I can duplicate 
the issue there. 

 Original message 
From: shift83...@gmail.com 
Date: 9/24/2019  23:21  (GMT-06:00) 
To: "'Discussion and general questions about FreeDOS.'" 
 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

Sorry for the confusion.  I’m new to QEMU.   So… I created the image with the 
below command: qemu-img create dos.img 200M This is my command line to execute 
QEMU and mount the drives and emulate devices is below: qemu-system-i386 -m 16 
-k en-us -rtc base=localtime -device cirrus-vga -fda FLOPPY.img -hda 
freedos.img -cdrom FD12CD.iso -boot order=d I have also tried to minimize the 
command to just: qemu-system-i386 -fda FLOPPY.img -had freedos.img -cdrom 
FD12CD.iso -boot order=d I believe the issue is that after it reboots from 
partitioning and formatting the C drive it no longer sees the CDROM when trying 
to access the source packages.  I issues trying to list the directory on the D 
drive when I exit from the installer.   From: Jon Brase  
Sent: Tuesday, September 24, 2019 11:09 PM
To: Discussion and general questions about FreeDOS. 

Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 FreeDOS 
(x86 software) won't boot (natively) on the Raspberry Pi 3 (ARM hardware), so 
if you got as far as to be able to select "install to hard disk", you must be 
using an x86 emulator, and, indeed, your screenshot shows that you're using 
QEMU. To minimize confusion, you should lead with the information that you're 
using QEMU, and follow it up with the fact that you're on a non x86 platform, 
as there are differences in how QEMU handles guest code for the same 
architecture that it's running on and how it handles code for other 
architectures. I myself haven't run FreeDOS on any platform other than x86 PCs, 
so I'm not sure how much help I can be, but can you say what emulated 
peripherals you set up for your FreeDOS  VM in QEMU?

 Original message 
From: shift83...@gmail.com 
Date: 9/24/2019 22:15 (GMT-06:00) 
To: freedos-user@lists.sourceforge.net 
Subject: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 I have tried 
multiple times to install FreeDOS on Raspberry Pi3. I have created a 100M and 
200M raw disk image. Mounted the Standard and then tried with the Legacy ISO. 
Both will boot the ISO, partition and format the hard disk. But when I reboot 
and select the Install to Harddisk after it goes to gathering settings a couple 
of minutes go by and I get: I have also tried to mount the floppy.img as well 
as the ISO and boot from floppy with the same results. Has anyone seen this and 
been able to resolve it? Thank you, Chris ___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Jon Brase]

Interesting, I did have a similar issue on real hardware recently, though the 
situation was enough different that I'm not sure whether they match up, and I 
didn't so much resolve it as work around it.
I generally use virt-manager rather than the command line to set up QEMU VMs. 
I'm not sure what QEMU defaults to on the command line for things that aren't 
specified (details of how the emulated hardware is presented to the guest OS 
and such).
I may try installing FreeDOS in a VM on my machine to see if I can duplicate 
the issue there. 

 Original message 
From: shift83...@gmail.com 
Date: 9/24/2019  23:21  (GMT-06:00) 
To: "'Discussion and general questions about FreeDOS.'" 
 
Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

Sorry for the confusion.  I’m new to QEMU.   So… I created the image with the 
below command: qemu-img create dos.img 200M This is my command line to execute 
QEMU and mount the drives and emulate devices is below: qemu-system-i386 -m 16 
-k en-us -rtc base=localtime -device cirrus-vga -fda FLOPPY.img -hda 
freedos.img -cdrom FD12CD.iso -boot order=d I have also tried to minimize the 
command to just: qemu-system-i386 -fda FLOPPY.img -had freedos.img -cdrom 
FD12CD.iso -boot order=d I believe the issue is that after it reboots from 
partitioning and formatting the C drive it no longer sees the CDROM when trying 
to access the source packages.  I issues trying to list the directory on the D 
drive when I exit from the installer.   From: Jon Brase  
Sent: Tuesday, September 24, 2019 11:09 PM
To: Discussion and general questions about FreeDOS. 

Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 FreeDOS 
(x86 software) won't boot (natively) on the Raspberry Pi 3 (ARM hardware), so 
if you got as far as to be able to select "install to hard disk", you must be 
using an x86 emulator, and, indeed, your screenshot shows that you're using 
QEMU. To minimize confusion, you should lead with the information that you're 
using QEMU, and follow it up with the fact that you're on a non x86 platform, 
as there are differences in how QEMU handles guest code for the same 
architecture that it's running on and how it handles code for other 
architectures. I myself haven't run FreeDOS on any platform other than x86 PCs, 
so I'm not sure how much help I can be, but can you say what emulated 
peripherals you set up for your FreeDOS  VM in QEMU?

 Original message 
From: shift83...@gmail.com 
Date: 9/24/2019 22:15 (GMT-06:00) 
To: freedos-user@lists.sourceforge.net 
Subject: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 I have tried 
multiple times to install FreeDOS on Raspberry Pi3. I have created a 100M and 
200M raw disk image. Mounted the Standard and then tried with the Legacy ISO. 
Both will boot the ISO, partition and format the hard disk. But when I reboot 
and select the Install to Harddisk after it goes to gathering settings a couple 
of minutes go by and I get: I have also tried to mount the floppy.img as well 
as the ISO and boot from floppy with the same results. Has anyone seen this and 
been able to resolve it? Thank you, Chris ___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[shift838cs]

Sorry for the confusion.  I’m new to QEMU.  

 

So…

 

I created the image with the below command:

 

qemu-img create dos.img 200M

 

This is my command line to execute QEMU and mount the drives and emulate 
devices is below:

 

qemu-system-i386 -m 16 -k en-us -rtc base=localtime -device cirrus-vga -fda 
FLOPPY.img -hda freedos.img -cdrom FD12CD.iso -boot order=d

 

I have also tried to minimize the command to just:

 

qemu-system-i386 -fda FLOPPY.img -had freedos.img -cdrom FD12CD.iso -boot 
order=d

 

I believe the issue is that after it reboots from partitioning and formatting 
the C drive it no longer sees the CDROM when trying to access the source 
packages.  I issues trying to list the directory on the D drive when I exit 
from the installer.

 

 

 

From: Jon Brase  
Sent: Tuesday, September 24, 2019 11:09 PM
To: Discussion and general questions about FreeDOS. 

Subject: Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

 

FreeDOS (x86 software) won't boot (natively) on the Raspberry Pi 3 (ARM 
hardware), so if you got as far as to be able to select "install to hard disk", 
you must be using an x86 emulator, and, indeed, your screenshot shows that 
you're using QEMU. To minimize confusion, you should lead with the information 
that you're using QEMU, and follow it up with the fact that you're on a non x86 
platform, as there are differences in how QEMU handles guest code for the same 
architecture that it's running on and how it handles code for other 
architectures.

 

I myself haven't run FreeDOS on any platform other than x86 PCs, so I'm not 
sure how much help I can be, but can you say what emulated peripherals you set 
up for your FreeDOS  VM in QEMU?



 Original message 
From: shift83...@gmail.com <mailto:shift83...@gmail.com>  
Date: 9/24/2019 22:15 (GMT-06:00) 
To: freedos-user@lists.sourceforge.net 
<mailto:freedos-user@lists.sourceforge.net>  
Subject: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

I have tried multiple times to install FreeDOS on Raspberry Pi3.

 

I have created a 100M and 200M raw disk image.

 

Mounted the Standard and then tried with the Legacy ISO.

 

Both will boot the ISO, partition and format the hard disk. But when I reboot 
and select the Install to Harddisk after it goes to gathering settings a couple 
of minutes go by and I get:

 

I have also tried to mount the floppy.img as well as the ISO and boot from 
floppy with the same results.

 

Has anyone seen this and been able to resolve it?

 

Thank you,

 

Chris

 

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

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Jon Brase]

FreeDOS (x86 software) won't boot (natively) on the Raspberry Pi 3 (ARM 
hardware), so if you got as far as to be able to select "install to hard disk", 
you must be using an x86 emulator, and, indeed, your screenshot shows that 
you're using QEMU. To minimize confusion, you should lead with the information 
that you're using QEMU, and follow it up with the fact that you're on a non x86 
platform, as there are differences in how QEMU handles guest code for the same 
architecture that it's running on and how it handles code for other 
architectures.
I myself haven't run FreeDOS on any platform other than x86 PCs, so I'm not 
sure how much help I can be, but can you say what emulated peripherals you set 
up for your FreeDOS  VM in QEMU?

 Original message 
From: shift83...@gmail.com 
Date: 9/24/2019  22:15  (GMT-06:00) 
To: freedos-user@lists.sourceforge.net 
Subject: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3 

I have tried multiple times to install FreeDOS on Raspberry Pi3. I have created 
a 100M and 200M raw disk image. Mounted the Standard and then tried with the 
Legacy ISO. Both will boot the ISO, partition and format the hard disk. But 
when I reboot and select the Install to Harddisk after it goes to gathering 
settings a couple of minutes go by and I get: I have also tried to mount the 
floppy.img as well as the ISO and boot from floppy with the same results. Has 
anyone seen this and been able to resolve it? Thank you, Chris ___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[Santiago Almenara]

Are you installing freedos under a VM or directly in the SD???


> El 24 set. 2019, a la(s) 22:16, shift83...@gmail.com escribió:
> 
> 
> I have tried multiple times to install FreeDOS on Raspberry Pi3.
>  
> I have created a 100M and 200M raw disk image.
>  
> Mounted the Standard and then tried with the Legacy ISO.
>  
> Both will boot the ISO, partition and format the hard disk. But when I reboot 
> and select the Install to Harddisk after it goes to gathering settings a 
> couple of minutes go by and I get:
>  
> I have also tried to mount the floppy.img as well as the ISO and boot from 
> floppy with the same results.
>  
> Has anyone seen this and been able to resolve it?
>  
> Thank you,
>  
> Chris
>  
> 
> ___
> 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

[Freedos-user] Issue installing FreeDOS on Raspberry Pi 3

[shift838cs]

I have tried multiple times to install FreeDOS on Raspberry Pi3.

 

I have created a 100M and 200M raw disk image.

 

Mounted the Standard and then tried with the Legacy ISO.

 

Both will boot the ISO, partition and format the hard disk. But when I
reboot and select the Install to Harddisk after it goes to gathering
settings a couple of minutes go by and I get:

 

I have also tried to mount the floppy.img as well as the ISO and boot from
floppy with the same results.

 

Has anyone seen this and been able to resolve it?

 

Thank you,

 

Chris

 

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