Hyper V doesn't start Free Dos due to out of memory error

Bree said:

@Erez I created an animated .gif of my install process. It's in the attached .zip file. Extract the Hyper-V_FreeDos_install.GIF from it, then right-click on it, use 'Open with' to view it in Photos or in your browser. You'll see that I followed the same steps as cereberus.

Thank you very much for your both help, assistance and support! But I tend to prefer more to watch a video rather than viewing an animated GIF file in general, because video can be paused in the middle unlike animated GIF file unless I use a software that can both play and pause animated GIF files in the middle!

Another possibility is to use a software that can extract all frames from an animated GIF file and then let me view them all one by one exactly like how Microsoft PowerPoint allows the user to view all the slides one by one.

You could also send me an animated PNG file instead of an animated GIF file by the way!

Anyway suddenly the newly created virtual machine has finally been started but I have no idea what to do anymore from there!

I both just and simply want to do what I have to do from there to execute and start using some dos program that I have downloaded from some website from the internet and then installed manually on my physical D hard drive.

The DOS program that I am talking about is in my physical D drive and I can both view and see that DOS program with the Windows File Explorer application but double clicking it won't create a new process instance from that DOS program of course in Windows 10 operating system!

So that's why I want to use Hyper V and Free Dos to execute and both start and begin using this DOS program in my physical D hard drive.

Bree said:

Hyper-V won't allow you direct physical access to your D: drive. You could share the folder on the D: drive that contains your DOS program then map a share to it in the FreeDos VM. You will probably also have to enable 'SMB 1.0/CIFS Sever' in your host machine's 'Turn Windows features on or off' to be able to access the share from the DOS machine.

For that you'd need to add the Legacy Network Adapter to the VM, and install networking in FreeDos.

Networking FreeDOS - NDIS driver installation - FreeDOS

The Legacy Adapter in Hyper-V emulates the Intel 21140-based PCI Fast Ethernet Adapter (generic).

I imagine it is possible to create a second virtual hard drive formatted as fat32 (32GB max).

Then you could mount vhd in windows, copy any files to it, dismount it, then attach vhd to vm?

cereberus said:

I imagine it is possible to create a second virtual hard drive formatted as fat32 (32GB max).

Then you could mount vhd in windows, copy any files to it, dismount it, then attach vhd to vm?

Thank you very so much! I will try these methods and then I will let you know which of the methods worked and which didn't!

Erez said:

Thank you very much! I will try these methods and then I will let you know which of the methods worked and which didn't!

Creating a second 32GB fat32 vhd worked a charm. I attached it in HyperV



I created a text file in windows and copied it to the vhd whilst attached to windows, and then attached it as above (detaching from windows).

I had a problem editing it as @Bree did due to CTMouse as edit hanged.

I reboooted, then copied autoexec.bat to D drive, then attached vhd to windows, edited it (had to unhide it) as @ Bree did put REM in front of line CTmouse.

I then reattached vhd to vm, copied updated autoexec.bat to C drive, rebooted, the edit now worked fine in text mode (no mouse control) ok.

I could then edit the txt file.

I could not get mouse to work, even running mouse command. Years since I had to do this.

Bree said:

I just rebooted then the first command I used was CTMOUSE /U to unload the driver.

Then I could use Edit from the keyboard without it trying to initialise the mouse (and disabling keyboard input).

Yeah of course - years since I had to do it.

Bree said:

I took the opportunity to make a bootable virtual floppy .vfd file (you never know when one might be useful). That found another Hyper-V incompatibility. A Full format will fail....



...fortunately it will succeed with a Quick format using the /Q switch.

My cupboards are full of stuff that might be useful but never are LOL.

Bree said:

Hyper-V won't allow you direct physical access to your D: drive.

To clarify this, all internal and external disks except Windows system disk and USB flash drives can be added to a Hyper-V VM for physical access, if disk in question is first set offline in Disk Management.



Kari