Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Detonator driver updated and problem

  1. #1
    Junior Member Regular Contributor
    Join Date
    Jan 2001
    Location
    Shanghai, China
    Posts
    128

    Detonator driver updated and problem

    I have updated my display driver to the latest Detonator 28.32 under win98, for my GF2MX400. And I always get an error when I try to debug Lightwave plugin programs. The error message is in Japanese(as my win98), which means some handle error in NVOPENGL.DLL at 0xC000001D, Illegal Instruction. I try to "downdate" my driver to 23.10, and it works with LW, but some error between it and the nView Desktop Manager installed by 28.32. I wonder who can help me solute the problem. I need to make some plugins for our project. I've found the latest 23.11 and 28.32 will cause the LW debug problem, but not the older driver. Can anyone help me? Thanks
    End of transmission...

  2. #2
    Super Moderator OpenGL Guru
    Join Date
    Feb 2000
    Location
    Montreal, Canada
    Posts
    4,256

    Re: Detonator driver updated and problem

    Ever since I went back to win98 on my home machine, its been nothing but trouble.

    I dont now what 0xc000001d means exactly, but it probably means an op code that wasnt supported by your CPU was executed. Im talking about 3dNow! and SSE.

    Go into Display->nvidia panel and go to tab (OpenGL) and disable enhanced CPU instrucution support.

    My chip is a P3, yet it sometimes says illegal instruction, bla bla bla, and it all points to soemthing like mulps, an SSE instruction.

    Leave win98 as soon as possible!

    V-man
    ------------------------------
    Sig: http://glhlib.sourceforge.net
    an open source GLU replacement library. Much more modern than GLU.
    float matrix[16], inverse_matrix[16];
    glhLoadIdentityf2(matrix);
    glhTranslatef2(matrix, 0.0, 0.0, 5.0);
    glhRotateAboutXf2(matrix, angleInRadians);
    glhScalef2(matrix, 1.0, 1.0, -1.0);
    glhQuickInvertMatrixf2(matrix, inverse_matrix);
    glUniformMatrix4fv(uniformLocation1, 1, FALSE, matrix);
    glUniformMatrix4fv(uniformLocation2, 1, FALSE, inverse_matrix);

  3. #3
    Senior Member OpenGL Pro
    Join Date
    Sep 2000
    Location
    Santa Clara, CA
    Posts
    1,096

    Re: Detonator driver updated and problem

    Yuck, you get an illegal instruction even though the OS has SSE context switch support?

    - Matt

  4. #4

    Re: Detonator driver updated and problem

    Matt: Yep, this does seem to happen. Scary isn't it? Or let's put it like this, certain SSE instructions will work fine (so a check for SSE support will pass), but other instructions might just randomly fail.

    The problem also seems to be WORSE when running an app in the debugger, when running outside of the debugger it often does work.

    At some point I was convinced this had something to do with missing femms instructions in the code, but I'm not so sure anymore, I never could get a handle on the problem very well, especially as Win2K worked just fine.

  5. #5
    Senior Member OpenGL Pro
    Join Date
    Sep 2000
    Location
    Santa Clara, CA
    Posts
    1,096

    Re: Detonator driver updated and problem

    emms/femms is NOT required for SSE. (Thank goodness! MMX is such a pain.)

    - Matt

  6. #6
    Senior Member OpenGL Pro
    Join Date
    Feb 2002
    Location
    Bonn, Germany
    Posts
    1,633

    Re: Detonator driver updated and problem

    Besides, FEMMS is only available with 3DNow. No 3DNow, no FEMMS.

  7. #7
    Super Moderator OpenGL Guru
    Join Date
    Feb 2000
    Location
    Montreal, Canada
    Posts
    4,256

    Re: Detonator driver updated and problem

    Originally posted by mcraighead:
    Yuck, you get an illegal instruction even though the OS has SSE context switch support?

    - Matt
    Not always, just sometimes.

    Could this have something to do with alignment in memory. The Intel tutorial talked about it, but it didnt say how to make sure memory is aligned (or unaligned).

    But that only concerns memory to register operations.

    V-man
    ------------------------------
    Sig: http://glhlib.sourceforge.net
    an open source GLU replacement library. Much more modern than GLU.
    float matrix[16], inverse_matrix[16];
    glhLoadIdentityf2(matrix);
    glhTranslatef2(matrix, 0.0, 0.0, 5.0);
    glhRotateAboutXf2(matrix, angleInRadians);
    glhScalef2(matrix, 1.0, 1.0, -1.0);
    glhQuickInvertMatrixf2(matrix, inverse_matrix);
    glUniformMatrix4fv(uniformLocation1, 1, FALSE, matrix);
    glUniformMatrix4fv(uniformLocation2, 1, FALSE, inverse_matrix);

  8. #8

    Re: Detonator driver updated and problem

    Matt: Sure, but often you will use MMX in combination with SSE, atleast I do, the two sortof go hand in hand. Now I do remember atleast one occasion where I forget the EMMS, and it went by unnoticed. Fixing this seemed to affect the illegal instruction problem.

    I say again, seemed, as I've seen it again later, and it always was a very random problem anyway.

    Let's just pray for 9x to die quickly.

  9. #9
    Senior Member OpenGL Pro
    Join Date
    Sep 2000
    Location
    Santa Clara, CA
    Posts
    1,096

    Re: Detonator driver updated and problem

    Nah, unaligned memory accesses require the special use of movups anyhow, so it's pretty hard to screw things up.

    This sounds like an OS or HW issue that I never encountered. I now use exclusively Win2K, but I used P3 w/ Win98 extensively and never once had it blow up on me like that.

    Could this be a hardware fault?

    - Matt

  10. #10

    Re: Detonator driver updated and problem

    I ran into the problem twice while doing final testing and debugging on win9x machines, both on different machines. Once a celeron, once a P3. Note that it has _never_ been a problem to me when running the game regularly, always just when (remote) debugging.

    I find it more likely to be a windows problem, maybe it's related to certain revisions? Perhaps the type of IE installed God knows (And isn't it much more fun to blame MS as it is to blame Intel?

    Btw, how could it be a hardware fault if 2K doesn't have the same problem?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •