LHC@home

Hi,

I noticed that on Windows 64 bits machines I'm ketting WUs that are using two different executables : one is called sixtrack_windows.exe and the other is simply called sixtrack.exe.

Can anyone explain what are the differencs between the two ?

they are exactly the same. Just some mishap when entering new versions created several files.

Hi,

I noticed that on Windows 64 bits machines I'm ketting WUs that are using two different executables : one is called sixtrack_windows.exe and the other is simply called sixtrack.exe.

Can anyone explain what are the differencs between the two ?

---

skype id: igor-zacharov

Thanks.

I also noticed that every time my cache runs dry, when I get the next bunch of WUs, executables are being downloaded again.

Is there something wrong with naming of the files and/or versioning ?

Previous files where called sixtrack_530.10_windows_x86_64.exe or sixtrack_530.10_windows_x86_64 or sixtrack_530.10_windows_intelx86 depdending on the version of the application and the architecture ...

Thanks.

I also noticed that every time my cache runs dry, when I get the next bunch of WUs, executables are being downloaded again.

Is there something wrong with naming of the files and/or versioning ?

Previous files where called sixtrack_530.10_windows_x86_64.exe or sixtrack_530.10_windows_x86_64 or sixtrack_530.10_windows_intelx86 depdending on the version of the application and the architecture ...

I'm getting the same. The sixtrack.exe is being downloaded with new tasks after the tasks in my cache have been finished. Looking in the sixtrack folder "sixtrack.exe" was there while tasks were being crunched but after the tasks are completed it gets deleted. However "sixtrack_530.10_windows_intelx86" is still there.