Nope - I cannot get the tuner in my 9600AIW working. I can get composite in working just fine, but the tuner won't see anything.
It's really a shame - the idea of the tuner and video capture being on the video card makes a great deal of sense, but the implementation of the software bites small rocks.
I'll believe that AMD/ATI is fixing their problems when I can have a driver that:
Supports XvMC
Supports the tuner on my All-in-Wonder, either via XVideo or Video For Linux
Has reasonable 3D performance without locking up (GoogleEarth will kill my card dead in seconds, requiring a hard power off to fix it.)
Has reasonable 2D acceleration.
Runs on the current release of the kernel - on i386 and i386-64 AT LEAST.
Supports PCIe cards
This is *the* limiting factor which has prevented me from buying a new computer - any new machine would be an i386-64 with PCIe video, and right now the only real choice there would be Intel graphics.
IPv4 sites can be accessed with IPv6; IPv6 addresses include IPv4 addresses as a subset.
That's like saying "My car can RUN on diesel because I can put a can of it in the trunk."
I will tell you what: if what you say is true, then you should be able to retrieve the front page of Slashdot using HTTP over TCP using IP6 headers rather than IP4 headers. Why don't you give it a try, watching with your favorite packet logger, and post the results.
Yes, IF:
Your computer has an IP6 stack.
Your ISP handles IP6 datagrams.
Slashdot's server have IP6 stacks.
THEN you might be able to do IP6 from your IP4 address to Slashdot's IP4 address.
BUT if ANY step in the way cannot handle IP6 datagrams — even a step as lowly as the cheap router your ISP gave you, or the cable modem head end unit, or.* — you WILL NOT BE ABLE TO USE IP6 DATAGRAMS.
Go onto her system, and replace every UI sound effect with the juiciest, longest, and nastiest fart sound effect you can find on the Internet. Think goatse for the ears.
She'll turn down her sound so fast it will violate Relativity.
Microsoft had two Oh So Happy It's Thursday moments this week so far: Tuesday's 0-day in Word (which has an exploit) and this one Friday (which currently does not have an exploit).
Unfortunately, there is no automatic fetching....
on
Tim Bray Says RELAX
·
· Score: 1
(damn short subject lines!)
I agree that RelaxNG is much easier to read, and it will much more completely describe a grammar than will the other standard - and MUCH more completely define it than will a DTD.
Unfortunately, as far as I can tell there is no way to, within an XML document, state "Use THIS RelaxNG schema file to validate this document", as you can with a DTD. Thus, even if I have placed my RelaxNG schema on my web server, I cannot set things up such that (for example) libXML2 can automatically fetch that schema when it starts parsing my document. I can map the RelaxNG schema to a DTD (losing information) and allow that to be fetched, but if I want to use a RelaxNG schema with libXML2 I the programmer must tell libXML2 where the schema is.
IMHO it would be a Good Thing if the W3C would standardize on some way to associate a RelaxNG schema with a given XML file - say, by some form of XML processing directive within the XML file.
If the site needs to mail you something to complete the registration, you have to be able to read the email address - and having one address that collects a ton of crap makes it hard to read the email address and get that one mail you care about to complete the registration.
Yes, if the site wants an email address, but you don't need to receive any emails from the site to continue, give it "i_dont_want_spam@localhost", or "i_dont_want_spam@example.org"
The Hindenburg fire was NOT caused by hydrogen, but rather by a new exterior covering that the Zeppelin company was trying out - a butyl rubber fabric coated with iron oxide and powered aluminum - in other words, a formulation very close to what the Space Shuttle Solid Rocket Boosters use for fuel.
In addition, the skin panels were not electrically bonded to the superstructure of the ship and formed a series of capacitors which were highly charged - when the ship was grounded by the mooring lines, the panels discharged, some through the wet cords binding them to the ship, some by arcing (and thus setting themselves on fire).
More screen real-estate will improve certain types of workers - I have dual 17" flat panels at work, and that helps a great deal in coding - I can have a header up in a window on one screen, and the code using that header on another, or a document of a protocol up on one and the state machine for that protocol up on another, and so on.
While I could just as easily do the same sort of thing with a single 30" screen, for the cost, having 2 cheap 17" panels makes a LOT more sense.
So while I do question the exact methodology Apple used (cp -r source_dir dest_dir works a whole lot faster and is pretty much screen-size independent), and I do question the idea that the best way to achieve the benefit is a single, very expensive screen, I don't dispute the basic conclusion - more screen area will increase productivity of many classes of employee.
Obviously, HP management said "These PCs are for tweakers" and they heard "leakers".
They thought that they could use Voodoo to find and punish the leakers. I see visions of HP management sticking needles into PCs as we speak: "Oh YEAH - TAKE THAT! AND THAT! AND THAT! BWAHAHAHAAHA!"
I'd like to see them make a simple, stupid framebuffer module for these things - just NTSC or PAL resolution output at 256 colors would be plenty - look at what the old Atari/Apple/Commodore computers could do.
I want to use these as a very simple display for home automation - hang one on the back of the TV, use a PIN switch video port (or the video input on the TV), run about a 40 by 24 character display - not fancy, but enough for display.
A frame buffer like that could easily be implemented in a small FPGA now-a-days.
Of course, a tiny X server or VNC client would be even better.
And of course, you will pay for the costs of freezing yourself, and maintaining the equipment, how, exactly?
More than likely, it will be much like a couple of SF stories by different authors - the section of Larry Niven's "The Long A.R.M. of Gil Hamilton" wherein a law allowing corpsicles to be thawed and broken up for parts is being considered.
However, I like a short story I read many years ago - a man has himself frozen, and is awakened. He wakes to find another, older man next to his bed. They strike up a conversation about what has changed - the young man asks about the older man's earrings, which he is informed are antenna. He is then told he is being prepped for heart surgery. "But I don't have a bad heart" the young man says. "No, but I do" says the older man.
That is because the US does not use Tetra, it uses APCO-25, a competing standard - a fact the article mentioned MULTIPLE TIMES.
The problem is not the lack of a standard, but the LACK OF MONEY. A plain-old stupid narrowband FM radio is about US$500. A somewhat less stupid radio using a simple trunking protocol like LTR or Passport would be around US$1500. The lowest end APCO-25 or Tetra radio would be about US$2500, with US$5000 being more commonplace. That's for a handheld radio - a mobile is more.
Then you have the trunking transmitter sites themselves. A plain-old narrowband FM site can be put in for about US$2000. An LTR controller and 2 RF channels would be around US$10000. An APCO-25 site is going to run you about US$250000 and up. WAAAAAY up. A system with multiple transmit sites plus a prime site (the main controller site) and dispatch can be over US$1 million.
Then there is the matter of coverage. Out in the country, you want to use VHF frequencies (around 150 MHz), as they will carry further through the air (lower attenuation losses) and they will diffract over the horizon more - thus requiring fewer transmit sites. However, there isn't as much VHF spectrum available, and in the big city VHF has real problems with Rayleigh fading and multipath. Also, VHF gets blocked more by metal buildings (it takes a bigger crack for the RF to get in).
In the city, you want to use the 700MHz, 800MHz, or 900MHz bands. These don't carry as far, but in the city who cares? There is a lot more spectrum in those bands, and the will penetrate a little better (what is a hole to 900 MHz is a wall to 150 MHz).
But if you operate both in the county and in the city, you now need either a) many 800MHz transmit sites (much more money) b) a dual band radio (more money) or c) multiple radios (more money) to be able to operate.
Then there is the problem that even if you have a radio that could operate on the system, if the system is not programmed to recognize your radio, and/or your radio does not recognize the system, you won't be able to connect. That's the PURPOSE of trunked radio - to control access. So now you have to have your radios programmed across multiple systems (more complexity, more money) or you have to only have one system for everybody (and now you have the cops stomping on the firemen stomping on the ambulances stomping on the Feds stomping on....). Alternatively, you can go for linked systems with roaming - and guess what that means: MUCH MUCH MORE MONEY.
Then you have the problem that you have a lot of Old Farts on the various forces, who don't like the new radios because they are more complicated to operate (and thus more likely to get screwed up by having a switch mis-set when things get hot) and they don't like digital - so you get a lot of resistance to the new radios.
I work in this field - I designed the equipment used to test and service APCO-25 radios, I've worked with Motorola designing test procedures for their APCO-25 transmit sites, I've worked with cities deploying APCO-25, and I've worked with various TLA's on their P25 testing requirements.
In case anybody wants to look up some of Jimbo's actions from another perspective, go to Wikitruth.
It is to Wikipedia what DailyKos is to conservatism or Instapundit is to liberalism - a completely biased site decrying the flaws in a philosophy. As such, take its claims with some skepticism and salt, feel free to reject them, but do at least consider them before you reject them.
Note: I am not associated with WikiTruth - but I feel they make some good points.
Slashdot Mirror
Nope - I cannot get the tuner in my 9600AIW working. I can get composite in working just fine, but the tuner won't see anything.
It's really a shame - the idea of the tuner and video capture being on the video card makes a great deal of sense, but the implementation of the software bites small rocks.
This is *the* limiting factor which has prevented me from buying a new computer - any new machine would be an i386-64 with PCIe video, and right now the only real choice there would be Intel graphics.
That's like saying "My car can RUN on diesel because I can put a can of it in the trunk."
I will tell you what: if what you say is true, then you should be able to retrieve the front page of Slashdot using HTTP over TCP using IP6 headers rather than IP4 headers. Why don't you give it a try, watching with your favorite packet logger, and post the results.
Yes, IF:
THEN you might be able to do IP6 from your IP4 address to Slashdot's IP4 address.
BUT if ANY step in the way cannot handle IP6 datagrams — even a step as lowly as the cheap router your ISP gave you, or the cable modem head end unit, or
This was announced on The Register yesterday, making it yet another
Oh
So
Happy
It's
Thursday
moment again.
I point this out every time the subject of IPv6 comes up, especially when people gripe about the slow update of IPv6:
Try to get a page from Slashdot's servers using IPv6 - that is to say, using IPv6 format packets, NOT IPv4 packets.
Then ask yourself again why IPv6 is NOT being adopted.
(NOTE: You can replace Slashdot with CNN, Digg, or whatever other mainstream site floats your boat.)
It might be worth noting that the "serious games" does not mean "Serious games" as in Serious Sam.
The collision distance for technical and gaming terms is getting smaller all the time....
Go onto her system, and replace every UI sound effect with the juiciest, longest, and nastiest fart sound effect you can find on the Internet. Think goatse for the ears.
She'll turn down her sound so fast it will violate Relativity.
Sorry, but I'm not into the N's yet...
There's only one thing to put on such a sign:
"Mostly Harmless"
Dirty. Few teeth. Lives "off the grid" "at the edges of society". Phreaker. Raver.
Sounds a lot like Blank Reg.
And the question I have is, Why? Why would I *want* to be a part of this? Are they going to pay me to endure the targeted advertising?
This makes as much sense to me as signing up for a free poke in the eye.
Microsoft had two
Oh
So
Happy
It's
Thursday
moments this week so far: Tuesday's 0-day in Word (which has an exploit) and this one Friday (which currently does not have an exploit).
(damn short subject lines!)
I agree that RelaxNG is much easier to read, and it will much more completely describe a grammar than will the other standard - and MUCH more completely define it than will a DTD.
Unfortunately, as far as I can tell there is no way to, within an XML document, state "Use THIS RelaxNG schema file to validate this document", as you can with a DTD. Thus, even if I have placed my RelaxNG schema on my web server, I cannot set things up such that (for example) libXML2 can automatically fetch that schema when it starts parsing my document. I can map the RelaxNG schema to a DTD (losing information) and allow that to be fetched, but if I want to use a RelaxNG schema with libXML2 I the programmer must tell libXML2 where the schema is.
IMHO it would be a Good Thing if the W3C would standardize on some way to associate a RelaxNG schema with a given XML file - say, by some form of XML processing directive within the XML file.
If the site needs to mail you something to complete the registration, you have to be able to read the email address - and having one address that collects a ton of crap makes it hard to read the email address and get that one mail you care about to complete the registration.
Yes, if the site wants an email address, but you don't need to receive any emails from the site to continue, give it "i_dont_want_spam@localhost", or "i_dont_want_spam@example.org"
There's your mistake - you don't want them to remove you from their lists.
You want them to add you to their do not call list - the one they are required by law to keep.
"Add me to all your do not call lists."
The Hindenburg fire was NOT caused by hydrogen, but rather by a new exterior covering that the Zeppelin company was trying out - a butyl rubber fabric coated with iron oxide and powered aluminum - in other words, a formulation very close to what the Space Shuttle Solid Rocket Boosters use for fuel.
In addition, the skin panels were not electrically bonded to the superstructure of the ship and formed a series of capacitors which were highly charged - when the ship was grounded by the mooring lines, the panels discharged, some through the wet cords binding them to the ship, some by arcing (and thus setting themselves on fire).
They are making a CGI version of Beowulf. Let the slashbot flogging of the demised equine that is the "imagine a Beowulf cluster" meme begin.
More screen real-estate will improve certain types of workers - I have dual 17" flat panels at work, and that helps a great deal in coding - I can have a header up in a window on one screen, and the code using that header on another, or a document of a protocol up on one and the state machine for that protocol up on another, and so on.
While I could just as easily do the same sort of thing with a single 30" screen, for the cost, having 2 cheap 17" panels makes a LOT more sense.
So while I do question the exact methodology Apple used (cp -r source_dir dest_dir works a whole lot faster and is pretty much screen-size independent), and I do question the idea that the best way to achieve the benefit is a single, very expensive screen, I don't dispute the basic conclusion - more screen area will increase productivity of many classes of employee.
Obviously, HP management said "These PCs are for tweakers" and they heard "leakers".
They thought that they could use Voodoo to find and punish the leakers. I see visions of HP management sticking needles into PCs as we speak: "Oh YEAH - TAKE THAT! AND THAT! AND THAT! BWAHAHAHAAHA!"
I think you got the company name wrong:
http://www.kleinbottle.com/
I'd like to see them make a simple, stupid framebuffer module for these things - just NTSC or PAL resolution output at 256 colors would be plenty - look at what the old Atari/Apple/Commodore computers could do.
I want to use these as a very simple display for home automation - hang one on the back of the TV, use a PIN switch video port (or the video input on the TV), run about a 40 by 24 character display - not fancy, but enough for display.
A frame buffer like that could easily be implemented in a small FPGA now-a-days.
Of course, a tiny X server or VNC client would be even better.
And of course, you will pay for the costs of freezing yourself, and maintaining the equipment, how, exactly?
More than likely, it will be much like a couple of SF stories by different authors - the section of Larry Niven's "The Long A.R.M. of Gil Hamilton" wherein a law allowing corpsicles to be thawed and broken up for parts is being considered.
However, I like a short story I read many years ago - a man has himself frozen, and is awakened. He wakes to find another, older man next to his bed. They strike up a conversation about what has changed - the young man asks about the older man's earrings, which he is informed are antenna. He is then told he is being prepped for heart surgery. "But I don't have a bad heart" the young man says. "No, but I do" says the older man.
That is because the US does not use Tetra, it uses APCO-25, a competing standard - a fact the article mentioned MULTIPLE TIMES.
The problem is not the lack of a standard, but the LACK OF MONEY. A plain-old stupid narrowband FM radio is about US$500. A somewhat less stupid radio using a simple trunking protocol like LTR or Passport would be around US$1500. The lowest end APCO-25 or Tetra radio would be about US$2500, with US$5000 being more commonplace. That's for a handheld radio - a mobile is more.
Then you have the trunking transmitter sites themselves. A plain-old narrowband FM site can be put in for about US$2000. An LTR controller and 2 RF channels would be around US$10000. An APCO-25 site is going to run you about US$250000 and up. WAAAAAY up. A system with multiple transmit sites plus a prime site (the main controller site) and dispatch can be over US$1 million.
Then there is the matter of coverage. Out in the country, you want to use VHF frequencies (around 150 MHz), as they will carry further through the air (lower attenuation losses) and they will diffract over the horizon more - thus requiring fewer transmit sites. However, there isn't as much VHF spectrum available, and in the big city VHF has real problems with Rayleigh fading and multipath. Also, VHF gets blocked more by metal buildings (it takes a bigger crack for the RF to get in).
In the city, you want to use the 700MHz, 800MHz, or 900MHz bands. These don't carry as far, but in the city who cares? There is a lot more spectrum in those bands, and the will penetrate a little better (what is a hole to 900 MHz is a wall to 150 MHz).
But if you operate both in the county and in the city, you now need either a) many 800MHz transmit sites (much more money) b) a dual band radio (more money) or c) multiple radios (more money) to be able to operate.
Then there is the problem that even if you have a radio that could operate on the system, if the system is not programmed to recognize your radio, and/or your radio does not recognize the system, you won't be able to connect. That's the PURPOSE of trunked radio - to control access. So now you have to have your radios programmed across multiple systems (more complexity, more money) or you have to only have one system for everybody (and now you have the cops stomping on the firemen stomping on the ambulances stomping on the Feds stomping on....). Alternatively, you can go for linked systems with roaming - and guess what that means: MUCH MUCH MORE MONEY.
Then you have the problem that you have a lot of Old Farts on the various forces, who don't like the new radios because they are more complicated to operate (and thus more likely to get screwed up by having a switch mis-set when things get hot) and they don't like digital - so you get a lot of resistance to the new radios.
I work in this field - I designed the equipment used to test and service APCO-25 radios, I've worked with Motorola designing test procedures for their APCO-25 transmit sites, I've worked with cities deploying APCO-25, and I've worked with various TLA's on their P25 testing requirements.
In case anybody wants to look up some of Jimbo's actions from another perspective, go to Wikitruth.
It is to Wikipedia what DailyKos is to conservatism or Instapundit is to liberalism - a completely biased site decrying the flaws in a philosophy. As such, take its claims with some skepticism and salt, feel free to reject them, but do at least consider them before you reject them.
Note: I am not associated with WikiTruth - but I feel they make some good points.
What? Nobody (at least, nobody above +2) has posted a link to WikiTruth? Well, let me do so then.