From: "Rich Gauszka" 

 "Robert Comer"  wrote in message
news:44046c42{at}w3....
>> According to VMWare group product manager Srinivas Krishnamurtiff, there
>> are some things that are not virtualizable.  One of them is the host
>> system's process.  Said Krishnamurtiff "there's a processor
ID that's not
>> virtualizable."
>
> That's a possibility, even with Virtual PC, neither one emulate the
> processor, that would be a big speed hit.  fwiw, in all my travels with
> VPC and VMWare, I never had to reactivate because of changing hosts. (not
> yet anyway!)  The processor ID isn't the only thing that's not
> virtualizable.
>
> Maybe I haven't had a problem with it because I don't have one of the
> newer processors...
>
> --
> Bob Comer
>
>
>

I think the blog author got into trouble when he copied his XP virtual
application from an AMD laptop to a Pentium laptop. That's when he got bit
by the processor ID change and subsequent XP activation

I loaded the VMware Player and several of the canned Platform Vendors
Virtual Applications are ok - Ubuntu Linux ( was even able to do Updates
once I figured out the password was Ubuntu )  and The Browser (Firefox )
Appliance. They all seem to work well with 256 mb of  allocated memory

Others - the 'community' virtual appliances -  have problems - KDE on SUSE
( no sound ) and ReactOS 0.29 ( really bad alpha version of a windows lone 
), Syllable ( no network,  0.6 release that needs work  )

--- BBBS/NT v4.01 Flag-5