#86box — Public Fediverse posts

BeOS 3.0 on 86Box with Socket 8 [1995]

BeOS 3.0 was a version of BeOS that was first made available for traditional Intel computers, alongside the PowerPC architecture. It was available for purchase at $69.95 then raised to $99.95.

Our focus in this article is testing BeOS 3.0 on an 86Box emulated machine with a Socket 8 [1995] motherboard. You can download it from here. However, you’ll have to create separate ISO files for the two tracks that were found in the BIN/CUE format:

• The first track is for the partitioning tool for Windows 95
• The second track is for the BeOS installation

You can use bchunk beos-3.0.bin beos-3.0.cue beos-3.0.iso to get the two ISO files for the above tracks. Please note that you’ll also need to install Windows 95 in order to be able to install BeOS 3.0.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1995] Socket 8
• Machine: [i440FX] Intel AP440FX (Apollo)
• CPU: Intel Pentium II Overdrive @ 100 MHz
• Memory: 32 MB
• Video: [ISA16] Cirrus Logic GD5434
• Keyboard: AT Keyboard
• Mouse: PS/2 Mouse
• Sound card: [ISA16] Sound Blaster 16 PnP
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: os2warp452.vhd
  • C/H/S: 2080/16/63
  • Size: 1024 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: ATAPI (0:1) HITACHI CDR-8130 0020 (16x)

Once everything is configured as above, we can now start the virtual machine. Before installing Windows 95 prior to BeOS 3.0, we need to change the following BIOS settings to ensure that BeOS can start successfully:

Now, let’s assume that Windows 95 has been successfully installed to the virtual machine. Insert the first disc called beos-3.0.iso01.iso to the CD-ROM reader, then let Windows start.

Open My Computer, then double-click on the BeOS logo to start the installation wizard for the PartitionMagic Special Edition partitioner.

Now, follow the steps to install this software.

As soon as you click Finish, Windows exits and the partitioner starts in a completely separate environment.

Since we need half the size of the Windows partition, we just need to click OK, then confirm the changes. Afterwards, the resize operation starts.

After the resize completes, you’ll be prompted to restart the virtual machine. Let it restart to Windows.

Once Windows starts, go to My Computer, then right-click on the CD-ROM drive (the BeOS icon), then navigate to experimental > Win95, and copy the BeLaunch folder to the root of the C: drive where Windows is installed.

After that, insert the second ISO file for the BeOS installer, just like below. Then, open the BeLaunch folder, and double-click on “BeOS Launcher”.

Wait for BeOS to start up…

You should be taken to a license agreement screen where you have to click Accept to continue the installation.

After that, make sure that the installer has automatically selected the newly-created BeOS partition created by PartitionMagic Special Edition. You can verify that by checking the partition ID, as well as the file system type. It should say “unknown”.

Press Begin, then let BeOS initialize the partition, just like below:

After initialization, the installation starts.

The installation should be successful at this point. Press Quit below.

Let the virtual machine reboot back to Windows. In case it hangs on the below screen (the tntats window), release the mouse control and press the reset icon.

Once Windows restarts, double-click on the BeOS Launcher icon. Afterwards, BeOS should automatically recognize the installed system. You should see the desktop below:

The installation is successful at this point! Here’s a demo screenshot of BeOS 3.0 installed alongside Windows 95.

Of course, when you try to shut down BeOS, you should see this window, since we have disabled APM:

Bin immer noch am Basteln mit meinem virtuellen EGA-System. Inzwischen sieht es schon deutlich besser aus:

- DOS-Shell im EGA-Grafikmodus
- Windows 3.11 läuft jetzt perfekt
- Datei-Manager mit Y2K-Update
- Entertainment Pack installiert

Das Ganze funktioniert jetzt auch einwandfrei mit nur 2MB Arbeitsspeicher und es sind dann immernoch 735KB RAM frei. So langsam kann man mit dem System auch arbeiten!

Nice! 😎

#RetroComputing #EGA #Grafikkarte #86Box #Emulation #Win311 #Windows #Retro

Bin immer noch am Basteln mit meinem virtuellen EGA-System. Inzwischen sieht es schon deutlich besser aus:

- DOS-Shell im EGA-Grafikmodus
- Windows 3.11 läuft jetzt perfekt
- Datei-Manager mit Y2K-Update
- Entertainment Pack installiert

Das Ganze funktioniert jetzt auch einwandfrei mit nur 2MB Arbeitsspeicher und es sind dann immernoch 735KB RAM frei. So langsam kann man mit dem System auch arbeiten!

