Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Olafur Gunnlaugsson

Pages: [1] 2 3 ... 15
Setup & Installation / Re: Quick question about boot manager
« on: January 08, 2022, 05:08:23 pm »
I want to setup a replacement computer system with multiple operating systems on it.

I have learned that the boot manager that comes with ArcaOS is useless on any of my AMD Ryzen based systems - it does not display any of the menus so it is impossible to select an OS.

Before I start this project I would like to know if anyone is using the old OS/2 boot manager in such a situation.  I know the primary partition limitations and since I only want three operating systems on this new system (Boot Manager, OS/2(ArcaOS), Linux Mint and Win7).  There will be several hard disks - the number will depend on how well the system will work.

The reason for this is because I am fedup with having 5 or more computers running at the same time all feeding into a KVM switch and two monitors, also on a HHDMI switch.

Any information and comments?  Thanks in advance.

I used the boot manager built into Windows 8 to boot into OS/2 and other OS's, a few years back. I have not tried it with Win 10 as I simply use the EFI/BIOS emulator switch built into the UEFI firmware to switch between two disks, one with GPT and one with MBR.

Web applications / Re: The MicroWeb DOS web browser
« on: January 08, 2022, 03:53:20 pm »
It is possible to run DOS packet drivers in a DOS session if you disable the DOS/2 networking, but not recommended, FTP Software (the company) also sold a TCP/IP stack for OS/2 that had a VDD that allowed DOS sessions to use DOS packets via emulation, but alas that is impossible to get hold of these days. The Essex Systems stack also had some VDD trickery, but I cannot remember it it supported the FTPS packets specification.

Is it true these older OS/2 TCP/IP and NetBIOS over TCP implementations used proprietary APIs which limited their use to only the network applications/services that were distributed with these packages?

The stacks were mostly compatible when using the same protocols, the low level or packet interfaces on OS/2 1.x varied from provider to provider however, for OS/2 2x this matterred less since NDIS was provided as standard and most stacks just layered on top of that (NDIS was available for 1.x, but not supplied as standard, except possibly with 1.3).

Web applications / Re: The MicroWeb DOS web browser
« on: January 08, 2022, 03:46:34 pm »

So, I need to  find the documentation inside the  "IBM TCP/IP for DOS 2.1.1 Programmer's Toolkit".

On the "IBM TCP/IP VERSION 2.0 FOR OS/2" announcement there are some references to something called "DOS/Windows Access Kit"

DOS/WINDOWS ACCESS KIT:  This facility allows DOS applications written to the IBM TCP/IP for DOS Version 2.1 programming interfaces, and Windows applications written to the Windows Sockets API Version 1.0 or Version 1.1 specifications to run in an OS/2 environment on top of IBM TCP/IP Version 2.0 for OS/2.  This product requires the customer to have the OS/2 Version 2.1 operating system installed.

I'm still trying to find something on a package of TCP/IP 2.0 for OS/2, but I still haven't find that documentation.


The OS/2-DOS TCP/IP interface is basically WINSOCK

Web applications / Re: The MicroWeb DOS web browser
« on: January 05, 2022, 02:27:38 am »
VDOSTCP.SYS emulates a Windows TCP/IP stack interface, MicroWeb uses a DOS TCP/IP stack (mTCP) that relies on DOS packet drivers, which are different to the Windows packet drivers, they are a bit more like early Unix an Linux packet drivers. It might be possible to configure the program to use the native stack .

It is possible to run DOS packet drivers in a DOS session if you disable the DOS/2 networking, but not recommended, FTP Software (the company) also sold a TCP/IP stack for OS/2 that had a VDD that allowed DOS sessions to use DOS packets via emulation, but alas that is impossible to get hold of these days. The Essex Systems stack also had some VDD trickery, but I cannot remember it it supported the FTPS packets specification.

You can also try the Archane browser, it used to work with Windows sockets/packets in an OS/2 DOS window, it saw some updates in the last two years.

Multimedia / Re: Updated Uniaud32 build
« on: October 25, 2021, 07:06:40 am »
Thanks for the heads up.
FYI, Here it is the link:


Is there a parsing bug in the forum software? The link shows up correctly as
However the actual link is ftp// i.e., the : is dropped

Utilities / Re: MultiUser support for OS/2
« on: October 15, 2021, 02:42:43 am »
Hi Martin

No idea if DeskMan/2 is still available

You can toy around with a slightly older version here:

Applications / Re: Time sync in VirtualBox guest off by 1 hour
« on: July 18, 2021, 10:15:16 am »

OS/2 doesn't adjust to daylight saving time anyway. Of course, I can set daytime (if I run it) to take DST into account, but I wasn't running daytime while using the additions.

Mine does, what am I doing right?

Applications / Re: Time sync in VirtualBox guest off by 1 hour
« on: July 16, 2021, 11:26:54 am »
The VM reads and presents the system time as the host operating system presents it, this means that when you install a guest system you should always instruct the guest operating system not to adjust to daylight savings time, and not to use internet time correction/lookup. It is getting the correct time from the host anyway.

Otherwise both the systems will correct themselves during DST changeovers.

Setup & Installation / Re: OS2 Warp 4.52 "vdi2hardware" result
« on: June 06, 2021, 03:07:41 pm »
I have done this for zonks, I believe there was a small article on the eComStation Facebook page that I wrote on the subject ca 2011, that was removed by Facebook when they changed the rules on article and file permissions when they split groups into groups and pages. I never bothered restoring it elsewhere since no-one ever showed any interest in the technique anyway, just like there was no interest in running OS/2 in a Hyper-V container.

