Date:         Thu, 21 Apr 2016 10:55:42 -0700
Reply-To:     Christophe Guilbert <cguilbert@PICASSO.UCSF.EDU>
Sender:       Vanagon Mailing List <vanagon@gerry.vanagon.com>
From:         Christophe Guilbert <cguilbert@PICASSO.UCSF.EDU>
Subject:      Re: ETKA
In-Reply-To:  <5718E656.5090407@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed

 Content preview:  You create a virtual machine windows XP using vmware player
    , its free. the advantage is that you can move and copy your virtual machine
    anywhere you want (linux , windows 7, 8, 10 and Mac). The disadvantage is
    that you need RAM, at least 2GB including 512MB for you virtual machine windows
    XP. With nowadays computer, it should not be a problem unless you are running
    my grandma computer [...]

 Content analysis details:   (-2.0 points, 5.0 required)

  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.0 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain

You create a virtual machine windows XP using vmware player , its free.
the advantage is that you can move and copy your virtual machine
anywhere you want (linux , windows 7, 8, 10 and Mac). The disadvantage
is that you need RAM, at least 2GB including 512MB for you virtual
machine windows XP. With nowadays computer, it should not be a problem
unless you are running my grandma computer

Chris

On 04/21/2016 07:40 AM, Jon VonOhlsen wrote:
> You should be able to install (for all users) the software using the
> "compatibility" option. Right click on the install icon and select
> properties, then select compatibility. Sounds like running under Win XP
> serv pack 3 is the option.
> Jon
>
> On 4/20/2016 7:48 PM, John Rodgers wrote:
>> Went to load my copy of ETKA on a newer computer - up from 32 bit to 64
>> bits, at 3.0 mhz , using Windows 7, and up pops a message that the
>> program
>> is not compatible. Apparently the software was written in the Win-XP
>> days.
>> So what to do? I'm sure I'm not the only one. Is there a
>> work-around?  I'm
>> lost without it!
>>
>> Thanks,
>>
>> John