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

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
  • OK. I just tried everything you suggested on another 1280x1024 and everything works well.

    1. What video card and video driver are you using?
    2. What version of Windows 98? Are you using 98SE?
    3. Are you using a US Govt version of Windows 98?
    If you can tell me these things, I can setup a machine here with that exact configuration.

    Jon

Reply
  • OK. I just tried everything you suggested on another 1280x1024 and everything works well.

    1. What video card and video driver are you using?
    2. What version of Windows 98? Are you using 98SE?
    3. Are you using a US Govt version of Windows 98?
    If you can tell me these things, I can setup a machine here with that exact configuration.

    Jon

Children
  • Here are a few other questions:

    1. What motherboard and BIOS do you have?
    2. Do all the computers you tested on have the same motherboard? Video card?
    3. Have you looked for an upgraded video driver?
    One thing to try (if you already haven't) is to reduce the amount of graphics acceleration and Window does. In Control Panel, open System and Select the Performance Tab and click on Graphics. Drag the slider to change the hardware acceleration settings as summarized below.

    • The default setting is Full, which turns on all graphics hardware acceleration features available in the driver.
    • The first notch from the right fixes many mouse problems.
    • The second notch from the right prevents some bit block transfers and disables memory-mapped I/O for some display drivers.
    • The last notch from the right (None) can be set to correct problems if your computer frequently stops responding to input or has other severe problems.
    You should be able to reduce the hardware acceleration one notch at a time and then check the results in uVision.

    Let us know if you have any success with this.

    Jon

  • OK, I got it working on one computer!

    I did as you suggested, Jon, and lowered the graphics acceleration one notch. Sorry I didn't try this simple step earlier, but I didn't since it worked with V2.36 at full acceleration. Why it works with 2.36 and not 2.40 is still a mystery....but is inconsequential at this point.

    I will try this on all our systems and am pretty sure it will solve this issue. I'll search for upgraded drivers and see if I can then increase the graphics acceleration back up to full.

    Thank you!

    Much appreciated,
    Brian

  • OK. Did that get things working on all of your PCs? If so, what video card were you using so the rest of us can avoid it.

    Jon

  • I got all the computers working now.

    The funny thing is I never installed the new version on my computer because of the problem, but when I did upgrade my version yesterday...I found that I didn't even have that problem on my computer! I guess it's cause I always search for updated drivers on a regular basis.

    But 2 computers here only work if the graphics acceleration is set down one notch (or if screen resolution is set to 1024x768 or less).

    Computer 1:
    - ATI XPERT@PLAY AGP 2X video card
    - Driver 4.11.2628
    (Trying to update this driver only caused computer to lock up when booting)

    Computer 2:
    - 3D Force B23 Plus NVIDIA RIVA TNT2 Model 64
    - Still need to upgrade to newest driver released 12/9/2003

    I haven't been able to play with Computer 2 yet...people get mad when you try to mess with their computer while they're using it, LOL.

  • "(Trying to update this driver only caused computer to lock up when booting)"

    And people were throwing mud at Keil... ;-)

  • It's a bit unlikely that two completely different drivers for two completely different cards happen to show exactly the same bug in exactly the same set of circumsdances. Sounds more like something not quite right with uvision to me.

    Stefan

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

    I have nothing against Keil and am very happy with their products and continuous improvements.

    People make mistakes, I just want to find to a way to fix them...and I have thanks to Jon.

    Regards,
    Brian

  • "And people were throwing mud at Keil... ;-)"

    Ah, but Keil software is *expensive* unlike video drivers supplied with far-eastern video cards. I guess people expect more.

    Stefan

  • 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