You can probably go with 802.11b to do this, too. There is not a DSL or cablemodem link that you can get which is going to saturate a 11 Mbps 802.11b, and I have yet to see an a/g card on the market which is not backwards compatible with b. When in doubt, definately go with the most reliable technology, as b has been out the longest and its implementations seem to have the fewest problems.
I've been a fan of Borland Delphi for many years now. After trying VB, MSVC++, and Delphi, I found Delphi the easiest to use. Its native code dependencies make it easy to deploy applications without worrying if the user is running the latest version of the MS C++ runtime libraries (MFC), and the ever growing library of natively written code makes it easy to deploy all kinds of applications. I do have one giant complaint about Borland, though. They make little effort to fix known and documented bugs in their software.
About three years ago, I found a bug in the implementation of the virtual list view. I filled out their online bug report, giving in excruciating detail an explanation of what the problem was, why I thought it was happening, and exactly what had to be done to reproduce it. Three days later, I got a response that the bug was verified as existing, had been cataloged, and would be fixed in the next update. That was in Delphi 5.0.2. Now, 3 years later, they're on Delphi 7, and the bug still hasn't been fixed. Talking to colleagues of mine, I have found other examples of the exact same pattern: Bug gets reported, bug acknowledged by Borland, bug never gets fixed.
Borland really needs to fix these kinds of problems, as they only lead to frustrations for programmers. If they're going to take the trouble to catalog and verify bugs, they really need to go one step further and fix them.
I agree that this action does look suspicious for a couple of reasons, but one thing that I think is important is that under payment options, COD is accepted.
The ultimate buyer (assuming the reserve ever gets met) would be a fool not to use this, as if the shipping company did not show up with the size equivalent of two refrigerator boxes full of games, it could be returned without a $20K+ loss.
Slashdot Mirror
You can probably go with 802.11b to do this, too. There is not a DSL or cablemodem link that you can get which is going to saturate a 11 Mbps 802.11b, and I have yet to see an a/g card on the market which is not backwards compatible with b. When in doubt, definately go with the most reliable technology, as b has been out the longest and its implementations seem to have the fewest problems.
I've been a fan of Borland Delphi for many years now. After trying VB, MSVC++, and Delphi, I found Delphi the easiest to use. Its native code dependencies make it easy to deploy applications without worrying if the user is running the latest version of the MS C++ runtime libraries (MFC), and the ever growing library of natively written code makes it easy to deploy all kinds of applications. I do have one giant complaint about Borland, though. They make little effort to fix known and documented bugs in their software.
About three years ago, I found a bug in the implementation of the virtual list view. I filled out their online bug report, giving in excruciating detail an explanation of what the problem was, why I thought it was happening, and exactly what had to be done to reproduce it. Three days later, I got a response that the bug was verified as existing, had been cataloged, and would be fixed in the next update. That was in Delphi 5.0.2. Now, 3 years later, they're on Delphi 7, and the bug still hasn't been fixed. Talking to colleagues of mine, I have found other examples of the exact same pattern: Bug gets reported, bug acknowledged by Borland, bug never gets fixed.
Borland really needs to fix these kinds of problems, as they only lead to frustrations for programmers. If they're going to take the trouble to catalog and verify bugs, they really need to go one step further and fix them.
Actually, Windows 95 came out on August 24, 1995. And its spelled Prodigy. There are more errors, but I don't have the time.
What happens when they enter the wrong IP address into their DoS client and eBay gets knocked offline?
Of course, the first patent infrigement case for this will involve the 'fuzzy logic' analysis of the criteria.
For example:
"But our code is far more fuzzy than theirs!"
There is a combination keyboard/controller in the works, per this previous post.
I agree that this action does look suspicious for a couple of reasons, but one thing that I think is important is that under payment options, COD is accepted.
The ultimate buyer (assuming the reserve ever gets met) would be a fool not to use this, as if the shipping company did not show up with the size equivalent of two refrigerator boxes full of games, it could be returned without a $20K+ loss.
My personal favorite is www.salshdot.org. It pulls up the slashdot page in a frame, and has its own banner ad frame at the bottom.