A couple months ago I asked folks here about their experiences with the EeePC (see <http://eeepc.asus.com>). In general folks seemed very happy with their purchase, but I thought it'd be interesting to see how they fare once the novelty wears off.

It's been long enough now that those who have them have had plenty of real-world use, and it may also be of interest to the readers here who don't have EeePCs to learn about usage patterns since they're among the best-selling laptops right now - from eeeuser.com:

   It looks like the Eee PC models are continuing to be strong
   in the marketplace, as the Eee PC 901 12G is currently the
   most popular item in the Computers & PC Hardware category
   of Amazon.com Also rounding out the top 10 are the Eee PC
   900 16G (white, Linux) in 7th spot and the Eee PC 900 16G
   (black, XP) in 9th. The Eee PC 1000H just missed the cut in
   12th place.

So if you have an EeePC, please take a moment to let us know how it's working out for you, esp. with regard to using Rev:

- Do you do any Rev development on your EeePC?

- If so, how much of your development do you do on your EeePC
  relative to your other computer(s)?

- What do you like most about using the EeePC,
  and what do you find most annoying?

- Do you target the EeePC in your deployment plans for
  commercial/shareware/freeware apps?

- Which model of EeePC do you have?

- Do you run Linux or XP on it?

- How do you manage synchronizing files (both development
  stackfiles and things like email) between the EeePC and
  your other computer(s)?

- Any other comments about your EeePC experience you can share?

TIA -

--
 Richard Gaskin
 Fourth World Media Corporation
 ___________________________________________________________
 [EMAIL PROTECTED]       http://www.FourthWorld.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to