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 - Roderick Klein

Pages: [1] 2 3 ... 49
1
Virtualization / Re: Win-OS/2 - Open vbesvga.drv video driver
« on: June 22, 2025, 01:07:25 am »
Oh, it works here, too!

Edit: Here is DBCS, Korean.

Are you running a UEFI boot of ArcaOS or in BIOS mode ? When WIN/OS2 did not work, what did not work ?

Thanks.

Roderick

2
Virtualization / Re: Win-OS/2 - Open vbesvga.drv video driver
« on: June 22, 2025, 01:04:37 am »
Hi Roderick,

  Would you have any insight into why this driver doesn't work with EFI? I would report to the developer, but don't want to just say 'It doesn't work'...

Regards,

I do not know. While I can understand people want to try other Windows 3.1 drivers. My first response is to no try the this VESA based Windows 3.1 driver with UEFI support.
The UEFI support indeed has a very very minimal VESA BIOS. Most of the support for this lives in VEFI.SYS.
I think you can get high resolutions with the Windows 3.1 driver from IBM.  This driver best I understand simply does not lean on the VESA BIOS.

Roderick

3
Virtualization / Re: Win-OS/2 - Open vbesvga.drv video driver
« on: June 21, 2025, 11:04:26 pm »
Thanks Martin. I don't get a hang, it just doesn't even seem to do anything.

 One thing I noticed I hadn't before - there are new WinOS2 settings for VEFI. Looks like they are probably mostly DOS oriented, but not clear...

Regards,

These settings do not influence WIN/OS2.

Roderick

4
Internet / Re: Dooble releases-Qt6
« on: June 08, 2025, 12:21:43 am »
Neil,

  I have never seen a mem /v result where the available high process memory is HIGHER than the available virtual memory. Like Steven says, that seems not right. Do you have all settings in your BIOS that reference 'Above 4GB...' turned off?

Also - what motherboard are you using? A testlog file might also be helpful...

Regards,


Just to be clear that has influence on the total amount of memory. This setting has todo with PCI MMIO regions that are will be remapped when booting ArcaOS in BIOS mode or in UEFI mode. It should not have an effect on the amount of memory you have. Or does it ?

Roderick

5
What might be a better option would be a kind of XP Mode, like in Windows 7. A lean and fast virtual environment for running a modern browser. And as if that weren't dreamy enough, perhaps even seamless on the WPS.

It can work, however the big issue is that if you look how much memory the VM needs, plus the memory to run the OS + the browser. With the limited memory ArcaOS has it will pretty quickly run out of gas.

All discussions about PAE memory is sadly a big fat none starter. Idea's to make any program on OS/2 use PAE memory is a pipe dream. Now the current ArcaOS loader enables you to put a ramdrive in PAE memory. However the amount of addressable memory is not increased. The PAE code is extremely cool bit of codingin the ArcaOS loader. However it has a hidden cost in terms of performance. When you want to access memory above the 4 GB address range (for the ram drive) the loader effectively holds the CPU, switched CPU to PAE mode safe stack again and switch back. I am not describing it technically 100% accurate but PAE support via the UEFI loader has performance cost. There is BTW no other way to implement this.

Patch the OS/2 kernel to support PAE would possibly take about 6 to 12 months of full time. It would be a gigantic job. But then the drivers  need to be updated for this.
I looked at this with Steve Levine years ago and its to much work that it will mostl likely never work.

One of the things that needs to be looked at is if the memory consumption of the QT webkit engine can be reduced. But this is currently under research. I will have more news on QT development. Tune into Warpstock Europe video stream, details on wwww.warpstock.eu.

Roderick

6
Programming / Re: A nice paper on DD Development on OS/2
« on: April 18, 2025, 03:24:04 pm »
I wonder if David his 32 bit driver development toolkit is of more use as it takes some stuff away from the developer such and pointer thunking.

Roderick

7
How can I get this software ?

Roderick

8
Hi Jailbird

Thank you for the reply. I was aware of the setting in the Info.plist that would make the app launch in non-retina mode. This then allows you to run the VM with 100% scaling. It's way too small normally to use 100% and you have to use 200% to give you the correct size when using a Retina display.

However if you make the suggested change and try to launch the Virtual Box VM under macOS Sonoma it refuses to start and complains about the app signature being broken. This doesn't happen with Monterey, so I thought I was stuck using the 200% setting with Sonoma.

BUT, I've just discovered that you can launch the app and pass an 'AppleMagnifiedMode' argument to open it in non-retina mode. This does work so I can launch a specific VirtualBox VM from the command line using:

   open /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app --args -AppleMagnifiedMode YES -comment ArcaOS-Exp --startvm 2f3f6889-be25-42ba-a78a-83a4c6be3139 --no-startvm-errormsgbox

This does indeed seem to be little bit faster. Not hugely, but everything helps.

So, after playing with lots of settings, the configuration I'm now using is:

   1920x1080 resolution, 65536 colours, 100% scaling, non-retina app mode

It is still too slow for comfort so I will continue to investigate and I might raise a ticket with the VirtualBox developers, but it is a bit more useable than it was.

Many thanks
David

Also run in single CPU mode, do not configure on Mac more then 1 CPU.

Roderick

9
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 01, 2025, 09:56:05 am »
Dear all,
How about an OS/2 or ARCOS without Windows and DOS? Wouldn't that be easier?

