[RWP] Windoweyes Still Can't Run Reaper 64

[Roy Shtupler]

just checked the menu feature with Jaws on my 2 systems , one with xp 32 bit 
, the other with win7 64 bit; it reports/changes the wrong track.
will surely find a solution eventually; probably using some Python and 
reaScript code.
you may be right , perhaps it's due to the difference in components , video 
drivers etc.
SA in its virtual mouse , sees the graphical buttons on the screen along 
with their tooltips , so you can right-click on them with Shift+Spacebar in 
virtual mouse mode , and it shows and alters the proper values.
cheers
Roy.
http://elephant-dolphin.bandcamp.com
----- Original Message ----- 
From: "Indigo" <33indigo at charter.net>
To: "Reapers Without Peepers" <rwp at reaaccess.com>
Sent: Tuesday, July 03, 2012 11:57 PM
Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64


> Roy, maybe it's best said that I heard; or imagined; hearing a hint from 
> Russia about Ivan's group being bought out, or was it muscled 
> out;whatever;   by another corporation with different interests, so, 
> realistically, that's the end of ReaAccess development.
> Frankly, with my simple recording needs; i get along fine with ReaAccess 
> like it is.
> Also, I use that extended track properties menu workaround all the time in 
> XP and Wineyes 6.1, and never had it alter the wrong track's properties.
>
> More and more, Roy, I realize these differences are caused by our 
> particular computer's mix of components, CPU made in Redlands, Washington, 
> or Israel, or Germany, , motherboard from Taiwan, Indonesia, or China, or 
> The Phillipines, memory from China, hard drive from Tialan, Korea, 
> whatever.
> No wonder we get such different results from the same software.
>
> This $378.98 AMD  four core Acer from Walmart is the friendliest to 
> screenreaders I've ever had; I believe because the CPU has totally 
> integrated graphics, onboard the CPU, only 32 microns distance between the 
> CPu and graphics,  graphics designed by AMD/A t i; drivers written by AMD, 
> and the motherboard is Acer designed, or at least they put their name on 
> it smile.
> The hard drive is a Seagate Barracuta, which should be okay, if it isn't 
> one of those last high failure rate  run Seagate put out just before they 
> merged with Samsung.
> Whatever the reason, maybe just luck, it works for screenreaders on win7 
> 64, better than the Intel I7 2600 I use for a daw.
> When the $17 swappable hard drive trays arrive, I'll make a hard drive for 
> this one  with XP, and at least have it as a backup daw
> I'm very curious to learn if it runs as glitch free on XP as it does on 
> Win7 64.
>
> I think your breakthrough for quantization in Reaper was about my last 
> stumbling block at making music totally within Reaper.
> I have nothing against using Sonar for what Reaper lacks, though.
> I had already dug out an ancient installer for Sonar Home Studio version 
> 4, and planned to do quantization in it.
> I felt totally at home in that simple program, it just can't compare to 
> Reaper's 64 bit clarity, but it can do all I need in midi quantization.
> I lost touch with sonar about version 6, and never got competence with 7 
> and 8., and don't miss them anymore.
>
> I believe it's magnificent for you to extend the capability of ReaAccess 
> though
> Even though we are discovering home made shortcuts and work arounds, we 
> shouldn't need to.
>
> Thanks,
> Indigo L
> .
>
>
>
>
> On 7/3/2012 3:00 PM, Roy Shtupler wrote:
>> here , it altered the wrong track also in xp.
>> so I'm working either in Jaws or System Access; SA also runs off a usb
>> hard drive , so it's a real handy solution when recording on someone
>> else's computer.
>> as for reaaccess , will begin tacling and learning Python to re-write it
>> , since I don't expect much from the original developers.
>> I don't want to put anybody down , but they spoke of a new version last
>> September , and nothing's new up til now.
>> cheers
>> Roy.
>> http://elephant-dolphin.bandcamp.com
>> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>> Sent: Tuesday, July 03, 2012 8:31 PM
>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>
>>
>>> Thanks, Roy.
>>> I found it, but I don't know what needs to be done to it to make
>>> Wineyes run both Reaper and ReaAccess.
>>> My personal solution is to record in XP.
>>> A little while ago, I retested the workaround to get the track
>>> properties menu with NVDA; and it did alter the input mode on the
>>> wrong track, as you suspected it might.
>>> Despite many different approaches, I would sometimes get the input
>>> monitor menu when pressing the applications key, and sometimes a Jump
>>> To Marker j menu, and sometimes a dialog for setting how the master VU
>>> meters read.
>>> I don't get those glitches in XP; with either Wineyes or NVDA.
>>> This is the friendliest computer for screenreaders I ever had, and
>>> Wineyes 7.5.2 is doing fine on Win7 64; but, for me, Win7 is better
>>> and more robust for surfing, and email; but I like the stability of XP
>>> for recording.
>>> Indigo L
>>>
>>>
>>> On 7/3/2012 10:58 AM, Roy Shtupler wrote:
>>>> it's a dll called Reaper-Access , located in the Reaper (or Reaper x64)
>>>> folder , in the plugins subdirectory.
>>>> hope this helps
>>>> Roy.
>>>> http://elephant-dolphin.bandcamp.com
>>>> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>> Sent: Tuesday, July 03, 2012 4:48 PM
>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>
>>>>
>>>>> Patrick, when you say you copied all the 32 bit files necessary for
>>>>> ReaAccess to work, can you list what those files are
>>>>>
>>>>> Last night I noticed that when I open Reaper with NVDA, there is a
>>>>> single file called Reaper X64 running in Windows Task Manager, but
>>>>> when I open Reaper with Wineyes there are two files running in Windows
>>>>> Task Manager: Reaper 1 and Reaper 2.
>>>>> When opened by NVDA, the task manager entry says Reaper x64, but when
>>>>> opened by Windoweyes neither of the 2 entries say x64.
>>>>>
>>>>> Some interaction of Wineyes Win7 and ReaAccess is opening 2 files, or
>>>>> maybe it's an erroneous display in Windows Task Manager.
>>>>> I tried the usual method in Task Manager of ending one of the files,
>>>>> but only succeeded in exiting Reaper.
>>>>> I changed a few cursorrrrr settings in Wineyes, thinking there's a
>>>>> setting that might open Reaper with only a single instance running, no
>>>>> luck so far.
>>>>>
>>>>> The fact that Wineyes can run Reaper 64 just fine, as long as
>>>>> ReaAccess is not installed, must indicate it's not a problem of how
>>>>> Wineyes opens Reaper, but some interaction between Wineyes and
>>>>> ReaAccess that doesn't occur in 32 bits.
>>>>> I tried to locate an actual reaAccess.exe to run Win7's troubleshoot
>>>>> compatibility mode on it, but can't find reaAccess.exe.
>>>>>
>>>>> I feel that the clue will be there, by comparing what is there in the
>>>>> Reaper folder in Program Files; with and without ReaAccess installed;
>>>>> and comparing what NVDA is doing with those files compared to what
>>>>> Wineyes is doing with them.
>>>>> This level of computer science is a mystery to me, though; I'll defer
>>>>> to you and Roy to hopefully discover something that will solve this.
>>>>>
>>>>> I notice in Reaper's installed data .ini file, whatever its proper
>>>>> title is, there is an entry Reaper 32 host equals 1, as well as Reaper
>>>>> 64 Host equals 1.
>>>>> I think I'll change that 1 for a zero on the 32 host entry, and see
>>>>> what happens.
>>>>> Indigo L
>>>>>
>>>>> On 7/3/2012 12:34 AM, Patrick Perdue wrote:
>>>>>> I believe ReaAccess uses the same files regardless of if you're
>>>>>> running
>>>>>> 32 or 64-bit Reaper. If you install the 64-bit version of Reaper on a
>>>>>> 64-bit system, it will install properly. If, however, you install a
>>>>>> 32-bit version of Reaper on a 64-bit system, where that is the only
>>>>>> installed version of Reaper, the ReaAccess installer will look for a
>>>>>> 64-bit Reaper that doesn't exist, complain loudly, and not work at
>>>>>> all.
>>>>>> If you have both the 32 and 64-bit Reaper installed, ReaAccess may
>>>>>> only
>>>>>> work with the 64-bit version by default.
>>>>>>
>>>>>> I use the 32-bit version of Reaper on my 64-bit system to have
>>>>>> access to
>>>>>> some old 32-bit DirectX plugins, which don't show up on any 64-bit
>>>>>> DAW.
>>>>>> 32-bit bridging only works with VST plugins, not DirectX ones. I also
>>>>>> have the 64-bit version installed. However, to make Reaper32 and
>>>>>> ReaAccess play nice together on the two Windows 7 64 systems I put it
>>>>>> on, I had to copy all the files necessary for ReaAccess to work from
>>>>>> another working 32-bit Reaper directory, which was installed on a
>>>>>> Windows XP machine.
>>>>>>
>>>>>> On 7/2/2012 10:37 PM, Indigo wrote:
>>>>>>> You're right, I should insert several tracks, to be sure the method
>>>>>>> works in Windows 7 with NVDA.
>>>>>>> However, it's the same method I've been using with Wineyes 6.1 in 
>>>>>>> XP,
>>>>>>> and there it always changes track properties for the selected track.
>>>>>>>
>>>>>>> meanwhile, I think I found a possible clue as to what's different
>>>>>>> when
>>>>>>> Reaper is opened with Wineyes as opposed to being opened with NVDA.
>>>>>>>
>>>>>>> If I start Reaper with NVDA, then press ctrl+shift+escape to open 
>>>>>>> the
>>>>>>> Windows task manager, in the applications list I find Reaper X64
>>>>>>> running.
>>>>>>>
>>>>>>> But, if i open Reaper with Windoweyes, it locks up, and in the
>>>>>>> Windows
>>>>>>> Task Manager there are 2 instances of Reaper shown as running.
>>>>>>>
>>>>>>> I tried ending one of the instances with E button, but only the top
>>>>>>> Reaper running 1 would close, no response when I tried closing 
>>>>>>> Reaper
>>>>>>> running 2.
>>>>>>>
>>>>>>> I have no idea how two instances could show when Wineyes opens
>>>>>>> Reaper,
>>>>>>> and only one when NVDA opens it, but maybe it's a clue as to what's
>>>>>>> going on.
>>>>>>> You know, Reaper opens just fine in Win7 64 with ReaAccess not
>>>>>>> installed, so it's something going on between Wineyes and ReaAccess,
>>>>>>> but
>>>>>>> only in Win7 64.
>>>>>>> Is there a special 64 bit version of ReaAccess, or only the one
>>>>>>> version?
>>>>>>>
>>>>>>> I tried to find the .exe file for ReaAccess, in hopes of running
>>>>>>> windows
>>>>>>> 7's troubleshoot compatibility on it; but couldn't find anything
>>>>>>> called
>>>>>>> reaAccess.exe.
>>>>>>> Indigo L
>>>>>>>
>>>>>>> On 7/2/2012 7:26 PM, Roy Shtupler wrote:
>>>>>>>> this method really works.
>>>>>>>> if however , you have multiple tracks in a project , there might
>>>>>>>> be a
>>>>>>>> difference between what you're told , and which track actually got
>>>>>>>> altered.
>>>>>>>> e.g insert 3 or 4 tracks.
>>>>>>>> change something in the first track e.g record mode , input , etc.
>>>>>>>> now , go down to another track and try the same method; do you
>>>>>>>> still get
>>>>>>>> a report on which track's properties got altered?
>>>>>>>> thanks a bunch
>>>>>>>> Roy.
>>>>>>>> http://elephant-dolphin.bandcamp.com
>>>>>>>> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
>>>>>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>>>>>> Sent: Tuesday, July 03, 2012 1:58 AM
>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>
>>>>>>>>
>>>>>>>>> Roy, I just looked at Reaper 4.22 again with NVDA.
>>>>>>>>> I inserted an empty track, armed it, pressed ctrl+up arrow to make
>>>>>>>>> the
>>>>>>>>> applications menu display.
>>>>>>>>> Then i selected the item with ctrl+shift+right arrow, even there
>>>>>>>>> was
>>>>>>>>> no actual item, then pressed the applications key, then down
>>>>>>>>> arrowed
>>>>>>>>> quickly.
>>>>>>>>> I got the correct track options menu that begins Monitor input M.
>>>>>>>>> You can arrow down to click on monitor input midi, or monitor 
>>>>>>>>> input
>>>>>>>>> audio.
>>>>>>>>> You can also select stereo there, instead of the default mono
>>>>>>>>> recording, plus many other track options not offered in ReaAccess
>>>>>>>>> from
>>>>>>>>> the tab key.
>>>>>>>>>
>>>>>>>>> i find that if I don't do that little nonsense step of selecting
>>>>>>>>> the
>>>>>>>>> non existent item; when I press the applications key and down
>>>>>>>>> arrow; I
>>>>>>>>> get another menu that begins with Jump to Marker J
>>>>>>>>> Once the monitorr input M menu displays, it displays every time
>>>>>>>>> after
>>>>>>>>> that, no problem.
>>>>>>>>> This behaveor is exactly the same for me in NVDA or Wineyes; any
>>>>>>>>> later
>>>>>>>>> Reaper version; in XP or Win7 64.
>>>>>>>>> Indigo L.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/2/2012 3:37 PM, Roy Shtupler wrote:
>>>>>>>>>> I suspect yes , maybe it's a tiny little fix , but we don't
>>>>>>>>>> have the
>>>>>>>>>> source code , and the developers vanished for some odd reason.
>>>>>>>>>> well ... on to learning Python and re-writing ReaAccess.
>>>>>>>>>> best
>>>>>>>>>> Roy.
>>>>>>>>>> http://elephant-dolphin.bandcamp.com
>>>>>>>>>> ----- Original Message ----- From: "Patrick Perdue"
>>>>>>>>>> <patrick at pdaudio.net>
>>>>>>>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>>>>>>>> Sent: Monday, July 02, 2012 1:46 AM
>>>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> I can get to that from the track context menu. Is this now 
>>>>>>>>>>> broken
>>>>>>>>>>> with
>>>>>>>>>>> later versions of reaper? This is actually the main reason I am
>>>>>>>>>>> still
>>>>>>>>>>> using 3.7.x.
>>>>>>>>>>> On 7/1/2012 6:29 PM, Roy Shtupler wrote:
>>>>>>>>>>>> for instance , the button that , when right-clicked on , brings
>>>>>>>>>>>> the
>>>>>>>>>>>> menu
>>>>>>>>>>>> that assigns a track to a particular input; either midi or
>>>>>>>>>>>> audio.
>>>>>>>>>>>> best
>>>>>>>>>>>> Roy.
>>>>>>>>>>>> http://elephant-dolphin.bandcamp.com
>>>>>>>>>>>> ----- Original Message ----- From: "Indigo"
>>>>>>>>>>>> <33indigo at charter.net>
>>>>>>>>>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>>>>>>>>>> Sent: Sunday, July 01, 2012 11:34 PM
>>>>>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> A while back; just to understand if; and how; it could be
>>>>>>>>>>>>> done, I
>>>>>>>>>>>>> installed a fresh copy of Reaper 4X plus ReaAccess, then
>>>>>>>>>>>>> assigned
>>>>>>>>>>>>> the
>>>>>>>>>>>>> audio and midi interface settings, plus tried as many usual
>>>>>>>>>>>>> actions as
>>>>>>>>>>>>> I could think of, all with NVDA, and found work arounds for
>>>>>>>>>>>>> everything.
>>>>>>>>>>>>> The part that concerned me was getting the midi portss 
>>>>>>>>>>>>> enabled,
>>>>>>>>>>>>> which
>>>>>>>>>>>>> ; when I did them in Wineyes and Jaws; required Wineyes mouse
>>>>>>>>>>>>> pointer/jaws PC cursor moves at the numPad, but a little
>>>>>>>>>>>>> experimentation with NVDA +flat review, move to focus, move
>>>>>>>>>>>>> navigator
>>>>>>>>>>>>> object to mouse, and I got all midi ports enabled with NVDA.
>>>>>>>>>>>>> I don't remember trying NVDA in Reaper's IO dialog, but I 
>>>>>>>>>>>>> can't
>>>>>>>>>>>>> think
>>>>>>>>>>>>> of anything in there that NVDA can't accomplish.
>>>>>>>>>>>>> Right click menus seem very similar to what I get with 
>>>>>>>>>>>>> Wineyes.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I still have Reaper 4.22 on this Win7 64 machine, so if you
>>>>>>>>>>>>> want
>>>>>>>>>>>>> me to
>>>>>>>>>>>>> try some particular move with NVDA, let me know.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'll go to the midi editor and see if it's as easy to edit 
>>>>>>>>>>>>> midi
>>>>>>>>>>>>> events as with Wineyes.
>>>>>>>>>>>>> If NVDA will do your midi quantization work arounds; Roy, I
>>>>>>>>>>>>> think
>>>>>>>>>>>>> nothing is lacking.
>>>>>>>>>>>>> I was going to uninstall Reaper, from this computer; since 
>>>>>>>>>>>>> it's
>>>>>>>>>>>>> totally impossible to run with Wineyes 7.5.22.
>>>>>>>>>>>>> I prefer Wineyes 6.1 to NVDA; in my XP daw; because I like to
>>>>>>>>>>>>> look at
>>>>>>>>>>>>> the whole screen with wineyes num pad navigation keys, and 
>>>>>>>>>>>>> feel
>>>>>>>>>>>>> half
>>>>>>>>>>>>> blinded by NVDA's lack of the same entire screen review
>>>>>>>>>>>>> facility.
>>>>>>>>>>>>> I don't doubt that very skilled NVDA user can find anything
>>>>>>>>>>>>> on a
>>>>>>>>>>>>> screen, it just frustrates me to get only bits and pieces;
>>>>>>>>>>>>> here and
>>>>>>>>>>>>> there; with various shortcuts; instead of the entire screen
>>>>>>>>>>>>> all at
>>>>>>>>>>>>> once.
>>>>>>>>>>>>> If NVDA ever gets easy screen navigation at the number pad,
>>>>>>>>>>>>> look
>>>>>>>>>>>>> out
>>>>>>>>>>>>> Jaws and Window-Eyes.
>>>>>>>>>>>>> My greatest frustration with NVDA lately is; on Win7; that it
>>>>>>>>>>>>> doesn't
>>>>>>>>>>>>> pop up Win7's U A C dialog for me.
>>>>>>>>>>>>> Instead it goes silent.
>>>>>>>>>>>>> I have poked around with the spacebar and pressing Y for
>>>>>>>>>>>>> yes, and
>>>>>>>>>>>>> actually got programs to run, but it's just guessing; no
>>>>>>>>>>>>> confirmation
>>>>>>>>>>>>> speech during the U A C dialog.
>>>>>>>>>>>>> Indigo L
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 7/1/2012 11:17 AM, Patrick Perdue wrote:
>>>>>>>>>>>>>> I haven't actually needed to access those controls in that
>>>>>>>>>>>>>> way,
>>>>>>>>>>>>>> since
>>>>>>>>>>>>>> I can do all that through ReaAccess. I am still using Reaper
>>>>>>>>>>>>>> 3.7.x by
>>>>>>>>>>>>>> choice. Maybe things are different now, not sure.
>>>>>>>>>>>>>> Case in point though. NVDA sometimes won't see stuff like
>>>>>>>>>>>>>> that,
>>>>>>>>>>>>>> but
>>>>>>>>>>>>>> it reads the Izotope RX stand-alone stuff better than System
>>>>>>>>>>>>>> Access
>>>>>>>>>>>>>> does, or Jaws, for that matter.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This entire discussion is kind of ironic, since all but one
>>>>>>>>>>>>>> of the
>>>>>>>>>>>>>> SeroTalk podcasts are produced with Reaper... using NVDA.
>>>>>>>>>>>>>> Oops!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Jul 1, 2012, at 10:08 AM, Roy wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> hi Patrick
>>>>>>>>>>>>>>> do you succeed in reading and right-clicking all the track
>>>>>>>>>>>>>>> control
>>>>>>>>>>>>>>> panel buttons using NVDA? e.g the i/o button , monitoring
>>>>>>>>>>>>>>> etc;
>>>>>>>>>>>>>>> these
>>>>>>>>>>>>>>> seem to read just with System Access's virtual mouse mode.
>>>>>>>>>>>>>>> cheers
>>>>>>>>>>>>>>> Roy.
>>>>>>>>>>>>>>> -----Original Message----- From: Patrick Perdue
>>>>>>>>>>>>>>> Sent: Sunday, July 01, 2012 4:54 PM
>>>>>>>>>>>>>>> To: Reapers Without Peepers
>>>>>>>>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yep, System Access does, indeed, work fine with ReaAccess. 
>>>>>>>>>>>>>>> It
>>>>>>>>>>>>>>> uses
>>>>>>>>>>>>>>> the same API NVDA does. I prefer using it with NVDA though,
>>>>>>>>>>>>>>> as it
>>>>>>>>>>>>>>> reads some of the plugin interfaces a bit better than System
>>>>>>>>>>>>>>> Access
>>>>>>>>>>>>>>> does. Functionality is basically the same with all the stock
>>>>>>>>>>>>>>> Reaper
>>>>>>>>>>>>>>> stuff.
>>>>>>>>>>>>>>> But, as is always the case, SA occasionally gets things that
>>>>>>>>>>>>>>> NVDA
>>>>>>>>>>>>>>> misses, and the other way around.
>>>>>>>>>>>>>>> It hasn't been a one screenreader world for a while now.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Jul 1, 2012, at 9:41 AM, Roy wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> yeh , system access works with no problems also on 64-bit
>>>>>>>>>>>>>>>> with
>>>>>>>>>>>>>>>> Reaper 64-bit.
>>>>>>>>>>>>>>>> cheers
>>>>>>>>>>>>>>>> Roy.
>>>>>>>>>>>>>>>> -----Original Message----- From: Kevin Brown
>>>>>>>>>>>>>>>> Sent: Friday, June 29, 2012 2:08 PM
>>>>>>>>>>>>>>>> To: rwp at reaaccess.com
>>>>>>>>>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Have you tryed system access?,...system access runs reaper
>>>>>>>>>>>>>>>> with no
>>>>>>>>>>>>>>>> problems,...I've been using it for 6 years now...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> 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
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>
>>
>> _______________________________________________
>> 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