LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview 3.1 file

Solved!
Go to solution
Hi all I'm a newbie in this. We have a verryyyy old PC with labview 3.1 on it and last week we have purchased new Labview software. When i tried open saved file from 3.1 on my new 8.6 I got the msg. that my file is too old. So my question is: Is there a way to make this conversion.
0 Kudos
Message 1 of 13
(5,189 Views)
Solution
Accepted by krasnal

Hi there,

 

You're going to need at least one intermediate conversion before opening your code in 8.6 

 

If you can, I'd suggest posting your code here.  There's a few people on the boards that still maintain older versions of LabVIEW for just this sort of thing. 

---------------------
Patrick Allen: FunctionalityUnlimited.ca
Message 2 of 13
(5,186 Views)

Take a look at this link.  http://zone.ni.com/devzone/cda/tut/p/id/8387

 

Not only will you need an intermediate version of LV, you will need a conversion get to get the LV3.1 files to LV4.

 

If you still have a working copy of LV3.1, I would recommend opening up the files in that and documenting them such as printing them out.  Then recreate from scratch in LV8.6.

 

It will save a lot of trouble in conversion, and there is no guarantee the conversions will work properly.  So many fundmental VI's have changed even since LV 7, that you should do a lot of editing anyway.  Even if by some chance the converted VI's did work, the front panel will look ancient by today's standards.

Message 3 of 13
(5,138 Views)

Hello, I've found some old floppy's and want to make backup's from then until I have a pc with a FDD

but I'm a little late, so here we are:

 

File request, my LabView 3.1 floppy's are not in good health, I guess bad sectors.

 

I would need from disk 1 of 4 this file:

ZADVD.LL_

 

and from disk 4 of 4 this files:

LVSE.EX_

SMPLSERL.LL_

 

Regards chatnick

 

0 Kudos
Message 4 of 13
(4,872 Views)

I would suggest you contact NI tech support directly. They may still have some LV 3.1 floppies around.

0 Kudos
Message 5 of 13
(4,864 Views)

Have you tried running chkdsk /f or recover from the command prompt as an attempt to recover the files or the disk?

 

Maybe I am showing may age here 🙂

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 6 of 13
(4,851 Views)

Hi chatnick,

 

Here's a list of the files that I believe you were referring to as well as an explanation of what they are and how you would get them:

 

ZADVD.LL_ = ZADVD.LLB:  Contains VIs associated with the NI-DAQ driver (Traditional DAQ) => Install Traditional DAQ

LVSE.EX_ = LVSE.EXE:  Some people use LVSE to refer to LabVIEW Signal Express, but I believe this .exe is actually the LabVIEW Student Edition 3.1 => Install LabVIEW Student Edition

SMPLSERL.LL_ = SMPLSERL.LLB:  Contains LabVIEW shipping example VIs associated with NI-VISA => Install NI-VISA (default path = C:\Program Files\National Instruments\LabVIEW XXXX\examples\instr)

 

I hope this sheds some light on the issue!

 

- Greg J

0 Kudos
Message 7 of 13
(4,808 Views)

Greg, you do realize that chatnick is trying to resurrect LabVIEW 3.1, right? He has the installation disks - he just can't read them. Have you seen LabVIEW 3.1 available for download at the NI site?Smiley Wink

0 Kudos
Message 8 of 13
(4,799 Views)
Missed it by that much, may be worth downloading and unzipping to see if files are there, it may work ftp://ftp.ni.com/support/labview/windows/updates/win3x/31-to-311/ -AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 9 of 13
(4,786 Views)

Unfortunately, downloads are not available online because LabVIEW 3.1 is no longer officially supported.  However, there is a link to the LabVIEW 3.1.1 updaters on ni.com that AnalogKid referenced on the ftp site.

 

But back to the bigger picture... chatnick, if all you need is a replacement of your NI software, then NI will gladly replace your installation files.  The first step will be to contact your technical sales representative.  If that doesn't work for you, please post back here and let us know.

 

Thanks!

 

- Greg J

0 Kudos
Message 10 of 13
(4,783 Views)