Nice! 😎

#RetroComputing #EGA #Grafikkarte #86Box #Emulation #Win311 #Windows #Retro

Bin immer noch am Basteln mit meinem virtuellen EGA-System. Inzwischen sieht es schon deutlich besser aus:

- DOS-Shell im EGA-Grafikmodus
- Windows 3.11 läuft jetzt perfekt
- Datei-Manager mit Y2K-Update
- Entertainment Pack installiert

Das Ganze funktioniert jetzt auch einwandfrei mit nur 2MB Arbeitsspeicher und es sind dann immernoch 735KB RAM frei. So langsam kann man mit dem System auch arbeiten!

Nice! 😎

#RetroComputing #EGA #Grafikkarte #86Box #Emulation #Win311 #Windows #Retro

Bin immer noch am Basteln mit meinem virtuellen EGA-System. Inzwischen sieht es schon deutlich besser aus:

- DOS-Shell im EGA-Grafikmodus
- Windows 3.11 läuft jetzt perfekt
- Datei-Manager mit Y2K-Update
- Entertainment Pack installiert

Das Ganze funktioniert jetzt auch einwandfrei mit nur 2MB Arbeitsspeicher und es sind dann immernoch 735KB RAM frei. So langsam kann man mit dem System auch arbeiten!

Nice! 😎

#RetroComputing #EGA #Grafikkarte #86Box #Emulation #Win311 #Windows #Retro

Mit ein Bisschen Basteln hab ich's jetzt am Ende doch hinbekommen, Windows for Workgroups 3.11 mit EGA-Grafik zum Laufen zu bekommen. Es funktioniert, aber - ja - es macht ehrlich nicht so wirklich Spaß. Windows for Workgroups mag EGA nicht besonders.😕

Es würde vermutlich mehr Sinn ergeben, Windows 3.1 (ohne Workgroups) zu verwenden und das System dann per FreshUp-Diskette auf Version 3.11 zu heben.

#EGA #RetroComputing #IBMPC #Windows #80s #90s #Oldschool #Grafik #86Box #Emulation

Mit ein Bisschen Basteln hab ich's jetzt am Ende doch hinbekommen, Windows for Workgroups 3.11 mit EGA-Grafik zum Laufen zu bekommen. Es funktioniert, aber - ja - es macht ehrlich nicht so wirklich Spaß. Windows for Workgroups mag EGA nicht besonders.😕

Es würde vermutlich mehr Sinn ergeben, Windows 3.1 (ohne Workgroups) zu verwenden und das System dann per FreshUp-Diskette auf Version 3.11 zu heben.

#EGA #RetroComputing #IBMPC #Windows #80s #90s #Oldschool #Grafik #86Box #Emulation

Mit ein Bisschen Basteln hab ich's jetzt am Ende doch hinbekommen, Windows for Workgroups 3.11 mit EGA-Grafik zum Laufen zu bekommen. Es funktioniert, aber - ja - es macht ehrlich nicht so wirklich Spaß. Windows for Workgroups mag EGA nicht besonders.😕

Es würde vermutlich mehr Sinn ergeben, Windows 3.1 (ohne Workgroups) zu verwenden und das System dann per FreshUp-Diskette auf Version 3.11 zu heben.

#EGA #RetroComputing #IBMPC #Windows #80s #90s #Oldschool #Grafik #86Box #Emulation

Mit ein Bisschen Basteln hab ich's jetzt am Ende doch hinbekommen, Windows for Workgroups 3.11 mit EGA-Grafik zum Laufen zu bekommen. Es funktioniert, aber - ja - es macht ehrlich nicht so wirklich Spaß. Windows for Workgroups mag EGA nicht besonders.😕

Es würde vermutlich mehr Sinn ergeben, Windows 3.1 (ohne Workgroups) zu verwenden und das System dann per FreshUp-Diskette auf Version 3.11 zu heben.

#EGA #RetroComputing #IBMPC #Windows #80s #90s #Oldschool #Grafik #86Box #Emulation

Ich beschäftige mich heut Abend nebenbei mal damit, ein virtuelles System mit klassischer EGA-Grafik aufzusetzen. Hab mich da in 86Box für eine "ATI EGA Wonder 800+" ISA-Karte mit 256K entschieden.

