Mod parent: -1 (Bad advice)

Frank, honest communication is one of the pillars of a lasting business relationship. Hiding things from your employer is only likely to cause more problems later when it comes out, with potential consequences ranging from a soured relationship with your boss all the way up to an expensive, bitter lawsuit. (Not to say you'd lose the suit, but I can certainly see it happening, and it's something you don't want to be involved in.)

Definitely bring it up, and definitely make separate arrangements for use of the IP. I would have that complement your salary rather than being a part of it. Not only is there the chance you might sell the IP elsewhere, but what happens when you leave? On either good terms or bad? As an employer, if I hire you, it's because I think you (and your knowledge / capabilities / skills) will be an asset to the company. I would not put myself in the position of bringing you on, becoming dependent (to any degree) on your IP, and then having you rip that out of my company when you leave.

Granted, on some level we employers EXPECT to become dependent on some level on our new hires' skills and abilities. But that particular person we hire does not have a monopoly on skill or ability, so if they get hit by a truck / leave / whatever, they can be replaced, though perhaps not easily.

With patents, you DO have a guaranteed monopoly on that particular benefit you can bring to the company. If you were applying to work for me, I would want to arrange -- perhaps parallel to your salary -- a separate licensing agreement for the IP. At the very least, I would require a perpetual (or at least renewable-at-my-option-under-original-terms), non-exclusive license to any IP that make their way into the business's core operations. I'm not saying I'd require that for free, but without the guarantee that bringing you on wasn't going to cripple me in the future, I would definitely not hire you at any price.

The simple fact that you were capable of developing the patented methods that I find important adds to your value as an employee, and therefore to the salary I'd be willing to pay.

Disclaimer: I consider myself a high-integrity businessperson, so I could be overlooking some way that a scoundrel would try to take advantage of you. Get a lawyer's advice on the contract. And don't apply to work for any scoundrels anyway, because that's just asking for trouble. ;)

Simple. Just write a custom driver on both the Windows and Linux boxes to handle both ends as described (you'll want the traffic duplicated both ways, I'd imagine, since you're not just dealing with one-way communication here).

I doubt there's anything off the shelf that will handle what you want. Sounds like a fun project... but don't undertake this unless you think the project will be as fun to work on as actually playing your game. And be prepared to drop a hundred hours into it (depending on your coding abilities and familiarity with the associated APIs).

Great for you. Now try doing the same thing on $30 of hardware that draws 5 watts. (And no, a crappy old computer doesn't count.)

"As long as no red flags are raised in the experiment, we plan to move forward with the project in November," said top engineer Fedwick McGillicutty. "Our hope is that, by reversing time itself, we can do away with the whole debacle that is 'daylight savings time.'"

Of course, LotR is really three books... (Or six. Or seven. (Depending on how you count them.))

The population of the US in 1790 was 3,929,214.