Have I missed a step in ghost removal?

Step #1: ignore it.

Works always, the WU is removed from your list after a while. ;-)

---

Thanks Link. That I can do. (^8

---

...

I should have known better than to use the FFTW provided dlls, the compiler put in a CMOVE instruction. That means Pentium-Pro is now the minimum for the stock version.

I hate incompatibility, so I may fix it. But it won't be a high priority compared to other fixes.

---

@SETIEric@qoto.org (Mastodon)

WOW! thank you for looking into my issues.

It seems like a lot of work for just mine and a few other very inefficient computers. The estimate is 11 1/2 days for the current wu. LOL!!

It is able to crunch v6.03 wu so we are good to go. It did crunch 10,000+ Classic wu back in its day.

---

...

The only problem is the only MBv6 work is going to be what's left in the field, so once that's gone that's all she wrote.

@Eric: And Athlon or later for AMD.

The only problem is the only MBv6 work is going to be what's left in the field, so once that's gone that's all she wrote.

@Eric: And Athlon or later for AMD.

I have 3 machines that I haven't moved over to v7 & after two weeks they are still filling up with v6 tasks.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

The only problem is the only MBv6 work is going to be what's left in the field, so once that's gone that's all she wrote.

@Eric: And Athlon or later for AMD.

I have 3 machines that I haven't moved over to v7 & after two weeks they are still filling up with v6 tasks.

Better look closer.

I checked all the SAH_enhanced tasks on all of your machines, and you currently have 36 showing. Of the ones in progress, all are resends.

I'm pretty sure there are no SAH_enhanced WU being split anymore.

The only problem is the only MBv6 work is going to be what's left in the field, so once that's gone that's all she wrote.

@Eric: And Athlon or later for AMD.

I have 3 machines that I haven't moved over to v7 & after two weeks they are still filling up with v6 tasks.

Better look closer.

I checked all the SAH_enhanced tasks on all of your machines, and you currently have 36 showing. Of the ones in progress, all are resends.

I'm pretty sure there are no SAH_enhanced WU being split anymore.

I currently have 51 tasks in progress. With 23 of them assigned today.
They are all resends, but those boxes are slow so they have full queues. With their slower processing rate I don't expect to change them over for a few months.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

<snip>

I currently have 51 tasks in progress. With 23 of them assigned today.
They are all resends, but those boxes are slow so they have full queues. With their slower processing rate I don't expect to change them over for a few months.

Agreed, but as time goes forward getting any will get progressively harder. Especially since the new app can crunch them as well as v7.

One bright side though, I don't think any of your old timers got bit by the CMOVE illegal instruction incompatibility issue like my K6's have. ;-)

<snip>

I currently have 51 tasks in progress. With 23 of them assigned today.
They are all resends, but those boxes are slow so they have full queues. With their slower processing rate I don't expect to change them over for a few months.

Agreed, but as time goes forward getting any will get progressively harder. Especially since the new app can crunch them as well as v7.

One bright side though, I don't think any of your old timers got bit by the CMOVE illegal instruction incompatibility issue like my K6's have. ;-)

The oldest bit of kit I am running right now is a PIII. So even if the code doesn't get changed I think I should be OK. That machine will have to go to the stock app when I change it over. So I shall see how it goes when it is forced to change over.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

<snip>

I currently have 51 tasks in progress. With 23 of them assigned today.
They are all resends, but those boxes are slow so they have full queues. With their slower processing rate I don't expect to change them over for a few months.

Agreed, but as time goes forward getting any will get progressively harder. Especially since the new app can crunch them as well as v7.

One bright side though, I don't think any of your old timers got bit by the CMOVE illegal instruction incompatibility issue like my K6's have. ;-)

The oldest bit of kit I am running right now is a PIII. So even if the code doesn't get changed I think I should be OK. That machine will have to go to the stock app when I change it over. So I shall see how it goes when it is forced to change over.

You're golden. PII and higher have no issues with v7. Pentium Pro for that matter, but they are as scarce as hen's teeth (even back in the day).

j mercer wrote:

WOW! thank you for looking into my issues.

It seems like a lot of work for just mine and a few other very inefficient computers. The estimate is 11 1/2 days for the current wu. LOL!!

It is able to crunch v6.03 wu so we are good to go. It did crunch 10,000+ Classic wu back in its day.