Spannenderweise sehen mit EGA sogar schon die Schriften im BIOS und im SETUP-Programm subtil anders aus als mit VGA. Für PC-DOS 5 wird beim Booten auch gleich ein EGA-Treiber geladen. Glücklicherweise verbraucht der nur 3.2KB an Arbeitsspeicher

#Retro #RetroComputing #EGA #DOS #80s #86Box #Emulation

Ich beschäftige mich heut Abend nebenbei mal damit, ein virtuelles System mit klassischer EGA-Grafik aufzusetzen. Hab mich da in 86Box für eine "ATI EGA Wonder 800+" ISA-Karte mit 256K entschieden.

Spannenderweise sehen mit EGA sogar schon die Schriften im BIOS und im SETUP-Programm subtil anders aus als mit VGA. Für PC-DOS 5 wird beim Booten auch gleich ein EGA-Treiber geladen. Glücklicherweise verbraucht der nur 3.2KB an Arbeitsspeicher

#Retro #RetroComputing #EGA #DOS #80s #86Box #Emulation

Ich beschäftige mich heut Abend nebenbei mal damit, ein virtuelles System mit klassischer EGA-Grafik aufzusetzen. Hab mich da in 86Box für eine "ATI EGA Wonder 800+" ISA-Karte mit 256K entschieden.

Spannenderweise sehen mit EGA sogar schon die Schriften im BIOS und im SETUP-Programm subtil anders aus als mit VGA. Für PC-DOS 5 wird beim Booten auch gleich ein EGA-Treiber geladen. Glücklicherweise verbraucht der nur 3.2KB an Arbeitsspeicher

#Retro #RetroComputing #EGA #DOS #80s #86Box #Emulation

Ich beschäftige mich heut Abend nebenbei mal damit, ein virtuelles System mit klassischer EGA-Grafik aufzusetzen. Hab mich da in 86Box für eine "ATI EGA Wonder 800+" ISA-Karte mit 256K entschieden.

Spannenderweise sehen mit EGA sogar schon die Schriften im BIOS und im SETUP-Programm subtil anders aus als mit VGA. Für PC-DOS 5 wird beim Booten auch gleich ein EGA-Treiber geladen. Glücklicherweise verbraucht der nur 3.2KB an Arbeitsspeicher

#Retro #RetroComputing #EGA #DOS #80s #86Box #Emulation

These early versions of Tetris from 1986 are remarkably playable and addictive, even today. I just wanted to compare different revisions of the game, but found myself playing and coudn't stop. Oh, well.. Tetris is Tetris 😉

#Tetris #IBMPC #Retro #80s #SovietUnion #DOS #86Box #Emulation #RetroGaming #DOSGaming

Admittedly, there are easier ways to emulate original DOS games like "Maniac Mansion" on a modern computer, but I gotta say: I'm not a huge fan of these dumbed-down, 1-click-and-play solutions like "DOSBox" or "ScummVM".

To me, using an emulator like "86Box" to create my own, virtual PC with its own operating system, startup scripts and file management is so much more enjoyable. And with floppydisk audio emulation, it even sounds authentic! 😉

#Emulation #86Box #90s #Gaming #Retro #RetroGaming

I'm checking out the original Wing Commander Deluxe Edition CD-ROM, I recently found on the Internet Archive's redump library. This one lets you make a dedicated data disk for your savegames.

I ran this on my virtual Compaq Deskpro 386/25MHz without any modification or issue using the latest 86Box v6.0 Beta.

Link to the redump library (W...): https://archive.org/download/redump_pc_W

Retro Gaming rulez!

#Retro #Gaming #RetroGaming #DOS #86Box #MSDOS #PCGaming #90s #90er #WingCommander #SpaceSim

I'm checking out the original Wing Commander Deluxe Edition CD-ROM, I recently found on the Internet Archive's redump library. This one lets you make a dedicated data disk for your savegames.

I ran this on my virtual Compaq Deskpro 386/25MHz without any modification or issue using the latest 86Box v6.0 Beta.

Link to the redump library (W...): https://archive.org/download/redump_pc_W

Retro Gaming rulez!

#Retro #Gaming #RetroGaming #DOS #86Box #MSDOS #PCGaming #90s #90er #WingCommander #SpaceSim

I'm checking out the original Wing Commander Deluxe Edition CD-ROM, I recently found on the Internet Archive's redump library. This one lets you make a dedicated data disk for your savegames.

I ran this on my virtual Compaq Deskpro 386/25MHz without any modification or issue using the latest 86Box v6.0 Beta.

