LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

MBR not being written to during install of RT to a Desktop Computer.

So, it turns out that the PC Eval disk will always fail after reformatting the hard drive in Windows, and then trying to boot from the Eval disk. The PC Eval says that everything is successful only after formatting a single(and only) primary partition on a hard drive, setting it to active, running the HD Format disc,  then running the Safe mode disk in order to boot up, configuring the target remotely to load on the RTOS and drivers.

 

I thought the PC Eval was supposed to check to see if your hardware is correct BEFORE you load the RTOS on it…. not afterwards, which appears to be the only way to run it without any errors.

 

I have tried numerous times to run the HD format disk at different points during this process, and I have gotten multiple errors. Some saying that it can not read files such as C:\hdmon.bin, to telling me that my floppy disk has errors and cannot copy over boot.exe to the C:\ drive.

 

I have used different floppy disks as the HD Format disk, and ran disk checks on them as well to make sure they were operating properly. MAX has never given me any problems while formatting these disks.

 

Considering this product costs over $3,000, I would hope that bugs like this would be fixed, and ‘unusual behavior’ would not be taking place. This entire situation has cost us a lot of time and money, and has put a strain on projects that we were expecting to be using RT with. The slow operation of having to use floppy disks, and slow formatting of the hard drive has made this a pretty painful and time consuming experience.

 

 

If nothing else, and a solution is not found within a few weeks, can the boot sector, mbr, and partition of a basic RT target(no drivers, etc) be sent so that we have something to work with? I’m seriously considering looking into modifying our MBR manually in order to get this hard drive booting on its own, since this seems like our only option at the time being. If you have any advice for modifying the MBR as well, I’m all ears.

0 Kudos
Message 11 of 13
(2,148 Views)
I agree that the installation process could be improved. Even the installation of LabVIEW on a Windows machine is very tedious. I believe putting everything on a DVD and letting the process run with an occasional prompt for user input would be much better than the 3hr 10-CD process that NI has currently. Now, coming back to the issue at hand, I have discussed what the Eval utility does with a very knowlegeable person at LabVIEW RT R&D. The reason a platform can pass the compatibility test and still fail LabVIEW RT installation is because the Eval utility only performs a limited number of tests. In my experience, most motherboards with multi-core CPUs will fail. I have tested 4 or 5 different duo-core motherboards without any success. Some fail the compatibility test outright, others pass compatibility but fail during the install process, while a third class installs correctly but fails to boot, even with the help of a boot disk. NI is aware of all this -- it is an active issue. Hopefully I'll get some answers pretty soon.

Thanks,

-C

0 Kudos
Message 12 of 13
(2,139 Views)
Thanks for the info chatonda! Seems like you've spent a lot of time on this as well.

What I'm going to try next is to go through the entire install process on another computer, but use the same hard drive. If I manage to get it installed on another computer, I'll just swap the HD back to the original computer I was working with, and see if I can get it booting without the need of a floppy. I have a few different computers over here to try it on... so hopefully one of them will work.

I'll post back if I have any luck... but for now this seems like the only quick solution I can think of.
0 Kudos
Message 13 of 13
(2,061 Views)