Whoa I should have mentioned this.
Hang on guys. I just put the new 1.63 on my computer this past week.
I experienced the 'stall' as I call it for the past year at least and even
communicated with Wayne about thinking is was a WL problem.
It was also the 1.6? version running standalone that I experienced the stall
after repeated transmission of the same buffer when trying to work a DX
station.
This stall is not new, some of us have experienced it for quite a while.
I've experienced it under win98 with absolutely no ancillary programs
running.
And I have experienced it under XP which controls 'resources' very well.
No matter how many concurrent programs I'm running do I see a critical level
of resources now under XP.
While the 'stall' is a bit annoying, I no longer concern myself with it.
I no the buffer will start in a few moments and things will work without
problem.
I made 800+ qso, mostly cqing and I only experienced the 'stall' maybe 4 or
4 times in the 20+ hours.
Not a major problem.
----- Original Message -----
From: "Don Hill AA5AU" <aa5au@bellsouth.net>
To: "WriteLog Reflector" <Writelog@contesting.com>
Sent: Monday, January 06, 2003 9:46 PM
Subject: [WriteLog] MMTTY 1.63 Problem Summary
> I received quite a few responses on this one. Seemed a lot of people
> had the same problem. The post from Bill, W9OL, showed he had the
> problem with MMTTY 1.63 stand alone. Everyone that replied was
> running MMTTY 1.63.
>
> I also received this directly from Hisama, 7L1IOU, who gave me permission
> to post to the reflector:
>
> > Hi Don and John
> >
> > I also had the same problem.
> >
> > I prepared for roundup, exchanged new sound card
> > and upgraded to MMTTY163.
> >
> > I think that MMTTY163 is the cause.
> >
> > It happened similarly not only by Writelog SO2R
> > but by RTCL(by JK1IQK).
> >
> > by resource meter of Win2k, CPU load pointed to 100%
> > in between key up.
> >
> > The solution was restoring to MMTTY162 and
> > sound card which verified.
> > Watching CPU meter,
> > the MMTTY parameter was changed and load was lowered.
> > It returned to SO2R after adjustment.
> >
> > PC is a AT cloen PII 260MHz, Windows 2000, 128MB Mem
> >
> > 73, Hisami 7L4IOU
>
> So it appears to be a problem with MMTTY version 1.63. Although I've
> had reports that 1.63 copied much better than 1.62, I didn't see it.
Personally,
> I thought it was about the same. I can only notice by how it compares
with
> the DXP-38 which runs in a separate RTTY window on both computers.
> MMTTY ran slightly better as usual, but on occasion, the DXP-38 copied
> better (that's the reason we do dual receive, right?).
>
> I plan on going back to 1.62, but I'm not sure what all that entails. I
don't
> know if you can simply re-install 1.62. I'll ask Hisami how he did it.
>
> I will reply directly back to all that replied, but it may take some time.
Some
> of you asked other questions that I would like to comment on.
>
> Was a hell of a contest, eh? Ever seen 80M that good for a RTTY
contest???
>
> 73, Don AA5AU
>
>
> http://www.aa5au.com
> http://www.geocities.com/writelog
>
>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
>
>
|