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 ... 4 5 [6] 7 8 ... 320
76
SNAP works with UEFI after installation, so install with Panorama and then run setup.cmd from the ISO's SNAP directory. How well it will work with a modern computer and X600 card is unknown, at least to me.
CSM is legacy, if it is failing in CSM mode, I'd suspect that there is something missing from the ancient card that modern systems require.
If buying a card, try to get an ATI as they're a lot friendlier, things like custom resolutions.
One other idea, can you fiddle with the PCI settings in the BIOS? Mine allows changing it from X3 to X2 or X1 or similar, slowing it down might be a workaround.

77
General Discussion / Re: Reg article on CUA
« on: January 26, 2024, 06:56:11 pm »
An X86 CPU can be emulated so that it will run OS/2. But OS/2 exploits almost all HW features of that chip, in contrast to DOS and Windows-16 bit (DOS only runs in real mode and therefore all "protected mode only" instructions are irrelevant, it also only supports 16-bit segments/operand and address sizes). And that will make the emulation incredibly slow.

Lots of DOS programs run in 32 bit protected mode, from using DOS extenders such as DOSGW (sp?) to Win 3.x and even Win9x. Even in 16 bit mode, those prefixes for 32 bit are available.
Reading up on it a bit, there's otvdm, based on winevdm, https://github.com/otya128/winevdm for running 16 bit software on 64 bit Windows, which due to design decisions (64 bit handles) does not run 16 bit and even 32 bit needs WOW. It uses the X86 emulator from Mame IIRC and works well.
There's also DosBox-X which is actually capable of running Windows XP as well as Win2K, which runs OS/2 1.x binaries mostly fine. Graphical programs need the Presentation Manager kit.
These emulators could be extended to support Ring 2 etc. It also raises the question about if OS/2 is running Protect Only, does it need as much CPU support.
Anyways, it will be a while before the new architecture takes over and who knows what AMD will do. I note that AMD brought back segments on the 2nd release under 64 bit to make virtulizers work better.

78
General Discussion / Re: Reg article on CUA
« on: January 26, 2024, 06:27:47 pm »
Can you be clearer about "incredibly slow"? We are running 1990s programs on 2020s hardware. How slow could it be?

With a decent JIT compiler, it could be almost as fast as native speed once a program is running, depending on the program.

79
Try a legacy install. As the message says, the X600 is too old for UEFI.

80
General Discussion / Reg article on CUA
« on: January 25, 2024, 03:35:26 am »
Somewhat interesting article on the CUA at the Reg,
https://www.theregister.com/2024/01/24/rise_and_fall_of_cua/

81
Looks like it is a C99 thing, so the IBM compilers are too old.
https://en.cppreference.com/w/c/variadic/va_copy

82
Hardware / Re: The last nail in OS/2's coffin
« on: January 23, 2024, 05:42:16 pm »
Correct. Virtualization of OS/2 (and likewise: DOS and Windows 16-bit) will not be possible once x86-S is introduced. Only emulation will be possible (with a huge performance impact, of course).

This raises the question of how virtualization works currently with a 64 bit system running 16 bit code. My understanding is that in 64 bit mode, 16 bit software doesn't work.
As for emulation, with JIT compiler, performance can be pretty good. The PowerPC OS/2 was supposed to run DOS/WinOS2 well, as well as some versions of NT such as the Alpha port.
I doubt that anyone will actually do it but possible.

83
Hardware / Re: The last nail in OS/2's coffin
« on: January 22, 2024, 06:08:22 pm »
In theory, you could have a 286 emulator in ring -1 along with a program to take control when there was an illegal instruction trap and emulate the 16 bit instructions. Ring -1 is for hypervisors and such. The missing ring 2 and IOPL flag would be harder if even possible.
Not going to happen with the shortage of developers. Besides, in this 64bit world, hardware manufacturers no longer care about the lower 4GB's so what is happening, fractured memory leaving too little visible to 32 bit applications and the killer, the framebuffer being mapped above 4GB.
One thing is hardware lasts now, I just retired a 13 year old machine that was still running fine, just slow IO and a crappy EUFI. So there's another decade where OS/2 will run on older hardware. I doubt that I'll be around that long.

84
Programming / Re: CMake
« on: January 20, 2024, 07:31:42 pm »
Part of Qt, 5&6, I think the webengine. Paul might have the best port, here's one.
May be incomplete

85
Setup & Installation / Re: Are there any 8GB Nvme compatiable motherboard
« on: January 20, 2024, 06:48:56 pm »
What do you mean by the full 8GB's? OS/2 is limited to 4GB address space, minus PCI address space. So my system gives,
Code: [Select]
Total physical memory:      8,078 MB
Accessible to system:       3,502 MB
Additional (PAE) memory:    4,576 MB
which is as close as your likely to get for memory. It has an Nvme slot, actually 2 including one for wifi, plus 4 SATA ports (one is eSATA).
It's a Lenovo 910s, about 6 years old.

86
Programming / Re: CMake
« on: January 20, 2024, 04:49:33 pm »

87
Programming / Re: CMake
« on: January 20, 2024, 06:14:28 am »
Glad it worked for you, plus a different thing for Martin to play with.

88
Programming / Re: CMake
« on: January 19, 2024, 10:14:43 pm »
From @unixroot\usr\share\cmake\Modules\Platform\OS2.cmake
...
Code: [Select]
# With the TARGET_SHORT you can create a shorter name for the dll
#
# The 2 settings with OS2_DEF_EXE_ are for executables only.
# Usually the Stack value is not needed, so omit it please.
#
# if(OS2)
#   set_target_properties(<TARGET> PROPERTIES
#    OS2_DEF_VENDOR "whoever you are"
#    OS2_DEF_PATCH "${VERSION_PATCH}"
#    OS2_DEF_VERSION "${VERSION}"
#    TARGET_SHORT shortn
#    OS2_DEF_EXEType "WINDOWAPI"
#    OS2_DEF_EXEStack "STACKSIZE 0x8000")
# endif()
#
...
includes stuff for bldlevel.
Edit: Typo

89
Warpcentre is an option during install, IIRC, it has a different name then warpcenter.
You probably need to update Python for ANPM. IIRC, you need to update/install python2.7 and python3 in one shot by themselves, along with dependencies such as python3-libs. Close and open ANPM after.
In my experience and testing Dooble did pull in all the needed dependencies. Anything in popuplog.os2? @unixroot/var/log/app? May want to try starting it on a cmd line as "dooble 2>&1 | tee dooble.log and post the log.

90
Networking / Re: Updated Samba Client
« on: January 16, 2024, 01:14:36 am »
Yes, breaks symbolic links, don't use on @unixroot
Code: [Select]
[H:\tmp]SET LIBC_UNIX_EAS=!H
[H:\tmp]ln -s test.txt t.txt
ln: failed to create symbolic link 't.txt': Operation not supported on socket
Edit: ls -la also no longer see symbolic links,
Code: [Select]
lrwxrwxrwx 1 root root      8 Jan 15 16:13 t.txt -> test.txt
...
Code: [Select]
-rw-rw-rw- 1 root root      8 Jan 15 16:13 t.txt

Pages: 1 ... 4 5 [6] 7 8 ... 320