> On Jun 20, 2016, at 3:04 PM, userbeit...@abwesend.de wrote:
> 
> Why?
> Every emulator or VM I know about will quickly install any operating 
> system from a virtual CD-ROM. So if you just assign the FreeDOS-ISO as 
> the virtual ATAPI-CDROM you will very easily install it to the virtual 
> Hard Disk Drive, which will be either .VHD, .VHDX (Virtual PC and 
> Hyper-V), .VMDK (VMware), .QCOW (QEMU) or .VDI (VirtualBox). Or any 
> other format.
> 
> A prepared installation will not help alot, aside from you not being 
> completely aware, which installation was used (full installation, 
> partial installation, which packages).

Well, yes and no.

Using FDI (the new FreeDOS Installer) to install the v1.2 preview versions 
takes under most 60 seconds in most VMs.

There are odd compatibility issues from VM to VM. The installer compensates for 
most of these by tweaking the installed config files.

But, for some users getting a pre setup VM that booted to a menu of Games and 
other cool freebies.  

> 
> Also, for each emulator or VM you will require different hardware 
> drivers (for the virtual hardware) and integration drivers (for guest 
> integration).
> 
> Therefor I would suggest to better add an installation package for 
> FreeDOS as a guest operating system under various emulators and VMs. A 
> user could then just install FreeDOS and select "guest drivers and 
> tools" as an additional package, which would then ask "a) Virtual PC, b) 
> Hyper-V, c) VMware, d) VirtualBox, e) QEMU" and install+setup the 
> required stuff for you.
> 

V8Power Tools (used by FDI for a lot of its magic) already detects several 
different virtual machine platforms. This was needed to prevent problems with 
several drivers used by FDI and to aid in configuring the installed system on 
specific VMs. It also can detect some other and unknown VMs. But, for the 
installer, that is not useful. 

If there are drivers for a QEMU, VirtualBox or VMWare that can be included with 
FreeDOS without violating and licensing restrictions, it is possible to just 
have them installed normally. Or, throw up a prompt when one of those VMs  are 
detected.

> 
> I write this because this is my experience. Installing an OS on a 
> virtual PC is easy, getting the drivers set up sometimes is hard work, 
> because you have to find those drivers first. Including them as an 
> installation package would be sufficiently easy for uses IMHO. Just my 2ยข.
> 
> Cheers,
> userbeitrag

Yes, finding, installing and configuring DOS drivers is not for the faint of 
heart.

Jerome

Sent from my iPhone, ignore bad sentence structures, grammatical errors and 
incorrect spell-corrected words. 

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to