OS Support

There simply are things that you shouldn't do inside of Limbo PC Emulator. These things involve:
-Running anything higher than Windows ME (Millenium Edition).
-Using Ubuntu or any other resource heavy Linux Distros

---

Some OS that do work:
-DankOS Beta
-NanoLinux (Project here on SourceForge)
-Windows ME and lower
-TinyCoreLinux (slow to boot)
-React OS (Experience may vary, also on SourceForge)
-Kolibri OS
-AROS (Amiga Research Operating System)
-DSL (Damn Small Linux)

Windows VMs (Older than XP, and various Betas) are available on www.winworldpc.com
Various light-weight Linux distros can be found here on SourceForge.

Reommended OS to run include:
-DankOS
-NanoLinux
-Windows NT 4
-Kolibri OS
-React OS
-Windows 9x
-AROS
-DSL

---

You can comment on this page and list OS that do and do not work. They will be listed on this page.

[Patrick Zumstein]

Hello
I am just trying around with the Limbo-emulator.

As I can see not just qcow2 is supported, also img - format.
But, are there some special versions required for the images ? It is because I would like to setup the system using VirtualBox, VMWare or whatever. If I try to convert images let's say with qemu-convert or VBoxManage, I never get a usable format, limbo does not boot into the image and resets directly.

Also if I try to create the qcow2 file in limbo, up to create partitions, the qcow2 - file created is not readable by VirtualBox, WMWare.

Please specify how to create images vdi or qcow2 on the computer.

Thank you

[vynncengm]

Weird.

Have you tried just using a vdi created in VirtualBox without any type of conversion? Those are known to work.

Otherwise, the OS you are trying to boot into may not be supported.

[Patrick Zumstein]

Stange. I tried from VirtualBox under Linux, normal VDI, allocated space and dynamic also. I tried to setup puppy within VirtualBox.
One point is that I downloaded some VDI that are working. But when I try to mount them with losetup and access /dev/loop0 with gparted, the partitions are not recognized on these.

But my own created VDI work well to manipulate on Linux, but could not boot with limbo.

Maybe I need some more Coffee and a few tries more. The program is interesting.

[Patrick Zumstein]

You are right! VDI default from VirtualBox is working.

Whatever I did yesterday it was definitively not default settings. Tried to install now ubuntu-minimal, working without problems.

Thanks.