Now that Eric has diagnosed the problem, there is a workaround you could use to process v7 tasks. The libfftw3f-3-1-1a_upx.dll version of FFTW has the same functions as libfftw3f-3-3_upx.dll because they're both FFTW 3 DLLs. The 3.3.3 version is extended to support capabilities in new hardware, but not by adding or changing functions.

So the workaround is to use a copy of libfftw3f-3-1-1a_upx.dll which has been renamed to libfftw3f-3-3_upx.dll . The setiathome_7.00_windows_intelx86.exe program will work with that DLL with no issues.

OTOH, some care will be needed to keep BOINC from deleting the DLL. Because you have BOINC 7.1.17 on that system now, you will need a cc_config.xml file including a <dont_check_file_sizes>1</dont_check_file_sizes> option.

For some earlier BOINC 7 versions the workaround wouldn't be possible, while with BOINC 6 and earlier the cc_config.xml option wouldn't be needed.

There may be no need to enable v7 tasks on that system, but that's the bones of how to do it if you want.

                                                                  Joe

Thanking you Josef. I have downloaded the DLL and will rotate out when wu is done.

With only 118MB I can't run AP v6 which requires 160MB. Before I get my hopes up too much is there a place that lists the minimum memory for the different wu applications?

---

...

Thanking you Josef. I have downloaded the DLL and will rotate out when wu is done.

With only 118MB I can't run AP v6 which requires 160MB. Before I get my hopes up too much is there a place that lists the minimum memory for the different wu applications?

Both Sah Enhanced and v7 have a peak memory usage over 100MB shortly after a task starts, during the "Choosing optimal functions" tests. After that they drop down to something in the 30 to 40 MB range, with v7 needing roughly 1MB more than Enhanced. They'll actually run on a system with less than 64MB, the test which causes the extra memory usage is omitted in that case.

Astropulse doesn't actually need 160MB, but it does need a faster CPU than your 200 MHz Pentium MMX. The deadline is 25 days, the servers won't send AP to a host which they estimate will take more than 19.23 days to do it, and on CPU AP tasks take about ten times as long as Sah Enhanced tasks. I had a similar system, and there's just no way to make it suitable for AP work.

                                                                   Joe

Thanks Joe.

YAY! there is hope it will be able to crunch till it croaks. LOL!!

---

...

Thanks Joe.

YAY! there is hope it will be able to crunch till it croaks. LOL!!

Agreed, the good news is the workaround works for W2K and higher.

The bad news is the main executable has a problem on 9x. There's a problem with the linking to some system dll's. This might be the end of the road for 9x on MB.

AP still works, but the deadlines are too tight for K6.

My second/backup PC is a Pentium II running Windows 98, currenly with 256 RAM. BOINC version is 6.6.38 (the lastest that will run Windows 98 apparently). This PC has been crunching along slowly but surely on all the SETI applications except Astropulse 6, which is not allowed to run.

I understood V7 would still work on my machine per review of various Forum threads and "official" announcements. However, when my last SETI@home enhanced job finished and uploaded normally, it began to process the v7 job that had previously downloaded without incident. This ran for just a few seconds and errored out. Please see the log excerps below.

Hopefully, no new hardware will be needed to get this back up and running. I may spring for another 128 of RAM if absolutely necessary. However, I'm concerned that the followng statement bodes as a deathknell for my machine (at least with crunching for SETI).

The bad news is the main executable has a problem on 9x. There's a problem with the linking to some system dll's. This might be the end of the road for 9x on MB.

