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 - Dave Yeo

Pages: 1 2 [3] 4 5 ... 318
Hardware / Re: OpenWatcom Discussion
« on: February 02, 2024, 04:23:04 am »
So Jiri has two github repositories? Reading the newsgroup, I see his announcement on 07/30/12 and then Lynn posting on 02/13/14 "The Open Watcom unofficial fork project has its
own version 2.0 now", to quote Jiri further down the thread,
Initial base is at change 37426 (OW 1.9).
All important changes after 37426 were aplied to V2 fork.
Some changes were not included because they are problematic or introduce
some problem.

Anyway V2 fork is too different from Perforce now that back nerge to OW 1.9
has no much sense.
I think that oficial OW is now realy dead.

Now I have to restart SeaMonkey as it is not happy after downloading the 13.5K headers that were on the news server, openwatcom contributers.
Actually, should I download all the bodies and make them available somewhere, I have access to the other newsgroups that were carried on the Open Watcom news server as well, back to around 2005.

Hardware / OpenWatcom Discussion
« on: February 01, 2024, 08:11:36 am »
....One version of Watcom being incompatible with the next and unfortunately picking the "official" version does not help because it is the one that is buggy.

Where are you getting an official version of OW? Last was 1.9 and there are betas on netlabs that seem as compatible with that as any.
There is Jiri's fork, I doubt that he tests OS/2.

Hardware / Re: The last nail in OS/2's coffin
« on: January 31, 2024, 07:41:20 am »
That's why I mentioned systemd. Consider my phone and the majority in the world. Sure I can download the source code for the Linux kernel in my phone, what can I do with it? It's not like I have root and while my particular phone has instructions for rooting, unlike many, the kernel is still locked down by being signed and interacts with binary blobs.
Also consider IBM owned RedHat, you have to sign a contract to get access to the source, including the kernel which is likely patched.

I have rEFInd setup here to boot to my legacy MBR SSD (and then airboot comes up) as well as my UEFI M2, it'll even boot the install stick in legacy mode allowing me to do a legacy install while in UEFI mode.
Much easier then using the F12 boot menu or going into the BIOS to change boot order.
Search for rEFInd on the main forum page.

Hardware / Re: The last nail in OS/2's coffin
« on: January 30, 2024, 04:18:15 pm »

I hope for that. But I still have the itchiness that we should try what the Linux community accomplished. By being open source they are vendor free, they do not longer need IBM, Microsoft or anyone else to keep updating their OS. Distributions comes and goes for them, but the source code is always there to create, modify and expand their OS. Being more open source will allow us to reduce our issues with hardware changes, we will have something to reuse and update.

Well, Microsoft and IBM are the top committers to the Linux kernel. Then there's systemd.

Applications / Re: AcpiDaemon start
« on: January 30, 2024, 04:18:14 am »
It says "version 3 and lower", Warp was version 3. Wouldn't be surprised if FP17changed that as it had the SIQ fix in it.

It seems in your case, the X1 etc is the number of lanes. I'm a little surprised you have such good results with only one lane. I guess you have a M:2 SSD so can't try the 4 lane slot, which might work and be faster.
Anyways, if you are happy with the performance, you have a satisfactory workaround.
As for the testlog, one taken from the working install is better then nothing, it will show the hardware. Probably want to use the newest testlog, and comment on how you created it along with why. Remember it is only accurate on the first run after a boot.

Good modern video card where the BIOS supports 4K and a Display Port connector for 60 Hz, HDMI for 30 Hz. Need lots of bandwidth. See

Applications / Re: Mouse chording in OS/2
« on: January 29, 2024, 12:22:14 am »
It has always worked for me as well, excepting the cut part, testing, it seems to work the same as copy.
Open E and test, or even a cmd prompt, where I think you need Mouse Actions active, click on the icon in the upper left of cmd to check if active.

Applications / Re: David's Doodles
« on: January 28, 2024, 07:29:14 pm »
Paul's Qt6 builds of Dooble still work at Github, the Qt5 ones mostly did until recently when the code stopped rendering. There are issues but it is usable by mousing over the odd element that doesn't display.

General Discussion / Re: Hobbes Retirement
« on: January 28, 2024, 07:17:17 pm »
I have decided to cancel work on that mirror as Nathan went ahead.

Who is "Nathan"?  And why would you (or any of us) care what "Nathan" is doing?

Nathan Woodruff, Long discussion on

Hi Doug, as Pete says, the warning can be taken with a large grain of salt. Still reading your MB manual wasn't inspiring. It did hint at boot options, crappy manual didn't go into specifics, you need legacy boot if you want to enjoy your X600.
You may well have to return the MB, with ones that support legacy boot with CSM getting rare.
Testlog explained here, scroll down to the various testlog sections. You are probably are fine with the testlog that came with 5.1. Attach it to your ticket as that is the first thing you will be asked for, I almost did but there are way more knowledgeable people to advise.

I have had a couple of those MSI boards and never had anything but trouble with them wehen it came to installing ARCA OS. Personally I settled with a ASUS TUF GAMING X670E-PLUS WIFI. Works great.

I notice that the manual says,
Code: [Select]
Incompatible UEFI cases
∙ 32-bit Windows operating system - this motherboard supports only Windows 10
64-bit operating system.
∙ Older graphics card - the system will detect your graphics card. When display a
warning message There is no GOP (Graphics Output protocol) support detected in
this graphics code

The lack of support for 32 bit Windows does not look promising.

@Pete, it simply is too old for UEFI.
Looks like, on page 43 of the manual, you can set CSM boot mode in the BIOS mode page when first entering the BIOS, it's at the top of the screen. You also will need a MBR partitioned disk,
Code: [Select]
CPU Temperature:
Motherboard Temperature:
DDR Voltage:
CSM boot mode

Unluckily, UEFI, or at least the way it works with OS/2, custom resolutions do not work. Newer graphics card or figure out if a legacy boot is possible on your MB. I'll look at your manual.
BTW, add a testlog generic to your ticket.

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