Link to the redump library (W...): https://archive.org/download/redump_pc_W

Retro Gaming rulez!

#Retro #Gaming #RetroGaming #DOS #86Box #MSDOS #PCGaming #90s #90er #WingCommander #SpaceSim

I'm checking out the original Wing Commander Deluxe Edition CD-ROM, I recently found on the Internet Archive's redump library. This one lets you make a dedicated data disk for your savegames.

I ran this on my virtual Compaq Deskpro 386/25MHz without any modification or issue using the latest 86Box v6.0 Beta.

Link to the redump library (W...): https://archive.org/download/redump_pc_W

Retro Gaming rulez!

#Retro #Gaming #RetroGaming #DOS #86Box #MSDOS #PCGaming #90s #90er #WingCommander #SpaceSim

Oh, cool! Telev78 just shared a working 5.25 inch disk image of the original TETRIS by MirrorSoft. Back in 1987, EGA was the fanciest available graphics mode on the IBM-PC! Hell yeah! Interestingly, this European release was slightly different from the Spectrum Holobyte version. Comparing them side by side using 86Box.

Link: https://archive.org/details/tetris-mirrorsoft-360k-kfx

Thank you @Telev

#RetroGaming #Retro #Gaming #80s #80er #TETRIS #InternetArchive #IBMPC #FloppyDisk #Diskette #Emulation #86Box

Oh, cool! Telev78 just shared a working 5.25 inch disk image of the original TETRIS by MirrorSoft. Back in 1987, EGA was the fanciest available graphics mode on the IBM-PC! Hell yeah! Interestingly, this European release was slightly different from the Spectrum Holobyte version. Comparing them side by side using 86Box.

Link: https://archive.org/details/tetris-mirrorsoft-360k-kfx

Thank you @Telev

#RetroGaming #Retro #Gaming #80s #80er #TETRIS #InternetArchive #IBMPC #FloppyDisk #Diskette #Emulation #86Box

Oh, cool! Telev78 just shared a working 5.25 inch disk image of the original TETRIS by MirrorSoft. Back in 1987, EGA was the fanciest available graphics mode on the IBM-PC! Hell yeah! Interestingly, this European release was slightly different from the Spectrum Holobyte version. Comparing them side by side using 86Box.

Link: https://archive.org/details/tetris-mirrorsoft-360k-kfx

Thank you @Telev

#RetroGaming #Retro #Gaming #80s #80er #TETRIS #InternetArchive #IBMPC #FloppyDisk #Diskette #Emulation #86Box

Oh, cool! Telev78 just shared a working 5.25 inch disk image of the original TETRIS by MirrorSoft. Back in 1987, EGA was the fanciest available graphics mode on the IBM-PC! Hell yeah! Interestingly, this European release was slightly different from the Spectrum Holobyte version. Comparing them side by side using 86Box.

Link: https://archive.org/details/tetris-mirrorsoft-360k-kfx

Thank you @Telev

#RetroGaming #Retro #Gaming #80s #80er #TETRIS #InternetArchive #IBMPC #FloppyDisk #Diskette #Emulation #86Box

OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]

OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.

Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1998] Super Socket 7
• Machine: [SiS 5591] Gigabyte GA-5SG100
• CPU: Intel Pentium @ 166 MHz
• Memory: 128 MB
• Video: [ISA16] Cirrus Logic GD5434
• Keyboard: AT Keyboard
• Mouse: PS/2 Mouse
• Sound card: [ISA16] Sound Blaster 16 PnP
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: os2warp452.vhd
  • C/H/S: 1054/16/63
  • Size: 518 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)

Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called mcp2-refresh-boot-en.iso to the CD-ROM reader, then configure BIOS as necessary.

To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.

After that, we save the changes and restart the virtual machine.

The installer starts by telling you to insert the installation CD-ROM to the drive.

In this case, right-click on the CD-ROM icon, select “Insert…”, select mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.

After that, you should be able to see this welcome screen:

Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.

Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.

Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.

After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:

Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.

Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.

After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.

After that, this partition should be created.

We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.

You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.

Press ENTER again, then select “Use existing partition”.

Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.

Press ENTER, and you should see the menu box below:

Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.

Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.

At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.

Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:

Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.

Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.

After that, the installation of the base system begins.

After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.

After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.

First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.

Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”

Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.

We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.

Once we’ve selected OK, we’re then presented with a set of packages to install.

As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.

Once we clicked Next, we’re presented with a prompt to identify ourselves.

