16
Setup & Installation / OS2 Warp 4.52 "vdi2hardware" result
« on: June 06, 2021, 01:00:09 pm »
Hi all, I believe the following experience could be of any interest in this forum for those ones that can go deeper due to their excellent system knowledge rather than me, an average user with peaks of curiosity sometimes -helped a lot here to realize some configuration tasks-
I've seen this videotutorial for converting Virtualbox vdi machines into real hardware installed systems.
https://www.youtube.com/watch?v=60Nv1zPVzjc
and have applied the procedure on my 20 Gb size OS2 Warp 4.52 vdi machine hosted on Windows, so have converted it in an .img file which have then burned in a USB3 pendrive 64 Gb.
After this, I have plugged the USB pendrive on an eeepc netbook Asus T101MT -year 2010 hardware with LEGACY BIOS- for booting. In the image you can see how it went.
Also tried to boot same USB pendrive from my HP 15 serie laptop -year 2017 hardware with UEFI+LEGACY BIOS-, same result with one beep sound alert at the ending message: hardware conflict?
This is not too bad for me, at least the converting method seems to have done the job; the OS2 Warp installation has been placed inside that USB volume and started the boot sequence. A little bit better than the case of "no bootable OS found in this volume" message, if the conversion had not worked at all.
Pheraps some of you already know what prevented OS2 Warp to boot in this case.
My two cents guess is : unrecoverable real hardware issues with such OS2 Warp installation having all peripherals interfaced by Virtualbox filters. Maybe config.sys has the wrong entries for the hardware items on the netbook.
Then I made the "reverse-proof" test : had booted that USB volume from inside a separate Virtualbox session, and it works. It is the OS2 installed system at the state of its first Virtualbox boot, missing the next improvements I made (Guest Additions and other configurations + software + utilities). Means that the .vdi machine selected for the conversion was the one keeping the original state, but it seemed to me the only valid .vdi file I could choose.
Thank you
I've seen this videotutorial for converting Virtualbox vdi machines into real hardware installed systems.
https://www.youtube.com/watch?v=60Nv1zPVzjc
and have applied the procedure on my 20 Gb size OS2 Warp 4.52 vdi machine hosted on Windows, so have converted it in an .img file which have then burned in a USB3 pendrive 64 Gb.
After this, I have plugged the USB pendrive on an eeepc netbook Asus T101MT -year 2010 hardware with LEGACY BIOS- for booting. In the image you can see how it went.
Also tried to boot same USB pendrive from my HP 15 serie laptop -year 2017 hardware with UEFI+LEGACY BIOS-, same result with one beep sound alert at the ending message: hardware conflict?
This is not too bad for me, at least the converting method seems to have done the job; the OS2 Warp installation has been placed inside that USB volume and started the boot sequence. A little bit better than the case of "no bootable OS found in this volume" message, if the conversion had not worked at all.
Pheraps some of you already know what prevented OS2 Warp to boot in this case.
My two cents guess is : unrecoverable real hardware issues with such OS2 Warp installation having all peripherals interfaced by Virtualbox filters. Maybe config.sys has the wrong entries for the hardware items on the netbook.
Then I made the "reverse-proof" test : had booted that USB volume from inside a separate Virtualbox session, and it works. It is the OS2 installed system at the state of its first Virtualbox boot, missing the next improvements I made (Guest Additions and other configurations + software + utilities). Means that the .vdi machine selected for the conversion was the one keeping the original state, but it seemed to me the only valid .vdi file I could choose.
Thank you