[Freedos-user] FreeDOS images for VirtualBox

[Ulrich Hansen]

I also had time to update my VirtualBox images of FreeDOS. So if anybody liked these images in the past: Here are the new ones: :-)

https://www.lazybrowndog.net/freedos/virtualbox/ <https://www.lazybrowndog.net/freedos/virtualbox/>

[Ralf Quint]

Post by Ulrich Hansen
I also had time to update my VirtualBox images of FreeDOS. So if
anybody liked these images in the past: Here are the new ones: :-)
https://www.lazybrowndog.net/freedos/virtualbox/

Well,...

On the side for the version supposedly without network, you are talking
an awful lot about the networking stuff being installed and following
the link for the supposedly networked version I just get

Post by Ulrich Hansen
https://www.lazybrowndog.net/freedos/virtualbox/downloads/vdi/FreeDOS1.2net.vdi.zip
Not Found
The requested URL /index.php was not found on this server.
------------------------------------------------------------------------
Apache Server at www.lazybrowndog.net Port 443

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

[Ulrich Hansen]

Post by Ralf Quint
Well,...

Post by Ulrich Hansen
Not Found

Oh, sorry. I forgot to change one of the two links there. Thanks!! I repaired it.

Post by Ralf Quint
On the side for the version supposedly without network, you are talking an awful lot about the networking stuff being installed

Hmm. You’ve got a point. The thing is: FTPSRV was for some years the fastest way of getting files in and out of the FreeDOS guest. So I considered it something most people would want, also in the „normal“ image without additional networking software.

Now with the VHD image type, you can mount it in your host OS and drag’n drop files with your Explorer, Nautilus, Finder, whatever. So now in VirtualBox FreeDOS can be used fine without a network.

So you’re right. But what are you suggesting? Making the FreeDOS1.2 image just a pure FreeDOS 1.2 version without any changes?

[Ralf Quint]

Hmm. You’ve got a point. The thing is: FTPSRV was for some years the
fastest way of getting files in and out of the FreeDOS guest. So I
considered it something most people would want, also in the „normal“
image without additional networking software.
Now with the VHD image type, you can mount it in your host OS and
drag’n drop files with your Explorer, Nautilus, Finder, whatever. So
now in VirtualBox FreeDOS can be used fine without a network.
So you’re right. But what are you suggesting? Making the FreeDOS1.2
image just a pure FreeDOS 1.2 version without any changes?

Let's say that I was surprised to see that you mentioned loading
networking stuff in the image that wasn't labeled "non-networked". Your
explanation kind of makes sense, but I think it can also confuse the
hell out of people, specially when they notice that they end up with
less free RAM then they anticipated.
Maybe you can have an startup option for it, but not load the networking
stuff you just mentioned by default. Then it is easier for people that
don't want it or don't need it. And they still can get that feature if
they decide otherwise...

Ralf

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

[Eric Auer]

Hi everybody,

I agree with Ralf - it is not intuitive that a non-network
operating system installs a network, even if it is only for
FTP file exchange. I think those who do want to use network
tools to communicate between host OS and a virtual PC with
FreeDOS inside will be able to deliberately select the DOS
install variant WITH network, while the rest will enjoy a
lean install without anything network related at all :-)

By the way, it would be nice to include VMSMOUNT which lets
DOS mount VMWare shared directories as drives, similar to
the magic "directory as a drive" function in DOSEMU. Both
require no network drivers at all, as far as I know :-)

Cheers, Eric

[Ralf Quint]

Post by Eric Auer
By the way, it would be nice to include VMSMOUNT which lets
DOS mount VMWare shared directories as drives, similar to
the magic "directory as a drive" function in DOSEMU. Both
require no network drivers at all, as far as I know :-)

Well, that works only with VMware, but unfortunately not with
VirtualBox, AFAIK.

Otherwise, that would be my preferred method, similar to how you can
share data with the host in DOSBox/VDOS...

Ralf

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

[Eduardo Casino]

Post by Ralf Quint
Well, that works only with VMware, but unfortunately not with
VirtualBox, AFAIK.

Right.

Post by Ralf Quint
Otherwise, that would be my preferred method, similar to how you can
share data with the host in DOSBox/VDOS...

