[RWP] reaaccess won't install despite doing the obvious

Gianluca Apollaro gianluca.apollaro88 at gmail.com
Mon Jun 11 11:17:00 EDT 2012


Hi Derek and list,
Another thing you can try is running a portable version of reaper 32 bit 
on your 64 bit machine. I think the fact you're installing a 32 bit 
version on a 64 bit machine might confuse rea-access.
Bye,
Gianluca
SkypeID: gianluca8815
Il 11/06/2012 17:02, Indigo ha scritto:
> Are you running Jaws or Window-Eyes?
> So why not install the 64 bit version of Reaper onto a 64 bit machine; 
> open and close it at least once; then install ReaAccess?
> Would you get the same issues then?
> More and more I find these issues are according to the hardware in the 
> computer, what CPU combo with which motherboard and; especially for 
> screenreaders; which video graphics chipset is used.
> Before I got my I7 on an MCI board ; I tried an AMD Phenom on another 
> model of MCI board, and it was very jittery, not at all stable on Win7 
> 64 with Window-Eyes.
> I'm typing now on another AMD Phenom, on a Alvarex FoxCon motherboard, 
> also on same Win7 64 and Window-Eyes, and it's very steady and 
> dependable, and very fast.
> My own theory is that NVidia drivers are not well written, so I avoid 
> NVidia N"Force video chipsets now.
> This motherboard has AMD graphics, which work perfectly with the AMD 
> CPU to make it very stable.
> I'm looking for another of this same model, the Hewlett Packard 
> P6719C, just because I don't need to gamble on its stability.
> Anyway, just because you got away with 32 bit Reaper on many 64 bit 
> systems, doesn't mean all hardware combos will work with it.
>
> Also, on my I7 with MCI board; although it is very stable running; I 
> could not get 64 bit Reaper to run simultaneously with ReaAccess when 
> running Window-Eyes 7.5.2.
> They installed fine, but when I attempted to open Reaper it locked up.
> If I removed ReaAccess, then I could run Reaper just fine, only 
> without all the great benefits of ReaAccess.
> So, I decided not to butt my head against the brick wall of 
> inaccessibility, I uninstalled Win7 64 from the I7 machine and now run 
> XP Pro 32 on any 32 bit version of Reaper.
> As far as I can tell, except for giving up running more than 4gbs of 
> Ram, I can record in Reaper as well as one can do with 64 bit.
> Reaper is so efficient you can run many tracks, soft synths and 
> effects on 4 gigs of ram, no crackling or dropout issues.
> Just my 2 cents worth,
> Indigo L
>
>
>
>
> On 6/10/2012 4:13 PM, Derek Lane wrote:
>> I've successfully installed and configured reaper/reaaccess for many 
>> people, including all of my pc's with the exception of my new 
>> production machine. I get the error message that says that some 
>> components can't be found, and the installer closes. This would 
>> normally mean that I hadn't ran or initially configured reaper.
>> The problem is that I had ran reaper before and everything was where 
>> it should be in the reaper folder and in %appdata%
>> The only weird thing is that I'm installing the 32 bit reaper on a 64 
>> bit version of windows 7. However, this shouldn't matter especially 
>> considering I've done this twice.
>> I can get the reaaccess plugin, and import the key map from another 
>> computer containing a working reaper/reaccess combo. However, that 
>> doesn't solve the underlying issue and could cause others.
>> Help.
>>
>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>






More information about the Rwp mailing list