Speedo measures at the output shaft of the transmission on modern vehicles.
I would imagine that if someone saw the car go from 100 to 0 mph in under a second, they might realize what was going on.
Seeing as speedometers in newer cars are almost entirely electronic, I would imagine it gets its speed data from that. So long as your tire size is the same as OEM, the speedometer should be correct.
Other information that would is recorded (position of accelerator and brake pedal, etc) is used by other systems in the car (ABS, fuel injection, all-wheel-drive, just to name a few). Seeing as this information is already being monitored accurately enough to make the car run properly, I would imagine that it's accurate enough to tell whether you were doing 100 or 30 and how far open the throttle was at the time of impact.
In some cars, the car even uses this information to tailor itself to your driving habits (by setting transmission shift-points, etc.). It's particularly annoying in rental cars for obvious reasons.
Mine (40GB firmware 2.1) makes no mention of FairPlay at all:
(Apple logo) (c)2001-2003 Apple Computer, Inc. All Rights reserved. Apple and the Apple logo are trademarks of Apple Computer, Inc., registered in the US and other countries. iPod is a trademark of Apple Computer, Inc.
(Portal Player Logo) Portions Copyright (c) 2001-2003 PortalPlayer, Inc. All rights reserved. PortalPlayer and the PortalPlayer logo are trademarks owned by PortalPlayer, Inc.
MPEG Layer-3 audio coding technology licensed from Fraunhofer IIS and THOMSON multimedia.
ACELP(r) is either registered trademark or trademark of VoiceAge Corporation in the United States and/or other countries and used under license from VoiceAge Corporation. The ACEPL(r).net codec in this product is used under license from VoiceAge Corporation. Portions Copyright (c) 2002 VoiceAge Corporation. All rights reserved.
The Audible software in this product is used under license from Audible. Copyright (c) 2002 by Audible, Inc. All rights reserved.
AMD and Apple both have manufacturing contracts with IBM. I imagine this is where the sharing would be taking place, as both are using.13 SOI processes in their chips. It is quite feasible that what IBM learns from making PPCs could be applied to Athlons.
My comment was intended to point out that the entire Athlon line (server and desktop/workstation parts included) has had 2 sockets/slots. Pentium has had 5 (server/desktop combined).
From what I've read (and I could very well be wrong, so don't take this as fact), Prescott is P4 with 13 new instructions, a la MMX or SSE, in a new package on a new process.
Somewhat like Athlon vs. Athlon XP (although that didn't include a die shrink until later).
P4 has had 3 sockets (including the new Prescott) with the same types of changes that Athlon has gone through. Don't forget that the server chip (Xeon) has had a few sockets of its own. Athlon has had 2 (including Slot A). Since Thunderbird, there have been no changes to Athlon's socket. Compare the amount of time that each chip has spent on its current socket. Athlon has had around 2 years, P4 around 1.
Not to be labeled a fanboy (although not necessarily denying that status)... but this sounds like a paper launch just to take some press away from AMD.
"He [Burns] said the chip will be available to buy in the 30-60-day timeframe." from this article.
Prescott is going to be late and has been getting bad press for not being backward compatible with current motherboards. Why not make some noise with a product that wont be around for another month?
Hey!
I'm a Senior Network Admin for STAC (check the ws for info: www.stac.org) at my HS.
Basically, my 'job' is to run around and make sure that our 13 linux servers and 400+ client boxes are running appropriately.
STAC runs its own network separate from the district's, although we often end up fixing crap that the district owns and is too lazy to deal with in a timely manner.
We wrote our own curriculum and had it implemented into the networking and cs classes at the school.
Honestly, I spend a good 2 class periods a day working on this type of stuff. From imaging labs (fun fun fun! Esp when Ghost goes haywire), fixing DNS, IPTables, and DHCP issues, to simple 'reboot the computer please' style tech support.
I would suggest the following:
Hook up with a teacher and a friend or two who know what they are talking about.
See if you can't scrape together some old hardware into a functioning network that you can show off (READ: Bring your own stuff for temporary use if necessary).
We have gotten so well liked by the administration that when the district threatened to cut our T1 line due to some legal issues, we (students) were asked to talk to the head network support team and plead our case. Not only did we convince them that we were worthwhile (we have more computers on campus than any other school in district, yet our official helpdesk file is smaller than many of the elementary school ones), but they offered us funding.
I hate to sound like I'm bragging (OK, well I am...), but you have to make yourself seem worthwhile before you'll get what you want. I've stayed at school until 7:00 or later many times this year alone (school ends at 3:30), not even counting the saturdays we come up to do work on. The other 3 senior admins and I were at the school weeks before classes started getting labs ready. It takes dedication, but you can get really far.
All of the Senior Admins have gotten jobs due to the talents we've gained doing this work.
--Ari
Slashdot Mirror
There's a Bluetooth version of this mouse out now. The MX 900 I believe.
Speedo measures at the output shaft of the transmission on modern vehicles. I would imagine that if someone saw the car go from 100 to 0 mph in under a second, they might realize what was going on.
Seeing as speedometers in newer cars are almost entirely electronic, I would imagine it gets its speed data from that. So long as your tire size is the same as OEM, the speedometer should be correct.
Other information that would is recorded (position of accelerator and brake pedal, etc) is used by other systems in the car (ABS, fuel injection, all-wheel-drive, just to name a few). Seeing as this information is already being monitored accurately enough to make the car run properly, I would imagine that it's accurate enough to tell whether you were doing 100 or 30 and how far open the throttle was at the time of impact. In some cars, the car even uses this information to tailor itself to your driving habits (by setting transmission shift-points, etc.). It's particularly annoying in rental cars for obvious reasons.
Mine (40GB firmware 2.1) makes no mention of FairPlay at all:
(Apple logo)
(c)2001-2003 Apple Computer, Inc. All Rights reserved. Apple and the Apple logo are trademarks of Apple Computer, Inc., registered in the US and other countries. iPod is a trademark of Apple Computer, Inc.
(Portal Player Logo)
Portions Copyright (c) 2001-2003 PortalPlayer, Inc. All rights reserved. PortalPlayer and the PortalPlayer logo are trademarks owned by PortalPlayer, Inc.
MPEG Layer-3 audio coding technology licensed from Fraunhofer IIS and THOMSON multimedia.
ACELP(r) is either registered trademark or trademark of VoiceAge Corporation in the United States and/or other countries and used under license from VoiceAge Corporation. The ACEPL(r).net codec in this product is used under license from VoiceAge Corporation. Portions Copyright (c) 2002 VoiceAge Corporation. All rights reserved.
The Audible software in this product is used under license from Audible. Copyright (c) 2002 by Audible, Inc. All rights reserved.
AMD and Apple both have manufacturing contracts with IBM. I imagine this is where the sharing would be taking place, as both are using .13 SOI processes in their chips. It is quite feasible that what IBM learns from making PPCs could be applied to Athlons.
The specs for the x86-64 instruction set were finalized well before Linux was ported.
My comment was intended to point out that the entire Athlon line (server and desktop/workstation parts included) has had 2 sockets/slots. Pentium has had 5 (server/desktop combined).
From what I've read (and I could very well be wrong, so don't take this as fact), Prescott is P4 with 13 new instructions, a la MMX or SSE, in a new package on a new process. Somewhat like Athlon vs. Athlon XP (although that didn't include a die shrink until later).
P4 has had 3 sockets (including the new Prescott) with the same types of changes that Athlon has gone through. Don't forget that the server chip (Xeon) has had a few sockets of its own. Athlon has had 2 (including Slot A). Since Thunderbird, there have been no changes to Athlon's socket. Compare the amount of time that each chip has spent on its current socket. Athlon has had around 2 years, P4 around 1.
1 4
Here's some press about Prescott:
http://www.theinquirer.net/?article=10438
http://www.theinquirer.net/?article=8011
And to prove that I don't only read The Inq:
http://www.anandtech.com/news/shownews.html?i=200
I could probably dig up some more if you are really interested.
Not to be labeled a fanboy (although not necessarily denying that status)... but this sounds like a paper launch just to take some press away from AMD.
"He [Burns] said the chip will be available to buy in the 30-60-day timeframe." from this article.
Prescott is going to be late and has been getting bad press for not being backward compatible with current motherboards. Why not make some noise with a product that wont be around for another month?
Repeat after me: viruses not "virii"
Granted I never did that well in Latin, but I'm going to have to disagree with that.
Remind me to use some html formatting next time.
--Ari
Hey! I'm a Senior Network Admin for STAC (check the ws for info: www.stac.org) at my HS. Basically, my 'job' is to run around and make sure that our 13 linux servers and 400+ client boxes are running appropriately. STAC runs its own network separate from the district's, although we often end up fixing crap that the district owns and is too lazy to deal with in a timely manner. We wrote our own curriculum and had it implemented into the networking and cs classes at the school. Honestly, I spend a good 2 class periods a day working on this type of stuff. From imaging labs (fun fun fun! Esp when Ghost goes haywire), fixing DNS, IPTables, and DHCP issues, to simple 'reboot the computer please' style tech support. I would suggest the following: Hook up with a teacher and a friend or two who know what they are talking about. See if you can't scrape together some old hardware into a functioning network that you can show off (READ: Bring your own stuff for temporary use if necessary). We have gotten so well liked by the administration that when the district threatened to cut our T1 line due to some legal issues, we (students) were asked to talk to the head network support team and plead our case. Not only did we convince them that we were worthwhile (we have more computers on campus than any other school in district, yet our official helpdesk file is smaller than many of the elementary school ones), but they offered us funding. I hate to sound like I'm bragging (OK, well I am...), but you have to make yourself seem worthwhile before you'll get what you want. I've stayed at school until 7:00 or later many times this year alone (school ends at 3:30), not even counting the saturdays we come up to do work on. The other 3 senior admins and I were at the school weeks before classes started getting labs ready. It takes dedication, but you can get really far. All of the Senior Admins have gotten jobs due to the talents we've gained doing this work. --Ari