Mert,
I figured out what was causing my program to act up on me in Vista.
1.) Vista is the problem, first off.
2.) My com write and read functions are fine where they are, but in XP, those operations are faster!
3.) In Vista, my com read functions needed a delay after and apparently before for stability. I added a half second delay before a read operation.
4.) It's not CVI, and I don't know if the 8.5 runtime engine is necessarily needed for creating a Vista installation package.
5.) I knew that MS was the culprit of my problems. I had to download the evaluation software v.8.5 CVI to debug the problem in the source of the problem, Vista. After I did just that, I set breakpoints around my reading functions and found that I wasn't getting all the bytes that I requested in the ComRd function. Vista has some crazy stuff going on in the backgound that most users don't know about and can't configure. What a pain.
6.) My indication that I was offline was that I wasn't getting the correct information about my module updated to the GUI regularly; I was getting a ton of garbage data for my device's firmware version and other EEPROM stored data items. This was tough becuase CVI's program wasn't crashing or anything like that. I wasn't fully reading the input buffer in the CPU. Once again, works in XP and any other MS OS earlier, but not in the new flagship OS. I really don't care for Vista too much as you can tell. Things like this make me become agitated. Anyhow, I know what I am dealing with. Thank you everyone for trying to keep me brainstorming.
Have a great day to whomever reads this,
Chrisg101080
