OS/2, eCS & ArcaOS - Technical > Virtualization

Win-OS/2 - Open vbesvga.drv video driver

<< < (5/6) > >>

Roderick Klein:

--- Quote from: David McKenna on June 21, 2025, 09:26:09 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,

--- End quote ---

These settings do not influence WIN/OS2.

Roderick

David McKenna:
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,

Dave Yeo:
One thing I discovered was that the X VESA driver failed on a UEFI install, to quote myself.

--- Code: ---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

--- End code ---

Developer answered,


--- Code: ---   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.

--- End code ---

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.

Roderick Klein:

--- Quote from: David McKenna on June 22, 2025, 12:05:14 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,

--- End quote ---

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

Roderick Klein:

--- Quote from: KO Myung-Hun on May 17, 2025, 03:07:13 pm ---Oh, it works here, too!

Edit: Here is DBCS, Korean.

--- End quote ---

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

Thanks.

Roderick

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version