Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

TB 3.0: Certain operations on certain ng's hang

0 views
Skip to first unread message

Dudley Brooks

unread,
Nov 29, 2009, 3:27:13 PM11/29/09
to
I recently started using 3.0 as my e-mail and newsgroup reader. Certain
ng's cause it to hang when doing View/Threads/Unread. So far this
happens only with the ng's from Sibelius Music (a music notation
product), so I have also posted this to one of their ng's. But it
didn't happen with TB 2.0, so I am posting it here.

I'm mystified: Isn't viewing unread threads purely a function of the
client? If so, why would only certain ng's cause a problem?

FWIW, the Sibelius ng's are privately hosted by Sibelius. Does that have
anything to do with it? Has anyone else experienced a similar problem?

Thanks.

-- Dudley
TB 3.0, MacBook Pro 2.16 GHz Intel Core 2 Duo, 1 GB 667 MHz RAM

Nir

unread,
Nov 30, 2009, 8:53:20 AM11/30/09
to
On Monday 30 November 2009 01:57 AM, Dudley Brooks wrote:
> I recently started using 3.0 as my e-mail and newsgroup reader. Certain
> ng's cause it to hang when doing View/Threads/Unread. So far this
> happens only with the ng's from Sibelius Music (a music notation
> product), so I have also posted this to one of their ng's. But it
> didn't happen with TB 2.0, so I am posting it here.
>
> I'm mystified: Isn't viewing unread threads purely a function of the
> client? If so, why would only certain ng's cause a problem?
>

Right, this problem is related to Tb, not that NG. Tb generally hangs
when index file (.msf) becomes corrupted. You can do following.
Unsubscribe from that NG.
Close Tb.
Goto Tb profile folder / News / Folder of that news account.
Delete that ng related files.
Start Tb.
Subscribe to that ng.

> FWIW, the Sibelius ng's are privately hosted by Sibelius. Does that have
> anything to do with it? Has anyone else experienced a similar problem?
>
> Thanks.
>
> -- Dudley
> TB 3.0, MacBook Pro 2.16 GHz Intel Core 2 Duo, 1 GB 667 MHz RAM

Correct signature syntax is
--<Space Here><Newline><Your sig. text>

--
Nir

signature.asc
0 new messages