On Mon, 2007-11-26 at 15:29 -0200, Gerhard Fiedler wrote:
> Herbert Graf wrote:
> 
> >> The other option is to use a virtual machine and run one of them 
> >> virtualized, rather than dual-boot. I generally find dual-boot a nuisance 
> >> and tend to use it only when absolutely necessary, because you usually 
> >> don't have easy access to your tools and data from the other system (not 
> >> every application is multiplatform :).
> > 
> > For tools wine covers some, but you are correct, many tools, especially
> > in the MCU world are windows only.
> > 
> > As for data, that's a non issue. 
> 
> Not always. I didn't mean access to the raw data (which is of course
> possible), but to the content. Sometimes data is stored in an
> application-specific way, and the access to the file doesn't help you much.
> (E.g. you may have your banking data in a Palm application that runs on
> Palm and Windows, but not on Linux and that stores the data in a
> proprietary encrypted form.)
> 
> Usually you can find some kind of workaround or even solution, but then the
> question is as always how much time you want to spend on this -- or whether
> it's not easier to simply run one of the two systems in a virtual
> environment and not have to spend any time on workarounds and solutions.

My solution is simple: I just don't use apps that do that.

All my day to day apps either are multiplatform, or store their data as
plain text, meaning a "conversion" for a new app is as simple as perhaps
a few commands in vile, or a quick perl script at worst.

Yes, at first the transition will hurt time wise, but once you make it
the freedom in no longer being at the mercy of some software vendor when
it comes to access to your data is very liberating.

TTYL
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist