@Slayer

The sluggishness is probably the pager kicking in, presuming you have a swap partition which is unavoidable (of course, none of IBrowse 2.4's memory is swapable). There is an "issue" with OS4.1 in that it will lock up when running low on ram. A smaller image cache may be advisable in order to help avoid the problem. This is not an IBrowse bug (I get the problem with AWeb and OWB, and practically anything else that starts to exhaust available ram).

BTW, note that "avail flush" is a no-op on OS4.1.

@Monoxyde

You need to disable "Additional buffer-level checking" if you want to rotate between OGR-NG and RC5-72, unless you are offline at the time your OGR-NG in buffer becomes empty, in which case the client will automatically switch to RC5-72 until it is able to grab new work for OGR-NG.

@sundown

http://faq.distributed.net/?file=107

@K-L

For sure the stats are not looking very impressive for AmigaOS PPC - given about 3000 of those 11000 Gnodes completed were from my A1 alone, there can't be many people running the AmigaOS PPC clients at the moment .

@sundown

OGR packet size is variable, so it's hard to say - unless you happen to have some small packets, it's probably hours rather than minutes. The client will only normally flush packets once it has run out of packets to work on. However, via the GUI you can force it to flush any completed packets.

@sundown

Well, you have to submit some packets first, and wait for the stats database to update (which as at midnight GMT every day), assuming you have configured your client correctly (i.e. put your e-mail in as the id). Once you show up, you can login there and assign your work to the Amiga team effort.

@Atheist

It seems some teams diverted their RC5-72 work effort to OGR-25 during the latter stages, hence why the Amiga team was overtaken. Currently we have just moved up to 7th place in OGR-26.

Of course, there are no rules against using linux/PS3 and quad core PCs in the Amiga team effort . That said, there is no PS3 OGR-NG client yet - apparently due to technicial limitations, it might be some time off yet. Altivec equipped AmigaOne's are still pretty fast at OGR-26 in comparison to most PCs.

This isn't an IBrowse thread - maybe I should change my avatar?

@K-L

Quote:
Yep . Glad it's working for you now. Still can't believe I missed that bug in the first place, but then again, it's been over 3 years since I've needed to build a new distributed.net client, so I think I can be excused for being a bit rusty - in a way, it's a miracle I even remembered how the whole process worked

@abalaban

Hadn't thought of that - yeah, maybe AmiUpdate support is worth looking at. Certainly, the clients should not be uploaded to Aminet or OS4Depot, and indeed anywhere else other than distributed.net - that's a general distributed.net rule (not AmigaOS specific ).

Hopefully only the one person noticed that the new OS4 client crashed on anything other than an A1 with G4/Altivec - there's now an updated v2.9101.507b build available that fixes that bug (I took the opportunity to update the icons too, while I was at it).

New AmigaOS clients now available at http://www.distributed.net/download/prerelease.php

@abalaban

OGR-NG has been running on my A1 since yesterday... Will be uploading new client builds for AmigaOS later today/tonight .

@Hans

As I've said before, not too much should be read into the bug count values - not all development or bug fixes are logged on the bugtrack. Besides, it's more important that the closed bugs number goes up than the open issue count goes down (remember that the open issue count is around about the same as when IB2.4 was released - it just wasn't made public). Probably we need to create a vault to move all the issues that are not worth fixing for 3.0 . However, to answer your other question... No, there hasn't been a lot of progress lately, but that's mainly due to cvs downtime and me being busy with other stuff instead.

The site is back to normal now, hopefully.

@Antique

It has been temporarily removed because it suddenly stopped working and was the reason the site has been failing to load at all over the past few days. As soon as I figure out why, teh bug count will be back - looks like our webhost may have changed something on the php side.

@LyleHaze

Unfortunately, there is a bug in the PPC builds of the JavaScript library which can cause the symptoms, that you describe, on exit. This has been fixed for the next IBrowse release.

@AmiDog

Anybody with a serious interest in developing a plugin for IBrowse is welcome to contact me - although there is no SDK yet, the current flash plugin source code is available to those interested and we have set up a mailing list to help support plugin developers (a substitute for the docs, at the moment).

@Atheist

Quote:
Work is going on behind the scenes to bring IBrowse users a better and more stable flash plugin. I somehow doubt we will ever see a flash plugin (or standalone player) on the Amiga as up to date as Adobe's latest version though .

@abalaban

Quote:
Maybe. In what sense though? I should point out that I am not that familiar with dockies. I presume you mean a crunching rate meter/graph or something?

The biggest problem I have right now, with the A1 being my main machine, is accessing the distributed.net cvs. I can't seem to find any cvs client for OS4 that has support for SSH2 connections (without it, I cannot access the distributed.net cvs). The OS4 dnetc port is certainly overdue an update, and there will probably need to be new client builds quite soon when OGR-25 is completed.

@Atheist

Quote:
Try this:

- dnetc -config (or select config from the menu)
- Select "3) Performance related options"
- Select "3) Priority level to run at ==> 0 (lowest/at-idle)"

I would suggest you change this option to 0 (you probably have it set to 4 at the moment).