I started a VirtualBox version a couple of years ago, but I lost
interest in it. Maybe one day...

[Eric Auer]

Hi Eduardo,

Post by Eduardo Casino

Post by Ralf Quint
Well, that works only with VMware, but unfortunately not with
VirtualBox, AFAIK.

Right.

As with drivers for other things, it would still be good to
include vmsmount for those who use vmware to run FreeDOS :-)

Post by Eduardo Casino

Post by Ralf Quint
Otherwise, that would be my preferred method, similar to how you
can share data with the host in DOSBox/VDOS...

I started a VirtualBox version a couple of years ago, but I lost
interest in it. Maybe one day...

That sounds interesting! How far did you get, what is needed?

Cheers, Eric

[Ulrich Hansen]

Post by Eric Auer

Post by Eduardo Casino

Post by Ralf Quint
Well, that works only with VMware, but unfortunately not with
VirtualBox, AFAIK.

Right.

As with drivers for other things, it would still be good to
include vmsmount for those who use vmware to run FreeDOS :-)

Vmware uses vmdk images, my VirtualBox images are VHD. So that’s a whole new story.

I don’t see much use in including vmsmount on VHD image. And I have no experience with converting everything to VMDK images, how reliable they work with VirtualBox on Windows, Ubuntu and Mac hosts or how they can be mounted from the host OS. So that would require some researching and creating and converting and re-writing.

At the moment I would prefer a separate image for vmware users.

@Eric and @Ralf: About the clean FreeDOS 1.2 VirtualBox image:

I have done it: It is now EXACTLY what you get by installing manually with the FD12CD.iso and accepting everything. No networking. :-)

See: https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21 <https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21>

cheers
Ulrich

[Ralf Quint]

Post by Eric Auer

Post by Eduardo Casino

Post by Ralf Quint
Well, that works only with VMware, but unfortunately not with
VirtualBox, AFAIK.

Right.

As with drivers for other things, it would still be good to
include vmsmount for those who use vmware to run FreeDOS :-)

Vmware uses vmdk images, my VirtualBox images are VHD. So that’s a
whole new story.

I think both can handle a variety of virtual disk files, just haven't
used VMware in a couple few years now, ever since the they discontinued
the "VMware player" and now have only some weird "Workstation player"
that is more restricted. Haven't honestly looked at it again in at least
two years or so...

I don’t see much use in including vmsmount on VHD image. And I have no
experience with converting everything to VMDK images, how reliable
they work with VirtualBox on Windows, Ubuntu and Mac hosts or how they
can be mounted from the host OS. So that would require some
researching and creating and converting and re-writing.
At the moment I would prefer a separate image for vmware users.
I have done it: It is now EXACTLY what you get by installing manually
with the FD12CD.iso and accepting everything. No networking. :-)
See: https://www.lazybrowndog.net/freedos/virtualbox/?page_id=21

Thanks will take a look at it when I get home tonight...

Ralf

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

[Eduardo Casino]

Post by Eric Auer
That sounds interesting! How far did you get, what is needed?

Hi Eric,

The low level pci interface is there, as well as some initialisation
stuff and code taken from vmsmount. All the shared folders protocol is
missing, so there is nothing functional apart from getting the names
of the shares.

What is needed? Self-motivation ;)

The code is at https://www.eduardocasino.es/code/vbsmount in case
anyone is interested.

Cheers,
Eduardo.

[Ralf Quint]

Post by Eduardo Casino
I started a VirtualBox version a couple of years ago, but I lost
interest in it. Maybe one day...

Well, despite being "from Oracle" these, days, it is the best "freely
available" hypervisor out there. The VMware stuff is all for pay these
days, and the Workstation Player constantly bugs about updating to the
Pro version for mullah...


Ralf

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

[Ralf Quint]

Post by Ulrich Hansen
I also had time to update my VirtualBox images of FreeDOS. So if
anybody liked these images in the past: Here are the new ones: :-)
https://www.lazybrowndog.net/freedos/virtualbox/

And to add to my last email, the supposedly non-network image starts
with network stuff enabled...

Might want to take another look at your links I guess...

Ralf

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