I have been having 100% failure over several machines, all Win2000 with 3.32. Some machines are workstations and there is at least 1 Server. 3.30 worked fine. Yes my Java is up to date (checked today).

Chablis

with 3.32.

The GetProcessId() function isn\'t available in Win2K. It was introduced in XP SP1 and Server 2003.

If it\'s essential to use process identifiers rather than handles the only ways I\'m aware of that you can get hold of it directly in Win2K are:

• 
  
• when a child process is created it\'s returned in the PROCESS_INFORMATION structure passed to CreateProcess().
  
  
• a process can get it\'s own identifier by calling GetCurrentProcessId(), but that\'s only available in Win2K Pro and Server and above.
  

I don\'t think process identifiers existed in 9x or NT.
____________
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

I got the same here, all those WorkUnits fail with Error Code 128 like this one.

(loose translation : there are no subordinate processes that have to be waited for)
____________
Scientific Network : 44800 MHz - 77824 MB - 1970 GB

Maybe it\'s a little bit shortsighted to optimize your apps for the latest OSes, only. I think, you will lose a lot of crunching power if you continue with that.
____________

I doubt they did it on purpose. Even the developers here are only human and are allowed to make mistakes.

____________
Jord.

BOINC FAQ Service

OK, in dubio pro reo ;-)
____________

Confirmed, both my W2k systems successfully crunched at least one optimizer WU. Most likely my NT4 box will succeed, too. If it gets one.

No offense meant! Well done!
____________

Sorry, but I have to revert my confirmation concerning WinNT4. Now my NT box got an optimizer WU and crashed with the following pop up message:

It won\'t work on any Windows 98/SE/ME versions then either.

According to this site:

OpenThread() returns a handle to a thread object from its thread identifier (TID). It\'s a convenient way of converting a TID to a thread handle. The Kernel32 function OpenThread() is only implemented on Win 2000 or higher and Win ME. On Windows NT, the undocumented NTDLL function NtOpenThread() can be used to emulate OpenThread()

In Win9x, Kernel32 OpenProcess() can also be used to open a thread: instead of passing it a PID (Process ID), a TID (Thread ID) is passed to it. Inside OpenProcess(), there\'s a check to verify if the passed Id corresponds to a PID and if not returns ERROR_INVALID_PARAMETER, therefore a method to bypass this check is necessary to be able to use OpenProcess() to open a thread object. There are two ways of doing this: skip the test inside OpenProcess() (ATM method by Enrico Del Fante), or change the thread object type to process (Each Kernel object -- process, thread, file, mutex, ... -- has a corresponding data structure that holds information about the object. These structures are undocumented, but you can find the description of some of these structures in [1]. The first field of each Kernel object struct is always the object type: K32OBJ_PROCESS, K32OBJ_THREAD, K32OBJ_FILE, K32OBJ_MUTEX, ...). After the initial checks, OpenProcess() just calls the Kernel32 internal function OpenHandle() that returns a handle to an object -- that\'s why we can use OpenProcess() to open both process/thread objects.

(they have code examples)

Or just set a minimum Windows version for the Optimizers and advertise that via the thread and the news. It\'s too bad BOINC can\'t recognize the individual Windows platforms.
____________
Jord.

BOINC FAQ Service

OpenThread() isn\'t available in NT.

As with processes, there are 2 values used to identify threads: the handle and the identifier. Both are returned by the call to CreateThread(). If the handle isn\'t available for some reason (e.g. it\'s not inheritable), OpenThread() has to be used to convert the thread identifier into the handle needed for operations such as thread suspend, resume and termination.
____________
"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Does the fact that there\'s no further reaction allow the conclusion, that optimizer will not run on WinNT 4.0 further on?

Any message planned to inform the public about that?

OK, according to BOINCstats there are only 51 machines left running WinNT but it would be nice to know before wasting more time.

Thanks.
____________

Does the fact that there\'s no further reaction allow the conclusion, that optimizer will not run on WinNT 4.0 further on?

Any message planned to inform the public about that?

OK, according to BOINCstats there are only 51 machines left running WinNT but it would be nice to know before wasting more time.

Thanks.

Done!
____________