3E. To confirm that it works, type qbasic in the DOS window. (The working directory should be the directory that now holds QBASIC.EXE.) The window will be filled with the QBasic system:
At this point, you could run QBasic by starting a DOS window, changing to the subdirectory that holds QBASIC.EXE, and typing "qbasic" at the command prompt. But it is more convenient to be able to run QBasic from any subdirectory.
This sounds so exciting. Let me ask a few questions. If I understand you I can get and install QB64 v1.5 on my windows 7 laptop? Now the big question, the code I had written using Quickbasic 4 will it run using QB64 or do I have to modify some of my coding to get it to run? That's important for me to know since I really don't feel like rewriting anything since it often leads to many headaches. If I remember when I developed this application all I would have to do if I remember correctly use a command something like QB\L and then some object modules. Anyway Cast thank you for your attention on this matter and I will anxiously wait for your response.
YesI have test the cablethe qbasic program and the labview program. I can use the cable and qbasic programe to control my machine very well. And I can use labview to send and receive from one pc to another.
I think what you said is right. The qbasic command PRINT #1 maybe modify the sending data a little bit, for example, add some additional letter before or after the command. But I don't know what it is.
I have no idea why your qbasic program would stop at line 40 and say device timeout. If anything, it would stop at line 60 if it is waiting for data to come into the serial port that never comes because you didn't write your LabVIEW program in a way to send back any data like your device would do.
356178063d