Announcement

Collapse
No announcement yet.

PB35 Graphics Screen problem with XP

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Daniel Raymer
    replied
    Now we're getting silly, guys! Seriously, thanks to all who responded. My user is happy, XP or otherwise.

    Dan Raymer

    ------------------

    Leave a comment:


  • Lance Edmonds
    replied
    LOL!

    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Michael Mattias
    replied
    One of my users has reported that my good old PB35-compiled DOS program acts strangely under XP.
    Hmm, small world: One of my PB/DOS programs has reported one of my users acts strangely under Win/XP....

    MCM


    Leave a comment:


  • Guest's Avatar
    Guest replied
    Originally posted by Uros Kocevar:
    Thanks for the "follow up". Actually I have found the bug in the system by myself. As the last post from Lance Edmonds suggests I tried to disable graphic adapter (Control Panel /Appearance and Themes /Display /Settings /Advanced /Adapter /Properties / Disable device). After restarting the computer in VGA mode the RDS is running as it should.

    I have Gateway system with
    Intel 1993 MHz Pentium 4 processor and
    NVIDIA GeForce2 MX 400 (Gateway) Graphic Processor.

    Problem solved!

    Hello, I work in Gateway tech support as a manager, and can make
    a suggestion.

    The drivers on Gateway.com for your video card have not been
    updated since 2001, so the best drivers to use would be the
    Detonater XP drivers from NVIDIA.COM. I have had users install
    them numerous times for many different video issues and they
    did the trick. Granted it's an 8Mb download but it is well
    worth it.

    ------------------
    Amos
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Guest's Avatar
    Guest replied
    Have your user give this program a try. It uses 25 and 50 line
    text mode, and Screen 12 for the purpose of testing mouse and
    video.

    There isn't a whole lot to it, but it is a good diagnostic test.
    http://sealsystem.sourceforge.net/link/mstest.exe

    ------------------
    Amos
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Tom Hanlin
    replied
    As noted in the file description, the PB/Vision demo (not PB/Vision itself)
    requires VESA graphics support to work. Although Microsoft helped invent the
    VESA standard, it is badly supported by Windows. You may be able to get the
    demo to work in a full-screen console, if your video card supports VESA--
    which is less common, these days, since its advantages apply only to DOS
    programs.

    ------------------
    Tom Hanlin
    PowerBASIC Staff

    Leave a comment:


  • Uros Kocevar
    replied
    Thanks for the "follow up". Actually I have found the bug in the system by myself. As the last post from Lance Edmonds suggests I tried to disable graphic adapter (Control Panel /Appearance and Themes /Display /Settings /Advanced /Adapter /Properties / Disable device). After restarting the computer in VGA mode the RDS is running as it should.

    I have Gateway system with
    Intel 1993 MHz Pentium 4 processor and
    NVIDIA GeForce2 MX 400 (Gateway) Graphic Processor.

    Problem solved!



    ------------------

    Leave a comment:


  • Lance Edmonds
    replied
    When your app switched to SCREEN 12, are you testing ERR to see if the mode could be set successfully?

    Also, find out what graphics card and drivers he is using. He might also try to reboot in standard VGA mode and see if that makes any difference.


    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Daniel Raymer
    replied
    My problem user says he has it in full-screen mode, as the instructions indicate. But, when did a modern user ever actually read the manual before reporting a "bug"?

    ------------------

    Leave a comment:


  • Tom Hanlin
    replied
    PB/Vision requires full-screen, like many of the more serious console
    programs. Oddly enough, Windows does not provide decent console emulation
    inside a window-- has to be "full-screen mode". This is very important
    for handling many DOS programs properly.

    ------------------
    Tom Hanlin
    PowerBASIC Staff

    Leave a comment:


  • Roy Scott
    replied
    I have had problems running PBVision programs in a DOS window, but
    they work fine full screen. It may be in the remapping for the semi
    graphic characters or some programs may attempt to access the video
    hardware directly in the old fashion. I believe that a DOS window
    is the equivelant of a console screen and full screen mode is the
    equivelant of a virtual DOS machine.


    ------------------
    Roy Scott
    http://www.royscott.net

    Leave a comment:


  • Jerry Fielden
    replied
    I tried an old graphic antimation in screen 12 in XP home, it
    worked alright in full screen, but when I hit Alt Enter it minimized
    and displayed the desktop.

    I have tried several times to get DOS programs to run in a window
    and haven't been successful yet.

    ------------------

    Leave a comment:


  • Tom Hanlin
    replied
    Make sure he's running in full-screen mode, not in a window.

    It's possible that his hardware doesn't support DOS graphics modes, although that would be unusual.


    ------------------
    Tom Hanlin
    PowerBASIC Staff

    Leave a comment:


  • Daniel Raymer
    started a topic PB35 Graphics Screen problem with XP

    PB35 Graphics Screen problem with XP

    Hi, fellow "classic" PB users!

    One of my users has reported that my good old PB35-compiled DOS program acts strangely under XP. It is probably peculiar to his machine and/or its setup, but I thought I'd post this to see if anyone else has reported anything similar (didn't find it in a forums search).
    He claims that all the text-mode stuff works fine, but as soon as he goes to any of the modules that use graphics mode (SCREEN 12), he just gets a blank screen. Weirdly enough, he says this also happens when he runs the TurboPascal graphics module that is SHELLed from my PB35 program.
    Any thoughts? (other than to find customers with fewer complaints)

    Dan Raymer
    Grizzled but still puzzled TurboBasic/PowerBasic veteran

    ------------------
Working...
X