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 - jailbird

Pages: [1]
« on: November 06, 2021, 01:08:49 am »
So going through the properties on the DOS Session icon, I noticed the setting VIDEO_MODE_RESTRICTION with a comment that says 'Set to CGA to increase available memory to 736K.'.

However, it doesn't matter if I set it to "CGA" or "MONO", the available memory information in MEM doesn't change at all on ArcaOS 5.0.6.  This is under VirtualBox, so maybe VBox isn't following the original PS2 memory layout exactly which is causing it?

I tried and that didn't make it change either. Is it working for anybody else?

Hardware / Re: OS/2 Video Performance
« on: November 06, 2021, 12:48:48 am »
I agree that HDA does well in SysBench DIVE measurements. I have run SNAP measurements for a long time, and unless the graphics card is 15 years old, they are never far from Panorama. For some systems, there are performance issues with SNAP, but the Arca Noae version seems to solve them. I've gotten used to all the goodies that come with Panorama, so I don't give SNAP much attention.

Forgive me if I'm being naive or dense, I'm not an OS/2 expert at all.  From what I've picked up so far in this thread is:

- On "modern" graphics, SNAP and Panorama are about equal in performance
- DIVE seems to always been faster than PM
- In SM/FF/TB, Panorama with shadow buffers enabled disables DIVE
- Disabling shadow buffers in Panorama lowers PM performance, I believe?

So if Panorama has a tradeoff of either slower SM/FF/TB by preventing the use of DIVE or slower everything else in the disabling of the shadow buffer and SNAP *doesn't* have this issue as far as I can tell, then how in Panorama superior to SNAP on modern cards?

Setup & Installation / Re: Booting with NVMe
« on: April 28, 2021, 06:47:07 am »
Adding it to the .ISO itself doesn't seem to work, as it seems to use ramdisk images on the ISO.  So you'd have to modify those and then reburn the ISO.

So the easiest solutions seem to be USB stick or floppy.

Setup & Installation / Re: Booting with NVMe
« on: April 20, 2021, 11:35:10 pm »
For those playing around inside a VM, the easiest method (for me) was to just keep the .iso as-is, not bother with a virtual USB stick, and to just use the old method of a virtual floppy with just the NVME.* files and a blank BOOT_UPD.TXT.

That seemed to work just fine...

There's always the option of running at 64K colours. Even on real hardware, Arca Noae recommends 64K colours for maximum performance. Less memory per pixel and doesn't look much different. Of course depends on your usage.

Good idea, I'll try that.

Here's the full instructions on what I did:

1) Shut down all VBox VMs, but leave VBox itself running.
2) On a command line window, run:
Code: [Select]
VBoxManage.exe setextradata global GUI/MaxGuestResolution any   (on Linux, leave out the .exe of course)
( Or inside of VBox, Preferences->Display, Maximum Guest Screen Size to "None" ).
3) On the same command line window, run:
Code: [Select]
VBoxManage.exe setextradata "OS/2" "CustomVideoMode1" "1920 x 1200 x 24"   (change OS/2 to match the VM name)
4) Power on the VM and wait for the desktop to finish loading
5) At the command line again, run:
Code: [Select]
VBoxManage.exe controlvm "OS/2" setvideomodehint 1920 1200 24( Yes, there's no consistency in the formatting of the resolution between the two commands, it's annoying )
6) Back inside the VM, go into the Screen settings and 1920x1200x16777216 should now show up.

This assumes you have the VBox's version of GENGRADD.DLL loaded following either the instructions with the GAs, or by selecting guest additions in the ArcaOS installer.

Basically, #2 lets you set custom resolutions (they won't work without it), #3 adds the new resolution, and #5 tells the VM about it.

So I did a fresh install and still see it.  If I run the VM in fullscreen mode, it acts better but is still slightly laggy.

If I build the VM under Parallels instead using Panorama, it works fine.  So it must be some weird macOS + VBox + OS/2 GA issue.

Sorry for the noise!

Strange.   This is a fresh install  too.  I guess I'll try a reinstall (again).

And it looks like the ArcaOS installer already does 'SET C1=GENGRADD,SBFILTER' :(

I've noticed this for a while now but I only recently figured out the situation.

On any version of VBox from the last couple of years, when you install ArcaOS (any version, I'm using 5.0.6 now), the default resolution is pretty low and everything is good. After installing the VBox Guest Additions and GRADD (in newer releases, ArcaOS will do this for you during install if you tell it to), everything is still pretty good up to about 1024x768. There's probably very slight lag, but nothing really noticeable unless you're specifically looking for it.

At 1280x1024, there's definitely noticeable UI lag just moving the cursor around. Eg, you can definitely see the mouse pointer "stutter" moving it to the XCenter menu button and clicking on something and selecting it.

At 1600x1000, the UI lag is so bad it's very aggregating trying to navigate around.

So it seems like the larger, the slower it is. This is basic 2D stuff, not 3D. Increasing the VRAM assigned to the VM doesn't help.

Is this a generic OS/2-related issue (eg, the way GRADD works), or is it a VBox guest additions issue?

Internet / Re: The new browser / QT5
« on: August 19, 2019, 02:01:20 am »
Qt 6.0 is already in the planning stages. So hopefully we won’t have to go through this all yet again.

Events / Re: ArcaOS 5.0.4 is out!
« on: July 30, 2019, 05:53:14 am »

I still can not get ArcaOS. I asked the order page to build the ISO and I got the confirmation e-mail, but the mail link and the webpage gave me a connection timeout (The connection has timed out). Anybody else with the same problem?


I had an issue where something was trying to upgrade the connection from http:// to https:// .  Using http:// finally worked.  https:// will timeout.  It appears that they firewall the https port (443) so instead of a quick connection failed, it just sits there...

Applications / Re: ODIN Revisited
« on: June 25, 2019, 08:06:42 am »
getaddrinfo() was added for IPv6.  It sounds like Odin probably doesn't grok IPv6 yet :(.

Pages: [1]