I have posted a warning about the app_info bugfix at beta number crunching. To lazy to repost. To cranky. Stay the *poot* away from it.

Carl

---

It is SEXY to DONATE!
Skype = demiurg2

I'm not quite sure why, but I'm running optimized apps just fine. When I first did the app_info fix, it worked (once). Then when I reverted to the original file name, it stopped working. So I did what seemed to be the next logical thing and renamed the app_info file again and left it that way. And I've been uploading and downloading with zero problems (except for occasionally not being able to update, which eventually works itself out) for a full day now. I have no idea why the renamed file isn't fouling things up, but at least on my two crunchers (one PC, one Mac), it's running smooth as butta. Hope that helps.

I removed the app_info.xml file (put it on the desktop) and restarted BOINC and got me a full tub of work on all machines. I've put it back in and restored it several times with no difficulty. Just shut down BOINC before doing it

---

I have posted a warning about the app_info bugfix at beta number crunching. To lazy to repost. To cranky. Stay the *poot* away from it.

Why? It works perfectly...and it's easy to do. The only problem is that it's not automated.

---

Dublin, California
Team: SETI.USA

I have posted a warning about the app_info bugfix at beta number crunching. To lazy to repost. To cranky. Stay the *poot* away from it.

Why? It works perfectly...and it's easy to do. The only problem is that it's not automated.

Have a look at Jason Gee's profile

I have posted a warning about the app_info bugfix at beta number crunching. To lazy to repost. To cranky. Stay the *poot* away from it.

Why? It works perfectly...and it's easy to do. The only problem is that it's not automated.

Have a look at Jason Gee's profile

I don't think that applies to my Macs.... =;^)

---

Dublin, California
Team: SETI.USA

I have posted a warning about the app_info bugfix at beta number crunching. To lazy to repost. To cranky. Stay the *poot* away from it.

Why? It works perfectly...and it's easy to do. The only problem is that it's not automated.

Have a look at Jason Gee's profile

I don't think that applies to my Macs.... =;^)

...however you could take some time and modify it to apply to your Macs and then post it in your profile and help others... :)

At any rate, I asked some that had the expertise on various platforms to make an automated job for the common platforms, so alternatively you could wait on someone to automate it for Mac platforms...

Why? It works perfectly...and it's easy to do. The only problem is that it's not automated.

Have a look at Jason Gee's profile

I don't think that applies to my Macs.... =;^)

...however you could take some time and modify it to apply to your Macs and then post it in your profile and help others... :)

At any rate, I asked some that had the expertise on various platforms to make an automated job for the common platforms, so alternatively you could wait on someone to automate it for Mac platforms...

I just don't have the l33t sklz to do something like that. My point earlier in this thread was to show that the work-around...er...worked. No problems at all. Someone was saying that it didn't work.

---

Dublin, California
Team: SETI.USA

I have posted a warning about the app_info bugfix at beta number crunching. To lazy to repost. To cranky. Stay the *poot* away from it.

Why? It works perfectly...and it's easy to do. The only problem is that it's not automated.

