DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

GetB bit 32 Diadem 2015 (64 bits) vs Diadem 2018 (64 bits)

Solved!
Go to solution

Hi,

 

I have some scripts running in Diadem 2015 which after installing Diadem 2018 get different results

 

An example Script:


Num32bits=&H80000000
MyBit = GetB(Num32bits,31)
MsgBox(Num32bits & VBCRLF & MyBit)

 

Result 2015:

-2147483648

1

Result 2018:

-2147483648

0

How could I get the correct value for the last bit?

 

Thank you for your help

 

0 Kudos
Message 1 of 4
(836 Views)

Hi Dimashoo,

 

I have reproduced your issue in DIAdem 2015 (=1) and DIAdem 2018 (=0) and DIAdem 2019 (=0).  I have created CAR 740870, and hopefully R&D will address this soon.  If I had to guess, I would think that this had something to do with DIAdem switching from a 32bit application to a 64bit application.

 

Thanks for pointing this out,

Brad Turpin

DIAdem Product Support Engineer

National Instruments

0 Kudos
Message 2 of 4
(747 Views)
Solution
Accepted by topic author Dimashoo

Hi Dimashoo,

 

I got an answer from R&D.  They say you can configure recent versions of DIAdem to give the expected high bit result with a change to the registry.

 

[HKEY_CURRENT_USER\Software\National Instruments\DIAdem\18.0\Settings]

"BinaryOperation"=dword:00000002

 

OR

 

[HKEY_LOCAL_MACHINE\Software\National Instruments\DIAdem\18.0\Settings]

"BinaryOperation"=dword:00000002

 

Brad Turpin

DIAdem Product Support Engineer

National Instruments

0 Kudos
Message 3 of 4
(739 Views)

Hi Brad_Turpin, I added the BinaryOperation variable to the HKEY_LOCAL_MACHINE and now I get the correct value for the Bit. It solves the problem.

 

Thank you very much!!!

0 Kudos
Message 4 of 4
(727 Views)