16
Comments, Suggestions & Questions / Re: How to Ignore User in OS2World Forum
« on: January 16, 2024, 05:29:48 pm »
Thanks a lot Silvan. Without your picture I overlooked the obvious.
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
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.
/c mode 120,65 & pgmcntrl /po:2100,25,820,950 & p:\4os2\4os2.exe @p:\4os2\4os2.ini "p:\4os2\4start.cmd & p:\usr\local\bin\old\ssh -l git nas-ab"
would open exactly on top of the first one, which is obviously not desirable.Which I think is not that bad. I think this is the usual way window positioning worked the last centuries. I mean why should a program decide by itself where it is positioned and sized? It's the task of the OS to keep window positions (and sizes) stored and restore them. Usually at the place it was when closed the last time. When a user explicitly wanted to have it positioned on some special other place, you can always use pgmctrl or like or implement cli options or.... But hey - I wanna my windows at the place I put it. That's one reason I stay with OS/2. I don't wanna an OS or a program which decides this by itself. YMMV, but in this case you have other OS options anyway.
In Windows, they have to setup external monitors to do what Xpager does.I use VirtuaWin (v4.5) on Win to replicate xpagers behavior and even set up the same keys for switching between the pages. There are other tools which do the same. But long time ago when I looked for it I choosed this one.
{0}[e:\_work\pmprintf\trunk] ctoi WPSTEST.CSC
WPSTEST.CSC:
"wpobject.sc", line 440: error: Override method "somInitClass" not in base class.
"wpobject.sc", line 444: error: Override method "somNew" not in base class.
"wpobject.sc", line 448: error: Override method "somRenew" not in base class.
Number of errors: 3
error in converting WPSTEST.CSC
At the moment I'm experiencing that if you BIOS does not support that resolution I can not make a 4K monitorI would it express in other words - the BIOS offers Panorama only resolutions it thinks the 'monitor in conjunction with the current connection' (DP, DVI, HDMI, ...) is capable. Then Panorama tries to select the predefined BIOS mode (resolution) which matches best OR tries to patch on of the BIOS modes to a better resolution.
Panorama v1.18 log for GID=0 started at 2023-12-8 10:9:43
This copy of Panorama is licensed to Martin Iturbide #xxxxxxxxxx.
Profile setting for Shadow...Enabled
VESA version is 201
BIOS-supplied information
OemVendorNamePtr = 8B000022
OemProductNamePtr = 8B000031
VideoModePtr = 8B00004D
TotalVramSize = 1000000
OemVendorName = Arca Noae, LLC
OemProductName = UEFI VESA Emulator v1.0
Emulated environment detected.
Initial PmRes X=1920 Y=1080 C=16777216
EDID Version 1.4
Display size 31 cm x 17 cm
Display resolution is 1920x1080
Info: 14100,1920,1080,184,36,16,16,3,14
Checking BIOS...
Mode 0x120: 1920x1080x32bpp planes=1 Attr=0xDB
Mode 0x121: 640x480x32bpp planes=1 Attr=0xDB
Mode 0x122: 800x600x32bpp planes=1 Attr=0xDB
Mode 0x123: 1024x768x32bpp planes=1 Attr=0xDB
Mode 0x124: 1280x1024x32bpp planes=1 Attr=0xDB
Mode 0x125: 1366x768x32bpp planes=1 Attr=0xDB
PmRes X=1920 Y=1080 C=16777216
X=1920 Y=1080 C=16777216 LoX=65535 LoY=65535 LoC=0
Requested mode=120
Video Aperture: Base=0xD0000000 Size=0x800000
Attempt to allocate shadow buffer...Success
Shadow Buffer locked at 0x5E5F7000, Length 0x800000 bytes
Trying D0000000 size 800000.
MTRR Write Combine caching enabled Base=D0000000 Size=800000.
Requested mode=120
Panorama v1.16 log for GID=0 started at 20.12.2023 20:26:17
This copy of Panorama is licensed to andreas.xxxxxxxxxxxxxx.
Profile setting for Shadow...Enabled
VESA version is 300
BIOS-supplied information
OemVendorNamePtr = C0000170
OemProductNamePtr = C0000102
VideoModePtr = 8D000044
TotalVramSize = 3000000
OemVendorName = (C) 1988-2010, Advanced Micro Devices, Inc.
OemProductName = LEXA
Manual custom resolution is set to 3840x2160
Checking BIOS...
Mode 0x110: 640x480x16bpp planes=1 Attr=0xBB
Mode 0x111: 640x480x16bpp planes=1 Attr=0xBB
Mode 0x113: 800x600x16bpp planes=1 Attr=0xBB
Mode 0x114: 800x600x16bpp planes=1 Attr=0xBB
Mode 0x116: 1024x768x16bpp planes=1 Attr=0xBB
Mode 0x117: 1024x768x16bpp planes=1 Attr=0xBB
Mode 0x119: 1280x1024x16bpp planes=1 Attr=0xBB
Mode 0x11A: 1280x1024x16bpp planes=1 Attr=0xBB
Mode 0x165: 1280x960x16bpp planes=1 Attr=0xBB
Mode 0x166: 1280x960x32bpp planes=1 Attr=0xBB
Mode 0x121: 640x480x32bpp planes=1 Attr=0xBB
Mode 0x122: 800x600x32bpp planes=1 Attr=0xBB
Mode 0x123: 1024x768x32bpp planes=1 Attr=0xBB
Mode 0x124: 1280x1024x32bpp planes=1 Attr=0xBB
Mode 0x145: 1400x1050x16bpp planes=1 Attr=0xBB
Mode 0x146: 1400x1050x32bpp planes=1 Attr=0xBB
Mode 0x175: 1600x1200x16bpp planes=1 Attr=0xBB
Mode 0x176: 1600x1200x32bpp planes=1 Attr=0xBB
Mode 0x1D2: 3840x2160x16bpp planes=1 Attr=0xBB
Mode 0x1D4: 3840x2160x32bpp planes=1 Attr=0xBB
Mode 0x1D8: 2560x1440x16bpp planes=1 Attr=0xBB
Mode 0x1D9: 2560x1440x32bpp planes=1 Attr=0xBB
Video Aperture: Base=0xE0000000 Size=0x2000000
Attempt to allocate shadow buffer...Success
Shadow Buffer locked at 0xABFE0000, Length 0x2000000 bytes
Trying E0000000 size 2000000.
MTRR Write Combine caching enabled Base=E0000000 Size=2000000.
Requested mode=1D4
If there is any additional trick you may suggest for 3840x2160 I will try it out.
You can search the Mantis ticket about that from me a few years ago. Basically before playing games with custom resolution settings (you shouldn't do that) check what your hardware offers. I think it's listed in a testlog but there's also some util IIRC.