*chiming in* I also have Rev 2.0 and it is also one of the most stable boards I've had. It runs Windows 2000 most of the time currently. It used to reboot all the time (randomly) with my D-Link USB wireless card...I'm not sure whether it was the USB port or the D-Link, but it happened no matter which set of ports I used, so I'm guessing it was a D-Link driver conflict.
Other than that, it's done quite well, even with my flaky video card:)
You can get pretty detailed information about the chip by looking at the drivers. Then you can see what's working for Intel and make something very similar without having to do the R&D that Intel did when making the chip.
It's a common business tactic. Go to the grocery store sometimes, and see how often the generic brands look similar to popular name brands. Never enough to be infringing on trademark or anything, but the name-brand probably did market research into the colors that people like, etc. By just copying them, you can get the benefit of that research without the expenditure.
Don't know about California, but in Texas, it's required that you have it on you. That's what the ticket says if you drive without a license. However, unless you get an asshole judge, once you go to them and show that you are a licensed driver, they'll throw that ticket out.
Hum Tone: Requires the client to deliver a hum resonance while blowing the alcohol test prior to starting the vehicle. Deters techniques utilized to mimic human breath or to absorb alcohol.
This is good, if you are concerned about people faking it.
Random or Fixed Retest: Programmable. The client is alerted and given a grace period to retest after the vehicle is put into the run state. The test can be delivered while operating the vehicle or after pulling off the road. Breath test refusal or failure is recorded and sanctions are imposed, including honking of the car's horn. Deters drinking after completing a sober start and vehicle idling at bars.
Probably most useful for DUI offenders, not for everyone...but who knows how far this legislation will go?
Bypass Detect: If a vehicle is started and the breath test is not passed, the horn will begin honking until the vehicle is turned off or a breath test is successfully completed. All events are recorded. Deters hot-wiring and push-starting of vehicles.
There had better be a small amount of time that the vehicle can be driven before the test but after you start the car. Otherwise, that 30 seconds is going to be a major pain. Not only that, but what if you are fleeing from an attacker? I guess our own personal safety isn't as important as those on the road who might be killed if I end up behind the wheel drunk (which, statistically, the majority of people do not do.)
Events Log: A built-in memory chip records all events associated with the use or misuse of the device. Reports are generated through a personal computer in a summary and complete hard-copy format.
Cool.. Now when are these reports read? For DUI offenders, it's presumably fairly often. For everyone else...when? When you get your car inspected? These things had better have a pretty big memory.
Violations Reset: Programmable. If the predetermined number of violations occurs during a monitoring period, an early inspection is required within three (3) days. Failure to report will result in immobilization of the vehicle. Violations are quickly identified and reported to the jurisdiction.
Again, most useful with DUI offenders. But honestly, after one violation, I'd think that you'd want inspection.
Service Reminder Reset: Reminds the client of a scheduled monitoring check. Failure to have the device monitored within the prescribed time period results in the device interlocking.
Power Interrupt: A dated record, in the event 12 volt power has been disconnected or interrupted. The device maintains memory through an onboard back-up lithium battery. This condition (other than tampering) can occur when a vehicle's battery is disconnected due to repairs or is replaced. Clients are required to provide documentation of repairs.
Whoa whoa whoa.... So if my battery dies, I'm fucked? No documented repair. This absolutely is only good for DUI offenders, because frankly, it's an unreasonable burden on your average person. I change my own batteries. There are also times when I take the battery off for other reasons. I should just be able to, period. Demanding documentation as to why the battery was removed is simply unacceptable unless there is good cause to believe that I was trying to get around the system.
Vehicle Restart: In the event of a vehicle stall, the driver has a grace period during which the ignition can be turned off and re-engaged without having to submit an additional breath test.
This somewhat mitigates the 30 second timer, but it also leads me to believe that that timer is a hard limit, and that this device actually prevents the car from being started until the check has completed. That's scary, to me. 30 seconds is a long time. Get a stopwatch, go outside, sit in your car for 30 seconds. It's an unreasonable imposition for someone who has neither broken the law, nor has a history of alcohol problems.
Also, consider the rolling retest. If they think driving while talking on a cellphone is bad, imagine trying to grab the tube, bring it to your mouth, and then blowing forcefully (enough that some people with low lung capacities can get dizzy and light headed). Cute.
Although the fact that rolling retests are possible means that it should be possible to let the car start and drive away without a test, but if a test isn't taken within, say, 60 seconds, then the alarms start going off, etc. Solves the "quick getaway" problem, though then we are back to the issue of fumbling with the gear while you're driving.
Now they'll start suing everyone for hundreds of thousands of dollars instead of offering to settle. And they've got the perfect excuse--the US government made them do it.
No, they're having a hissy fit because they can no longer distribute binaries of GPL'd software linked to xfree86. This is because the GPL and the new xfree86 license are incompatible. The GPL clearly stipulates that additional restrictions on the distribution of the software is not allowed. Requiring attribution, as minor as this is, is an additional restriction.
You're hurting your own argument in your analogy. IE6 is available for free on Microsoft's website. YOu can download just it or any other update they've released. You can't, as you say, download Windows XP. But the point is, you aren't stuck buying a whole new product just to fix this security vulnerability.
I'd say he makes a couple of good points, even if he didn't intend to. I agree with the source code arguments, though open source software tends to get bugfixes earlier, which/is/ a concern. Nevertheless, if you're using this boot CD, you're probably using Windows anyway, so it truly/doesn't/ matter. However, "open" means more than just the source. It's also about protocols, interoperabillity, etc. To me, that's more of a concern, even as a non-programmer Linux user.
Driver install disks? If you're doing an install of the operating system (which is what WinPE is all about, as opposed to BartPE) you actually need disks with drivers on them. At least, for storage controllers, etc. on Windows 2000 or before. BarPE seems to try to get around this, but the originall troller^Wposter probably didn't read anything about it:)
Registry editing...well now this/is/ an issue with BartPE (I suspect) because somehow you have to get the registry settings for your application into the registry on your bootable CD. Presumably this can be done, and I suspect that a large part of the BartPE plugin's work is doing this.
Haven't done this myself, but presumably you could use RegEdt32 and just load the hive that you want to edit. I've done this on a normal windows installation, so as long as you have RegEdt32 and any required files, I don't know why it wouldn't work.
Interesting on the processes...both Microsoft's site and Bart's site list this as a limitation. Seems pretty odd that it's not actually a limitation. Er, I did mean to say "concurrent processes".. could that be what it actually is? As for resolution, well I hadn't thought of a commandline util, that's pretty slick. I hate working in 800x600:)
Among other things, the PE environment (or at least, the ones made with PE builder) are limited to 6 processes. They also reboot after 24 hours (intentionally, no less!), resolution is limited to 800x600, 16 bit color, etc. What this tool is really good for is scanning for viruses, doing repairs that otherwise would be difficult (or impossible) under your normal operating environment, etc. In fact, one thing I just saw PE builder used for was to flash a firmware on a machine that only had Linux on it.
He also asked the following questions: # What is the required number of the participants for a class-action lawsuit to be instantiated? # Do you think that this course of action will yield any results?
Both of which should be answered by an experienced lawyer.
Why do people insist on asking for legal advice on Slashdot?
Anyway, I'm sure you know that Class Action lawsuits rarely have a good outcome for the class...usually they get a $5 coupon for some product the company makes, while the lawyers get millions.
Lastly, I really think it's your fault for purchasing it before a given feature was actually available. Unless the box promised multiplayer, you did this to yourself. The feature that was touted appears to be reviews of the product (i.e. the beef you have is with the reviewers, in that case) and if that's all you based your purchase on, I suspect that you'll be out of luck when you begin discussing this with your lawyer.
Anyway, what does any of this have to do with EULAs? Reading through your post and links, I found nothing of relevance. Looks to me like you're trying to get Slashdotters to your cause by bringing up a hotly debated part of closed source (and even some open source) software.
Are there players out there that can do extremely high bitrate DivX? It would be interesting to see a version of the film that takes up 4 gigs but is mpeg-4:)
Even lousy video cards can capture decent quality. Which one do you have, by the way?
Here are some tips: 1) Use HuffYUV as your capture codec. This is a lossless AVI format, but it is very big. You'll need a large, fast hard drive to cap with no frame drops. To be safe, I capture to a RAID0. For audio, use PCM 48000. Don't try to compress the audio, as the AVI spec doesn't deal with with VBR audio, and almost all audio compression that's worth a damn for capturing is VBR.
2) Get a color corrector. Most of these also remove Macrovision. Don't rely on software to do this, for $50 or so you can get a good hardware one that sits between the LD player and your capture hardware.
3) AVISynth (on Windows) is your friend for processing. Pay attention to the Levels function, but you can mess with the just about anything. You can also apply different functions to different parts of the video, although as a scripting language, it can take some time to get things perfectly right. You might also try a sharpness filter. Make sure all your filters are interlaced compatible, as you'll probably be dealing with an interlaced AVI. Don't deinterlace unless you know what you are doing--it can make the video look really bad.
4) Track down someone who has a copy of CCE and encode the video with that. Use 4 passes (5 or 6 if you really have time to waste, but most of the video quality will be obtained in the first 4). Make sure that you are encoding interlaced. Look for a good guide to CCE at http://www.doom9.net/ to get all the settings right. I'd go ahead and do a 4.7GB version and a 9.0GB version, as dual layer DVD burners will be coming out sometime this year, and it would be a pain to do the encoding again. You may wish to encode the credits separately at a much lower bitrate to save bits for the movie.
5) Do whatever you need to to encode the audio. I use BeSweet to get AC-3, but there may be better solutions.
Advanced usage would be making the video anamorphic, but I've never really messed with that, so you're on your own:)
You think your CDs are going to last forever? There have been a bunch of studies and corresponding articles that indicate that you shouldn't expect CDs to last more than 25 years. CDRs, typically even less than that, although being able to back up to CDR certainly can help extend that life, they'd better be good CDRs, and you're still having to expend money to ensure that the data remains (at some point, the cost will become equivalent to re-buying it). Storing massive amounts of music on hard drive is fine, but then you have to worry about hard drive failures. I guess RAID5 could help with that a bit;)
Reality is far too complex and has far too many variables that are impossible to even guess.
Yup. Maybe we should scrap the whole economic system. Go back to foraging for food. No, can't do that, we've destroyed too much of nature. Guess we're all just screwed.
Baen has discovered that sales of an author go up with the offer a free novel or two online.
Of course, what really matters is whether they want piracy at all. They can ignore the potential earnings from piracy if they want. Hell, they could stop selling the product altogether, and still legitimately go after copyright infringers.
But besides, your formula is far too complex and with too many variables that are impossible to even guess. It's a safe bet that there are some people out there who illegally download files to save money, and who would buy the product if they couldn't download it for free. It's not necessarily a safe bet that, by allowing piracy, you'll end up with more overall sales.
I only said the most recent CVS because that was what I currently was using. I suspect that that commandline switch was around for some time.
Looking over the thread, though, my solution is all you can do if you want to stream.wma files in Linux (or maybe use the crossover plugin, which has a dreaded cost associated with it). But to the original post, which was about how Car Talk was alienating Linux users, it holds little meaning I suppose. I was rebutting that, and we moved off into a slight tangent.
Getting a little off-topic, I'd say that Linux will always be playing catch-up until developers begin coding new technologies for Linux as well as other, more prevalent operating systems. Look at it this way. New video format is released. First it's released for Windows, because 95% of the computer using world uses Windows. Then it's probably released for the Mac, because there are a couple of millionaires who have that as their toy. Finally, Linux hackers reverse engineer the format and release an unstable version. It gets more and more stable, but it still lags behind the other releases. Eventually, the Windows developers stop development and move on to something else, at which point the open source project can surpass the original--after the technology is somewhat dated and redundant.
Wine and the like keep this outlook from being so bleak, but then (like MPlayer) you're relying on Windows to make Linux work. I think most true zealots consider that to be a bad thing.
I don't think that open source projects are "never quite done." I think the problem is that, for interoperability purposes, they always get a late start. Look how long it was before Sorenson (the primary codec for Quicktime) was available for Linux. I remember not too long ago (just a few years) when a trailer would be released, posted to slashdot, and the whining would commence about how impossible it was to view in our favorite OS. Now, finally, it is, and streaming WMA has moved to take its place. What's next? Probably whatever new fad comes about.
Slashdot Mirror
*chiming in*
:)
I also have Rev 2.0 and it is also one of the most stable boards I've had. It runs Windows 2000 most of the time currently. It used to reboot all the time (randomly) with my D-Link USB wireless card...I'm not sure whether it was the USB port or the D-Link, but it happened no matter which set of ports I used, so I'm guessing it was a D-Link driver conflict.
Other than that, it's done quite well, even with my flaky video card
You can get pretty detailed information about the chip by looking at the drivers. Then you can see what's working for Intel and make something very similar without having to do the R&D that Intel did when making the chip.
It's a common business tactic. Go to the grocery store sometimes, and see how often the generic brands look similar to popular name brands. Never enough to be infringing on trademark or anything, but the name-brand probably did market research into the colors that people like, etc. By just copying them, you can get the benefit of that research without the expenditure.
Don't know about California, but in Texas, it's required that you have it on you. That's what the ticket says if you drive without a license. However, unless you get an asshole judge, once you go to them and show that you are a licensed driver, they'll throw that ticket out.
I'd be pretty happy if DUI offenders were never allowed to drive in the US again. That'd be a good friggin penalty.
Technically, you could pull the car over for 30 seconds. Doing this every 30 minutes or so on a long trip would get really, really tiresome though.
"Whatever happened..." indeed.
From a link link further down the page....
PRODUCT AND DESIGN FEATURES
Hum Tone: Requires the client to deliver a hum resonance while blowing the alcohol test prior to starting the vehicle. Deters techniques utilized to mimic human breath or to absorb alcohol.
This is good, if you are concerned about people faking it.
Random or Fixed Retest: Programmable. The client is alerted and given a grace period to retest after the vehicle is put into the run state. The test can be delivered while operating the vehicle or after pulling off the road. Breath test refusal or failure is recorded and sanctions are imposed, including honking of the car's horn. Deters drinking after completing a sober start and vehicle idling at bars.
Probably most useful for DUI offenders, not for everyone...but who knows how far this legislation will go?
Bypass Detect: If a vehicle is started and the breath test is not passed, the horn will begin honking until the vehicle is turned off or a breath test is successfully completed. All events are recorded. Deters hot-wiring and push-starting of vehicles.
There had better be a small amount of time that the vehicle can be driven before the test but after you start the car. Otherwise, that 30 seconds is going to be a major pain. Not only that, but what if you are fleeing from an attacker? I guess our own personal safety isn't as important as those on the road who might be killed if I end up behind the wheel drunk (which, statistically, the majority of people do not do.)
Events Log: A built-in memory chip records all events associated with the use or misuse of the device. Reports are generated through a personal computer in a summary and complete hard-copy format.
Cool.. Now when are these reports read? For DUI offenders, it's presumably fairly often. For everyone else...when? When you get your car inspected? These things had better have a pretty big memory.
Violations Reset: Programmable. If the predetermined number of violations occurs during a monitoring period, an early inspection is required within three (3) days. Failure to report will result in immobilization of the vehicle. Violations are quickly identified and reported to the jurisdiction.
Again, most useful with DUI offenders. But honestly, after one violation, I'd think that you'd want inspection.
Service Reminder Reset: Reminds the client of a scheduled monitoring check. Failure to have the device monitored within the prescribed time period results in the device interlocking.
Power Interrupt: A dated record, in the event 12 volt power has been disconnected or interrupted. The device maintains memory through an onboard back-up lithium battery. This condition (other than tampering) can occur when a vehicle's battery is disconnected due to repairs or is replaced. Clients are required to provide documentation of repairs.
Whoa whoa whoa.... So if my battery dies, I'm fucked? No documented repair. This absolutely is only good for DUI offenders, because frankly, it's an unreasonable burden on your average person. I change my own batteries. There are also times when I take the battery off for other reasons. I should just be able to, period. Demanding documentation as to why the battery was removed is simply unacceptable unless there is good cause to believe that I was trying to get around the system.
Vehicle Restart: In the event of a vehicle stall, the driver has a grace period during which the ignition can be turned off and re-engaged without having to submit an additional breath test.
This somewhat mitigates the 30 second timer, but it also leads me to believe that that timer is a hard limit, and that this device actually prevents the car from being started until the check has completed. That's scary, to me. 30 seconds is a long time. Get a stopwatch, go outside, sit in your car for 30 seconds. It's an unreasonable imposition for someone who has neither broken the law, nor has a history of alcohol problems.
Also, consider the rolling retest. If they think driving while talking on a cellphone is bad, imagine trying to grab the tube, bring it to your mouth, and then blowing forcefully (enough that some people with low lung capacities can get dizzy and light headed). Cute.
Although the fact that rolling retests are possible means that it should be possible to let the car start and drive away without a test, but if a test isn't taken within, say, 60 seconds, then the alarms start going off, etc. Solves the "quick getaway" problem, though then we are back to the issue of fumbling with the gear while you're driving.
Now they'll start suing everyone for hundreds of thousands of dollars instead of offering to settle. And they've got the perfect excuse--the US government made them do it.
No, they're having a hissy fit because they can no longer distribute binaries of GPL'd software linked to xfree86. This is because the GPL and the new xfree86 license are incompatible. The GPL clearly stipulates that additional restrictions on the distribution of the software is not allowed. Requiring attribution, as minor as this is, is an additional restriction.
You're hurting your own argument in your analogy. IE6 is available for free on Microsoft's website. YOu can download just it or any other update they've released. You can't, as you say, download Windows XP. But the point is, you aren't stuck buying a whole new product just to fix this security vulnerability.
So what exactly is it doing when you open up Regedt32 and choose "Load hive" ? I guess I don't understand the distinction....
I'd say he makes a couple of good points, even if he didn't intend to. /is/ a concern. Nevertheless, if you're using this boot CD, you're probably using Windows anyway, so it truly /doesn't/ matter.
:)
/is/ an issue with BartPE (I suspect) because somehow you have to get the registry settings for your application into the registry on your bootable CD. Presumably this can be done, and I suspect that a large part of the BartPE plugin's work is doing this.
I agree with the source code arguments, though open source software tends to get bugfixes earlier, which
However, "open" means more than just the source. It's also about protocols, interoperabillity, etc. To me, that's more of a concern, even as a non-programmer Linux user.
Driver install disks? If you're doing an install of the operating system (which is what WinPE is all about, as opposed to BartPE) you actually need disks with drivers on them. At least, for storage controllers, etc. on Windows 2000 or before. BarPE seems to try to get around this, but the originall troller^Wposter probably didn't read anything about it
Registry editing...well now this
Haven't done this myself, but presumably you could use RegEdt32 and just load the hive that you want to edit.
I've done this on a normal windows installation, so as long as you have RegEdt32 and any required files, I don't know why it wouldn't work.
Interesting on the processes...both Microsoft's site and Bart's site list this as a limitation. Seems pretty odd that it's not actually a limitation. Er, I did mean to say "concurrent processes".. could that be what it actually is? :)
As for resolution, well I hadn't thought of a commandline util, that's pretty slick. I hate working in 800x600
Among other things, the PE environment (or at least, the ones made with PE builder) are limited to 6 processes. They also reboot after 24 hours (intentionally, no less!), resolution is limited to 800x600, 16 bit color, etc. What this tool is really good for is scanning for viruses, doing repairs that otherwise would be difficult (or impossible) under your normal operating environment, etc. In fact, one thing I just saw PE builder used for was to flash a firmware on a machine that only had Linux on it.
He also asked the following questions:
# What is the required number of the participants for a class-action lawsuit to be instantiated?
# Do you think that this course of action will yield any results?
Both of which should be answered by an experienced lawyer.
Why do people insist on asking for legal advice on Slashdot?
Anyway, I'm sure you know that Class Action lawsuits rarely have a good outcome for the class...usually they get a $5 coupon for some product the company makes, while the lawyers get millions.
Lastly, I really think it's your fault for purchasing it before a given feature was actually available. Unless the box promised multiplayer, you did this to yourself. The feature that was touted appears to be reviews of the product (i.e. the beef you have is with the reviewers, in that case) and if that's all you based your purchase on, I suspect that you'll be out of luck when you begin discussing this with your lawyer.
Anyway, what does any of this have to do with EULAs? Reading through your post and links, I found nothing of relevance. Looks to me like you're trying to get Slashdotters to your cause by bringing up a hotly debated part of closed source (and even some open source) software.
Are there players out there that can do extremely high bitrate DivX? It would be interesting to see a version of the film that takes up 4 gigs but is mpeg-4 :)
Even lousy video cards can capture decent quality. Which one do you have, by the way?
:)
Here are some tips:
1) Use HuffYUV as your capture codec. This is a lossless AVI format, but it is very big. You'll need a large, fast hard drive to cap with no frame drops. To be safe, I capture to a RAID0.
For audio, use PCM 48000. Don't try to compress the audio, as the AVI spec doesn't deal with with VBR audio, and almost all audio compression that's worth a damn for capturing is VBR.
2) Get a color corrector. Most of these also remove Macrovision. Don't rely on software to do this, for $50 or so you can get a good hardware one that sits between the LD player and your capture hardware.
3) AVISynth (on Windows) is your friend for processing. Pay attention to the Levels function, but you can mess with the just about anything. You can also apply different functions to different parts of the video, although as a scripting language, it can take some time to get things perfectly right. You might also try a sharpness filter. Make sure all your filters are interlaced compatible, as you'll probably be dealing with an interlaced AVI. Don't deinterlace unless you know what you are doing--it can make the video look really bad.
4) Track down someone who has a copy of CCE and encode the video with that. Use 4 passes (5 or 6 if you really have time to waste, but most of the video quality will be obtained in the first 4). Make sure that you are encoding interlaced. Look for a good guide to CCE at http://www.doom9.net/ to get all the settings right. I'd go ahead and do a 4.7GB version and a 9.0GB version, as dual layer DVD burners will be coming out sometime this year, and it would be a pain to do the encoding again. You may wish to encode the credits separately at a much lower bitrate to save bits for the movie.
5) Do whatever you need to to encode the audio. I use BeSweet to get AC-3, but there may be better solutions.
Advanced usage would be making the video anamorphic, but I've never really messed with that, so you're on your own
Fair enough :)
;)
Still gotta worry about those EMPs, though
You think your CDs are going to last forever? There have been a bunch of studies and corresponding articles that indicate that you shouldn't expect CDs to last more than 25 years. CDRs, typically even less than that, although being able to back up to CDR certainly can help extend that life, they'd better be good CDRs, and you're still having to expend money to ensure that the data remains (at some point, the cost will become equivalent to re-buying it). Storing massive amounts of music on hard drive is fine, but then you have to worry about hard drive failures. I guess RAID5 could help with that a bit ;)
Reality is far too complex and has far too many variables that are impossible to even guess.
Yup. Maybe we should scrap the whole economic system. Go back to foraging for food.
No, can't do that, we've destroyed too much of nature. Guess we're all just screwed.
Baen has discovered that sales of an author go up with the offer a free novel or two online.
Worked out well for Stephen King, did it?
Of course, what really matters is whether they want piracy at all. They can ignore the potential earnings from piracy if they want. Hell, they could stop selling the product altogether, and still legitimately go after copyright infringers.
But besides, your formula is far too complex and with too many variables that are impossible to even guess. It's a safe bet that there are some people out there who illegally download files to save money, and who would buy the product if they couldn't download it for free. It's not necessarily a safe bet that, by allowing piracy, you'll end up with more overall sales.
Since it's a bug in ipv6, I bet you have to have a modified ipv6 stack in order to fix it, too. :)
I only said the most recent CVS because that was what I currently was using. I suspect that that commandline switch was around for some time.
.wma files in Linux (or maybe use the crossover plugin, which has a dreaded cost associated with it). But to the original post, which was about how Car Talk was alienating Linux users, it holds little meaning I suppose. I was rebutting that, and we moved off into a slight tangent.
Looking over the thread, though, my solution is all you can do if you want to stream
Getting a little off-topic, I'd say that Linux will always be playing catch-up until developers begin coding new technologies for Linux as well as other, more prevalent operating systems. Look at it this way. New video format is released. First it's released for Windows, because 95% of the computer using world uses Windows. Then it's probably released for the Mac, because there are a couple of millionaires who have that as their toy. Finally, Linux hackers reverse engineer the format and release an unstable version. It gets more and more stable, but it still lags behind the other releases. Eventually, the Windows developers stop development and move on to something else, at which point the open source project can surpass the original--after the technology is somewhat dated and redundant.
Wine and the like keep this outlook from being so bleak, but then (like MPlayer) you're relying on Windows to make Linux work. I think most true zealots consider that to be a bad thing.
I don't think that open source projects are "never quite done." I think the problem is that, for interoperability purposes, they always get a late start. Look how long it was before Sorenson (the primary codec for Quicktime) was available for Linux. I remember not too long ago (just a few years) when a trailer would be released, posted to slashdot, and the whining would commence about how impossible it was to view in our favorite OS. Now, finally, it is, and streaming WMA has moved to take its place. What's next? Probably whatever new fad comes about.