Problem loading VI's on a different laptop

[Scott in New Mexico]

I've done some LabVIEW 6.1 development on a laptop
that was dropped and is no more. I had backed up my
work by copying my development directory to CD.
I've built another laptop but when I try and load
my top level VI I get this error:
"A bad argument was passed to a manager function. An
error occurred loading vi (vi name) LabVIEW load error
code 33: could not load front panel data logging and
retrieval information."
I've searched this forum and tried various things.
It is a different brand of laptop but I made sure I
have all the latest drivers, same operating system,
same DAQ card, same directory structure (best I can
remember). I can create and run new VI's just fine
but I can't load my old ones. I'm new to
LabVIEW so
I'm wondering if I did something wrong with the way
I first created and saved these VI's. I've asked my
boss to buy me LabVIEW 7 but for now I'm stuck using
this. Am I screwed?

[Joe_Guo]

I think the drop shifted the arguments to the wrong places 🙂 .

Do all the old VIs experience the same problem? When you check the propery of the files, what do they show? Can you upload one small vi that we can try it out? Maybe someone has the system than can open your file.

-Joe

[Brian_Powell]

I'm not an expert on the front panel data logging, so I'm not exactly sure what's the best solution. It sounds like the VI has a reference to the front panel datalogging file that you were using, and it's unable to load this datalog file. I'm surprised that this is a fatal error.

You should first ensure that you actually have this datalog file. It probably either needs to be in the same place relative to the VI as on the old system, or it might have to be installed in exactly the same directory as the old system. You might try both.

I suppose it could also be that the datalog file is present, but somehow got corrupted. You could also try removing the datalog file, and see if the VI will load successfully without it.

Sorry I can't be of more help. Y
ou may end up having to post your VIs and datalog files.

Brian

[Scott in New Mexico]

I borrowed a couple laptops today (IBM Thinkpad, Dell
Latitude) and finally got it working on the IBM. The IBM
screen resolution only goes up to 1024x768 so I gotta
fix that now but I can live with this. Things still
did't work on the Latitude or my old Sager. Maybe it
is a driver thing but the error doesn't suggest that.
My problem is only with the top-level VI's. I have a
few sub-VI's that don't do much and I can edit them ok.
File properties look ok. On the Dell when I load my top
VI's LabVIEW starts searching and then says it cannot
find the VI that I just tried loading. Kinda wierd.
Why can't it find the VI that I just clicked on?
Unfortunately I do not have internet access at work
(typing this at home) and security won't l
et me
take stuff out (paranoid). I was hoping this was a
simple mistake that I've done when I first created and
saved these VI's. So I guess I need to buy a IBM laptop.
I'll keep trying to get it working on the Dell or Sager.

[Scott in New Mexico]

I'll try this tomorrow but since I got it to work on
the IBM but not the Dell or Sager I don't think it is
this. Plus I'm pretty sure I never turned any logging
features on unless it is on by default. I enabled
debugging but not any logging. I can't access the
original laptop hard drive anymore so I don't know
what the path should be.

Thanks guys for the advice. I'll let you know if I
figure it out.