1. Download of v7 elements:
6/17/2013 11:08:47 PM|SETI@home|Sending scheduler request: To fetch work.
6/17/2013 11:08:47 PM|SETI@home|Requesting new tasks
6/17/2013 11:08:53 PM|SETI@home|Scheduler request completed: got 1 new tasks
6/17/2013 11:08:56 PM|SETI@home|Started download of setiathome_7.00_windows_intelx86.exe
6/17/2013 11:08:56 PM|SETI@home|Started download of setigraphics_7.00_windows_intelx86.exe
6/17/2013 11:09:02 PM|SETI@home|Finished download of setiathome_7.00_windows_intelx86.exe
06/17/13 23:09:02|SETI@home|Finished download of setigraphics_7.00_windows_intelx86.exe
06/17/13 23:09:02|SETI@home|Started download of libfftw3f-3-3_upx.dll
06/17/13 23:09:02|SETI@home|Started download of seti_700.jpg
06/17/13 23:09:03|SETI@home|Finished download of seti_700.jpg
06/17/13 23:09:03|SETI@home|Started download of setiathome-7.00_AUTHORS.txt
06/17/13 23:09:05|SETI@home|Finished download of setiathome-7.00_AUTHORS.txt
06/17/13 23:09:05|SETI@home|Started download of setiathome-7.00_COPYING.txt
06/17/13 23:09:06|SETI@home|Finished download of setiathome-7.00_COPYING.txt
06/17/13 23:09:06|SETI@home|Started download of setiathome-7.00_COPYRIGHT.txt
06/17/13 23:09:07|SETI@home|Finished download of setiathome-7.00_COPYRIGHT.txt
06/17/13 23:09:07|SETI@home|Started download of setiathome-7.00_README.txt
06/17/13 23:09:08|SETI@home|Finished download of setiathome-7.00_README.txt
06/17/13 23:09:08|SETI@home|Started download of 14ja12ac.28713.20517.14.12.3.vlar
06/17/13 23:09:09|SETI@home|Finished download of libfftw3f-3-3_upx.dll
06/17/13 23:09:12|SETI@home|Finished download of 14ja12ac.28713.20517.14.12.3.vlar

2. Start of V7:
6/18/2013 10:54:51 PM|SETI@home|Computation for task 03jn10aa.17696.306726.10.11.220.vlar_2 finished
6/18/2013 10:54:51 PM|SETI@home|Starting 14ja12ac.28713.20517.14.12.3.vlar_1
6/18/2013 10:54:52 PM|SETI@home|[error] Process creation failed: A device attached to the system is not functioning. (0x1f)
6/18/2013 10:54:54 PM|SETI@home|[error] Process creation failed: A device attached to the system is not functioning. (0x1f)
6/18/2013 10:54:55 PM|SETI@home|[error] Process creation failed: A device attached to the system is not functioning. (0x1f)
6/18/2013 10:54:56 PM|SETI@home|[error] Process creation failed: A device attached to the system is not functioning. (0x1f)
6/18/2013 10:54:58 PM|SETI@home|[error] Process creation failed: A device attached to the system is not functioning. (0x1f)
6/18/2013 10:54:59 PM|SETI@home|Computation for task 14ja12ac.28713.20517.14.12.3.vlar_1 finished
6/18/2013 10:54:59 PM|SETI@home|Output file 14ja12ac.28713.20517.14.12.3.vlar_1_0 for task 14ja12ac.28713.20517.14.12.3.vlar_1 absent
6/18/2013 10:55:00 PM|SETI@home|Started upload of 03jn10aa.17696.306726.10.11.220.vlar_2_0
6/18/2013 10:55:05 PM|SETI@home|Finished upload of 03jn10aa.17696.306726.10.11.220.vlar_2_0
6/18/2013 10:55:55 PM|SETI@home|Sending scheduler request: To fetch work.
6/18/2013 10:55:55 PM|SETI@home|Reporting 2 completed tasks, requesting new tasks
6/18/2013 10:56:01 PM|SETI@home|Scheduler request completed: got 0 new tasks
6/18/2013 10:56:01 PM|SETI@home|Message from server: Project has no tasks available
6/18/2013 11:01:08 PM|SETI@home|Sending scheduler request: To fetch work.
6/18/2013 11:01:08 PM|SETI@home|Requesting new tasks
6/18/2013 11:01:14 PM|SETI@home|Scheduler request completed: got 0 new tasks
6/18/2013 11:01:14 PM|SETI@home|Message from server: No tasks sent
6/18/2013 11:01:14 PM|SETI@home|Message from server: No tasks are available for SETI@home Enhanced
6/18/2013 11:01:14 PM|SETI@home|Message from server: No tasks are available for Astropulse v505
6/18/2013 11:01:14 PM|SETI@home|Message from server: No tasks are available for SETI@home v7
6/18/2013 11:01:14 PM|SETI@home|Message from server: A newer BOINC may be required for some tasks.

The problem for you isn't with the PII, it's with 9x.

MBv7 would run fine on it with W2K or higher with no fooling around with it whatsoever.

You may try KernelEx
http://kernelex.sourceforge.net/
http://sourceforge.net/projects/kernelex/

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Cool....

Thanks for the links, will give that a try ASAP!