Futher corrections

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@1841 a1c6a512-1295-4272-9138-f99709370657

1 files changed, 75 insertions, 73 deletions

diff --git a/www/docs/FAQ b/www/docs/FAQ
index da11257430..791be64663 100644
--- a/www/docs/FAQ
+++ b/www/docs/FAQ
@@ -12,40 +12,41 @@
 -------------------------------------------------------------------
 
 
-Rockbox FAQ 
------------
-
 Q1. What is a FAQ?
 A1. A rare small animal of the species 'Textius Electronicus'. It is known for
     its helpful attitude and vicious misspellings.
 
-Q2. What is Rockbox?  What is it's purpose?
-A2. The purpose of this project is to write an Open Source replacement 
+Q2. Okay, fine, what is _this_ FAQ?
+A2. This FAQ is for questions (that we have answers too) that have been asked
+    repeatedly either in emails or on IRC.
+
+Q3. What is Rockbox?  What is it's purpose?
+A3. The purpose of this project is to write an Open Source replacement 
     firmware for the Archos Jukebox 6000, Studio 20 and Recorder MP3 players.
 
-Q3. I want to write code for my Archos, how do I proceed?
-A3. First make sure to read the file CONTRIBUTING in the firmware directory
+Q4. I want to write code for my Archos, how do I proceed?
+A4. First make sure to read the file CONTRIBUTING in the firmware directory
     on Sourceforge.  See http://rockbox.haxx.se/firmware/CONTRIBUTING
     if you do not want to have to wade through the CVS directories.
 
