Skip to main content

Install OS/2 Warp with (or without) virtualbox

-- Install the oracle virtual box (ex. 4.2.0)
-- Create a new v.machine  with the settings for your os/2 warp version

ex.:
 Name(anything): os2warp
 Type: IBM OS/2
 Version (the version that you are installing - 4 in my case): OS/2 Warp 4

-- Add one Disk and one Floppy as storage(s) for the virtual machine. Add a CD/DVD drive if you want to install a bit faster (see below).


-- extract the os2warp.iso so that you can use the dsk images for the installation (located in \DISKIMGS\OS2\35\)

-- Load in the floppy device the disk0.dsk and swap when requested by the os2 setup.


-- when the setup asks for the floppy 1 (after 0) use the DISK1_CD.DSK as floppy and remember to put the CD or load the cd iso image in the, virtual or real, cd drive

-- Choose "easy installation" if you don't need particular things.

When you the "Fdisk" application appears it can show you that the first disk is corrupted. Just go ahead and press enter.
press tab and press -> (right) to choose your disk.
Avoid the 1024kb that is the floppy disk -- that should be type 83 and "startable".

Your destination disk should be also with free space if not previously formatted.
Once you are in the disk page you need to press tab to choose your partition.
Press "Enter" and if there's no partition choose "create partition" and "primary partition".


If you are going to use more than one os (ex. os2+dos) on the same disk create the first partition of 1mb where you are going to install the boot manager.
See those faqs for more informations:
http://www.mit.edu/activities/os2/faq/os2faq0403.html

-- Create the first primary partition of 500mb where os/2 warp will reside and (press Enter)

-- Set the partition as startable and as Installable (!!Important).

The first partition must be smaller than 512mb (I've personally used 256mb) due to *old* bios restrictions.
Fdisk will assign automatically the C: drive letter.
"Also, on many PCs, because of BIOS restrictions, your startable (primary) partition must be physically located entirely below the 1024th cylinder on your hard disk (or, roughly speaking, it must be no larger than about 511 MB)" (as already stated in the previously linked faqs).
Another good page is suggesting, with far more useful informations,

http://pclt.cis.yale.edu/pclt/BOOT/OS2.HTM

-- press f3 and exit

it could happen that the system doesn't recognize your primary partition even if you've done everything correctly. Just exit anyway and let the system restart. It should recognize your partition and start the regular installation (from floppy3).

if something goes wrong while formatting (red screen) restart (ctrl+alt+canc), choose advanced installation and try to reformat.
In case of other problems try to repartition with gparted (gparted live iso linux http://gparted.org/download.php) in fat16.


-- (If you want) Add a second "extended" partition that will fill all the remaining data and d: will be assigned automatically.

-- continue the setup



-- hit "enter" at the end of the installation process and restart













_____________________________________________


Errors:
OS/2!! SYS02025

OS/2!! SYS02027

Those errors are common if you are trying to use a non IBM machine, if the boot sector is corrupted (as I can read from the various docs), if there are HDD issues or if you are running non fully startable floppies.

http://service5.boulder.ibm.com/pspsdocs.nsf/8d77653332b629ab862563cc005ee09a/dc6f1f67b91441a2852561ac0076dd72?OpenDocument
http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-44388


To solve the problem in virtualbox just make sure to run the first floppy and switch floppy as needed from the current virtual machine without closing the v.m. window (check the devices in the toolbar/menu) and make sure that you have selected the correct OS/2 system when you have created the vm.

____________________________________________________________



please make questions and suggestions in the comments. This is not a *guide* but something like a personal reminder for myself.

Comments

Popular posts from this blog

Moodle 3.8.1+ - path leak via errors in several files

Moodle 3.8.1+ ----------------------------------------------- File: admin/mailout-debugger.php #!/usr/bin/php Notice : Disabled. in \admin\mailout-debugger.php on line 73 File: admin/settings/appearance.php Notice : Undefined variable: hassiteconfig in \admin\settings\appearance.php on line 10 Fatal error : Uncaught Error: Call to undefined function has_any_capability() in \admin\settings\appearance.php:10 Stack trace: #0 {main} thrown in \admin\settings\appearance.php on line 10 File: admin/settings/badges.php Notice : Undefined variable: hassiteconfig in \admin\settings\badges.php on line 30 Fatal error : Uncaught Error: Call to undefined function has_any_capability() in \admin\settings\badges.php:30 Stack trace: #0 {main} thrown in \admin\settings\badges.php on line 30 File: admin/settings/courses.php Notice : Undefined variable: hassiteconfig in \admin\settings\courses.php on line 32 Fatal error : Uncaught Error: Call to undefined function

2022 - Remove (the too many) Ads from Memu launcher

Simple method Download from pureapk "MEmu Launcher2" ex: MEmu Launcher2_v6.0.9_apkpure.com Install "System app remover" (root) remove from system apps the "memu launcher 2" import the "purified" MEmu Launcher2 apk with the Memu utility ("apk" on the right toolbar) Longer method Install "Export Apk" Export the memu launcher2  Install purify https://github.com/echo-devim/purify/raw/master/Purify.apk use purify with the exported memu launcher 2 Install "System app remover" (root) remove from system apps the "memu launcher 2" import the "purified" MEmu Launcher2 apk with the Memu utility ("apk" on the right toolbar)