RipBAR 6.0 Not Compatible with Windows NT 3.5

 Last reviewed: May 6, 1997
Article ID: Q93790
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

RipBAR for Windows NT, version 6.0, is not compatible with Windows NT version 3.5.

The application starts, but it doesn't complete painting the screen and an error message appears stating that the instruction at "0x00033d4b" referenced memory at "0x00000021" and the memory could not be read.

CAUSE

This problem occurs because the application is dereferencing a GDI object handle as if it were a pointer. This doesn't cause a problem in Windows NT version 3.1, but it causes an access violation in Windows NT version 3.5.

RESOLUTION

This problem has been confirmed with SoftDesign and an update is now available. To obtain an update to RipBAR version 6.04, contact the author, Jonathan Carroll, at one of the following addresses:

Conventional mail: 

   Jonathan Carroll
   28 Parkland
   Pointe Claire, Quebec
   CANADA  H9R 2 E8
CompuServe: 

   User ID: 74017,3242
GEnie: 

   User ID: J.H. Carroll
E-mail (Internet): 

   74017.3242@compuserve.com
RipBAR is manufactured by SoftDesign, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words: prodnt third-party 3rdparty thirdparty
Keywords : kb3rdparty nt32ap
Version : 3.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.