Thanks Alan,
I will try the tutorial.
luckily, portuguese is not a problem ;-)
Cesar
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
No more attached file, link here:
https://www.dropbox.com/s/wk22xq6ecgb85ga/Tec_NetBootDisk%20-%20Cosmodata.html?dl=0
--
You should try *NetBootDisk*, it's a MS-Client
Attached a tutorial I made for a very basic instalation. (portuguese)
Alain
On 5/26/22 10:07, Louis Santillan wrote:
Hello Louis,
> You also need to provide a ‘model’ on the ‘network’ parameter. e1000 or
> rtl8139 have DOS packet drivers available.
I tried with the command below, and some variations
--network bridge=virbr0,model=rtl8139
> You can also use nicscan.exe (
> http://www.georgpotthast.de/sioux/pac
You can also use nicscan.exe (
http://www.georgpotthast.de/sioux/packet.htm) or pcinic.com (
http://dunfield.classiccmp.org/dos/index.htm) to verify the nic is
correctly configured in the VM.
On Thu, May 26, 2022 at 6:07 AM Louis Santillan wrote:
> You also need to provide a ‘model’ on the ‘netw
You also need to provide a ‘model’ on the ‘network’ parameter. e1000 or
rtl8139 have DOS packet drivers available.
On Thu, May 26, 2022 at 4:29 AM wrote:
> Hello everybody. Thanks for the help so far, sorry for the delay in
> responding.
>
> The simplest way for me to create a FreeDOS VM on my
Hello everybody. Thanks for the help so far, sorry for the delay in responding.
The simplest way for me to create a FreeDOS VM on my server was to install it
on a local VM and copy the disk image to the server, once there I created the
VM with the following command.
virt-install \
--name DO
>I believe the simplest will be to create the VM on another machine and learn
>how to import it to the host machine.
No, the simplest thing is to open up virt-manager on the other machine, go to
"File -> Add connection", fill out the dialog to connect to the host machine,
then go to "File -> Ne
>KVM is the underlying hypervisor here. It uses QEMU tools for creating disk
images and things, but it doesn't use the core QEMU emulator for
running x86 OSes on x86.
KVM is a kernel component, so userland processes use it for things, not the
other way around (specifically, it's a virtualization
Hi Louis,
> KVM/qemu as presented by virt-manager/virsh does something funny with the
> config of the VM. After initial boot it’ll “forget” about the CDROM. Seems
> like it’s intended for OSes that don’t need to reboot after formatting the
> primary drive. I saw this behavior in RHEL and Fed
On Mon, 23 May 2022 at 04:02, wrote:
>
> I'm trying to install FreeDOS in a virtual machine via virt-install, as the
> host machine is remote and doesn't have a graphical environment, so I only
> have access via ssh. Still, I can export the installer screen via VNC.
>
> The installation process
>It would probably be more straightforward for me to use qemu directly, but as
>I already have several VMs running managed by virt-manager, I wanted to keep
>using it for FreeDOS.
So virt-install is a tool for virt-manager, but I don't think I've ever used it
directly (there's a good possibilit
>KVM/qemu as presented by virt-manager/virsh does something funny with the
>config of the VM. After initial boot it’ll “forget” about the CDROM.
I think what's happening is that it detaches the disk image if the virtual CD
drive receives an eject command. On real hardware, if the software opens
KVM/qemu as presented by virt-manager/virsh does something funny with the
config of the VM. After initial boot it’ll “forget” about the CDROM.
Seems like it’s intended for OSes that don’t need to reboot after
formatting the primary drive. I saw this behavior in RHEL and Fedora using
Cockpit, virt
Hi!
I'm trying to install FreeDOS in a virtual machine via virt-install, as the
host machine is remote and doesn't have a graphical environment, so I only have
access via ssh. Still, I can export the installer screen via VNC.
The installation process loads, and I can get to the part of creating
14 matches
Mail list logo
