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 ... 13
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

Marketplace / Re: ebay Stuff
« on: March 03, 2020, 01:28:41 pm »
Business cards and whatnot shapes were around. Fortunately this madness didn't last long. Some bands released some music on these, but mostly just novelty items that were not meant for use :D

Business card CD's are still a thing

They will survive a high speed drive unlike some of the more interesting shapes did, not to mention thin walled DVD-RW's that exploded if you tried to write to them at high speeds

Marketplace / Re: ebay Stuff
« on: March 01, 2020, 10:06:36 am »
It is the first time I see a "Software Choice" box. I guess it is in Japanese or Chinese, but I haven't even saw this one in English.

It is in Japanese, Chinese would be in simplified Chinese characters only, this is a mix of Kanji (Traditional Chinese characters) , rĊmaji and katakana, which are unique to Japanese.

Web applications / Re: FF 45.x and VIRTUALADDRESSLIMIT setting...
« on: February 25, 2020, 09:16:53 pm »
I only remember that I read on some gamers forum that Bulldozer even performs slightly better with only one core per unit active. In practice I can say that using 4 cores instead of 8 on my Bulldozer type of CPU makes close to no difference (Windows is busy rotating the hard disk and OS/2 is busy on choking and scheduling on that many cores).
That tells you how insanely good the AMD marketing is.

I cannot speak for your setup, but on mine performance degrades on both eCS and windows if I disable the secondary cores this is especially noticeable in Win10-64, and on well multithreaded tasks such as as OCR the difference is striking, over 40%. And citing games benchmarks that do limited multithreading, and no application to OS/2 is odd.

My point still stands, AMD cores do real work, Hypercores do not, and in fact they mess timing up if you use any sort of application or drivers that require RT response.

The second point is that people on here are advising someone that has a computer that has neither Hyperthreading nor CMT, to adjust his CMT settings in response to a problem. If you lot fail to see the stupidity there, then there is little hope of seeing it elsewhere ...

Web applications / Re: FF 45.x and VIRTUALADDRESSLIMIT setting...
« on: February 25, 2020, 01:32:17 pm »
Have you ever tried to reduce your number of cores to one core per package/unit ? The BIOS should allow this and I would expect that fixes your stability problems. That will leave you with 3 cores which is no loss, really. At least the Bulldozer architecture is offering miserable performance gain from the "hyperthreading" (AMD names this differently but it is the same thing). There are just too many HW components being shared amongst two cores of a common package/unit or whatever they call it.

He uses a Phenom II X6 with 6 full Int/FPU cores, no hyperthreading in sight. PII X6 is not a Bulldozer but a K10 architecture, and Ryzen has hyperthreading while Bulldozer has not but rather CMT (Clustered Multi Threading) where the secondary core does not have a FPU unit so some tasks are not assigned to the secondary core, but it is still a full core rather than the fake core hyperthreading offers, e.g. a 6x Bulldozer core has 6 integer units but only 3 floating point ones. That people believe that CMT is the same as Hyperthreading just tells you how insanely good the Intel marketing division is.

Programming / Re: Trim command
« on: January 28, 2020, 10:24:29 pm »
Maybe trimming support was introduced in NTFS and FAT32 with later WinXP service packs?
You cannot trim if you don't know what sectors are used or not.
It was introduced in a Vista service pack, and initially at the least only for NTFS, no idea if it is supported in xFATx by MS. It is still a manual process on NFTS by the way, the OS does not trim the drive unless you ask it.

P.S. It is not just SSD's, shingled hard drives from WD and Toshiba also support the Trim command, makes sense on a shingled drive if you think about it. The WD shingled drives are usually large "archive" drives, while Toshiba shingled drives are usually small budget 2.5 external drives.

Programming / Re: Trim command
« on: January 28, 2020, 12:39:34 pm »
If a tool is used,then the FS will still need explicit support for trimming (knowing or finding the blocks to trim).

No, witness the WinXP era NTFS/FAT32 TRIM tools supplied by the likes of Samsung

Pages: [1] 2 3 ... 13