Although in general it is very helpful, there are a few issues doing this, while VB etc. are highly compatible with real hardware there are edge cases of incompatibility, you can end up with an image that boots on VB but not on real hardware and vise versa. It can sometimes by tricky to place an image onto a drive correctly especially if you have multiple partitions and boot drives, for those cases investing in DFSee becomes an absolute must, alignment issues are frequent with any sort of solid state media for instance. The weird behavior of the VirtualBox image manager in recent versions can make maintaining a large  number of VBox images and copies a real pain (unlike VirtualPC, VBox registers (and re-registers) each image into a database). Each version of VBox introduces a new collection of bugs which can throw a spanner into the works, these get fixed eventually but OS/2 is not high upon their priority list (and they are downright hostile to ArcaOS), not a huge issue with images but this makes install in-place frequently impossible on modern VBox which was relatively easy on older VBox versions. In-Place installs were extremely convenient since you could remount the drive on VBox in you had any problems on real hardware. On older versions of OS/2 getting data onto the virtual machine can in some cases be much more time consuming than on real hardware, weirdly enough. etc etc etc

I only really use this technique these days for when installing "legacy" versions of the system, that means I do not have to bother with floppies and I can get the system into a fixpack state that will actually run on the hardware (memory & disk size & driver issues etc). Apart from that and for the fact that I already have a large collection of ready made VBox images, I am not altogether sure I would use the technique except for installing onto systems that run on consumer solid state media eg. embedded systems with SDCards, thin clients with Compact Flash drives or old IDE PC's with CF adapters. In those cases it is very quick, just plonk a converted VBox image onto start of the SD drive and then create other partitions as needed from the install.

I am currently setting up a couple of old VIA C3 systems for compatibility testing, basically each system has 2 or 3 "legacy" Windows installs on primary partitions and a host of various "common" OS/2 versions in an extended partitions. I had intended to convert and copy already made basic installs from VBox onto the extended partition but in the end it actually made more sense time wise to buy a floppy emulator off eBay, load it with a large collection of OS/2 installer floppy images and install from there.

Using PCE rather than VirtualBox also has some advantages since Windows can mount the PCE images directly, you can load software onto the PCE image that contains a windows readable partition type directly from the file manager or folder. It also has a better hardware compatibility in some cases.

And remember you can also go the other way round, DFSee can easily convert your existing OS/2 installs into VBox images.

Hardware / Re: IBM Thinkpad with floppy drive
« on: May 26, 2021, 08:42:47 am »
As far as an UltraBay Floppy that can be swapped in place of the CD drive, I think the T540p series is the last one.

I thought the ultrabay 2000 was the last ultrabay that was hooked up to the legacy controller, was there an internal floppy drive available for the 540?

Hardware / Re: IBM Thinkpad with floppy drive
« on: May 25, 2021, 12:12:00 pm »
What is the latest model of thinkpad with integrated floppy drive ?
Thank you.
IBM stopped supplying floppie drives as standard back in the 90's, they replaced them with "Ultrabay" a hot swappable slot that can take CD-ROM's, floppies or batteries etc., depending on need. I think the last Thinkpad series that came standard with a floppy were some of the 300 series (486 era), AFAIK all the newer models had the floppy drives as Ultrabay options, the last models that could take an Ultrabay with an internal Floppy (Ultrabay 2000) were the T2x series and the A3x series.

Programming / Re: Installing Prominaire Designer
« on: April 30, 2021, 11:44:53 am »
You can try downloading the demo version, from the publishers old web page on the Internet Archive if it is not on one of the FTP sites, install it and then installing your archive over that.

Hardware / Re: Hardware Wiki report
« on: March 28, 2021, 08:26:08 pm »
Some USB audio devices were also tested, all with the same hardwareID: 8086:0808
Fairly certain this is the default HiD for the C-Media CM108 USB codec

Multimedia / Re: Updated Uniaud32 build
« on: March 21, 2021, 11:59:01 am »

  Thanks for the head's-up... it is working well here. One thing I notice - with your build on my machine, the driver uses IRQ16, but David A's version uses IRQ55. Does he add some secret sauce for that? Is there an advantage to a higher IRQ?

Yes, in that AT compatibles had 15 interrupts available while early APIC based system had 24 interrupts, with the extra 9 interrupt lines being handled dynamically in a way that could cause problems with certain drivers and hardware, in some cases drivers either did not see any interrupt above 15 or saw any interrupt above 15 a IRQ16 even though the hardware itself supported higher IRQ's. Modern MSI based APIC systems have 224 interrupt lines available, BTW.

A number of old OS/2 drivers will only work correctly with interrupts <16 or <25 and a number of them showing problems with IRQ's higher than 15. While sharing an interrupt is possible both from a hardware and software perspective it can have side effects both on the software side and with the hardware itself such as the interrupt switching modulating the analogue gain stages on a soundcard or a video card with analogue (VGA) outputs. And there are some other issues, drivers like the old Martox ones being quite aggressive in claiming interrupts, clashing with other dirvers and sometimes with the OS itself.

By moving as much of the modern drivers/hardware to interrupts higher than 24 you are simply leaving more space free to legacy drivers and hardware to play with, so to speak, minimising the possibility of software/hardware clashes.

Pages: [1] 2 3 ... 15