Umh, it's iRiver that makes the RioVolt...They also do firmware upgrades...
So, they are the one to pester...of course, the iMP-250 is not available from iRiver America (exclusitivity agreements)...
But, the SlimX series (iMP-350 and iMP-400) are more likely to get Ogg Vorbis support...
From what I hear the SlimX players are more powerful than previous players...
So, it's not likely that your 250 will get support...maybe the iMP-150 (which seems to be the only early model still being produced)...of course, you should check out the FAQ first...
You should check out The History of NASCAR...very interesting read...many ppl know about the moonshine thing, but how many know about the real history of the sport???
There's a lot of science and engineering involved with NASCAR...which is why the modern drivers are more engineers than mechanics...
This is also one reason why I think the current drivers and crews are much better role models than most of our athletes in traditional sports (football, baseball, boxing, etc)...
How dense does it have to be? The tiles were known to break under the finger pressure required to secure the pieces to the body of the craft...
Re:What do you mean, "...Wants us to believe?"
on
More on Columbia
·
· Score: 3, Interesting
How so?
First thing is they did not have the docking equipment to dock with another craft (shuttle or otherwise)... and they only had 2 EVA suits onboard...which would have required an almost impossible minimum of 4 EVAs...but assuming that, against all odds, they could do the impossible and get all 7 members safely aboard, you have the logistics problems to consider...
The Soyuz needs 2 ppl (1 if safety is thrown to the wind) to launch...it can only take 3 back with it...which means they would need to put up at least 4 Soyuz capsules to get all 7 back...and this is if they had 4 of them ready to launch...which they don't...
Atlantis could be ready in ~2 weeks if safety checks were thrown out...they'd have to prep the crew (2 man launch crew is the absolute minimum)...and make modifications to carry 9 crew members...
This mission wasn't scheduled to dock with the ISS...so aside from not having the docking kit, it was not aligned correctly...which also means it would not have had enough fuel to get to the ISS...
So, assuming that you didn't lose any astronauts in this amazing feat...you would also have to explain to the American taxpayers why you had to spend billions of dollars, risk many lives, and leave a billion dollar piece of equipment to burn up in orbit because of a "possible" risk...
Also remember that the crew only had enough supplies to last them until the 5th of February (4 days from when it burned up)...the problem was that there are not enough CO2 scrubbing canisters...Now, they only use up a portion of all of the canisters, so if they dug the old ones out of the trash and went to the threshold of pain for each one, they could maybe have made that last for a maximum of 7 days...
I have to stress that I do not agree with the original poster. I think the astronauts knew the risks as well, but I don't think they were somehow going on knowing that they would burn up on reentry...they would have listened to the engineers who were telling them that it didn't prove any significant risk to the success of the mission...while all of the astronauts were extremely smart human beings, they are only trained in what they need to know...they are not going to be second guessing the decisions of the ground crew...
Not sure if the size is a major factor, but I think that's where the number 3 comes in...This was the same size of the crews aboard the MIR...
As a matter of fact, Russia wasn't ever able to send up more than 3 Cosmonauts at a time (the limitation of the Soyuz Space Capsule)...
If I'm not mistaken, the ISS actually only requires 2 ppl to keep it functional...the 3rd crew member does scientific research...
What actually happens is that they trade off...
But, the current plan is to send up 2 more crew members aboard the Soyuz Space Capsule in May...One Russian and one as yet unnamed American...
They would spend their time keeping the Space Station functional, and if the shuttle is still grounded when they are to return, 3 would go up this time, and the Space Station would function by using the Soyuz as the primary method of operation...
As far as the rockets onboard the station, they still use the engines from the progress capsule to help reduce wear on the station's engines...
The ISS would probably stay up (supported by the Russians) even if the shuttle program were to be dismantled. Remember the complaints about MIR...that the Russians weren't going to be serious about the ISS till they left the MIR...
While that's what the astronauts might have wanted, and "they knew the risks", there's also a specific monetary and infrastructure impact resulting from the loss of the Columbia...
There's 1 less shuttle now, and there's still question of whither or not this could happen again. Also worth a mention is that the only purpose the shuttle is serving now is strictly scientific...satellite ground-to-orbit and military missions are using other methods (many are unmanned)...
As emotional as this topic might be, it may be better to come up with another reusable design, or it might even make sense to go back to a disposable craft design...
Like it not, the astronauts didn't design the shuttle and they didn't deal with the economics of space flight...those people are still with us...and they will be the ones that decide the future of NASA...
It worked OK for the Apple II, amongst many early home micros...
And the only way they started selling those systems was when they started giving the IIe to schools...if they start giving schools their hardware, then I'll change my tune...
1. I had to specially select Vi for install and emacs auto installed...(Flame away)..
The most likely reason for this is that emacs needs to be installed to use "set -o emacs" and make the prompt behave like doskey in M$-DOS. Just a guess, but Mandrake probably has a good bit of "converts" from Windoze/M$-DOS systems...
If not for this requirement, it is likely that neither would be installed...both are not really "easy" for the average user to pick up...
I personally use VI, but I understand that a great deal of users would prefer to use another app (something more GUI friendly)...
2. Gnome meeting was not installed...by default
Should you really expect this??? I mean, if you know you need VoIP support, you'll probably already be looking for it...
The other reason this is probably not installed by default is that H.323 requires opening of firewalled ports...which could be a bad thing if you're trying to harden your system...
3. I am having trouble changing some of the default loggin, and boot manager stuff....
How??? Are you using a command line or GUI...what exactly are you trying to change? This is rather vague...if you're a little more specific, maybe I can help...
I'm going to pay $200 for a system that was designed by 1 person???
I think not...how much debugging has she done? Has she tested with alternate configurations? How do I know there aren't any bugs in the hardware? What about software bugs??
Not something for people trying to do serious work -- that's what your desktop computer is for -- but something for people that like really get into the guts of the system.
How so? Umh, you can't get into the "guts" of a desktop? There were certainly a lot of hacks for the old C= 64...but this is going to be a piece of compatable hardware...many of the old "hacks" will be impossible with this new hardware...in that case, wouldn't it be better for them to make a new system?
That's nice...but, this will not be very useful compared to todays apps and emulators...now if they could get the hardware down to size, this would be a great PDA...
Looking at the pictures & specs, it requires an ATX case & power supply...
And it's listed at ~$200 for just the board...there isn't even a real SID chip in there...you have to add your own SID chips to get the "authentic experience"...by comparison, the same $200 should get you an AMD-based motherboard+cpu+ram combo in the 2-2.5 GHz range...which should be more than enough power to run any 6502 emulator...
** Floppy/IDE Interface In the initial release these interfaces will not have any support software (with the exception of 1581 emulation), it is hoped that with the ease of interfacing to the floppy and IDE drives a more 'software oriented individual' will develop the necessary support software for these devices.
Translation: You'll only be able to use the 3.5 floppy drive emulation...and we couldn't get anything else to work with it...we hope you can write the software...
I'll wait for the next generation...or maybe the generation after that...
Umh, actually no...this was before most of the error correction schemes that appeared after the technology hit 14.4Kbps...
Before that, when you would pick up a phone, the modem would drop carrier almost instantly.
However, one of the kewlest things I've seen was what I was able to do with my Vic-Modem (C= 64)...the modem was a 300 baud modem, but you could force the modem to renegotiate @450bps after you were connected (for some reason it wouldn't dial out @450bps)...but this was so kewl at the time...imagine being able to squeeze out an extra 50 MegaBits from a 100 MegaBit NIC today...very kewl stuff at the time...
As for the most resilient modem I've seen...it would have to be my old LineLink ProModem 144e (from my Amiga days)...the thing still works...
Because it's been done before...I mean there's nothing ultra kewl about old technologies...all of the cars on the list are unique because they are firsts in some way or use alternative fuel sources...
The only one that seems to stray from that definition is the Audi A8 and the Trailblazer...the A8 is just lotsa goodies...and the displacement-on-demand technology in the Trailblazer has been used by Mercedes for a while...
Umh, since when did they start telling ppl what to do with their project page? What keeps the author from editing the project comment text or opening a bug saying that the project is dead...yea, you would have to look for it, but it's not hard to do it for yourself...
What would be helpful is an option to only show projects with files available...a lot of the projects on SourceForge are "wouldn't it be kewl if" projects...
Just a wild guess, but it's probably similar to how the Tivo does its update procedure. There are 2 boot partitions on the system...when an upgrade comes through, the system tests the integrity of the upgrade, switches the boot partition and reboots...
I would figure they probably use a more elaborate system...but it's probably the same in practice...of course, they have simulators/emulators on the ground that can accurately recreate the satelite's internal components...so, there should be no bugs in the system when the patches are sent...
The only thing they'ld need to worry about is noise on the uplink (corrupted files) and possible hardware failure...corrupted files could be tested for prior to patching, and hardware problems can be fixed by having backup systems...
As a side note, if these students are not disabled, then it might be better to use a browser to teach them to read rather than have it read for them...
As far as Westwood, although they are disolving the subsidiary, EA still owns rights to some of their previous games...Most likely, they will still release C&C titles with the Westwood name...
Actually, the same thing happened to Psygnosis US when they were merged with 989 Studios...
Just a thought, but the shuttle isn't exactly a plastic toy...meaning that exterior paint, glue for tiles, interior cabin material (PVC especially), fuel, etc can become toxic when it burns...
Yea, there might have been something on the shuttle that we didn't know about...but this was a civilian mission and not a military mission. We already know they were doing research into various medical technologies (draw you own conclusions here)...What if if it happens to be an electronic device, there is possibility of static discharge...I mean, wouldn't it be tragic if someone found a data recorder that "survived" and a static discharge from picking it up destroyed it???
Then again, we don't know what hit the shuttle...maybe it was radioactive...
Of course, anyone following the salvage effort knows that they are using GPS coordinates to map all debris...moving a piece would certainly throw off the calculations...
So, there could be a lot of reasons for the request to not touch debris...it might be related to a specific concern, but they are most likely just "playing it safe"...
Well, it's fairly clear...if you admit to stealing that code, you are clearly in violation...if, on the other hand, if you deny that is where you obtained the code, they would have to prove the likely-hood that you came up with those 3 lines of code on your own...
In this case, it's probably a much larger chunk of code (PCI Subsystem and IO Subsystem)...and, upon review of the code, it will be obvious that they stole code...
The TiVo hacking community does not support it to a large degree...it's kind of like the hack to read the video fom the player...TiVo doesn't want it done so their wish is respected because of all of the support they give to the hacking community...
This shouldn't stop you...because if you know anything about the TiVo, you'ld know that it runs Linux...and the programming is in a standard format...as a matter of fact, there are scripts for the TiVo that pull data from from free listing sites.
There's also the fact that you can use the TiVo like a "Smart VCR" to record shows without any listings...
So, unless you're completely clueless, a working TiVo will never be a "doorstop"...
Umh, it's iRiver that makes the RioVolt...They also do firmware upgrades...
So, they are the one to pester...of course, the iMP-250 is not available from iRiver America (exclusitivity agreements)...
But, the SlimX series (iMP-350 and iMP-400) are more likely to get Ogg Vorbis support...
From what I hear the SlimX players are more powerful than previous players...
So, it's not likely that your 250 will get support...maybe the iMP-150 (which seems to be the only early model still being produced)...of course, you should check out the FAQ first...
You should check out The History of NASCAR...very interesting read...many ppl know about the moonshine thing, but how many know about the real history of the sport???
There's a lot of science and engineering involved with NASCAR...which is why the modern drivers are more engineers than mechanics...
This is also one reason why I think the current drivers and crews are much better role models than most of our athletes in traditional sports (football, baseball, boxing, etc)...
How dense does it have to be? The tiles were known to break under the finger pressure required to secure the pieces to the body of the craft...
How so?
First thing is they did not have the docking equipment to dock with another craft (shuttle or otherwise)... and they only had 2 EVA suits onboard...which would have required an almost impossible minimum of 4 EVAs...but assuming that, against all odds, they could do the impossible and get all 7 members safely aboard, you have the logistics problems to consider...
The Soyuz needs 2 ppl (1 if safety is thrown to the wind) to launch...it can only take 3 back with it...which means they would need to put up at least 4 Soyuz capsules to get all 7 back...and this is if they had 4 of them ready to launch...which they don't...
Atlantis could be ready in ~2 weeks if safety checks were thrown out...they'd have to prep the crew (2 man launch crew is the absolute minimum)...and make modifications to carry 9 crew members...
This mission wasn't scheduled to dock with the ISS...so aside from not having the docking kit, it was not aligned correctly...which also means it would not have had enough fuel to get to the ISS...
So, assuming that you didn't lose any astronauts in this amazing feat...you would also have to explain to the American taxpayers why you had to spend billions of dollars, risk many lives, and leave a billion dollar piece of equipment to burn up in orbit because of a "possible" risk...
Also remember that the crew only had enough supplies to last them until the 5th of February (4 days from when it burned up)...the problem was that there are not enough CO2 scrubbing canisters...Now, they only use up a portion of all of the canisters, so if they dug the old ones out of the trash and went to the threshold of pain for each one, they could maybe have made that last for a maximum of 7 days...
I have to stress that I do not agree with the original poster. I think the astronauts knew the risks as well, but I don't think they were somehow going on knowing that they would burn up on reentry...they would have listened to the engineers who were telling them that it didn't prove any significant risk to the success of the mission...while all of the astronauts were extremely smart human beings, they are only trained in what they need to know...they are not going to be second guessing the decisions of the ground crew...
Not sure if the size is a major factor, but I think that's where the number 3 comes in...This was the same size of the crews aboard the MIR...
As a matter of fact, Russia wasn't ever able to send up more than 3 Cosmonauts at a time (the limitation of the Soyuz Space Capsule)...
If I'm not mistaken, the ISS actually only requires 2 ppl to keep it functional...the 3rd crew member does scientific research...
What actually happens is that they trade off...
But, the current plan is to send up 2 more crew members aboard the Soyuz Space Capsule in May...One Russian and one as yet unnamed American...
They would spend their time keeping the Space Station functional, and if the shuttle is still grounded when they are to return, 3 would go up this time, and the Space Station would function by using the Soyuz as the primary method of operation...
As far as the rockets onboard the station, they still use the engines from the progress capsule to help reduce wear on the station's engines...
The ISS would probably stay up (supported by the Russians) even if the shuttle program were to be dismantled. Remember the complaints about MIR...that the Russians weren't going to be serious about the ISS till they left the MIR...
While that's what the astronauts might have wanted, and "they knew the risks", there's also a specific monetary and infrastructure impact resulting from the loss of the Columbia...
There's 1 less shuttle now, and there's still question of whither or not this could happen again. Also worth a mention is that the only purpose the shuttle is serving now is strictly scientific...satellite ground-to-orbit and military missions are using other methods (many are unmanned)...
As emotional as this topic might be, it may be better to come up with another reusable design, or it might even make sense to go back to a disposable craft design...
Like it not, the astronauts didn't design the shuttle and they didn't deal with the economics of space flight...those people are still with us...and they will be the ones that decide the future of NASA...
It worked OK for the Apple II, amongst many early home micros...
And the only way they started selling those systems was when they started giving the IIe to schools...if they start giving schools their hardware, then I'll change my tune...
1. I had to specially select Vi for install and emacs auto installed...(Flame away)..
The most likely reason for this is that emacs needs to be installed to use "set -o emacs" and make the prompt behave like doskey in M$-DOS. Just a guess, but Mandrake probably has a good bit of "converts" from Windoze/M$-DOS systems...
If not for this requirement, it is likely that neither would be installed...both are not really "easy" for the average user to pick up...
I personally use VI, but I understand that a great deal of users would prefer to use another app (something more GUI friendly)...
2. Gnome meeting was not installed...by default
Should you really expect this??? I mean, if you know you need VoIP support, you'll probably already be looking for it...
The other reason this is probably not installed by default is that H.323 requires opening of firewalled ports...which could be a bad thing if you're trying to harden your system...
3. I am having trouble changing some of the default loggin, and boot manager stuff....
How??? Are you using a command line or GUI...what exactly are you trying to change? This is rather vague...if you're a little more specific, maybe I can help...
Well, then I'm mistaken...that's even worse...
I'm going to pay $200 for a system that was designed by 1 person???
I think not...how much debugging has she done? Has she tested with alternate configurations? How do I know there aren't any bugs in the hardware? What about software bugs??
Not something for people trying to do serious work -- that's what your desktop computer is for -- but something for people that like really get into the guts of the system.
How so? Umh, you can't get into the "guts" of a desktop? There were certainly a lot of hacks for the old C= 64...but this is going to be a piece of compatable hardware...many of the old "hacks" will be impossible with this new hardware...in that case, wouldn't it be better for them to make a new system?
That's nice...but, this will not be very useful compared to todays apps and emulators...now if they could get the hardware down to size, this would be a great PDA...
Looking at the pictures & specs, it requires an ATX case & power supply...
And it's listed at ~$200 for just the board...there isn't even a real SID chip in there...you have to add your own SID chips to get the "authentic experience"...by comparison, the same $200 should get you an AMD-based motherboard+cpu+ram combo in the 2-2.5 GHz range...which should be more than enough power to run any 6502 emulator...
What's worse is listed at the end of this page...
** Floppy/IDE Interface
In the initial release these interfaces will not have any support software (with the exception of 1581 emulation), it is hoped that with the ease of interfacing to the floppy and IDE drives a more 'software oriented individual' will develop the necessary support software for these devices.
Translation: You'll only be able to use the 3.5 floppy drive emulation...and we couldn't get anything else to work with it...we hope you can write the software...
I'll wait for the next generation...or maybe the generation after that...
Umh, actually no...this was before most of the error correction schemes that appeared after the technology hit 14.4Kbps...
Before that, when you would pick up a phone, the modem would drop carrier almost instantly.
However, one of the kewlest things I've seen was what I was able to do with my Vic-Modem (C= 64)...the modem was a 300 baud modem, but you could force the modem to renegotiate @450bps after you were connected (for some reason it wouldn't dial out @450bps)...but this was so kewl at the time...imagine being able to squeeze out an extra 50 MegaBits from a 100 MegaBit NIC today...very kewl stuff at the time...
As for the most resilient modem I've seen...it would have to be my old LineLink ProModem 144e (from my Amiga days)...the thing still works...
Because it's been done before...I mean there's nothing ultra kewl about old technologies...all of the cars on the list are unique because they are firsts in some way or use alternative fuel sources...
The only one that seems to stray from that definition is the Audi A8 and the Trailblazer...the A8 is just lotsa goodies...and the displacement-on-demand technology in the Trailblazer has been used by Mercedes for a while...
Umh, since when did they start telling ppl what to do with their project page? What keeps the author from editing the project comment text or opening a bug saying that the project is dead...yea, you would have to look for it, but it's not hard to do it for yourself...
What would be helpful is an option to only show projects with files available...a lot of the projects on SourceForge are "wouldn't it be kewl if" projects...
Not exactly...Most small businesses use a "middle man" for their transaction completion...
Yahoo is one of the most common...they keep information on shipping charges, taxes, price, etc and it is their responsibility to secure the process...
Just a wild guess, but it's probably similar to how the Tivo does its update procedure. There are 2 boot partitions on the system...when an upgrade comes through, the system tests the integrity of the upgrade, switches the boot partition and reboots...
I would figure they probably use a more elaborate system...but it's probably the same in practice...of course, they have simulators/emulators on the ground that can accurately recreate the satelite's internal components...so, there should be no bugs in the system when the patches are sent...
The only thing they'ld need to worry about is noise on the uplink (corrupted files) and possible hardware failure...corrupted files could be tested for prior to patching, and hardware problems can be fixed by having backup systems...
If you're using Linux on your iPaq, try Festival...
As far as I know, TTS is not included in the newest builds of Mozilla, so Access Mozilla is still your best location for TTS needs...
Access Mozilla should be a good starting point...even better is that ViaVoice is free for the disabled...
Blind Linux is also a good start...
As a side note, if these students are not disabled, then it might be better to use a browser to teach them to read rather than have it read for them...
They basically invented the RTS market which makes this a sad time.
... Dan Bunten ...
Really? Actually, probably not...That probably belongs to one guy
M.U.L.E. - Ozark Softscape (1984)
Modem Wars - Electronic Arts (1988)
Command HQ - Microplay (1991)
Global Conquest - Microplay (1992)
Compare that to Westwood's first RTS game...
Dune II (1992)
As far as Westwood, although they are disolving the subsidiary, EA still owns rights to some of their previous games...Most likely, they will still release C&C titles with the Westwood name...
Actually, the same thing happened to Psygnosis US when they were merged with 989 Studios...
Just a thought, but the shuttle isn't exactly a plastic toy...meaning that exterior paint, glue for tiles, interior cabin material (PVC especially), fuel, etc can become toxic when it burns...
Yea, there might have been something on the shuttle that we didn't know about...but this was a civilian mission and not a military mission. We already know they were doing research into various medical technologies (draw you own conclusions here)...What if if it happens to be an electronic device, there is possibility of static discharge...I mean, wouldn't it be tragic if someone found a data recorder that "survived" and a static discharge from picking it up destroyed it???
Then again, we don't know what hit the shuttle...maybe it was radioactive...
Of course, anyone following the salvage effort knows that they are using GPS coordinates to map all debris...moving a piece would certainly throw off the calculations...
So, there could be a lot of reasons for the request to not touch debris...it might be related to a specific concern, but they are most likely just "playing it safe"...
Well, it's fairly clear...if you admit to stealing that code, you are clearly in violation...if, on the other hand, if you deny that is where you obtained the code, they would have to prove the likely-hood that you came up with those 3 lines of code on your own...
In this case, it's probably a much larger chunk of code (PCI Subsystem and IO Subsystem)...and, upon review of the code, it will be obvious that they stole code...
The TiVo hacking community does not support it to a large degree...it's kind of like the hack to read the video fom the player...TiVo doesn't want it done so their wish is respected because of all of the support they give to the hacking community...
This shouldn't stop you...because if you know anything about the TiVo, you'ld know that it runs Linux...and the programming is in a standard format...as a matter of fact, there are scripts for the TiVo that pull data from from free listing sites.
There's also the fact that you can use the TiVo like a "Smart VCR" to record shows without any listings...
So, unless you're completely clueless, a working TiVo will never be a "doorstop"...
I wasn't suggesting that this policy is correct, but just that the hacking community respects their wishes...