Thanks everyone

Its about 25% of the kernel source is the VDM support. But removing that is not going to make it easier I am afraid to get a new kernel.

Roderick

10
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 01, 2025, 09:55:07 am »
Hello

For the moment we have in no specific order:
1) Modern web browser
2) Wifi Driver.
3) Memory issues
4) IPv6.

And side discussion:
1) There is no need to worry because we have virtualization.
2) The dislike of RPM/YUM or FHS.

Regards

It would be great if Arca Noae can officialy support QEMU as of version 2.92 or 2.94 QEMU now works with ArcaOS. But we would need mouse and clipboard integration.
I think VMworkstation is less attractive with the unknown commercial goals of Broadcom (read VMware). Sorry there ESXi server prices are a pure rip off. Some company customers I know that have seen in 1 year time
the cost of ESXi go up by a factor of 10. I wonder how price competitive VMware (Broadcom products will remain).

Roderick

11
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 01, 2025, 09:52:42 am »
Another up coming problem is IPv6, which luckily for us is taking forever to catch on. Eventually we would need a new network stack.

Its going to be interesting I would need to have more indications about this. What I see happening i that some modems from ISP have IPv4 emulation and tunnel over IPv6 if I get it correctly.
The company I work still has with 800 people IPv4 internally on the company LAN. I agree a multi protocol stack (Ipv4 and IPv6) might be nice to have but we simply lack the human resources.
From what I understand the old socketsk.sys is 98% recompiled FreeBSD code and 2 is OS/2 specific code. The point being we might be able to port a new stack from FreeBSD.
But this will not be done in month and will require a full time developer.

Roderick

12
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 01, 2025, 09:49:53 am »

I still think that we are falling behind in applications. A modern web browser will help on that, since there are a lot of applications that are on the web without the need to install those, and on the other side compiling and porting applications are now starting to get complicated because of the 32bits/Memory limitation.

A Modern Browser and solving the memory limitations are getting more important for new apps.

Regards

The memory limitation can be solved with magic wand with the current kernel. We might want to wish for this but its not going to happen.
Talk to Steve Levine who helps BWW out with debugging GCC programs. He also helps Paul Smedley to debug programs. But you need to use possibly memory dumps, Thesues and othee tootls to find out WHY a program runs out of memory.
From what I understand from Steve is that for example in the current PHP there is code added to prevent PHP for allocation more memory (Steve if you are reading can you comment please).  While not all limitations of 64 bit apps can be resolved some of them can be resolved by digging in the code for example and add checks to prevent it from consuming to much memory.  But this is of course time consuming process.

Roderick

13
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 01, 2025, 08:12:08 am »
memory issues:
as I understand, libc uses shared memory.
there were attempts to make it use HighMem.
There were discussions, there were announcements.
there were attempts to patch exe files to use HighMem.

But current situation: you can start Firefox and OpenOffice only 1 time.
if you load this heavy apps then memory is occupied and you should reboot system to use firefox again.
Java VM (I don't remember, does it depend on libc), is consuming low memory too.

Question: what is the current state of libc ? it was modified?

P.S. It's not a claim. I make  technical request.

I think its kernel 14.203 from Arca Noae that resolves this issue. High memory with older kernel (if DLL's are loaded high into memory) and then unloaded the memory is not released.
Using the latest ArcaOS kernel this should work.

Roderick

14
Comments, Suggestions & Questions / Re: ArcaOS TestLog
« on: February 28, 2025, 12:26:02 pm »
I understand something like is being worked on.

Roderick

15
Virtualization / Re: Win-OS/2 - Open vbesvga.drv video driver
« on: February 08, 2025, 09:47:27 pm »
Hello

Currently my Win-OS2 full screen session (1920x1080) has a "slow-choppy" mouse and you can not move the mouse pointer down from the middle of the screen. (ArcaOS 5.1 BIOS running on a VirtualBox host. )

On the "OS/2, EComStation & ArcaOS Discussion group" facebook page, it was posted something about this new video driver for Windows 3.1:
- https://github.com/PluMGMK/vbesvga.drv?tab=readme-ov-file

It has some instructions on how to install it, but if I follow the procedure and it gives me an error when I load Windows 3.1.
Quote
Unsuitable settings for current driver / hardware
Press any key to about booting Windows...

If I only remove from the modified system.ini all the [VBESVGA.DRV] part...
Quote
[VBESVGA.DRV]
PMIDcheck=sanity
Width=1920
Height=1080
Depth=16
DoubleBufRefreshRate=75
...Win-OS2 full screen runs with the newer vbesvga.drv and vddvbe.386. But the screen resolution is smaller (1024 × 768), mouse now works fine and I can go to the bottom part of the screen with the pointer.

Do you think this drivers can be useful for our Win-OS2? Can we benefit in some way from this driver? Any other suggestion on how to make this drivers work at 1920x1080?

Regards

I am not certain but I think what is being overlooked is that the WIN/OS2 driver uses I think a special GRADD driver that deals with the WIN/OS2 screen resolution. I think this bypasses the normal DOS video support. This alternative Windows 3.1 video driver looks nice. However you might be out of luck with this driver as I think (based on the file name) this is a VESA driver. And this alternative Windows 3.1 driver then depends on the VESA bios in the DOS session.

But I could be wrng.

Roderick

Pages: [1] 2 3 ... 49