• State Not Answered
  • Locked Locked
  • Replies 20 replies
  • Subscribers 21 subscribers
  • Views 4306 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Workbook mode not working at high screen resolutions

Brian Michaud

Has anyone else noticed that Uvision V2.39 has a bug when using workbook mode at high screen resolutions (greater than 1024x768)?

The workbook tabs at the bottom of the windows will become erratic, disappear, not refresh properly, etc. Keil has said this is not a bug....but it obviously is.

V2.36 does not have this problem at high screen resolutions, so they did something from V2.36 - V2.39 to cause this.

Parents
  • 0 in reply to Brian Michaud

    No, the mud was thrown when Keil added something to V2.40 which created this "problem"... which was not evident in V2.36. ;-)

    Well, I'm not sure just WHAT we could have done to uVision to create the problem. We use Microsoft Visual C++ and the only things I can find that we changed there with regard to windows or dialogs is that we added more descriptive text on the left side of windows that dock. This was done using an MFC routine -- uVision doesn't manipulate the display directly, it uses MFC library calls to do stuff like that.

    So, I contacted a buddy of mine who is one of the software developers at Microsoft and described the problem. His first question was ... does this involve an ATI video card...

    Here were his comments.

    • If changing the hardware acceleration level fixes the problem, then the problems is not in MFC.
    • The Microsoft video driver for ATI video cards is well tested and stable. In fact, it's probably more stable than the ATI driver. You may want to use the Microsoft driver (if there is one for 98se).
    • Run the card at 60Hz and see if this solves the problem.
    As for the Riva TNT card, we have several of these here and they all work beautifully.

    One thing to consider for both cards is that the problem only shows up when you increase the resolution. Increased resolution means more memory to access. And, the memory has to be accesses faster (because the screen refresh stays the same). So, flaky (or slow) video memory could be causing this problem. Setting the refresh rate slower may solve the problem -- it may also cause siezures (I have problems with refresh rates below about 72Hz).

    Hopefully, some of these comments help you get up and running.

    Jon

Reply
  • 0 in reply to Brian Michaud

    No, the mud was thrown when Keil added something to V2.40 which created this "problem"... which was not evident in V2.36. ;-)

    Well, I'm not sure just WHAT we could have done to uVision to create the problem. We use Microsoft Visual C++ and the only things I can find that we changed there with regard to windows or dialogs is that we added more descriptive text on the left side of windows that dock. This was done using an MFC routine -- uVision doesn't manipulate the display directly, it uses MFC library calls to do stuff like that.

    So, I contacted a buddy of mine who is one of the software developers at Microsoft and described the problem. His first question was ... does this involve an ATI video card...

    Here were his comments.

    • If changing the hardware acceleration level fixes the problem, then the problems is not in MFC.
    • The Microsoft video driver for ATI video cards is well tested and stable. In fact, it's probably more stable than the ATI driver. You may want to use the Microsoft driver (if there is one for 98se).
    • Run the card at 60Hz and see if this solves the problem.
    As for the Riva TNT card, we have several of these here and they all work beautifully.

    One thing to consider for both cards is that the problem only shows up when you increase the resolution. Increased resolution means more memory to access. And, the memory has to be accesses faster (because the screen refresh stays the same). So, flaky (or slow) video memory could be causing this problem. Setting the refresh rate slower may solve the problem -- it may also cause siezures (I have problems with refresh rates below about 72Hz).

    Hopefully, some of these comments help you get up and running.

    Jon

Children
No data