Saw exactly the same behavior last night. I _think_ it is related to LV not being able to
get permission from the OS to access the serial port. Can you try rebooting the PC and
going straight to your LV app (without running hyperterm), then shutdown LV, then try
hyperterm, then back to LV? I'll be trying the same here later today and will report
back.
Matt