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] 4 5 ... 15
Multimedia / Re: Audigy 2 ZS Notebook
« on: August 31, 2020, 08:15:50 pm »
This information is interesting Martin. I will check for more details. Until now I was checked only the old archived The Notebook/2 Site

Jonas Buys had an updated version of that site

P.S. There was someone releasing updated versions of IBM's PCMCIA drivers and applications in the latter half of the noughties and distributing it from their homepage, but as I did not own a laptop at the time I did not have the presence of mind to download them and cannot remeber his name.

Multimedia / Re: Audigy 2 ZS Notebook
« on: August 29, 2020, 02:32:40 pm »
(based in Ricoh RL5C746)

I may be wrong, but this device is more likely to be an SD card reader, with nothing to do with PCMCIA.

Ricoh RL5C746 is an old PCMCIA interface chip not an USB/mass media interface, it is sufficiently generic to work with some even older Ricoh PCMCIA drivers on Windows so there is a possibility it will do the same on OS/2.

BTW, the Audigy ZS Notebook is basically the same card as the later Soundblaster X-Fi Cardbus card except for the mechanical interface, I have one of those but no OS/2 based computer with a Cardbus interface to test it on.

Programming / Re: Non-English programming questions - in English
« on: August 25, 2020, 05:06:27 pm »
When non-English speakers write programs, such as Rexx, SQL or C, what language do they write in?

For example in SQL - in English a query looks like

SELECT column1, column2 FROM thisTable WHERE someCondition ORDER BY column3

Does a Spanish speaker or German speaker write the same thing, or do they write the Spanish/German words for SELECT FROM WHERE and ORDER BY?

Likewise in Rexx, does everyone write DO UNTIL and SELECT , or do they write their own language equivalents?

IBM languages and the C class of languages in general were never fully localised, so they use English keywords but user generated input such as identifier names and so on may be in any language. A number of other languages especially those intended for end users rather than professionals such as BASIC, Comal, Pascal and LOGO are sometimes localised, LOGO in particular sees more use localised than in English. Some programming languages were originally in other natural languages and translated into English, so you may find code for PROLOG for instance in French and ALGOL was originally in German.

To make it more complicated some languages, in particular some database query systems and so on are partly localised, they use English keywords but defer to local conventions on number and word usage.

I tried that "mod" and now I get a blank screen(well I did delete the logo) and my hard disk light stays on forever.  This is NOT an upgrade I had MS-DOS 6 and Windows 3.1 on the Fat(I think it's Fat and NOT Fat32) drive before.(and FreeDos before that). This is a sort of eraish-appropriate laptop(IMB Thinkpad 380Z).

UPADTE#3: Turns out that "mod" is for version 4 and I have version 3, so that's no good.

That technique also works in W3 and in v2.1 for that matter, I replace boot disk drivers all the time, the reason I asked is that as shipped W3 only sees hard drives of a certain size, simply because it was originally shipped in 1994 and HD's did not go above a certain size back then. The most common disk related problem when installing old versions of OS/2 onto hardware more modern that the OS itself (even computers from 1996/7/8) is that the drivers refuse to operate the hard drive because the BIOS is reporting size numbers back to the OS that the driver/OS thinks are impossible.

To fix this you need to 1) modify the drivers on the boot diskette and 2) Instruct the installer to copy the drivers from the boot diskette over the drivers the installer copied from the CD or floppy onto the hard drive because the drivers contained on the CD/Floppy install image are the same as the original, so will have the same error. This can also be done by hand by booting the modified floppy again after install and going into the command line and manually copying the files onto the drive.

This is explained in some detail in the original link.

IBM used to supply replacement driver install diskettes with fixes from FP40, but that site has sadly been taken down, but they do have a replacement driver set at: but it should be noted that this is outdated and the original method is recommended.

My compute froze at "Loading system files. Please wait" after I told it to NOT reformat my C: drive. This is on real hardware and from floppies. What do you suggest I do?

is this after an install or an upgrade?

If so this could simply be outdated drivers loaded from the diskette, download and updated boot floppy and replace the drivers on the disk by the ones from the floppy, or roll your own boot disks as below:

BTW the boot floppy format is DOS FAT so it can be done from any system including Win10 or Linux with a USB floppy

Hardware / Re: Odroid H2+
« on: July 16, 2020, 07:54:25 pm »

However - it does have SATA ports in addition to NVMe.

You can also use SATA M.2 boards.

BTW ASRock makes mini ITX and mini DTX boards that almost all support BIOS emulation, although they are mostly sold by the consumer division as mini PC's such as , but their industrial division actually sells most of those as boards as well:

Turn to page 46 for a mini DTX board with some real power

a mini DTX board is the same with as a mini ITX board but a little longer

Internet / Re: Replacing the OS/2 URL object - DIY version...
« on: June 18, 2020, 08:50:59 pm »
Hi Andreas,

Without fully understanding your problem: You need to restore the .TYPE EA to UniformResourceLocator.

The core of my problem is that that NAS box does not support the approach you suggest, as much as I would love to do so will not work. I do appreciate your response though!

Problem solved, the WPS URL object recognizes filenames ending in '.URL' extension as URL objects, as such, a file re-name works!
What NAS box are you using? EA'support can be enabled in most of them ...

