I want to upgrade my LABVIEW 4.0 code to LABVIEW 8.0. I am using LV 7.0 to do this. The problem i am facing is 16 bit defined DLL's. As I cannot open it or see whats inside. These DLL's are used by different libraries

[PakAsia]

rename these .jpg files and rename them as LATTICE.DLL and COMPARE.DLL. I also have uploaded the vi which is creating problem

Taimoor

[Coq_Rouge]

The code you posted is not very good written. Local and globals variables are NOT pointers. You can not think C style then writing Labview code. What kind of instrument do you try to communicate with. Perhaps it is a drive on the net someplace

[rolfk]

I didn't look at the VI source code but the other comment doesn't promis much good!

For the DLLs you need to find a way to replace those DLLs with something else. 16 Bit DLLs are for Windows 3.1 and there is no way to get them to work in 32 Bit Windows.

So your options are, to either stay with Windows 3.1 (good luck with that !!) or maybe Windows 98 and use a LabVIEW 16 Bit version (<= version 5.1 only) to run your program, or get those DLLs removed/replaced.

The Compare.DLL might be just some comparison routines which might be easily implemented in LabVIEW itself. The Lattice.DLL is most likely a DLL which tries to do direct register access somehow which is in Windows 32 a protected operation and shouldn't be done in an application but instead in a kernel driver. In the latest LabVIEW versions with 64 Bit support it is even completely unsupported to do that.

I would say there is a lot of work ahead by trying to figure out what this DLL does and how to replace it. You need to at least get a 32 Bit version of that DLL if it is available and change the VIs accordingly as there might be difference in parameter sizes when they use for instance simply int as data type. If you can't find a 32 bit version of that DLL and failing that haven't got the source code to the DLL to create your own 32 Bit version (which would be likely some serious porting work) then the only option left is to either stay with Windows 3.1 (resp. 16 Bit mode in Windows 9x) or rewrite that part of the application from scratch to do the according IO with modern hardware.

[altenbach]

Well, at least the diagram matches the front panel in color and style!

You don't see that every day! 😄

[Dennis_Knutson]

It seems that this is doing some GPIB communication. If so, there is no need for any sort of dll. With the instrument manual, you can write your own communication routines fairly easily. Post the make and model of the instrument.

[PakAsia]

The code is not mine. I have just given task to upgrade it from LV4 to LV8 and operating system from 16bit to 32bit.  I got stuck with 16bit dll's

[PakAsia]

The code is not mine. I have just given task to upgrade it from LV4 to LV8 and operating system from 16bit to 32bit.  I got stuck with 16bit dll's

[Dennis_Knutson]

And you are unwilling to name the instrument? Youve already been told about the difficulty with the dll and what has to be done if you want to keep using that approach. If it's impossible to get 32 bit versions from the original vendor, you'll have to do it my way - which is probably what should have been done in the first place.

[PakAsia]

I have sent you only 2 DLL's and just 1 library. The code i have sent you is a part of software that handles BackGroundMonitoringSystem. There are many instruments like signal generator oscilloscope power suppllies. here is the list

Instrument#1=VX4286
Instrument#2=HPD20
Instrument#3=ARINC-429
Instrument#4=HPE1420B
Instrument#5=HPE1440A
Instrument#6=VX4234
Instrument#7=A5410C-30-1
Instrument#8=73A-453
Instrument#9=VX4367
Instrument#10=RD1260-35
Instrument#11=HP8116A
Instrument#12=TEK460
Instrument#13=HP66000A-1
Instrument#14=HP66000A-2
Instrument#15=HP66000A-3
Instrument#16=HP66000A-4
Instrument#17=HP66000A-5
Instrument#18=HP66000A-6
Instrument#19=HP1_VXI_COMMANDER
Instrument#20=HP2_VXI_COMMANDER
Instrument#20=RD_VXI_COMMANDER
Instrument#21=NI_VXI_COMMANDER.

Beside this there is Wiserver and Iserver for transputer, server 96(SLIGOS) and server 56 for ONCE card and motorola server, C code. DIO32HS, GPIB, taxi cards are also in use...  I want to upgrade code but stuck with these DLL's

[Dennis_Knutson]

I know some of those have LabVIEW drivers. Do you even know who created the original DLLs? Do you have the source code?As I'm sure you are aware, most of those VXI cards are no longer supported by the original vendors.