- #Ibm os 2 warp 3 iso download install#
- #Ibm os 2 warp 3 iso download software#
- #Ibm os 2 warp 3 iso download windows#
Add this to registry, and ye will get non-default right-clicks for HLP and INF files, to look at them in Windows.OS/2 Multi-Bootable Recovery Live CD Project alternately, for iview There are three files, that need to be in the path.
#Ibm os 2 warp 3 iso download software#
HLP and INF files: Look at, eg under software | win32 and look down the list for an INF viewer for win32. If you want to look at os/2 logos, icons, bitmaps (including multipage ones), etc under windows, get a hold of a program hight PMVIEW from. Set the desired partition to 'installable'. Use the one from 2.11 (google for "oldfdisk" finds it readily. OS/2 fdisk for modern hardware seems a little too restrictive. (along with the usual three.), Opening up os2image\disk_1\os2logo reveals the OS/2 Warp wave logo. The version of OS/2 3.1 gives a cd label LANCLNT, with directories like ASKPSP, GRPWARE, NETWARE, NSC, MMPM2 and CID. The version of OS/2 3.0 gives a cd label OS_2_CDROM, with the usual three directories (diskimage, mmpm2, os2image) When i open os2logo, it's the white square one Directory dates are 1994.10.10 It was mainly used because the bulk of the hard drive can be seen, (1 gb when bios supported 504mb), and the cdrom software was an os/2 proggie hight "Gear for OS/2"
#Ibm os 2 warp 3 iso download windows#
Anothe reason for buying the WinOS2 versions is that IBM and Microsoft were becoming increasingly different to each other, eg the changes in Windows 3.11 from 3.10 included things to prevent it running under OS/2.Īlso, unlike 2.x, vers 3.1 and later used a lot of resources for an unconnected 486 with 20 MB ram.
This is because i believe that IBM's recompile of Windows was better than Microsoft's, and much of the utilities was dragged back over MSFT's. The versions i have are cdroms of the OS/2 with Win-OS/2. OS/2 v 3 (Warp) and v 3.1 (Warp Connect). Is there a "red" version that isn't Connect? And do you have that one too?. OS/2 Warp 3 (Blue) - floppy edition already on the FTP. OS/2 Warp 3 Connect (Blue) - the one you sent up And you seem quite resourceful and knowledgeable of OS/2.
So my questions are, is there a non-connect version that matches the floppy version on the FTP, and do you have it? I am just trying to fetch every possible version of OS/2. The release you uploaded is not the same as the floppy version on the FTP. The wavy Warp logo is only for the "Connect" editions while the other one is for non-Connect. It still shows the "wavy" Warp logo and not the right one I posted.
I extracted the floppy images from the disc and booted it up.
#Ibm os 2 warp 3 iso download install#
I tested the release you uploaded, it wouldn't install in vmware (it went through the installer but apparently didn't make the harddrive bootable, weird thing).īut I did notice something that I need some explanation with, since I can't understand it. Thanks for the info, if you have any versions not present on BA then please send it up, OS/2 stuff is hard enough to get and if there are more variants of the OS:es then we need to collect them all. It wasn't until this bug featured in no less a journal than WSJ (apparently a money market paper), that MSFT belatedly released a fix. The calculator, for example, was not affected by the 3.11-3.10=0.00 bug. I mainly had the OS/2 blue box version, except for an illadvised redbox 2.1, because its version of the Windows 3.1 stuff was better than microsoft's ones. The same picture turns up in \os2\bitmap\os2logo.bmp, this is the only bitmap different between the two versions. The wavy logo comes from OS/2 3.1, or "Warp Connect". The white box logo is for OS/2 Warp, identifying as 3.0 by TCMDOS2 (gui 4os2). Both of my versions were the blue-box or WinOS2 versions. Os2fan2 wrote:I have used both of these operating systems as my primary 32-bit OS at stages.
0 kommentar(er)