Motorola 68k was the only CPU similar to Intel.

!!??? M68k is similar to an early VAX, not a x86.

If you mean they are both CISC, and not RISC, HA or VLIW, there is a boatload of CISC architectures out there ...

Hardware / Re: Report: ArcaOS on Panasonic Toughbook CF-M34 MK1
« on: May 27, 2020, 12:12:43 am »
I suppose wifi is pointless anyway, as the standard is most likely not supported by any access point anymore? ; )
I can access my new AC2300 access point using the first ever Wi-Fi device to get OS/2 drivers, a Cisco pre-B card that I bought in the 90's, the router tries to hide the fact that it has WEP support and nags about security, but it works.

But anyhow the Intel 2100 shipped with the toughbook actually supports WPA so it should not be a problem with any router and you can still get G and even dual-band N spec mini-PCI cards new on eBay if you want to upgrade.

KDE seems to be heavily using Qt these days and maybe that is why they want to fork it.

KDE was based on QT even before QT became an open source project back in the 90's as it was the only generic OO C/C++ library available for Linux at the time, in fact the availability of QT was the inspiration for KDE. There is no realistic alternative for them, the whole shebang relies on QT and needs to be re-written from scratch if they want to get off it. A fork is also not a good idea long term.

This makes no difference to the OS/2 port, open source projects will continue to use the open source version of QT and commercial vendors are unlikely to target OS/2.

Storage / Re: How to make a disk drive for a distant computer
« on: March 20, 2020, 09:43:00 pm »
Or to simplify my last answer, the only other option I know is to send a raw partition or disk image file as there is a whole host of tools available for any OS that will write those to disk, with the caveat that Linux based and or Linux derived tools will usually write OS/2 partitions incorrectly to disk. Partitions must be copied in DOS/Windows style.

Storage / Re: How to make a disk drive for a distant computer
« on: March 20, 2020, 09:16:33 pm »
You have tried both sending a functional drive and an image previously? Or have you only sent an image?

I cannot really comment on this as I have never had any computer fail to boot from a DFSEE cloned drive that is within the boot specifications of the target computer in regards to disk size or geometry.

What occasionally happens is that if I send a partition image to a third party they will incorrectly copy the partition onto a drive with incorrect partition settings, the usual partition not marked active or bootable etc, incorrect alignment on an SSD etc.

I have solved this either by sending them a compressed disk image for a drive slightly smaller than the drive that is going to be used on the other end, rather than a partition image, this ensures that the partitions are written to the drive as found. The other option is to make them install Air-Boot as it can force boot the image regardless of it is partition settings.

The only other problems I have ever encountered are embedded BIOS's from a company called Insyde, used in Axiom industrial computers and 10Zig (Clientron) Thin Clients for instance. They both have incompatibilities with standard BIOSes when it comes to booting especially if they are used in conjunction with eMMC and also weird BIOS boot lockdowns intended to ensure you only use HDD's and software from the original supplier.

But as I said, I regularly clone OS/2 drives and partitions here for testing back and forth on hardware ranging from Cyrix based thin clients from the late 90's with tiny featureless embedded BIOSEs , to modern Xeon hardware with UEFI and never seem to have any problems going backwards and forwards regardless of hardware, with the obvious caveats about configuration setting.

There may be other options available, send them a VBox image converted to raw, transfer that to hd using rufus? YMMV but works for me with some caveats ...

Applications / Re: DOS VDM and Win-OS2 Fans ?
« on: March 18, 2020, 08:02:12 am »
Having worked on eCS, the fact seamless WIN/OS2 sessions do not work has been the case since eCS. The cause is VSVGA.SYS. It does not matter if you install SNAP, Panorama or GRADD they all use the same VSVGA.SYS driver. Its pretty complex driver VSVGA.SYS that relies on the VESA BIOS/VGA hardware. It just seems not all support in around that VSVGA.SYS is looking for.


Has nothing to do with eCS per se, it is simply a hardware issue, screen sizes have changed and the VSVGA driver has not been updated or re-written to comply with newer screen geometries. I can run DOS/Win sessions just fine here with eCS 2.1 but I have to choose a vintage screen geometry and have a screen that supports it, some NEC LCD's have excellent support for odd/vintage geometries, but they tend to be expensive.

VSVGA does support some high resolutions above UXGA (1600x1200), such as 3k for instance and possibly QSXGA (5:4) if I remember it correctly, but that is using geometries that are normally not supported on modern hardware. (IBM had a 3K screen for sale in the 90's, used for medical research etc., it had Win, AIX and OS/2 drivers.)

Hardware / Re: OS/2 and the Mainframe
« on: March 10, 2020, 06:27:17 pm »
Regarding earlier post
Early Unisys SCAMP on a card here:

People forget how much OS/2 support there was by Unisys

Some info on SCAMP, but with lots of factually incorrect information:

Hardware / Re: OS/2 and the Mainframe
« on: March 10, 2020, 01:08:40 am »
There was also a Unisys "Clearpath on a Card" that worked with OS/2 v1x

Pages: 1 2 [3] 4 5 ... 15