Trouble setting up PharLap ETS LabVIEW RT 8.2

[ndo]

Hi Mark,

I have tried re-installing LabVIEW RT several time (even re-partitioning my hard drive to 10 GB & going through the entire install process).  I currently don't have any other versions of LVRT.   I will try to find a way to scan the disk.

I may have to use this system in a limited maner until I'm ready to upgrade.

ndo 

[NicoLeach]

1) You wrote earlier that you owned other targets with the same software configuration.

Do these target share the same hardware configuration, too?

2) You wrote earlier that your target has a FAT32 partition. Is this the only partition on the physical HDD?

Best regards,

Nicolas

[ndo]

Hi Nicolas,

To answer your questions:

1) No.  The computer on which I am trying to install LVRT is a Micro ATX architecture, while the others are industrial PCs.

2) Yes.  The hard drive is120 GB Samsung PATA drive, model HM120JC.  It has one 10 GB active FAT32 partition.

Regards,

Ndo 

[NicoLeach]

You could try to swap your ETS disks between your targets => it should help to know if your problem is related to your target or to the installation you've made.

If you can put your hands on another MB, it could be worth trying it.

Best regards,

Nicolas

[Sappster]

Hi Ndo,

Here is another copy of the dlls in questions. They are the 8.2.1 versions. I would expect since you have reinstalled several times that replacing the dll on your system with these won't change anything, but it's worth a shot.

Let me know if you are able to scan the sectors on the hard drive.

[ndo]

Hi Mark,

As you have guessed, the 8.2 versions you the DLL's did not work and also caused the system to freeze.  I tried once again to install LVRT from scratch.  I created a 10 GB FAT32 primary partition, formated the disk and performed a disk scan.  Everything clean.  Still the same problems.

Ndo 

[Sappster]

Hi Ndo,

Do you have any other systems you have setup with the same software or discs? Or do you have another computer we could swap the hard drive into to verify that it isn't hardware related? I don't think that it is a hardware issue, but we might as well eliminate the possibility.

I'm still working to try and find out what might be the cause of those dlls not loading properly.