If M$ is allowed to pay that 1.1 billion using the retail value of it's software, then that's not even going to start to hurt them, given their profit margins on software. I don't know what the cost for M$ to produce a bulk CD is, but I'm betting it's waaaay lower than the retail price for the software on it. And most of the software would be one CD + a bunch of license keys, anyhow.
Re:OpenBSD is INSECURE, try Cryptech RAP BSD
on
OpenBSD 3.4 Released
·
· Score: 0, Redundant
Oh my, how can someone moderate a joke "informative"? Cryptech Radicacally Advanced PowerBSD -- C.R.A.P. And misspelt crap, as well.
No, much worse. This is a quote from their privacy statement (my highlighting though):
What software is on the host computer:
Information about software installed on the host computer may be accessed and stored on our servers. We may identify the existence or non-existence of certain software titles on the computer (including GAIN-Supported Software), as well as their version numbers, so that we can determine whether to take steps to offer new software that does not currently reside on the computer, to offer upgrades to the software that does currently reside on the computer, or, following the release of new versions of GAIN-Supported Software, to automatically upgrade, at GAIN Publishing's discretion, GAIN-Supported Software that has previously been downloaded onto the computer. We may also utilize this information to determine whether the users' of the computer are in compliance with The GAIN Publishing Privacy Statement and End User License Agreement.
A crowd of about 300 had gathered in one of Full Sail's larger classrooms for the monthly meeting of the Orlando chapter of the International Game Developers Association. Our guest speakers for the night were Infinium Labs, the company behind the oft-maligned and highly mysterious Phantom console. They were cautious with information, and while they did spill some details about the system, it's hardware, and their business model, they left a lot of critical questions unanswered. It was information about The Phantom, however, which until now had been almost non-existent.
The speaker for most of the presentation was Robert Shambro, one of two large Italian fellows who looked like they could moonlight as enforcement agents for various underground loan agencies. Rob spoke eagerly and seemed genuinely excited to present the Phantom and it's details to the crowd, but there was definitely a shiny coating of PR and spin covering the words of his oration. The other speaker was a third man, a generally non-descript laid back fellow by the name of Tim Roberts, who is the CEO of Infinium Labs. He answered a few questions but for the most part Rob did all the talking.
Yes, they did bring an actual Phantom "console" to the meeting. It looked exactly like the mock ups on the Infinium Labs website, and was about as big as a standard PC-- just picture your home desktop laying on it's side. Yes, it even had that glowing blue Phantom logo on the front. There were no visible controller ports, however there were some USB ports in the back, along with various outputs for S-Video, Component, A/V, a few USB ports and even a FireWire connection.
The Hardware
One of the first topics in the presentation was the Phantom's hardware. It was markedly different from what is listed on their website and in their promotional video, however Rob stressed that it was a beta box and that it may upgrade before release. They listed a 1.8Ghz Pentium 4 processor, 256mb of RAM (didn't mention what type) which could be upgraded to 512 or a full gig. An 80 gigabyte "storage device"-- no further specs than that were given. Rob also mentioned the system would be using "NVidia's NV36 graphics card." All the controllers and peripherals were made by Logitech, cord connected at first but wireless if you upgrade. He also said that currently the box was running on a standard ATX motherboard, which explained the console's size. Rob said he'd like it to be smaller but that's dependent on pricing issue, of course. He then went on to say that they had but five of these prototypes, which goes in direct contrast with previous statements from Tim Roberts that they "have several hundred prototype models here in the office." Well, perhaps those were earlier (Alpha?) prototypes.
As far as specs go, that's all we got. There are lots of little details missing-- RAM type, bus speeds, etc etc... technical as they are, they really make a difference in a high performance gaming machine. Again, Rob stressed that this was a Beta version of the hardware so things were subject to change.
Basically, the hardware is presented as a fair-to-middling PC. It even runs on a "specialized" Windows XP kernel. Now remember, consoles can get by with slower processor speeds and less RAM because they have very powerful hardware configurations made solely for pushing polygons around on screen. Also, most games run at a low resolution compared to your computer monitor. When questioned, Rob stated that the console is aimed for TV use.
Next topic was protection-- keeping the user out of the Phantom's hardware and software. He very quickly listed off lots of technologies and encryptions, nothing on the software end was out of the ordinary but some of the more interesting hardware ones were "Case Intrusion Detection" and "Epoxy Encapsulation of Critical ROMs." Yes, no going inside your own hardware for you, young gamer.
More and more governmental bodies consider switching from closed (read: MS) source to open source software. With this change, they become more reliant on OSS existing and flourishing. Thus, the power of the patent mongers should wane.
Hey, we've been kicking butt in FPS ever since Clan Nine took out Thresh's gang (I forget what they were called) in Quakeworld championships... 8 to 2.
What's he's done isn't comparing oranges to oranges. To use your car analogy, he's been comparing acceleration, braking distance and top speed for a sports car, a bus and a main battle tank.
Sure, the comparison is valid, you can compare those elements, but are the results relevant? Not many would use OpenBSD in a performance (as in speed) critical role, and not many would expect Linux to have the security track record of OpenBSD.
If I'm going to war, I'll take the tank. If I'm going to race, I'll use the sports car. And if I'm taking 40 friends to the mountains for some skiing, count me in on that bus.
I'm not an OpenBSD dev member, but I am someone who started out with Linux (Redhat 5), trying some distros (SuSE, Mandrake, slackware), before moving to FreeBSD and then to OpenBSD, where I've stayed. I prefer the stability and security to performance and features. But then, I have no need to serve 100.000 hits per minute off a 386, nor do I need to support all the latest hardware and whizbang features.
The reviewer does sound a bit biased towards Linux. In the same way Bill sounds a bit biased towards Microsoft.
It can under special circumstances. If both NAT firewalls are "game-friendly" and keep a list of outgoing UDP packet destinations from port X, will send UDP datagrams to several destinations from the same source port and will direct incoming UDP packets on that port back to the original sender, you could do this:
Client A sends an UDP datagram to server
Client B sends an UDP datagram to server
Server sends originating IP and port for the other client to both clients
Both clients use that information to send UDP datagrams to each other
The NAT firewalls should then hopefully forward the incoming UDP traffic. Note that this won't work with TCP, only UDP.
Looking inside the archive, one will find a file called ihvtest_readme.txt. Doesn't have to mean that this is an IHV-only source code tree, it'd make sense to have stuff like that on the main branch, I think.
Snippet:
-Make sure you have the processor pack/msdev sp4 installed.
-type "buildall" to build everything
-type "run" to run.
You will get higher performance if you disable some of the timing code.
To do this, edit src/common/MaterialSystem/ShaderDX8/CMaterialSyste mStats.h and change:
#ifdef IHVTEST
#define MEASURE_STATS 1
#endif
This is a digital world. Evidence is easy to fake and destroy. Picture a scenario where I download a BO (back orifice) client to my machine. Then it's up to the attorney to prove that someone didn't use that BO client to download things, first to my computer and then FTP:ing them to their own.
"The double-blind laboratory tests -- meaning no one in the survey knew if a base station was transmitting signals or not -- exposed test subjects to levels of radiation average for third generation networks when they become commercial in coming years."
More high frequency radiation. Just what we needed. Now someone will tell me that all those radiation sources (2G, 3G, wireless LANs, digital handsets, etc) don't add up, and each must be considered individually. Sure. Tell that to your sterile grandchildren.
Well, in case you haven't noticed, cell phone antennas get put up on buildings, and beam right into people's bedrooms. Not intentionally, of course, but since it's not proven dangerous (to the minds of the cellphone companies), they don't give a shit anyway.
I've wrote an OO language back in 1993 that's being used by two medium-sized companies. It's garbage collected, and it's kernel is written in C. The language is not interpreted; it gets translated into C and then compiled. The applications written with the language are fairly large. The source code of one is 28MB uncompressed. I'll skip the general implementation details, and just go over the garbage collection approach I used. These definitions are true for that language; they're not meant to be general.
A program variable is either a global variable, a stack variable, a class variable or an instance variable. Global and stack variables are held in lists. Class and instance variables are kept inside objects.
Every class object has a global variable that always refers to it.
Any object that is not, and that can not become referenced (directly or indirectly) by a global or stack program variable is garbage.
Each object has a 'not-garbage' flag.
For each global and stack variable, if the referenced object is not marked not-garbage, mark the referenced object as not-garbage, and recurse for that objects contained variables.
Delete all objects that are not marked not-garbage.
There are a few more twists, like handling return values on the stack, but this algorithm correctly handles self-referencing objects no matter the complexity.
And 15" may be pushing it. It's closer to 20".
It's also a 20" flat panel display, so I'm not too worried about my eyes; that site does seem to say that it's OK to sit closer to FPD's.
Exactly why aren't you supposed to sit close? I'd think that as long as I can read the text clearly, what's the problem?
"In fact, if you just sit directly in front of the display at about 30" away, as you normally do with any display, you will be in a position where you see 3D."
Thirty inches (75 cm)? I don't know about you, but I'm more like fifteen inches from the screen. At 30 inches, I couldn't read the damn thing.
"The protocol itself is derived from the Open Software Foundation (OSF) RPC protocol, but with the addition of some Microsoft specific extensions."
Now, why is that relevant? Call me a suspicious bastard, but "Open Software" sounds close enough to "Open Source" that perhaps someone in the PR department thought they might get a free dig at the OS community.
Aw, what do I know. Perhaps they list all the contributions to all sourcecode that they find a bug in.
Slashdot Mirror
...or are they experiencing one of the drawbacks of an uncontrolled (as opposed to UN-controlled) internet: The Slashdot Effect.
If M$ is allowed to pay that 1.1 billion using the retail value of it's software, then that's not even going to start to hurt them, given their profit margins on software. I don't know what the cost for M$ to produce a bulk CD is, but I'm betting it's waaaay lower than the retail price for the software on it. And most of the software would be one CD + a bunch of license keys, anyhow.
Oh my, how can someone moderate a joke "informative"? Cryptech Radicacally Advanced PowerBSD -- C.R.A.P. And misspelt crap, as well.
What software is on the host computer:
Information about software installed on the host computer may be accessed and stored on our servers. We may identify the existence or non-existence of certain software titles on the computer (including GAIN-Supported Software), as well as their version numbers, so that we can determine whether to take steps to offer new software that does not currently reside on the computer, to offer upgrades to the software that does currently reside on the computer, or, following the release of new versions of GAIN-Supported Software, to automatically upgrade, at GAIN Publishing's discretion, GAIN-Supported Software that has previously been downloaded onto the computer. We may also utilize this information to determine whether the users' of the computer are in compliance with The GAIN Publishing Privacy Statement and End User License Agreement.
Phantom Impressions
By Glaximus
The Presentation
A crowd of about 300 had gathered in one of Full Sail's larger classrooms for the monthly meeting of the Orlando chapter of the International Game Developers Association. Our guest speakers for the night were Infinium Labs, the company behind the oft-maligned and highly mysterious Phantom console. They were cautious with information, and while they did spill some details about the system, it's hardware, and their business model, they left a lot of critical questions unanswered. It was information about The Phantom, however, which until now had been almost non-existent.
The speaker for most of the presentation was Robert Shambro, one of two large Italian fellows who looked like they could moonlight as enforcement agents for various underground loan agencies. Rob spoke eagerly and seemed genuinely excited to present the Phantom and it's details to the crowd, but there was definitely a shiny coating of PR and spin covering the words of his oration. The other speaker was a third man, a generally non-descript laid back fellow by the name of Tim Roberts, who is the CEO of Infinium Labs. He answered a few questions but for the most part Rob did all the talking.
Yes, they did bring an actual Phantom "console" to the meeting. It looked exactly like the mock ups on the Infinium Labs website, and was about as big as a standard PC-- just picture your home desktop laying on it's side. Yes, it even had that glowing blue Phantom logo on the front. There were no visible controller ports, however there were some USB ports in the back, along with various outputs for S-Video, Component, A/V, a few USB ports and even a FireWire connection.
The Hardware
One of the first topics in the presentation was the Phantom's hardware. It was markedly different from what is listed on their website and in their promotional video, however Rob stressed that it was a beta box and that it may upgrade before release. They listed a 1.8Ghz Pentium 4 processor, 256mb of RAM (didn't mention what type) which could be upgraded to 512 or a full gig. An 80 gigabyte "storage device"-- no further specs than that were given. Rob also mentioned the system would be using "NVidia's NV36 graphics card." All the controllers and peripherals were made by Logitech, cord connected at first but wireless if you upgrade. He also said that currently the box was running on a standard ATX motherboard, which explained the console's size. Rob said he'd like it to be smaller but that's dependent on pricing issue, of course. He then went on to say that they had but five of these prototypes, which goes in direct contrast with previous statements from Tim Roberts that they "have several hundred prototype models here in the office." Well, perhaps those were earlier (Alpha?) prototypes.
As far as specs go, that's all we got. There are lots of little details missing-- RAM type, bus speeds, etc etc... technical as they are, they really make a difference in a high performance gaming machine. Again, Rob stressed that this was a Beta version of the hardware so things were subject to change.
Basically, the hardware is presented as a fair-to-middling PC. It even runs on a "specialized" Windows XP kernel. Now remember, consoles can get by with slower processor speeds and less RAM because they have very powerful hardware configurations made solely for pushing polygons around on screen. Also, most games run at a low resolution compared to your computer monitor. When questioned, Rob stated that the console is aimed for TV use.
Next topic was protection-- keeping the user out of the Phantom's hardware and software. He very quickly listed off lots of technologies and encryptions, nothing on the software end was out of the ordinary but some of the more interesting hardware ones were "Case Intrusion Detection" and "Epoxy Encapsulation of Critical ROMs." Yes, no going inside your own hardware for you, young gamer.
Comments?
Hey, we've been kicking butt in FPS ever since Clan Nine took out Thresh's gang (I forget what they were called) in Quakeworld championships... 8 to 2.
Sure, the comparison is valid, you can compare those elements, but are the results relevant? Not many would use OpenBSD in a performance (as in speed) critical role, and not many would expect Linux to have the security track record of OpenBSD.
If I'm going to war, I'll take the tank. If I'm going to race, I'll use the sports car. And if I'm taking 40 friends to the mountains for some skiing, count me in on that bus.
The reviewer does sound a bit biased towards Linux. In the same way Bill sounds a bit biased towards Microsoft.
200 lines to do what you described, plus 20.000 lines to interface with Windows.
Client A sends an UDP datagram to server
Client B sends an UDP datagram to server
Server sends originating IP and port for the other client to both clients
Both clients use that information to send UDP datagrams to each other
The NAT firewalls should then hopefully forward the incoming UDP traffic. Note that this won't work with TCP, only UDP.
- Ad Aware
- Extract Now
- Mozilla
- Zone Alarm
- Motherboard Monitor
- Total Commander
- Adobe Acrobat Reader
- Open Office
- BSPlayer
"Pedal you hamsters, PEDAL!!!"
Looking inside the archive, one will find a file called ihvtest_readme.txt. Doesn't have to mean that this is an IHV-only source code tree, it'd make sense to have stuff like that on the main branch, I think. Snippet: -Make sure you have the processor pack/msdev sp4 installed. -type "buildall" to build everything -type "run" to run. You will get higher performance if you disable some of the timing code. To do this, edit src/common/MaterialSystem/ShaderDX8/CMaterialSyste mStats.h and change:
#ifdef IHVTEST
#define MEASURE_STATS 1
#endif
This is a digital world. Evidence is easy to fake and destroy. Picture a scenario where I download a BO (back orifice) client to my machine. Then it's up to the attorney to prove that someone didn't use that BO client to download things, first to my computer and then FTP:ing them to their own.
"The double-blind laboratory tests -- meaning no one in the survey knew if a base station was transmitting signals or not -- exposed test subjects to levels of radiation average for third generation networks when they become commercial in coming years."
More high frequency radiation. Just what we needed. Now someone will tell me that all those radiation sources (2G, 3G, wireless LANs, digital handsets, etc) don't add up, and each must be considered individually. Sure. Tell that to your sterile grandchildren.
Well, in case you haven't noticed, cell phone antennas get put up on buildings, and beam right into people's bedrooms. Not intentionally, of course, but since it's not proven dangerous (to the minds of the cellphone companies), they don't give a shit anyway.
On what grounds should I be forced to pay an antivirus vendor fees, again, to protect myself from the incompetence of M$ programmers?
The reasonable thing would be to fine the author of the software that allowed the viral spread, if no patch is issued within a reasonable time period.
A program variable is either a global variable, a stack variable, a class variable or an instance variable. Global and stack variables are held in lists. Class and instance variables are kept inside objects.
Every class object has a global variable that always refers to it.
Any object that is not, and that can not become referenced (directly or indirectly) by a global or stack program variable is garbage.
Each object has a 'not-garbage' flag.
For each global and stack variable, if the referenced object is not marked not-garbage, mark the referenced object as not-garbage, and recurse for that objects contained variables.
Delete all objects that are not marked not-garbage.
There are a few more twists, like handling return values on the stack, but this algorithm correctly handles self-referencing objects no matter the complexity.
And 15" may be pushing it. It's closer to 20". It's also a 20" flat panel display, so I'm not too worried about my eyes; that site does seem to say that it's OK to sit closer to FPD's.
Exactly why aren't you supposed to sit close? I'd think that as long as I can read the text clearly, what's the problem?
"In fact, if you just sit directly in front of the display at about 30" away, as you normally do with any display, you will be in a position where you see 3D."
Thirty inches (75 cm)? I don't know about you, but I'm more like fifteen inches from the screen. At 30 inches, I couldn't read the damn thing.
"The protocol itself is derived from the Open Software Foundation (OSF) RPC protocol, but with the addition of some Microsoft specific extensions."
Now, why is that relevant? Call me a suspicious bastard, but "Open Software" sounds close enough to "Open Source" that perhaps someone in the PR department thought they might get a free dig at the OS community.
Aw, what do I know. Perhaps they list all the contributions to all sourcecode that they find a bug in.
Seems to me it would be a no-brainer to opt out of a $5 class settlement. Why waive all future claims against a measly $5??