Author Topic: Questions about the OS/2 System Full Screen Cmdline sessions  (Read 3605 times)

RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Hello all,

Here's an interesting question. I've got an old VIO app I wrote that I run full screen on an ancient OS/2 system I have. I am working on enabling it for a newer system.

Now... on to the problem. The app utilizes some very odd "mode" setting to set up the VIO screen size. (I think that size is something weird like 140x50). This is on an old Thinkpad system (TP600e and previously a TP600). If memory serves, I can use any number of columns and rows that is within the same limitation that a windows CmdLine session has (ie: COLxROW cant exceed xNumber (8,000 I believe)).

Interestingly, though the newer (various machines) and two old systems (the TP600s) are all running SNAP Full, the other systems I have seem to be limited to the standard original BIOS/DOS VIO modes (ie: the original 80x25, 80x43, 80x50) for full screen sessions.

Does anyone know if there is a way of bypassing those restrictions, or what's causing them?

Best,
Rob
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
I'm *guessing* this is a limitation determined by the video card's capabilities. Or it's implementation. The NeoMagic chip/capabilities (in the TP600's) may just be very odd?
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Radek

  • Full Member
  • ***
  • Posts: 201
    • View Profile
My guess is "not odd video but the ancient chaos". In those old days, every video card had its extras, its special video modes, and its special way of enabling them. These extras were supported by native video drivers but they usually aren't supported by SNAP or Panorama. SNAP usually restricts your fullscreen to (available) VESA modes. Panorama does not seem to support more than standard BIOS video modes (00h - 13h) in DOS sessions. In OS/2 sessions, it need not be better.

Check which VESA modes are supported by your comp. There exist a 132x50 VESA modes, which might be usable when rewritting "something weird". Note that not all VESA modes, which should be available on your HW, can be reported as available. The reason is the current very bad coding of VESA BIOS: Winblows does not need VESA so that BIOS coders do not waste time with implementing it and if they show any effort in implementing then the result is incomplete and full of bugs. I have seen "VESA VBE 2.0 compatible" video card which supported only 640x350x16 and 640x400x16 VESA video modes. Period.