had a functinal VB 6 prog. for HP NWA on Winds 98. with XP it crashes !

[Alimah]

I had a fully functinal VB 6 program for HP NWA on Windows  98 using NI-488.2.  I recently installed it on Windows XP and a new NI 488.2 . The NI config software communicates with the instument and identifies it. However my program gives ibsta error of " &H8000" with Iberr=EDVR<DOSError> and ibcnt<0X25>. That means,as I understand it,  it is having difficulty to write into the instrument. Am I missing somthing here? Please help. Thanks.

[Chris G in AE]

Hey Alimah,

It seems you're main error is a has to do with the driver.  Below you'll find a description of the error as well as suggestions on how to fix it.

EVDR (0)
Error Condition: Driver error.
Description: EDVR is returned when GPIB hardware is not configured properly, or the interface name or device name passed to the ibfind function is incorrect.
Possible Cause: Often EDVR errors are caused when you misspell the interface name of your board or the device name of your instrument. For example, the default interface name for National Instruments boards is GPIB0, but you may misspell it as GPIBO (with an "oh" instead of a zero). This error may also occur, if the board index passed to the ibdev function is incorrect. The board index is the number portion of the interface name for the GPIB board, but many people make the incorrect assumption that it is the primary address of the board. For example, I may install a PCI-GPIB board in my computer and give a primary address of 2. The default interface name for board is GPIB0, so it has a board index of 0, not 2.
Solutions:

• Use the default settings for your GPIB hardware in the GPIB Configuration Utility (i.e., GPIB0 for the interface name and zero for the primary address).
  
• Use the ibdev function instead of the ibfind function to open communications with your instrument (to avoid using its device name).
  
• If you must use device names for your instruments, then make sure they are correctly configured in the Device Templates of the GPIB Configuration Utility (see your NI-488.2 User Manual for more details).
  
• Use the unit descriptor returned from ibdev or ibfind as the first parameter in subsequent NI-488 functions. Examine the variable before the failing function to make sure its value has not been corrupted.

You can find more GPIB error codes listed in the GPIB Error Codes and Common Solutions KnowledgeBase article.  Hope this helps!



Message Edited by Chris G in AE on 01-22-2008 04:06 PM

Message Edited by Chris G in AE on 01-22-2008 04:06 PM

Message Edited by Chris G in AE on 01-22-2008 04:07 PM