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 ... 363
1
Virtualization / Re: Win-OS/2 - Open vbesvga.drv video driver
« on: June 22, 2025, 12:35:33 am »
One thing I discovered was that the X VESA driver failed on a UEFI install, to quote myself.
Code: [Select]
So out of curiosity, I tried opening a VESA xsession on a UEFI install. It failed, this seems to be the problem,
...
(EE) VESA(0): V_BIOS address 0x98000 out of range
...
On a BIOS install, it succeeds with,
...
(II) VESA(0): Primary V_BIOS segment is: 0xc000

Developer answered,

Code: [Select]
   BIOS at C000 can only be emulated in VDM. XFree86 definitely uses a
mini-VDM that lacks any functionality. "VGA BIOS" at 9xxx is an emulation
for system boot time and for panorama/gengradd.

So possibly the fact that the VGA BIOS is at a non-standard location on a UEFI install.

I also discovered that the changes that were made to SNAP broke the X VESA driver subtly, namely system hung when returning to the PM from X.
Another interesting discovery when reviewing the X source code was that X actually uses the SNAP code for its mini-VDM.

2
Games / Re: Revisiting some Flash Games
« on: June 19, 2025, 03:05:34 am »
My Odin install was broken. Reinstalled and the games eun

3
Games / Re: Revisiting some Flash Games
« on: June 18, 2025, 06:04:52 pm »
I tried these, nothing happened, possibly due to never having the Flash plugin installed here.
Bitwise simply wrapped the Win32 Flash plugin in an Odin wrapper so it is possible you have a Flash.exe or such installed somewhere.

4
Games / Re: OS/2 - ArcaOS - Native Games
« on: June 18, 2025, 01:39:15 am »
Hi Martin, tried building it, make seems to get into a loop early on, one core at 100% and after a while the system locks up. Not sure how to proceed.

5
The dani driver supports quite a few SATA drivers and he installed AOS 5.0 which, IIRC, didn't have os2ahci.add.
I'd still like to know how he copied the system over.
Shadow, OS/2 is very particular about the HD layout, partitions have to be aligned on a cylinder boundary and newer systems need the LVM info on the MBR/EBR as well. Basically you have to use OS/2 tools like LVM.EXE to partition the system and assign a drive letter. Then the simplest is to use xcopy /h /o /t /s /e /r /v D:\* C:\ or similar. need all those parameters to copy everything. You ca n use lvm or lvmgui to set and change drive letters. You need to end up with the same drive letter that you installed to, often C:

6
The convenience packs didn't have acpi.psd and didn't support SMP IIRC. He does have AOS 5.0 working which probably has acpi.psd.

7
What about binary vs text? Often in C have to purposely set the pipe to binary, though for sending sending commands to a program it shouldn't matter.

8
Another question. Did you simply move your HD from one system to the other of did you try copying the system to a new drive? If you copied it, how did you copy it? Either way, is the drive letter the same? OS/2 really doesn't like the drive letter changing and copying the system over has to be done correctly to copy everything including meta-data.

9
I've moved OS/2 installs to different computers many times. It usually mostly works though during boot there would be messages about a driver not loading, push enter to continue type of thing, usually the network adapter. Then these can be fixed.
You say you have AOS working on your device so most BIOS settings should be correct.
Boot AOS, do,
Code: [Select]
COPY IBMS506$ con:
or
Code: [Select]
COPY IBMS506$ anyfile
and post the output

10
Example 1: "SysFileTree" was unthinkable to me to use to find or search for files when I begun to try Rexx, the function should have been named SysSearchPath, SysFindFile or something along those lines, not "...Tree", totally bonkers name.

When sub-directories were first introduced, they were often described as a tree. The root (directory), branches or stems (sub-directories) and leaves (files). There were even commands such as deltree to delete multiple sub-directories in a branch.

11
Programming / Re: Qt6 Development
« on: June 10, 2025, 12:11:17 am »
Qt5 and Qt6 can coeexist fine. My comment on DLL hell was more for mixing versions of Qt6..

There will be some binaries that will take care, one example is qmake.
Code: [Select]
L:\qt6-6.2.x\bin>which2 -a qmake*
./qmake.exe (also ./qmake6.exe, ./qmake.exe, ./qmake6.exe,
 w:/usr/bin/qmake-qt5.dbg, w:/usr/bin/qmake-qt5.exe, w:/usr/bin/qmake-qt5.sh,
 w:/usr/bin/qmake.exe, w:/usr/bin/qmake-qt5.exe, w:/usr/bin/qmake.exe) 10

Code: [Select]
L:\qt6-6.2.x>qmake --version
QMake version 2.01a
Using Qt version 4.7.3 in W:\usr\lib

12
General Advertisements / Re: New Lenovo Tower Computer
« on: June 09, 2025, 11:56:39 pm »
The computer features 20 processing cores with hypertheading turned off.

Should be noted that it is a mix of 8 P (performance) and 12 E (economy) cores, which makes testlog report,
Code: [Select]
----- Configuration Check ------------------------------------------------------
More CPUs (20) than cores (14) detected.
HyperThreading/SMT can cause problems for OS/2 systems.

It's interesting that our ancient simple scheduler seems to be OK with it.
Edit: fix typo

13
For danis506, simply copy the DaniS506.ADD file to \os2\boot and change config.sys to rem out the IBM1S506.ADD and add the daniS506.ADD like
Code: [Select]
REM BASEDEV=IBM1S506.ADD
basedev=daniS506.ADD
Perhaps look at your AOS config.sys for any extra parameters for daniS505.add. They generally aren't needed but sometimes are.
I think you can copy the printer software over and it will work depending on whether it was expected to be installed. Look at config.sys for any entries related to the printer software. Others know the printing subsystem better then I do.

14
Have you a business case for using OS/2? You might want to upgrade to AOS, an OEM version of OS/2. https://www.arcanoae.com where you will get support as well as the latest drivers etc.

15
Internet / Re: Dooble releases-Qt6
« on: June 08, 2025, 12:10:12 am »
I really don't think the Available virtual memory is accurate as it seems to bounce all over the place. Here with Dooble and SM running, I get close to the same value as Neil.
Code: [Select]
Total physical memory:     16,270 MB
Accessible to system:       3,502 MB
Additional (PAE) memory:   12,768 MB

Resident memory:              180 MB
Available virtual memory:   1,443 MB

Available process memory:
  Private low memory:         306 MB
  Private high memory:      1,956 MB
  Shared low memory:          220 MB
  Shared high memory:          99 MB

I would suggest having a much larger starting value for the swap file to avoid the overhead of growing it, perhaps 1.5 GB and also keep an eye on it. Back in the day I had a system with 1.5GB's of ram, linking xul.dll needed VIRTUALADDRESSLIMIT=3072 or wlink would run out of memory. I had to be careful not to overflow the swap file as the system would die with a swap file full error once the swap file grew to about 2GB. It was on JFS but I assume internally OS/2 uses signed 32 bit variables. I'm sure back in the early 90's it was never expected to use so much memory and/or swap.

Pages: [1] 2 3 ... 363