I know that the current version of the app is pretty much EoL so I wouldn't expect a fix, but can somebody point me in the direction of the distro and version it was built for or at least a compatible one.

I have my AMD K6-2 ready to rock, and I've tried Debian lenny beta2 and sid, but it seems they are too new and error out.
I really don't want to have to dig out my Win98 cd.

Thanks for any help.

UncleVom

Hmmm...

Well it's been awhile since I tried, but my K6-2/500 gagged when I tried to install RH8. IIRC it swallowed RH7 without too much complaining.

That's when I decided it would be a lot happier on 2K and left it at that! ;-)

Alinator

Hmmm...

Well it's been awhile since I tried, but my K6-2/500 gagged when I tried to install RH8. IIRC it swallowed RH7 without too much complaining.

That's when I decided it would be a lot happier on 2K and left it at that! ;-)

Alinator

Both the distros I tried don't seem to have any problems with the ancient hardware and boinc works fine, it's just the 1.22 app itself.

I think it is the same problem that occurs with the newer 64 bit distros, the stock app is built linked to older library versions that don't exist in the newer distros.
Crunch3rs 1.24 build fixes that with statically linked libraries for 64 bit.

I just need pointing to a distro version that supports i486 and has the correct older libraries that will run the 1.22 version. It may be a lost cause.


UncleVom

I have been using Slamd64 12.0 and Bluewhite64 12.1, all working with 1.23. Both are based on Slackware 12.0 and 12.1.

I have been using Slamd64 12.0 and Bluewhite64 12.1, all working with 1.23. Both are based on Slackware 12.0 and 12.1.

I don't think a 64 bit distro is going to be much use with this AMD K6-2 box and I swore off Slack over a decade ago, but thanks. :-)

Anyway I've kinda solved the problem for now I have switched the box to s@h and moved my other quad which was split 50/50 between s@h and mw@h fully over to mw.

Given s@h's problems it suits the purpose, they get the same cruncher I started with back in 1999 and it keeps me running a box on that project.


UncleVom

I have been using Slamd64 12.0 and Bluewhite64 12.1, all working with 1.23. Both are based on Slackware 12.0 and 12.1.

I don't think a 64 bit distro is going to be much use with this AMD K6-2 box and I swore off Slack over a decade ago, but thanks. :-)

Anyway I've kinda solved the problem for now I have switched the box to s@h and moved my other quad which was split 50/50 between s@h and mw@h fully over to mw.

Given s@h's problems it suits the purpose, they get the same cruncher I started with back in 1999 and it keeps me running a box on that project.


UncleVom

I should have added that the 64 bit was built from Slackware, Slackware would most likely work. All for not, happy you found a solution.