I don’t know of any built-in tool in Windows that can do that. Again, AutoHotkey or a similar utility would be needed.

opening in fullscreen would ne nice

I was waiting for that being the next feature request… ;-⁠)

The graphics app does have a -⁠-⁠fullscreen option, but as well as making the window full-screen it causes it to act like a screensaver (such that it will exit as soon as you move the mouse or press a key), which will not be very useful when you are trying to use the machine at the same time.

The closest we can (easily) get is to open the window maximised, by changing

		PUSHD "%SLOTDIR%" && START "Rosetta Graphics" "%GFXRELPATH%" & POPD

to

		PUSHD "%SLOTDIR%" && START "Rosetta Graphics" /MAX "%GFXRELPATH%" & POPD

If you want true full-screen, you’ll need a utility that can modify another application’s window and remove its borders. AutoHotkey is probably able to do that, but I’m not sufficiently familiar with it to write a script.

opening in fullscreen would ne nice

I was waiting for that being the next feature request… ;-⁠)

Here’s a more robust version that will read the BOINC data directory from the Registry, pick a random slot directory instead of always looking in 0, and check it’s actually a Rosetta task (and not some other project) that’s running:

@ECHO OFF
SETLOCAL
SET GFXEXE=rosetta_graphics_4.20_windows_x86_64.exe
SET GFXRELPATH=..\..\projects\boinc.bakerlab.org_rosetta\%GFXEXE%
FOR /F "skip=2 tokens=2*" %%V IN ('REG QUERY "HKLM\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup" /v "DATADIR"') DO SET BOINCDATADIR="%%W"
SET /A SLOTNUM=%RANDOM% %% %NUMBER_OF_PROCESSORS%
SET SLOTDIR=%BOINCDATADIR%\slots\%SLOTNUM%
:BEGIN
TASKLIST /FO LIST /FI "IMAGENAME eq %GFXEXE%" | FIND "%GFXEXE%"
IF ERRORLEVEL 1 (
	IF EXIST "%SLOTDIR%\rosetta_*.exe" (
		PUSHD "%SLOTDIR%" && START %GFXRELPATH% & POPD
	)
)
TIMEOUT 600
GOTO BEGIN

i turned off "restart on crash" now for rosetta_graphics. maybe that was the problme.

Yes, it could be that. The message might be coming from the Rosetta application trying to communicate with a graphics application that is not operating as expected. Make sure there are no stuck rosetta_graphics_4.20_windows_x86_64.exe processes running.

A batch file like this might do what you want:

@ECHO OFF
SETLOCAL
SET GFXEXE=rosetta_graphics_4.20_windows_x86_64.exe
SET GFXRELPATH=..\..\projects\boinc.bakerlab.org_rosetta\%GFXEXE%
SET BOINCDATADIR=%ProgramData%\BOINC
SET SLOTDIR=%BOINCDATADIR%\slots\0
:BEGIN
TASKLIST /FO LIST /FI "IMAGENAME eq %GFXEXE%" | FIND "%GFXEXE%"
IF ERRORLEVEL 1 (
	IF EXIST %SLOTDIR%\graphics_app (
		PUSHD %SLOTDIR% && START %GFXRELPATH% & POPD
	)
)
TIMEOUT 600
GOTO BEGIN

C:Program FilesBOINC ( my boinc folder)
D:BOINC DATAprojectsboinc.bakerlab.org_rosetta (rosetta_graphics.exe)
D:BOINC DATAslots (the slots)

i turned off "restart on crash" now for rosetta_graphics. maybe that was the problme.

Yes, it could be that. The message might be coming from the Rosetta application trying to communicate with a graphics application that is not operating as expected. Make sure there are no stuck rosetta_graphics_4.20_windows_x86_64.exe processes running.

A batch file like this might do what you want:

@ECHO OFF
SETLOCAL
SET GFXEXE=rosetta_graphics_4.20_windows_x86_64.exe
SET GFXRELPATH=..\..\projects\boinc.bakerlab.org_rosetta\%GFXEXE%
SET BOINCDATADIR=%ProgramData%\BOINC
SET SLOTDIR=%BOINCDATADIR%\slots\0
:BEGIN
TASKLIST /FO LIST /FI "IMAGENAME eq %GFXEXE%" | FIND "%GFXEXE%"
IF ERRORLEVEL 1 (
	IF EXIST %SLOTDIR%\graphics_app (
		PUSHD %SLOTDIR% && START %GFXRELPATH% & POPD
	)
)
TIMEOUT 600
GOTO BEGIN

It’s certainly possible, in that some kind of launcher could communicate with the client to get the information needed to start the graphics for a task, watch for it to finish, then repeat for another task. But I don’t know whether there are any existing applications that do this.

BTW your i9 looks to be returning a lot of errors lately. Is it overclocked? Something might be unstable.

Or a memory issue (or both).

failed to create shared mem segment: rosetta Size: 25001680

appears in all the errors i checked out bar one, being the usual

Reason: Access Violation (0xc0000005) at address 0x000002674044BDA0

memory issue of some sort message.


I'd also check it's CPU temperature.

Each of your examples ran under Linux, If you scroll down to the stderr output of each, you will see that each of them gave signal 11.

Under Linux, signal 11 means segmentation error - in other words, the program tried to execute something that was not marked as executable code.

Error code 139 came from a higher level, which did not know what to do about signal 11.

This means that there's an error somewhere in the Linux version of Rosetta 4.20. You can't fix that. You can only wait for tasks that either use a corrected version of the program, or have the input files adjusted so that they don't try to use the part of the program that triggers the error.