-Q4: Whats CVS?
-A4: Concurrent Versions System (http://www.cvshome.org).  We have a small
+Q5: Whats CVS?
+A5: Concurrent Versions System (http://www.cvshome.org).  We have a small
     help page about how to use this to get, update and commit files on the web
     at http://rockbox.haxx.se/cvs.html
 
-Q5. What exactly is the CONTRIBUTING file? 
-A5. Just like the name implies, it lists conventions that the project follows, 
+Q6. What exactly is the CONTRIBUTING file? 
+A6. Just like the name implies, it lists conventions that the project follows, 
     and in turn asks you to follow, for the formating of source code in
     general.
 
-Q6. Okay, so I read CONTRIBUTING and although I don't agree with all your 
+Q7. Okay, so I read CONTRIBUTING and although I don't agree with all your 
     conventions, I am going to be sensible and follow them anyway.  Now what?
-A6. Start by reading up on the information about the jukeboxes on our web page.
+A7. Start by reading up on the information about the jukeboxes on our web page.
     Then go into CVS and look at the code we've written. Then take what you
     need and start writing.
 
-Q7. Okay, so how do I submit a patch?
-A7. Run: "diff -u oldfile newfile > patchfile" against the file(s) you have 
+Q8. Okay, so how do I submit a patch?
+A8. Run: "diff -u oldfile newfile > patchfile" against the file(s) you have 
     changed.  Then mail the output to any member of the development team and 
     we will take it under consideration.  (Please remember that all 
     submissions are not automatically accepted, this is nothing personal.)
@@ -53,52 +54,52 @@ A7. Run: "diff -u oldfile newfile > patchfile" against the file(s) you have
     Of if you would like to run the diff against the current cvs code:
         cvs diff -ub [file(s)]
 
-Q8. I want to join the development team, but don't have a SourceForge account,
+Q9. I want to join the development team, but don't have a SourceForge account,
     what should I do?
-A8. Head on over to http://sourceforge.net/account/register.php and create an
+A9. Head on over to http://sourceforge.net/account/register.php and create an
     account for yourself.
 
-Q9. Do you have a mailing list?
-A9. Sure do!  As a matter of fact, we have several of them for specific 
+Q10. Do you have a mailing list?
+A10. Sure do!  As a matter of fact, we have several of them for specific 
     things.  Please check out: http://rockbox.haxx.se/mail/
 
-Q10. Great you have a mailing list!  Is there anyway for me to catch up on
+Q11. Great you have a mailing list!  Is there anyway for me to catch up on
      past posts?
-A10. Check out the archives at: http://rockbox.haxx.se/mail.cgi
+A11. Check out the archives at: http://rockbox.haxx.se/mail.cgi
 
-Q11. How can I meet the developers working on the project?
-A11. One way is by visiting us on IRC.  Head on over to the server
+Q12. How can I meet the developers working on the project?
+A12. One way is by visiting us on IRC.  Head on over to the server
      irc.openprojects.net, and then join "#rockbox".  There is usually at 
      least one person there.  If you don't see any activity, feel free to post 
      questions anyway, serveral of us log the channel and will get you answers
      when we unidle.
 
-Q12: Wow, you guys talk on IRC alot?  I wish I had been around for those 
+Q13: Wow, you guys talk on IRC alot?  I wish I had been around for those 
      conversations to see what happened.
-A12: We are glad you mentioned that!  http://rockbox.haxx.se/irc happens
+A13: We are glad you mentioned that!  http://rockbox.haxx.se/irc happens
      to have a list of various logs we have recorded of events in the channel.
      Feel free to read up, and ask questions on what you find.
 
-Q13. What is this "SourceForge" you keep mentioning?
-A13. http://www.sourceforge.net
+Q14. What is this "SourceForge" you keep mentioning?
+A14. http://www.sourceforge.net
 
-Q14. Can the changes or the software that Rockbox suggests or offers 
+Q15. Can the changes or the software that Rockbox suggests or offers 
      possibly damage my Archos Player?
-A14. All firmware mods that are presented are still highly experimental. 
+A15. All firmware mods that are presented are still highly experimental. 
      Try them at your own risk. We offer no guarantee that this software, or 
      the hardware modifications we show, will not damage your player or void 
      your warranty.  That said, we have not been able to damage any of our 
      units by modifying only the firmware. You can accidentally password 
      protect your harddisk, but there are ways around that. (See below.)
 
-Q15. I want to see what the inside of my player looks like, but I would really
+Q16. I want to see what the inside of my player looks like, but I would really
      like to avoid voiding my warranty.  Is there anything you can suggest?
-A15. We have a collection of photos of both the player and recorder. Look at
+A16. We have a collection of photos of both the player and recorder. Look at
      http://rockbox.haxx.se/internals/
 
-Q16. What exactly are you trying to achieve with this line of development?
+Q17. What exactly are you trying to achieve with this line of development?
      (A.K.A. whats your purpose for being here?)
-A16. Firstly, we wouldn't start something like this if we didn't simply enjoy
+A17. Firstly, we wouldn't start something like this if we didn't simply enjoy
      it profusely. This is great fun!
      Secondly, we feel the firmware is lacking some features and contain a
      number of annoying bugs that we want to fix.
@@ -126,9 +127,9 @@ A16. Firstly, we wouldn't start something like this if we didn't simply enjoy
            being on the list does not mean it isn't a neat idea.  Bring it to 
            the list.
 
-Q17. I don't see you mentioning other file types on your list of ideas.  What 
+Q18. I don't see you mentioning other file types on your list of ideas.  What 
      about supporting those?
-A17. Pessimist's Answer: At the current time we belive this is not very likely 
+A18. Pessimist's Answer: At the current time we belive this is not very likely 
      The Micronas chip (MAS3507) decoder in the archos does not natively 
      support decoding and there is very little program space in the player to 
      implement it ourselves.  The alternative would be to write a software 
@@ -145,18 +146,18 @@ A17. Pessimist's Answer: At the current time we belive this is not very likely
      help, please get in touch!
 
 
-Q18. What about supporting playing of WMA files?
-A18. Dear Mr. Gates, you have two options.  Re-read question #17, or go buy 
+Q19. What about supporting playing of WMA files?
+A19. Dear Mr. Gates, you have two options.  Re-read question #17, or go buy 
      your own project.
 
-Q19. When do you think there will be a version available for my Archos?
-A19. We recently released version 1.2, so head on over to 
+Q20. When do you think there will be a version available for my Archos?
+A20. We recently released version 1.2, so head on over to 
      http://rockbox.haxx.se/download.html and pull it down.
      Make sure to read the release notes.
      (http://rockbox.haxx.se/download/rockbox-1.2-notes.txt).  
 
-Q20. What do you plan to add to coming versions?
-A20. We have a rough idea of which features we plan/expect/hope to be included
+Q21. What do you plan to add to coming versions?
+A21. We have a rough idea of which features we plan/expect/hope to be included
      in which versions.  Once again, remember that none of this is written in 
      stone (noticing a pattern yet?) 
 
@@ -166,16 +167,16 @@ A20. We have a rough idea of which features we plan/expect/hope to be included
      Version 1.4
          Recording?
 
-Q21. I tried one of your firmware files and now I can't access my harddisk!
+Q22. I tried one of your firmware files and now I can't access my harddisk!
      When I turn on my jukebox, it says:
                      Part. Error
                      Pls Chck HD
-A21. Your harddisk has been password protected. We're not 100% sure why it
+A22. Your harddisk has been password protected. We're not 100% sure why it
      happens, but you can unlock it yourself. Look at:
      http://rockbox.haxx.se/lock.html
 
-Q22: This FAQ doesn't answer the question I have.  What should I do?
-A22: You have a couple options here.  You could forget the question, find an
+Q23: This FAQ doesn't answer the question I have.  What should I do?
+A23: You have a couple options here.  You could forget the question, find an
      easier question, or accept '42' as the answer no matter what.  We don't 
      really recommend any of these (though I do opt for '42' often myself).
      What we do recommend is stopping by IRC, reading 
@@ -184,43 +185,43 @@ A22: You have a couple options here.  You could forget the question, find an
      mailing list (rockbox@cool.haxx.se) or the FAQ maintainer listed on the 
      project homepage.
 
-Q23: Are there other ways to contact the developers?
-A23: Yes.
+Q24: Are there other ways to contact the developers?
+A24: Yes.
 
-Q24: Are you going to tell us what they are?
-A24: No.  Post to the mailing list and we will get back to you.
+Q25: Are you going to tell us what they are?
+A25: No.  Post to the mailing list and we will get back to you.
 
-Q25: But I _really_ want to talk with you in person.
-A25: I'm sorry.  My girlfriend/boyfriend/pet says I'm not allowed to, and the
+Q26: But I _really_ want to talk with you in person.
+A26: I'm sorry.  My girlfriend/boyfriend/pet says I'm not allowed to, and the
      doctors here won't let me have pens or pencils.  They say its some rule
      about us not having sharp objects.  I'm sorry.  Now please stop calling me
      here.
 
-Q26: Will you ever port Quake II to the Archos?
-A26: If you ask that again, I'm sending your address and phone number to the 
+Q27: Will you ever port Quake II to the Archos?
+A27: If you ask that again, I'm sending your address and phone number to the 
      guy that mailed us with question #23.
 
-Q27: Umm, was that sarcasm?
-A27: That's it, I'm mailing him now.
+Q28: Umm, was that sarcasm?
+A28: That's it, I'm mailing him now.
 
-Q28: Is this legal? I mean, I'd just hate to see something like that 
+Q29: Is this legal? I mean, I'd just hate to see something like that 
      challenged under the DMCA in all its ridiculousness. Any thoughts or 
      ideas?
-A28: We believe we are in the green on this.  We are not violating anyone's
+A29: We believe we are in the green on this.  We are not violating anyone's
      copyright and we are not circumventing any copy protection scheme.
      This has been a big point for the project since its inception.  Some 
      people wanted us to distribute patched versions of the original firmware,
      but seeing as that _would_ have violated Archos' copyright, we didn't 
      follow that course of action.
 
-Q29: On the website [and various information postings] you state 
+Q30: On the website [and various information postings] you state 
         "Every tiny bit was reverse engineered, disassembled and then 
          re-written from scratch".  
      If it was rewritten from scratch then why was it first reverse-engineered
      and disassembled? Instead this sounds more like someone disassembled it
      then used the understanding that they gained to create a new version,
      which is not quite the same as "from scratch". 
-A29: Don't confuse the terms.  Reverse engineering means examining a product 
+A30: Don't confuse the terms.  Reverse engineering means examining a product 
      to find out how it works.  Disassembling the firmware is merely one tool 
      used in that examination.  Oscilloscopes and logic analyzers are other 
      tools we have used.  We have written every single byte of the Rockbox 
@@ -230,10 +231,11 @@ A29: Don't confuse the terms.  Reverse engineering means examining a product
      software without first researching the surrounding interfaces, then no 
      software has ever been written from scratch.
 
-Q30: Wait a minute here.  When you released version 1.0 you did not have a single
-     one of the ideas you have mentioned on your website actually implimented!  
-     Calling this version 1.0 is really misleading.  Whats the story?!
-A30: In simple terms, the first release was called 1.0 because it had a basic 
+Q31: Wait a minute here.  When you released version 1.0 you did not have a 
+     single one of the ideas you have mentioned on your website actually 
+     implimented!  Calling this version 1.0 is really misleading.  Whats the 
+     story?!
+A31: In simple terms, the first release was called 1.0 because it had a basic 
      working feature set that worked and had no known bugs. That is what 1.0 
      meant.  It is true that Rockbox 1.0 lacked most of the feature set that 
      every sane user wanted.  However, we never said it was more 
@@ -245,9 +247,9 @@ A30: In simple terms, the first release was called 1.0 because it had a basic
      releases we have completed many of our desired goals, and several new ones
      that were implimented to fullfill user requests.
 
-Q31: I've heard talk of a 'Rolo'.  What is that? (Or 'All you ever wanted
+Q32: I've heard talk of a 'Rolo'.  What is that? (Or 'All you ever wanted
      to know about Rockbox boot loaders')
-A31: The developers have discussed the possibility of a boot loader.  (Mainly
+A32: The developers have discussed the possibility of a boot loader.  (Mainly
      because having one sounds cool, and isn't Rolo just a great name?)
      The idea would be that a user could use the load to choose between
      different verions of Rockbox or the Archo firmware itself.  We have a 
@@ -258,11 +260,11 @@ A31: The developers have discussed the possibility of a boot loader.  (Mainly
      the main release.  Please check the mailing list logs and irc logs for more
      information.  
 
-Q32: I was thinking about making the USB a bit more usable.  What are the
+Q33: I was thinking about making the USB a bit more usable.  What are the
      chances of using the USB port to [play games / share files / list
      the device as something other then a hard drive / sell my soul to you
      for a nickel].  What do you think?
-A32: You really don't want to know what I think, it involves road flares, 
+A33: You really don't want to know what I think, it involves road flares, 
      microwave ovens and shaved cats.  Enough said.  But regarding the USB 
      portion of your question, this is not feasible.  First, any ideas 
      regarding special communications over the USB port will not work because
@@ -274,19 +276,19 @@ A32: You really don't want to know what I think, it involves road flares,
      master involved there can be no communication.  Sorry.  Now about your
      soul.  Would you settle for 3 cents and a small wad of belly button lint?
 
-Q33: When I use RockBox my jukebox's red "error" light turns on a lot, but this
+Q34: When I use RockBox my jukebox's red "error" light turns on a lot, but this
      doesn't happen on the factory firmware.  Why?
-A33: Rockbox uses the red LED as harddisk activity light, not as an error 
+A34: Rockbox uses the red LED as harddisk activity light, not as an error 
      light. Relax and enjoy the music.
 
-Q34: How do I use the loadable fonts?
-A34: Loadable fonts are a work in progress.  We do not have full documentation
+Q35: How do I use the loadable fonts?
+A35: Loadable fonts are a work in progress.  We do not have full documentation
      for it.  The best we can do now is tell you that you need a valid .bdf
      font, and to use the tool "bdf2ajf" from CVS to conver to the .ajf format.
      The final .ajf font must be stored in the archos root as 'system.ajf'
      We do expect more documentation on this process shortly.
 
-Q35: I have a question about the batteries...
-A35: STOP!  We have put togeather a completely different FAQ for battery 
+Q36: I have a question about the batteries...
+A36: STOP!  We have put togeather a completely different FAQ for battery 
      related questions.  Check out: http://rockbox.haxx.se/docs/battery.html