After that, we’re given another set of software packages to install. They represent the client services for OS/2.

Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.

We went to create a new ID and a password for the sharing service

Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”

Once we pressed OK, we’ve seen this result:

Now, we’ve pressed Install, and a confirmation dialog box appeared.

Now, the installation of the remaining system files started here.

Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.

We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.

After that, the remaining portions of the installation started. This is part one of the long waiting journey!

After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.

After that, the long waiting journey continues…

The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.

We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.

Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.

We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…

After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.

Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.

Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!

Nostalgic, isn’t it?

OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]

OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.

Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1998] Super Socket 7
• Machine: [SiS 5591] Gigabyte GA-5SG100
• CPU: Intel Pentium @ 166 MHz
• Memory: 128 MB
• Video: [ISA16] Cirrus Logic GD5434
• Keyboard: AT Keyboard
• Mouse: PS/2 Mouse
• Sound card: [ISA16] Sound Blaster 16 PnP
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: os2warp452.vhd
  • C/H/S: 1054/16/63
  • Size: 518 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)

Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called mcp2-refresh-boot-en.iso to the CD-ROM reader, then configure BIOS as necessary.

To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.

After that, we save the changes and restart the virtual machine.

The installer starts by telling you to insert the installation CD-ROM to the drive.

In this case, right-click on the CD-ROM icon, select “Insert…”, select mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.

After that, you should be able to see this welcome screen:

Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.

Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.

Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.

After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:

Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.

Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.

After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.

After that, this partition should be created.

We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.

You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.

Press ENTER again, then select “Use existing partition”.

Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.

Press ENTER, and you should see the menu box below:

Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.

Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.

At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.

Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:

Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.

Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.

After that, the installation of the base system begins.

After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.

After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.

First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.

Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”

Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.

We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.

Once we’ve selected OK, we’re then presented with a set of packages to install.

As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.

Once we clicked Next, we’re presented with a prompt to identify ourselves.

After that, we’re given another set of software packages to install. They represent the client services for OS/2.

Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.

We went to create a new ID and a password for the sharing service

Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”

Once we pressed OK, we’ve seen this result:

Now, we’ve pressed Install, and a confirmation dialog box appeared.

Now, the installation of the remaining system files started here.

Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.

We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.

After that, the remaining portions of the installation started. This is part one of the long waiting journey!

After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.

After that, the long waiting journey continues…

The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.

We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.

Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.

We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…

After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.

Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.

Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!

Nostalgic, isn’t it?

OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]

OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.

Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1998] Super Socket 7
• Machine: [SiS 5591] Gigabyte GA-5SG100
• CPU: Intel Pentium @ 166 MHz
• Memory: 128 MB
• Video: [ISA16] Cirrus Logic GD5434
• Keyboard: AT Keyboard
• Mouse: PS/2 Mouse
• Sound card: [ISA16] Sound Blaster 16 PnP
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: os2warp452.vhd
  • C/H/S: 1054/16/63
  • Size: 518 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)

Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called mcp2-refresh-boot-en.iso to the CD-ROM reader, then configure BIOS as necessary.

To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.

After that, we save the changes and restart the virtual machine.

The installer starts by telling you to insert the installation CD-ROM to the drive.

In this case, right-click on the CD-ROM icon, select “Insert…”, select mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.

After that, you should be able to see this welcome screen:

Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.

Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.

Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.

After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:

Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.

Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.

After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.

After that, this partition should be created.

We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.

You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.

Press ENTER again, then select “Use existing partition”.

Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.

Press ENTER, and you should see the menu box below:

Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.

Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.

At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.

Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:

Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.

Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.

After that, the installation of the base system begins.

After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.

After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.

First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.

Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”

Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.

We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.

Once we’ve selected OK, we’re then presented with a set of packages to install.

As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.

Once we clicked Next, we’re presented with a prompt to identify ourselves.

After that, we’re given another set of software packages to install. They represent the client services for OS/2.

Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.

We went to create a new ID and a password for the sharing service

Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”

Once we pressed OK, we’ve seen this result:

Now, we’ve pressed Install, and a confirmation dialog box appeared.

Now, the installation of the remaining system files started here.

Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.

We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.

After that, the remaining portions of the installation started. This is part one of the long waiting journey!

After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.

After that, the long waiting journey continues…

The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.

We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.

Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.

We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…

After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.

Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.

Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!

Nostalgic, isn’t it?

OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]

OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.

Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1998] Super Socket 7
• Machine: [SiS 5591] Gigabyte GA-5SG100
• CPU: Intel Pentium @ 166 MHz
• Memory: 128 MB
• Video: [ISA16] Cirrus Logic GD5434
• Keyboard: AT Keyboard
• Mouse: PS/2 Mouse
• Sound card: [ISA16] Sound Blaster 16 PnP
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: os2warp452.vhd
  • C/H/S: 1054/16/63
  • Size: 518 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)

Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called mcp2-refresh-boot-en.iso to the CD-ROM reader, then configure BIOS as necessary.

To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.

After that, we save the changes and restart the virtual machine.

The installer starts by telling you to insert the installation CD-ROM to the drive.

In this case, right-click on the CD-ROM icon, select “Insert…”, select mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.

After that, you should be able to see this welcome screen:

Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.

Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.

Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.

After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:

Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.

Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.

After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.

After that, this partition should be created.

We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.

You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.

Press ENTER again, then select “Use existing partition”.

Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.

Press ENTER, and you should see the menu box below:

Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.

Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.

At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.

Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:

Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.

Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.

After that, the installation of the base system begins.

After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.

After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.

First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.

Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”

Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.

We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.

Once we’ve selected OK, we’re then presented with a set of packages to install.

As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.

Once we clicked Next, we’re presented with a prompt to identify ourselves.

After that, we’re given another set of software packages to install. They represent the client services for OS/2.

Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.

We went to create a new ID and a password for the sharing service

Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”

Once we pressed OK, we’ve seen this result:

Now, we’ve pressed Install, and a confirmation dialog box appeared.

Now, the installation of the remaining system files started here.

Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.

We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.

After that, the remaining portions of the installation started. This is part one of the long waiting journey!

After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.

After that, the long waiting journey continues…

The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.

We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.

Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.

We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…

After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.

Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.

Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!

Nostalgic, isn’t it?

OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]

OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.

Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1998] Super Socket 7
• Machine: [SiS 5591] Gigabyte GA-5SG100
• CPU: Intel Pentium @ 166 MHz
• Memory: 128 MB
• Video: [ISA16] Cirrus Logic GD5434
• Keyboard: AT Keyboard
• Mouse: PS/2 Mouse
• Sound card: [ISA16] Sound Blaster 16 PnP
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: os2warp452.vhd
  • C/H/S: 1054/16/63
  • Size: 518 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)

Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called mcp2-refresh-boot-en.iso to the CD-ROM reader, then configure BIOS as necessary.

To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.

After that, we save the changes and restart the virtual machine.

The installer starts by telling you to insert the installation CD-ROM to the drive.

In this case, right-click on the CD-ROM icon, select “Insert…”, select mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.

After that, you should be able to see this welcome screen:

Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.

Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.

Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.

After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:

Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.

Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.

After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.

After that, this partition should be created.

We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.

You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.

Press ENTER again, then select “Use existing partition”.

Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.

Press ENTER, and you should see the menu box below:

Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.

Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.

At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.

Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:

Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.

Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.

After that, the installation of the base system begins.

After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.

After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.

First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.

Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”

Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.

We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.

Once we’ve selected OK, we’re then presented with a set of packages to install.

As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.

Once we clicked Next, we’re presented with a prompt to identify ourselves.

After that, we’re given another set of software packages to install. They represent the client services for OS/2.

Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.

We went to create a new ID and a password for the sharing service

Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”

Once we pressed OK, we’ve seen this result:

Now, we’ve pressed Install, and a confirmation dialog box appeared.

Now, the installation of the remaining system files started here.

Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.

We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.

After that, the remaining portions of the installation started. This is part one of the long waiting journey!

After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.

After that, the long waiting journey continues…

The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.

We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.

Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.

We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…

After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.

Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.

Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!

Nostalgic, isn’t it?

Playing DigDug from Microsoft's "Return of Arcade" on Windows 95 using 86Box. That's what #RetroGaming looked like 30 years ago! Still awesome! 😉

#90s #Windows #Win95 #Microsoft #Arcade #Retro #90er #Gaming #PCGaming #Emulation #86Box

Playing DigDug from Microsoft's "Return of Arcade" on Windows 95 using 86Box. That's what #RetroGaming looked like 30 years ago! Still awesome! 😉

#90s #Windows #Win95 #Microsoft #Arcade #Retro #90er #Gaming #PCGaming #Emulation #86Box

Playing DigDug from Microsoft's "Return of Arcade" on Windows 95 using 86Box. That's what #RetroGaming looked like 30 years ago! Still awesome! 😉

#90s #Windows #Win95 #Microsoft #Arcade #Retro #90er #Gaming #PCGaming #Emulation #86Box

