Hey, Microsoft almost bought Quicken too. There's a short list of companies hell-bent on being more evil than Microsoft, in the same field, like Real or Netscape used to be.
I think there might be a reason that it's a short list.
Now if he'd emulated a Bell 103 modem, he could have gotten 10 or even 30 cps rather than 5. If there's a controlled LED, that might have been another route. (If you open the case, it's even easier, but that's cheating!)
I did the Green Room for a science-fiction convention and sometimes we'd be in the supermarket with a huge pile of groceries, and no one had an Air Miles card. So we'd ask the person behind us if they'd like the credit on their card. (Air Miles claims there's no tracking and it's all statistical.. sure it is.)
No fire-starters in the party supplies that I remember, but it would make an interesting blip in someone's record. (Especially when we did the same in the liquor store afterwards. Hmm.. One bottle of wine and.. Holy Frack! Red flag their health and car insurance!)
Others have recommended all sorts of gaming platforms, but I think one of the most important things you're going to have to learn is project management and time budgetting.
You have a fixed deadline of June. You probably have some ideas about what kind of game you want to do. Create a design document. (Gamasutra has had articles about that. Links anyone?) Don't spend a lot of time on it--you don't have to justify this to the suits. You can start rough and refine it later as you get a better idea of where you're going. Start blocking out time estimates for various parts and keep track of it. (It's no good to wake up in May and try to bang it off on the fly.) Have a quick "status meeting" with yourself each week to see how you're doing and what needs to get done in the next week. Set project milestones. Keep a project log. (Hand it in with the project, it'll be good for marks.) If there's extra stuff that you're not good at, graphics, sound, etc, perhaps you can trade favours with friends who are? (Get permission, possibly retroactively.;) Have a Plan B for when your schedule shows that you'll be finished in August.
Technology comes and goes, but good time and management skills will pay off forever. Too many people in the gaming industry never learned those skills except the hard way, and that results in classic mistakes like continuous burn-mode, completely blown schedules and adding people to a late project. Don't spend more time planning than programming, but know where you're going and how late you are. Always wear sunblock.
Awww! But I've already got a sound effects + with a firewall program. Next I was thinking of a screen saver Tamagotchi-type pet that reacts to events from the firewall. (Too many *pings* and the little bugger goes hyperactive. Gotta fix that.)
Considering the UDP datagrams and even TCP requests that hit my firewall claiming to be from bogon-space, I wish them luck tracing forged IP addresses to the Martian Embassy. (A complete TCP session would be extremely difficult to forge, of course, but that's not what their "personal firewall" will be logging.)
Visual C++ 1.0 was a Windows front-end over their DOS-mode compiler. It was a real joy to keep blowing out real mode (640k) memory on a 16M+ box. (Even better was when it started running short, it would switch off some optimizations. Getting a consistant build was a nightmare.)
(d) tracing at least one of the traffic events utilizing the firewall; and
It doesn't work! The IP addresses of packets arriving at a firewall have no guarantee that they're really from that address. If it's a handshaking protocol like TCP, and if you open the port, let the syn/syn-ack/ack proceed, then you can trust the IP address--but that would be a strange thing for a "personal firewall" like McAffee to do on a blocked port. It definitely doesn't work for UDP IPs which are forged all the time.
Perhaps this patent can be booted just because their "invention" doesn't work as promised?
McAffee got a patent for displaying a map of where an incomming IP was from? Geez, some people hang some really dumb things on firewalls these days! (Unlike sound effects.;) Besides, unless it's a protocol like TCP with a completed handshake, the IP address isn't reliable. Datagrams like UDP routinely have forged IPs.
Slashdot Mirror
Don't dis Avi! He (with multiple authors) wrote a paper on how to automate a Slashdot snail attack (As in Spam King Al Ralsky.)
How would Avi Rubin do against Godzilla then?
A company that thinks they own a market niche by devine right always gets ugly. The oozing greed eventually backs up into the brain.
I think there might be a reason that it's a short list.
Now if he'd emulated a Bell 103 modem, he could have gotten 10 or even 30 cps rather than 5. If there's a controlled LED, that might have been another route. (If you open the case, it's even easier, but that's cheating!)
That would be 2.2 in RFC2396
It should be safe so long as the containment field doesn't fail.
No fire-starters in the party supplies that I remember, but it would make an interesting blip in someone's record. (Especially when we did the same in the liquor store afterwards. Hmm.. One bottle of wine and .. Holy Frack! Red flag their health and car insurance!)
The record for companies that were in 2001: A Space Odyssey very good. Pan-Am...
You have a fixed deadline of June. You probably have some ideas about what kind of game you want to do. Create a design document. (Gamasutra has had articles about that. Links anyone?) Don't spend a lot of time on it--you don't have to justify this to the suits. You can start rough and refine it later as you get a better idea of where you're going. Start blocking out time estimates for various parts and keep track of it. (It's no good to wake up in May and try to bang it off on the fly.) Have a quick "status meeting" with yourself each week to see how you're doing and what needs to get done in the next week. Set project milestones. Keep a project log. (Hand it in with the project, it'll be good for marks.) If there's extra stuff that you're not good at, graphics, sound, etc, perhaps you can trade favours with friends who are? (Get permission, possibly retroactively. ;) Have a Plan B for when your schedule shows that you'll be finished in August.
Technology comes and goes, but good time and management skills will pay off forever. Too many people in the gaming industry never learned those skills except the hard way, and that results in classic mistakes like continuous burn-mode, completely blown schedules and adding people to a late project. Don't spend more time planning than programming, but know where you're going and how late you are. Always wear sunblock.
Good luck and have fun!
They might be able to provide the domain name. Would that help? :)
Tune in next week when 133t theater performs Who Shot BSD?
Change the UserAgent to "iDidit". Then when the police ask who was hacking... (Using "iDiot" works too.)
I buy taylor made shoes, and my barber makes my suits.
Doesn't it use Curses? (Library for handling different terminal types.) Bummer if it doesn't work with my QVT-102.
I'd love to see their problem resolution flowchart that ends with the box "Call police!". It can't as simple as "Read logs. Are you confused? Yes/No"
15:00 Welcome our new cybernetic overlords, 16:00 ???, 17:00 Profit!
Awww! But I've already got a sound effects + with a firewall program. Next I was thinking of a screen saver Tamagotchi-type pet that reacts to events from the firewall. (Too many *pings* and the little bugger goes hyperactive. Gotta fix that.)
Considering the UDP datagrams and even TCP requests that hit my firewall claiming to be from bogon-space, I wish them luck tracing forged IP addresses to the Martian Embassy. (A complete TCP session would be extremely difficult to forge, of course, but that's not what their "personal firewall" will be logging.)
First they have to get a valid IP address. How do they get one from an incomplete TCP session or a UDP datagram?
Why duplicate an idea that doesn't work? (I thought an invention or idea had to work to be patentable?) My comment
Visual C++ 1.0 was a Windows front-end over their DOS-mode compiler. It was a real joy to keep blowing out real mode (640k) memory on a 16M+ box. (Even better was when it started running short, it would switch off some optimizations. Getting a consistant build was a nightmare.)
It doesn't work! The IP addresses of packets arriving at a firewall have no guarantee that they're really from that address. If it's a handshaking protocol like TCP, and if you open the port, let the syn/syn-ack/ack proceed, then you can trust the IP address--but that would be a strange thing for a "personal firewall" like McAffee to do on a blocked port. It definitely doesn't work for UDP IPs which are forged all the time.
Perhaps this patent can be booted just because their "invention" doesn't work as promised?
McAffee got a patent for displaying a map of where an incomming IP was from? Geez, some people hang some really dumb things on firewalls these days! (Unlike sound effects. ;) Besides, unless it's a protocol like TCP with a completed handshake, the IP address isn't reliable. Datagrams like UDP routinely have forged IPs.