How to set up ETS

[John_Smith]

I am running LabVIEW 8.2, MAX 4.1.0.3001 and cannot boot from the hard drive (only USB). Upon system restart, the error "non-system disk" is returned and when attempting to standard boot the LV RTOS, it defaults into safe mode. Perhaps boot.exe requires updating? I don't know how to find out what version of boot.exe I'm using or how to update it. Also, when I run the USB option to analyze hardware for compatibility with LV RTOS, it gets to "starting the IP stack...initializing network..." and returns the error "unable to configure the primary network device, IP stack configuration error." I have the NI PCI-8232 ethernet adaptor and have been able to communicate with the host, upload software, change the target's IP address and reboot the target remotely (even get to the "Welcome to LV RT!" message), but the hardware compatibility routine returns errors and I can't boot from the hard drive. I installed the deployment license and created the boot USB on this computer, but the host is another PC - could this be the source of my problems?

Thanks for viewing,

John

[Elizabeth_S]

Hi John,

Are you getting these errors when you run the LabVIEW Real-Time PC Eval utility?

Are you connected to a DHCP server?

Requirements for a Desktop PC as a Real-Time Target
http://digital.ni.com/public.nsf/allkb/440BAF128AA75F95862572580081EB3D?OpenDocument

How Can I Test My PC For Compatibility with LabVIEW Real-Time or LabWindows/CVI Real-Time for Desktop ETS?
http://digital.ni.com/public.nsf/allkb/82D66505D86349F38625722C00736AB8?OpenDocument

Real Time PC target ethernet problem
http://forums.ni.com/ni/board/message?board.id=170&message.id=214322&requireLogin=False

[John_Smith]

Hi Elizabeth,

Thank you for your suggestions. I connected the target over our network and that seemed to resolve our "IP stack" error. The RT PC Eval utility now runs with no errors. We managed to solve the "non-system disk or disk error" by flagging the partition on which the boot.exe was installed as bootable (the USB utility disk failed to do this during initialization).

Thanks again,
John