Playing DigDug from Microsoft's "Return of Arcade" on Windows 95 using 86Box. That's what #RetroGaming looked like 30 years ago! Still awesome! 😉

#90s #Windows #Win95 #Microsoft #Arcade #Retro #90er #Gaming #PCGaming #Emulation #86Box

After looking through several CD-ROMs, I guess I finallly found the best version of the Soundblaster 16 driver for DOS, Windows 3.1 or Windows 95. Here it is installing on my 25MHz COMPAQ Deskpro 386. 😉

https://archive.org/details/sb-16

#DOS #Retro #Tech #90s #90er #DOSGaming #PCGaming #Soundblaster #86Box #Emulation #Driver #Windows

After looking through several CD-ROMs, I guess I finallly found the best version of the Soundblaster 16 driver for DOS, Windows 3.1 or Windows 95. Here it is installing on my 25MHz COMPAQ Deskpro 386. 😉

https://archive.org/details/sb-16

#DOS #Retro #Tech #90s #90er #DOSGaming #PCGaming #Soundblaster #86Box #Emulation #Driver #Windows

After looking through several CD-ROMs, I guess I finallly found the best version of the Soundblaster 16 driver for DOS, Windows 3.1 or Windows 95. Here it is installing on my 25MHz COMPAQ Deskpro 386. 😉

https://archive.org/details/sb-16

#DOS #Retro #Tech #90s #90er #DOSGaming #PCGaming #Soundblaster #86Box #Emulation #Driver #Windows

After looking through several CD-ROMs, I guess I finallly found the best version of the Soundblaster 16 driver for DOS, Windows 3.1 or Windows 95. Here it is installing on my 25MHz COMPAQ Deskpro 386. 😉

https://archive.org/details/sb-16

#DOS #Retro #Tech #90s #90er #DOSGaming #PCGaming #Soundblaster #86Box #Emulation #Driver #Windows

#86Box Stream is live - and it's going to have hard disk sounds! https://www.youtube.com/watch?v=9EYc5tPoCyg #retrocomputing #retrotech

#86Box Stream is live - and it's going to have hard disk sounds! https://www.youtube.com/watch?v=9EYc5tPoCyg #retrocomputing #retrotech

#86Box Stream is live - and it's going to have hard disk sounds! https://www.youtube.com/watch?v=9EYc5tPoCyg #retrocomputing #retrotech

#86Box Stream is live - and it's going to have hard disk sounds! https://www.youtube.com/watch?v=9EYc5tPoCyg #retrocomputing #retrotech

Is anyone still familiar with this photo editing classic from 1997? "Kai's Photo Soap"... for Windows 95. I've had this as a young student back in the day... And I remember wasting a lot of expensive ink with my poor LPT1 ink-jet printer.

The CD-ROM runs great using 86Box. Pure nostalgia! 😍

P.S. Here's a link: Link: https://archive.org/details/kais_photo_soap_de

#RetroComputing #Windows95 #Win95 #PhotoEditing #90s #90er #Oldschool #CDROM #Retro #Tech #Emulation #86Box

Is anyone still familiar with this photo editing classic from 1997? "Kai's Photo Soap"... for Windows 95. I've had this as a young student back in the day... And I remember wasting a lot of expensive ink with my poor LPT1 ink-jet printer.

The CD-ROM runs great using 86Box. Pure nostalgia! 😍

P.S. Here's a link: Link: https://archive.org/details/kais_photo_soap_de

#RetroComputing #Windows95 #Win95 #PhotoEditing #90s #90er #Oldschool #CDROM #Retro #Tech #Emulation #86Box

Is anyone still familiar with this photo editing classic from 1997? "Kai's Photo Soap"... for Windows 95. I've had this as a young student back in the day... And I remember wasting a lot of expensive ink with my poor LPT1 ink-jet printer.

The CD-ROM runs great using 86Box. Pure nostalgia! 😍

P.S. Here's a link: Link: https://archive.org/details/kais_photo_soap_de

#RetroComputing #Windows95 #Win95 #PhotoEditing #90s #90er #Oldschool #CDROM #Retro #Tech #Emulation #86Box

Is anyone still familiar with this photo editing classic from 1997? "Kai's Photo Soap"... for Windows 95. I've had this as a young student back in the day... And I remember wasting a lot of expensive ink with my poor LPT1 ink-jet printer.

The CD-ROM runs great using 86Box. Pure nostalgia! 😍

