the time is near, I can smell death in the air, yup, the research presentation is due in a few days. I still haven't gotten the program to do anything productive. On the bright side, I actually got my hands on the CommunicationsSDK API, so this might help me with some stuff. But then after spending about two hours on it to figure out the structure, I found out that it's actually a chain of programs, and the one sent to me from cloudcap actually doesn't do anything productive. With the chain of pointers and stuff I'm pretty much left trying to figure out how to use it without the certainty of it actually working at all. One of the most disappointing thing about this is that it appears that the main program, made for most users were written in MSDN, which we can't use on the plane. We're using LINUX, cuz we're cool like that. So while I was searching for this stuff, I found out some guy from MIT actually did what I'm doing for about a quarter of his master thesis. He is also installing it onto the PC104 and then writing some sort of simulator. This is a CS guy too. Uninspiring, hell yes. Okay, so I was just extremely confused in reading the code because it keeps referring to COM1, which I knew for a fact didn't exsist in Linux, so i e-mailed the guy from cloudcap, and he replied "yes, it works" and i'm like... "okay, shit, tell me more." I'm starting to get really annoyed with the guy from cloudcap. Okay, also, the code he sent me makes me pick a constant, I don't know if this is a typical thing to do, but picking a constant for the serial buffer size before anything could be compiled? who knows. Today, I should be trying to get it to work more. Comeon!!!