LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

8.6.1 install error "0x010e2754" memory could not be "read"

Ben,

 

One thing you might try, too, if the MAX database can't be fixed using the KB is trying to do a repair of LV8.5.  I know 8.6.1 can coexist with the others.  My laptop has 6.1, 7.0, 7.1, 8.0.1, 8.2.1, 8.5.1, and 8.6.1, and possibly 6.0.

 

Matthew

0 Kudos
Message 21 of 29
(1,017 Views)

The next three evenings are already spoken for (Grandaughter wins out over LV) SO I will execute the log version this week-end.

 

Send me a normal support e-mail at

 

bar@dsautomation.com

 

So I can reply when I have the log file.

 

I'll re-group when we have more info about his issue.

 

Thank you,

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 22 of 29
(999 Views)
Will do
Misha
0 Kudos
Message 23 of 29
(983 Views)
I hac exactly this same error with different address!  I tried many things and this was a new computer!  It ended up with a bad sector on the main hard drive, and I had to reformat the HD to find this out.  A new HD and lots of reinstalling did the trick.
0 Kudos
Message 24 of 29
(977 Views)

Ben,

 

Am I correct in that you don't have Labview 8.6 on your machine right now? As in, you're trying a clean 8.6.1 install, not upgrading from 8.6 to 8.6.1? 

In that case, don't forget that you can download a fully functional 8.6 evaluation here. I remember Christina suggested it, but I don't think we ever followed through and downloaded it. 

Misha
0 Kudos
Message 25 of 29
(964 Views)

Ben,

 

After reading about hounddog's experience, it also makes sense to check for erros on your hard drive. You can do this by using windows' checkdisk utility

Misha
0 Kudos
Message 26 of 29
(947 Views)

Yes clean install of 8.6.1.

 

Please send me an e-mail at

 

bar@dsautomation.com

 

and I'll forward the log file (it contains a bunch of serial numbers etc.).

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 27 of 29
(885 Views)

mishkin wrote:

Ben,

 

After reading about hounddog's experience, it also makes sense to check for erros on your hard drive. You can do this by using windows' checkdisk utility


 

Went through the full Windows checkdisk with a few blocks marked free that where in use but afterwards no joy. Smiley Sad

 

Send me e-mail and I will reply with log file.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 28 of 29
(881 Views)

log as been sent.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 29 of 29
(851 Views)