It wrecked boinc so badly that I had 63 beta and main WUs get computational errors in a row. It whacked the ben_joe app beyond repair. So I had to reinstall everything and ditch the 63 WUs:-(
And yes I tested everything before doing it.

Carl

---

It is SEXY to DONATE!
Skype = demiurg2

Hmmm. OS/2 Warp, if I'm not mistaken. Looking at the SETI applications page, your operating system is not listed, so I guess there's no official, Berkeley-supported and Berkeley-hosted application for you.

So it must be a home-build or team-build version, right? And you must use the app_info.xml mechanism to get it to run?

That is, in fact, the primary purpose of the "anonymous platform" technique. And it's broken. If you use app_info, you get no work. And if you don't use app_info, you get no work. B****r.

All I can suggest is that you put pressure on David Anderson to get the BOINC Server source code fixed, perhaps adding to my bug report (trac ticket 194), or you put pressure on Eric and Matt to down-grade the BOINC servers to the earlier version of the BOINC server software. Neither will be easy, or welcome, but it's the best I can suggest. Sorry.

Edit - third possibility - could your team get the latest BOINC v5.9.11 to compile on OS/2? If so, there's a report in the Bugs...but where? thread - unconfirmed as yet - that the app_info will work again, and your existing application should work too.

Real edit - sorry, hit 'reply' to my own post instead of 'edit' - past midnight here, and I've been working on this one for 14 hours: time for bed very soon. But you get my drift....

Hi Richard, thanks for the skinny. I have been having no luck understanding all the tricks for the Windows platform and how to translate them to OS/2. We had one anonymous benefactor who was able to compile the BOINC and SETI source code for SETI Enhanced after the demise of Classic. But that has been the only application we have ever received. No updates to newer clients or newer BOINC platform software.. It was barely possible to compile the original source code from what I have been told. So unless SETI fixes the problem on their server side, it seems that all of us running OS/2 will have to say goodbye to SETI and all distributed computing. A real shame.

Thanks for the explanation, Keith

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

So unless SETI fixes the problem on their server side, it seems that all of us running OS/2 will have to say goodbye to SETI and all distributed computing. A real shame.

Keith,

Am I remembering correctly that an unofficial addon somewhere enabled Win32 (ala Windows 95) support in a Win-OS/2 emulation mode? If so, couldn't you run in that mode instead of OS/2 native? If it is still stuck at Windows 3.1 emulation (like it was when I left OS/2 at version 2.1), then nevermind...

Brian

So unless SETI fixes the problem on their server side, it seems that all of us running OS/2 will have to say goodbye to SETI and all distributed computing. A real shame.

Keith,

Am I remembering correctly that an unofficial addon somewhere enabled Win32 (ala Windows 95) support in a Win-OS/2 emulation mode? If so, couldn't you run in that mode instead of OS/2 native? If it is still stuck at Windows 3.1 emulation (like it was when I left OS/2 at version 2.1), then nevermind...

Brian

Hi Brian, no it never worked. We have ODIN that can run some very simple Windows 32 bit programs and there is some directly ported stuff from Innotek that uses some Windows 32 bit libraries but they are rare. I tried to run the Windows app under ODIN and it failed miserably and wouldn't even unpack or install. Thanks for the help anyway.

Keith

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

So unless SETI fixes the problem on their server side, it seems that all of us running OS/2 will have to say goodbye to SETI and all distributed computing. A real shame.

Keith,

Am I remembering correctly that an unofficial addon somewhere enabled Win32 (ala Windows 95) support in a Win-OS/2 emulation mode? If so, couldn't you run in that mode instead of OS/2 native? If it is still stuck at Windows 3.1 emulation (like it was when I left OS/2 at version 2.1), then nevermind...

Brian

Hi Brian, no it never worked. We have ODIN that can run some very simple Windows 32 bit programs and there is some directly ported stuff from Innotek that uses some Windows 32 bit libraries but they are rare. I tried to run the Windows app under ODIN and it failed miserably and wouldn't even unpack or install. Thanks for the help anyway.

Keith

Keith,

Have you seen the changes over at trac ticket 194? You may want to add another comment about your (lack of) ability to get new versions of BOINC.

So unless SETI fixes the problem on their server side, it seems that all of us running OS/2 will have to say goodbye to SETI and all distributed computing. A real shame.

Keith,

Am I remembering correctly that an unofficial addon somewhere enabled Win32 (ala Windows 95) support in a Win-OS/2 emulation mode? If so, couldn't you run in that mode instead of OS/2 native? If it is still stuck at Windows 3.1 emulation (like it was when I left OS/2 at version 2.1), then nevermind...

Brian

Hi Brian, no it never worked. We have ODIN that can run some very simple Windows 32 bit programs and there is some directly ported stuff from Innotek that uses some Windows 32 bit libraries but they are rare. I tried to run the Windows app under ODIN and it failed miserably and wouldn't even unpack or install. Thanks for the help anyway.

Keith

OK. I last ran OS/2 in like 1996, so I am not up on all of what happened since about Warp 3. Shame that IBM abandoned it though...

Brian

So unless SETI fixes the problem on their server side, it seems that all of us running OS/2 will have to say goodbye to SETI and all distributed computing. A real shame.

Keith,

Am I remembering correctly that an unofficial addon somewhere enabled Win32 (ala Windows 95) support in a Win-OS/2 emulation mode? If so, couldn't you run in that mode instead of OS/2 native? If it is still stuck at Windows 3.1 emulation (like it was when I left OS/2 at version 2.1), then nevermind...

Brian

Hi Brian, no it never worked. We have ODIN that can run some very simple Windows 32 bit programs and there is some directly ported stuff from Innotek that uses some Windows 32 bit libraries but they are rare. I tried to run the Windows app under ODIN and it failed miserably and wouldn't even unpack or install. Thanks for the help anyway.

Keith

Keith,

Have you seen the changes over at trac ticket 194? You may want to add another comment about your (lack of) ability to get new versions of BOINC.

Richard, I see they have closed the ticket. What I'm not sure of is whether they are implying that the issue or ticket is closed because a new client solves the problem. As you understand well is that we do not have access to a client app programmer. The "Yuri" guy is a phantom of some sorts. It was over a month before our 5.13 and 5.49 client apps showed up after shutting down of Classic. The link to the temporary server that hosted the apps for a short time is long gone. Nobody has a good email address to contact the programmer. We are just hoping that he is monitoring this mess and will once again come to our rescue.

Do you think that SETI's message about the problem from yesterday being solved means that our older anonymous platform apps will work again?

Keith

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

So unless SETI fixes the problem on their server side, it seems that all of us running OS/2 will have to say goodbye to SETI and all distributed computing. A real shame.

Keith,

Am I remembering correctly that an unofficial addon somewhere enabled Win32 (ala Windows 95) support in a Win-OS/2 emulation mode? If so, couldn't you run in that mode instead of OS/2 native? If it is still stuck at Windows 3.1 emulation (like it was when I left OS/2 at version 2.1), then nevermind...

Brian

Hi Brian, no it never worked. We have ODIN that can run some very simple Windows 32 bit programs and there is some directly ported stuff from Innotek that uses some Windows 32 bit libraries but they are rare. I tried to run the Windows app under ODIN and it failed miserably and wouldn't even unpack or install. Thanks for the help anyway.

Keith

OK. I last ran OS/2 in like 1996, so I am not up on all of what happened since about Warp 3. Shame that IBM abandoned it though...

Brian

Brian, actually, Serenity Systems International has been doing a quite credible job of enhancing and promoting the current invocation of OS/2 Warp. They are the defacto handlers of all current OS/2 development along with their parters Innotek Systems GMbH. Yes, shame that Microsoft killed the development of OS/2.

Keith

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Do you think that SETI's message about the problem from yesterday being solved means that our older anonymous platform apps will work again?

Keith

No, I'm afraid I don't: I think that message just relates to the complete server breakage yesterday.

But I do think that they've got a fresh team in the office today, and they are fully focussed on getting it working: we had a developer call 'Janus' pop up in Number Crunching an hour ago, asking for tests to see if the 'shared memory' error had been fixed. (It has, but not the app_info). We need to watch, test, watch, test and watch again.

I do hope, however, that we'll get a progress blog late afternoon (PDT), then we can start to enumerate what has been fixed and what is still broken. If anonymous platform is still on the second list, we start asking why.

Running chicken apps again apparently with no problem...this was after a personal discussion with Eric

---

Running chicken apps again apparently with no problem...this was after a personal discussion with Eric

Blurf: Was this a workaround on your computers (app_info etc...) or is a fix in place @ Berkeley to correct this issue?

---

Proud member of SETI.USA

Running chicken apps again apparently with no problem...this was after a personal discussion with Eric

Blurf: Was this a workaround on your computers (app_info etc...) or is a fix in place @ Berkeley to correct this issue?

Sorry missed this Chicken.

All of a sudden while on the phone with Eric it worked. Worked without the chicken app--went back to the chicken app and it worked.

Today however I'm getting http errors w/ and w/out Chicken App

---