Labview 7.0 install, Windows XP mode, LVCore10.cab error 1335

[corsaro]

Hello, I am trying to install Labview 7.0 in Windows XP mode. The laptop is running Windows 7 professional 64bit.

I receive the following error during installation:

"Error 1335. The cabinet file 'LVCore10.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package."

Labview installs fine directly in Windows 7, so I assume there are no errors on the CD.

I have also tried copying the CD to the virtual XP's C drive and install from there, however I get the same error.

The reason I am trying to install Labview, in virtual XP mode, is because I will also need to use DAQmx 8.1, and this will not install on Windows 7 64bit.

[Bob_Schor]

I don't think I've ever used Virtual XP Mode in Windows 7, but here's a question -- is that Virtual Windows 7 32-bit or Virtual Windows 7 64-bit?  If the latter, could this be the root of your problem?  [I tend to use VMWare VMs, myself ...]

Bob Schor

[corsaro]

I'm not sure what you mean by virtual Windows 7.  The OS on the laptop is Windows 7 Professional 64bit.  When I click on Start->All programs, there is a folder named "Windows Virtual PC", and it has a sub-folder named "Windows XP mode".

As far as the host OS being 64 bit, Labview installed on it without problems. The Labview 7.0 installer only seems to have problems in the virtual XP machine (virtual XP mode). After several hours of googling this does seem to be a Microsoft problem, not NI. However I can't blame Microsoft, they seem to have bent over backwards to accommodate  XP users.

I have found several suggestions but none have helped.

Copying CD contents to hard drive:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019L3ISAU&l=en-US

Changing XP emulator memory setting in boot.ini:

https://answers.microsoft.com/en-us/windows/forum/windows_other-gaming/error-1335-while-trying-to-in...

Last thing I tried was learning about CAB files to maybe find a hint to a solution, but I did not.

https://www.lifewire.com/cab-file-4144227

[RavensFan]

Take a step back.  What are you really trying to accomplish here?

Why not use modern software on a modern OS?

You are trying to run a 15 year old version of LabVIEW on a virtual machine of a 17 year OS under a 9 year old OS.  Without even talking about drivers, that is a lot of old software hoping it all works well together.

[corsaro]

I agree that it sounds like trying to fly against the wind in an ultralight, but there is a reason.

The customer I wrote the program for, ten years ago or more, has asked for a small change. There's one constant that needs to be changed from 65mph to 57mph. I can't charge him 3k for that. Had I had some foresight, all the constants would have been in an editable file, but they are not.

At the time, I was able to simulate the NI hardware, on my old xp laptop, with DAQmx, then compile. I am just trying to set up the same development environment. The original laptop that the work was done on has long since expired.

[RavensFan · Accepted solution]

I wonder if there is any chance that the constant is saved/buried somewhere within the .exe and that doing some byte editing would effectively change that.

I would consider trying to find the oldest PC you can get your hands-on and install XP and LV7 on that.  Don't try to complicate the situation with using virtual machines.

Other possibility.  Use a bit newer LabVIEW  (7.1, or even all the way up to 2015 SP1 which still has XP support).  Upgrade the development to a newer LabVIEW.  I think with the correct build settings, you can still develop on Windows 7 and have the executable be compatible with Win XP.  Of course you'll have to get the customer to install the run-time engine for whichever version of LabVIEW you use.    See https://www.ni.com/en/support/documentation/compatibility/17/labview-and-microsoft-windows-compatibi... for version comparisons.  I can't guarantee that something else might not break, but I think the process will be less painful than trying to put together an ancient combination of software, OS's and virtual machines.

[corsaro]

---

I would consider trying to find the oldest PC you can get your hands-on and install XP and LV7 on that.  Don't try to complicate the situation with using virtual machines.

Yup, at this point it appears that that is the most sensible solution. I had never tried xp mode, and it seemed to be working fine for most people.

[corsaro]

Just for completeness, the following hack seems to have worked.

1) Install Labview 7.0 in Windows 7, using compatibility mode xp

2) Copy the folder C:\program files(x86)\National Instruments (in Windows 7), to the virtual XP folder c:\program files

3) From the virtual xp, install Labview 7.0 from the original CD.

DAQmx 8.1

In virtual xp:

1) In folder C:\Program Files\National Instruments\NI-DAQ\HWConfig

Rename file daqConfig.llb to daqConfig_old.llb

2) Copy the DAQmx installation files to a folder in the virtual xp and install from there.

So far Labview is working, and I was able to create a virtual PCI 6601 card in Measurement and automation explorer. I have not yet tried to load original (old) vi, modify it and recompile it.