P.S. Here's a link: Link: https://archive.org/details/kais_photo_soap_de

#RetroComputing #Windows95 #Win95 #PhotoEditing #90s #90er #Oldschool #CDROM #Retro #Tech #Emulation #86Box

Thanks to #WireGuard, my emulated Windows 98 machine just mounted its Samba share on my home server, which happens to be 1,500 km away right now.

#86box #retrocomputing

Thanks to #WireGuard, my emulated Windows 98 machine just mounted its Samba share on my home server, which happens to be 1,500 km away right now.

#86box #retrocomputing

Thanks to #WireGuard, my emulated Windows 98 machine just mounted its Samba share on my home server, which happens to be 1,500 km away right now.

#86box #retrocomputing

Thanks to #WireGuard, my emulated Windows 98 machine just mounted its Samba share on my home server, which happens to be 1,500 km away right now.

#86box #retrocomputing

Thanks to #WireGuard, my emulated Windows 98 machine just mounted its Samba share on my home server, which happens to be 1,500 km away right now.

#86box #retrocomputing

Ubuntu 6.06 Dapper Drake (Alpha 6) on 86Box with Socket 370 [1998]

We’re now back with the sixth alpha of Ubuntu 6.06 Dapper Drake, which was released on June 2006! Two months shy of the 20th anniversary of the first Ubuntu LTS release, we are very excited for this experiment on 86Box.

Our focus in this article is testing Ubuntu 6.06 Dapper Drake on an 86Box emulated machine with a Socket 370 [1998] motherboard. You can download it from here.

We’ve configured the virtual machine as follows:

We’ve configured a virtual machine to run with:

• Machine type: [1998] Socket 370
• Machine: [i440BX] ASUS CUBX
• CPU: Intel Celeron (Mendocino) @ 533 MHz
• Memory: 256 MB
• Video: [AGP] 3dfx Voodoo3 3000
• Keyboard: AT Keyboard
• Mouse: PS/2 Mouse
• Sound card: [ISA16] Gravis UltraSound
• Floppy disk controller: Internal device
• Hard disk controller 1: Internal device
• New hard disk: UbuntuDapper.vhd
  • C/H/S: 16644/16/63
  • Size: 8192 MB
  • Bus: IDE
  • Channel: 0:0
• CD-ROM drive 1: ATAPI (0:1) TOSHIBA CD-ROM XM-6702B 1007 (48x)

Once everything is configured as above, we can now start the virtual machine. Insert the Ubuntu 6.06 installation disc called ubuntu-6.06-alpha6-install-i386.iso to the CD-ROM reader, then configure BIOS as necessary.

You’ll see this main menu where we can choose to installer either to the hard disk, in OEM mode, or as a server. Let’s choose the first option, which is a normal install.

Afterwards, the old-fashioned installer that looks similar to what a Debian textual installer would look like appears.

After we have chosen a language, we are asked for our location.

Finally, the installer asks us for the keyboard layout we need to select.

As soon as we press ENTER, the installer starts looking for the Ubuntu installation disc and load additional installer components after searching for CD-ROM hardware.

After that, the installer tried to find the network adapter. Since we don’t intend to have one installed, because this system is unsupported as of long ago, we have answered No when the installer asked us if we have FireWire Ethernet.

After that, we’re prompted for the host name.

Then, the installer asked us if we need to provide proxy information for Ubuntu mirrors. We left it blank.

Afterwards, the installer started finding hard disks and starting the partitioner.

The installer found an 8 GB hard disk, so we’ve agreed to install Ubuntu to it by erasing the whole disk.

Afterwards, we’re prompted for the full name, the user name, and the password of the new account that our Ubuntu installation will contain.

The installation then started from this stage.

It took a considerable amount of time, especially when it had to do with installing and configuring the desktop packages. After a lot of patience, the installer finally set everything up in the new installation, such as users, and gave us a congratulatory message below.

When we pressed ENTER, the system automatically rebooted to the new Ubuntu installation.

Then, the login screen appeared.

We signed in with our username and password, and the GNOME splash screen appeared with “Dapper Drake!” drawn over it, with “THIS IS NOT THE FINAL ARTWORK!” at the top. Those two writings don’t appear in the final version of Ubuntu 6.06 LTS, suggesting that this is the pre-release version.

Once the desktop gets loaded, the desktop looks like this:

We can verify that this alpha version of Ubuntu 6.06 LTS uses Linux version 2.6.15.

Applications, such as Firefox and gedit, work, too.