Hello Andy
On 15-Jul-01, you wrote:
>
> I am running the new beta of MD2 1.4.15 and recently it has been
> giving recoverable alerts, sorry I did not get the number. Soon after
> if I close down Voyager 3.3.104 I get a software failure in V,
> 80000003. Is this a problem with voyager or MD2 or just a general lack
> of memory? My A1200 only has 2+16Mb of memory at this time.
>
Since the new beta, sendbrowser.mdrx no longer works, and I am forced to
use Voyager to click on URLs. It went to the new beta of Voyager on my
dh1: partition, and not to 3.2 on dh0:. To get it back to 3.2, I had to
rename the new 101 beta directory, and copy the whole 3.2 drawer to dh1:
Why? And what has buggered sendbrowser.mdrx? Voyager 104, the new
beta was locking up on me most of the time, this is why I went back to
3.2. This is really strange behavior. Why does it go to dh1: and not
dh0: for Voyager? Is there something in the rexx settings I have
missed? Anyway to the subject, I too have had problems with 104 locking
up the system. I think it is at fault and not Microdot. I just hit the
same URL that locked up with 104 last night with 3.2, and it came in
fine. Enough said.
Regards
--
Mike Leavitt [EMAIL PROTECTED] + team Amiga +
__________________________________________________________________
MicroDot-II Mailing List - http://www.vapor.com/md2/
MicroDot-II FAQ: http://faq.vapor.com/md2/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
