MISFIT for MFAKTx

[swl551]

Originally Posted by Chuck

Unfortunately that doesn't work. The references to the .lnk files are converted to the names pointed to by the link, and the cmd windows open to the default settings.

You can reset the defaults and Windows will remember them. I ALWAYS use the START command which allows me to add a title to the window making it easier to identify.,

http://support.microsoft.com/kb/126410

[Chuck]

Originally Posted by swl551

You can reset the defaults and Windows will remember them. I ALWAYS use the START command which allows me to add a title to the window making it easier to identify.,

http://support.microsoft.com/kb/126410

Thank you for trying to help me but I can't get it to work. If I manually type in the \path\mfaktc-win-32.exe-shortcut.lnk in a command window the window opens as desired, but if I put the same thing in a .bat file instead of the program running a file explorer window opens in the specified directory.

It's easier just to click the four shortcuts on the desktop to get the instances started.

[Chuck]

Originally Posted by Chuck

Thank you for trying to help me but I can't get it to work. If I manually type in the \path\mfaktc-win-32.exe-shortcut.lnk in a command window the window opens as desired, but if I put the same thing in a .bat file instead of the program running a file explorer window opens in the specified directory.

It's easier just to click the four shortcuts on the desktop to get the instances started.

Update — I added the /D switch to the .bat files and that got them to work. I also renamed the links to mfaktc.lnk etc for ease in accessing them.

Things still did not work exactly as I expected. I thought MISFIT was going to automatically start the batch files when it was started, but it does not. When I click the "Start Batch" the windows do open to the positions and settings desired, so that part works.

I can see that automatically trying to start the batch could cause problems (like knowing if they are already running). I believe I can complete this project by adding the four .bat files to the Windows Startup folder, adding a TIMEOUT command to three of the files, specifying, say, a 10, 20 and 30 second delay to stagger the starts.

Attached is the window arrangement I have been working to produce.

[swl551]

Chuck you may find the SpeedController batch system useful
http://mersenneforum.org/showthread.php?t=17915

or Mini Geek's system http://mersenneforum.org/showthread.php?t=18088

[Chuck]

Originally Posted by swl551

Chuck you may find the SpeedController batch system useful
http://mersenneforum.org/showthread.php?t=17915

or Mini Geek's system http://mersenneforum.org/showthread.php?t=18088

Thanks but not needed. MFAKTC always runs full bore; I don't do any gaming.

Additional question: If I did a MISFIT "Start Batch" with my four instances already running, would it start an additional four? I guess I could try but why flirt with disaster...

[swl551]

Originally Posted by Chuck

Thanks but not needed. MFAKTC always runs full bore; I don't do any gaming.

Additional question: If I did a MISFIT "Start Batch" with my four instances already running, would it start an additional four? I guess I could try but why flirt with disaster...

If MISFIT starts more instances then you have a misconfiguration regarding instance names. I cannot answer it for you... You must flirt with disaster to prove out our setup.

Just try not to hurt anyone....

[kladner]

In my setup, selecting "Start Batch" in MISFIT, or running the underlying batch files manually more than once will result in multiple instances in different windows.*

Conversely, selecting "Send Ctl-C" when there are no mfaktX instances running produced an error message along the lines of "I'm sorry, Dave, I'm afraid I could not do that. (See actual message below!)

This is Win 7 64 bit running on AMD hardware.

* Obviously, not an optimal situation. Just be sure to kill the newer processes and leave only the oldest running. Or kill 'em all and start over.

[Chuck]

Originally Posted by swl551

If MISFIT starts more instances then you have a misconfiguration regarding instance names. I cannot answer it for you... You must flirt with disaster to prove out our setup.

Just try not to hurt anyone....

I tried "Start batch" with the jobs already running, and a window opened that said "Process Launch Failed". Good behavior. No harm done.

[swl551]

If you have at least one instance running, and you try to start more from the START PROCESS menu, MISFIT will give you dialog error. If MISFIT does start more instances the INSTANCE name configuration is incorrect.

Stalled process detection is in charge of telling which ones are not running.

[swl551]

Originally Posted by kladner

In my setup, selecting "Start Batch" in MISFIT, or running the underlying batch files manually more than once will result in multiple instances in different windows.*

Conversely, selecting "Send Ctl-C" when there are no mfaktX instances running produced an error message along the lines of "I'm sorry, Dave, I'm afraid I could not do that. (See actual message below!)

This is Win 7 64 bit running on AMD hardware.

* Obviously, not an optimal situation. Just be sure to kill the newer processes and leave only the oldest running. Or kill 'em all and start over.

Kladner,
Does MISFIT STOP all your instances when using the PROCESS STOP menu. Regardless of how you started them it should stop all of them.

[kladner]

Originally Posted by swl551

Kladner,
Does MISFIT STOP all your instances when using the PROCESS STOP menu. Regardless of how you started them it should stop all of them.

Yes. Process Stop has always worked without fail and taken down all instances.