I have no idea of how to get this working

[bluecat0531]

Originally Posted by kriesel

I don't have an issue with your posts or Chris's. Look again at post 4. He quoted my entire post, that included several questions, answered none, and provided little information or specifics. We don't know if he has installed mfaktc in Program Files or system32 or somewhere sensible, has a worktodo file, has proper permissions on the install folder and mfaktc files, has a suitable CUDA computing compatible driver installed, what batch file he has attempted, what cmd line he has attempted, etc etc etc. The details which we would need to see to provide effective help are all being kept secret. I think we may have another "help me in spite of my refusing to provide any useful diagnostic data or answer any questions" troll.

I do apologize for my brief answers. I was not fully thinking them out as each time I was in a rush to the get to work for my ~10 hr shifts. This has been so for the past few days since i first made the thread. I did try to answer some of your questions but I believe that some of them i could not answer as i previously stated could not get the program to run at all. And then perhaps some of your questions were categorized under "etc." which i may have brushed of as I could not ascertain what you wanted. To answer what questions I can see in this quote, I have the program installed on my desktop inside of a folder, I believe i have installed the latest cuda driver which i know is seperate from a geforce driver(but on that note i did see in another post i need some .dll file ill be sure to go and grab that), the batch file was just basically a copy of the cmds i was running something like "./mfaktc.exe -h and some other extensions like the -st or -st2, commandline im using is just the one that pops up when you search cmd in windows 10 (which gives you my OS which i have the latest version of), and lastly no i dont believe i have any diagnostic data to give you due to my current predicament just info on my system/setup.

[bluecat0531]

Originally Posted by Uncwilly

Do you have a worktodo.txt established? And IIRC there is a need for a config file to be established before it will stay running. That part was confusing to me too. (I tried running it on a machine with an integrated GPU. But it used shared memory and lowered my desired Prime95 performance.)

I do have a worktodo.txt file and it does have the necessary data as seen from an earlier reply but as for the config file.I would have no idea the format or info it would need. Did try getting some configs to work from mfaktx but was having no luck there either. But for now I am just working to get mfaktc running as suggested i can mess with other helper programs later.

[kriesel]

Still MUCH too vague. Until you provide lots of accurate specifics, effective help is not possible.

GIMPS GPU applications are all command line applications. If you don't know how to use the command line in your OS, learn that first. The disappearing command window is a symptom of someone who doesn't know even the basics of using the command line in their OS. Learn about cmd /k in Windows, or opening a terminal window in Linux.

Document in a post in the thread the exact cmd lines you use, working directory, OS & OS version, hardware, mfaktc version, driver version, cudart version, and the exact resulting content of mfaktc output redirected to a file. Also exact mfaktc worktodo content except mask AID. Copy/paste to avoid (more) typos.
For a rough idea of level of detail, see the Colab example. The level of detail required, is that which would be required if you were dictating keystrokes to someone else to reproduce your run attempt EXACTLY, plus include its output too. Every character of input. Exact reproduction of any info section and any error messages at the very least.

Originally Posted by bluecat0531

something like "./mfaktc.exe -h and some other extensions like the -st or -st2, commandline im using is just the one that pops up when you search cmd in windows 10 (which gives you my OS which i have the latest version of), and lastly no i dont believe i have any diagnostic data to give you due to my current predicament just info on my system/setup.

Linux syntax there vs Win 10 reference. "Something like" is pretty useless. We need to see EXACTLY what you attempt and EXACTLY what it generates as output. One wrong character, assumption, or omission can kill a run or send the helpful in the wrong direction.
Four posts in by the person requesting help, we know little more than there's a 5950 and a 3090 involved and a user who apparently needs a basic OS cmd line tutorial who claims he's set it all up correctly, but only sees a cmd box flash on and off the screen and can't or won't provide any useful detail such as program output or input.
I'm about done trying to help the OP due to the persistent lack of useful information from him. I wonder if he's ever debugged anything or is a frequent help desk user or how little computer experience or knowledge he has.

[bluecat0531]

So I have navigated to my installation folder and ran the following commands which didnt seem to give me any output or keep the window open even using /k "start mfaktc-win-64.exe /k -h > OutputTest.txt", "start mfaktc-win-64.exe /k -st > OutputTest2.txt" , and "start mfaktc-win-64.exe /k -st2 > OutputTest3.txt". The directory im using is "C:\Users\Bluecat\Desktop\PRIME STUFF".

OS is Windows 10 version 21H2 build 19044.1415 and experience? Windows Feature Experience Pack 120.2212.3920.0.

Hardware 5950x, rtx 3090 (Asus strix OC 24GB), Gigabyte x570 Aorus Master (Bios version F35E), 2 2x 16GB G. SKill Trident Z RGB for AMD F4-3200C16-16GTZRX, Corsair 1000W power supply that im not going to open my pc to find out the exact model for.

Mfaktc version is 0.21, Cuda driver is 11.5(also Geforce driver 497.29), ive downloaded cudart64_110.dll but tbh no idea where to put it other than in the above directory.

Each of those commands did create a file with the stated name and each were blank.

And lastly as far as worktodo.txt content "Factor=2021-12-30,21245513,73,74
Factor=2021-12-30,21245479,73,74"

[Dr Sardonicus]

Originally Posted by bluecat0531

So I have navigated to my installation folder and ran the following commands which didnt seem to give me any output or keep the window open even using /k "start mfaktc-win-64.exe /k -h > OutputTest.txt", "start mfaktc-win-64.exe /k -st > OutputTest2.txt" , and "start mfaktc-win-64.exe /k -st2 > OutputTest3.txt". The directory im using is "C:\Users\Bluecat\Desktop\PRIME STUFF".

OS is Windows 10 version 21H2 build 19044.1415 and experience? Windows Feature Experience Pack 120.2212.3920.0.

Hardware 5950x, rtx 3090 (Asus strix OC 24GB), Gigabyte x570 Aorus Master (Bios version F35E), 2 2x 16GB G. SKill Trident Z RGB for AMD F4-3200C16-16GTZRX, Corsair 1000W power supply that im not going to open my pc to find out the exact model for.

Mfaktc version is 0.21, Cuda driver is 11.5(also Geforce driver 497.29), ive downloaded cudart64_110.dll but tbh no idea where to put it other than in the above directory.

Each of those commands did create a file with the stated name and each were blank.

And lastly as far as worktodo.txt content "Factor=2021-12-30,21245513,73,74
Factor=2021-12-30,21245479,73,74"

Now, you're talking!

[kriesel]

Originally Posted by bluecat0531

So I have navigated to my installation folder and ran the following commands which didnt seem to give me any output or keep the window open even using /k "start mfaktc-win-64.exe /k -h > OutputTest.txt", "start mfaktc-win-64.exe /k -st > OutputTest2.txt" , and "start mfaktc-win-64.exe /k -st2 > OutputTest3.txt". The directory im using is "C:\Users\Bluecat\Desktop\PRIME STUFF".

OS is Windows 10 version 21H2 build 19044.1415 and experience? Windows Feature Experience Pack 120.2212.3920.0.

Hardware 5950x, rtx 3090 (Asus strix OC 24GB), Gigabyte x570 Aorus Master (Bios version F35E), 2 2x 16GB G. SKill Trident Z RGB for AMD F4-3200C16-16GTZRX, Corsair 1000W power supply that im not going to open my pc to find out the exact model for.

Mfaktc version is 0.21, Cuda driver is 11.5(also Geforce driver 497.29), ive downloaded cudart64_110.dll but tbh no idea where to put it other than in the above directory.

Each of those commands did create a file with the stated name and each were blank.

And lastly as far as worktodo.txt content "Factor=2021-12-30,21245513,73,74
Factor=2021-12-30,21245479,73,74"

There are errors, and info gaps:
1) Worktodo.txt should be without dates. To my knowledge no legit worktodo entry format in any GIMPS application includes dates of assignment or any dates.

Factor=21245513,73,74
Factor=21245479,73,74

or

Factor=WhateverTheFirstAIDis,21245513,73,74
Factor=WhateverTheSecondAIDis,21245479,73,74

2) "start mfaktc-win-64.exe /k -h > OutputTest.txt" is not a legal Win 10 command. There is no /k option for the Windows start command or for mfaktc*.exe. (I think the /k is just getting passed to mfaktc and ignored though.)

3) What's being redirected to OutputTest.txt is the output of the start command, which is null, so an empty zero-bytes file is created. Mfaktc's console output would go to a command window that blinks quickly in and out of existence. There are ways around that, using " " correctly, or otherwise correcting the command line used.

4) Mfaktc has not only multiple version numbers, but there are a lot of different compiled flavors in multiple dimensions:

• more-classes vs less-classes,
• standard 128M max GpuSieveSize vs. 2047M max size,
• many with different CUDA levels supported;
• Windows or Linux;
• moot in this case, but in older CUDA levels there were both 32-bit and 64-bit compiles.

The CUDA level compatibility could be a looming problem after the other issues are resolved. Can't tell from the info provided, which of the many flavors of mfaktc v0.21 is being used, or whether there is CUDA level compatibility throughout.

5) I think you're trying an inferior method to launch the mfaktc program. I don't see a need for the start command. It has to be already at a command line to use start to spawn another cmd.exe process, so just use the current cmd session instead.

Windows shortcuts can be much easier, faster, and less prone to pilot error in the long run than typing command lines. Creating a shortcut to launch and run mfaktc, a flavor of cmd /k mfaktc etc is the command line for the shortcut, your working mfaktc directory is the directory to start the process in.

I have shortcuts defined, configured with the equivalent of the command line
C:\Windows\System32\cmd.exe /k C:\Users\username\Documents\mfaktc-rtx2080\mf.bat
and start in C:\Users\username\Documents\mfaktc-rtx2080
All the device specification, executable flavor selection, setting window title, output redirection, restart or chaining to another task upon crash, etc, is housed in mf.bat for easy reliable quick production running.

6) We don't know from the preceding post whether the installation folder is ok, with correct file and folder permissions & location, or somewhere the OS restricts. But he earlier posted somewhere under desktop. Which should be ok unless properties got oddly set.

7) We still don't know whether there's an mfaktc.ini present, whether it's been customized, what it contains, or whether the OP's introduced issues there. The earlier issues are enough to prevent productive troubleshooting or use, so this can wait a bit.


See also https://www.mersenneforum.org/showpo...19&postcount=8


Putting the CUDArt .dll file in the working directory is fine, and simpler than messing with search paths. (Though possibly less space efficient.)

[LaurV]

Originally Posted by kriesel

1) Worktodo.txt should be without dates. To my knowledge no legit worktodo entry format in any GIMPS application includes dates of assignment or any dates.

Small correction: mfaktX doesn't give a dime about the AID field, but it MUST be present. If you have no AID, you can put a comma, or write "N/A" there, or.... use a date. Using a date is a common practice when you have lots of assignments, for many days, to know when you got them (and eventually, where did you get them from, like gimps, gpu72, mersenne.ca, etc), and for example, MISFIT has options/checkboxes to automatically substitute AID with dates or any custom text. So, the OP's assignment lines are correct. What (mess) he does with the "start" command is another story. You explained right for the points 2 to 5.

I usually open a command prompt and type "mfaktc" there
The rest is organized by the ini file, etc.

(well, I am telling lies, in fact, I only type "misfit" , but a batch file launching the adequate copies of mfaktc in their specific folders was the working mode for years).

[bluecat0531]

With the help so far I have gotten the program working hooray! I tried two things at once so I dont know which fixed it. One was fixxing the command to only "mfaktc-win-64.exe and the appendages ie -h -st and got it output to a file. The second was just wiping all previous mfaktc files and redownloading it (which btw was mfaktc-0.21.win.cuda11.2-2047). For now I am just using the command but now that its working hopefully I can eventually setup a shortcut. Ideally now id like to get misfit and/or mfaktx controller working so that its a bit more automated.

Oh I guess I should mention how I knew it worked. I just went to the main website and got some manual assignments to copy/paste into my worktodo file and when the program finished running i copy/pasted the contents of my results file into the form and I got credited for my GHZ/Days.

[kriesel]

Originally Posted by LaurV

Small correction: mfaktX doesn't give a dime about the AID field, but it MUST be present.

(bold emphasis in preceding quote mine) No, the AID field is clearly optional for mfaktc. Check the source code. Or try it. I'm running currently, on a GPU, the worktodo line "Factor=1250000029,86,87" which is accepted just fine. Mersenne.ca assignments such as for OBD don't include AIDs and can be run unchanged.

got assignment: exp=1250000029 bit_min=86 bit_max=87 (12537.18 GHz-days)

From mfaktc's source code module parse.c, routine parse_worktodo_line, the AID field and its associated trailing comma ARE OPTIONAL:

  if ((2!=number_of_commas) && (3!=number_of_commas))    // must have 2 or 3 commas...
    return INVALID_FORMAT;

  if(2==number_of_commas)
    assignment->assignment_key[0] = '\0';
  else
  {
    strncpy(assignment->assignment_key,ptr,1+(strstr(ptr,",")-ptr) );    // copy the comma..
    *strstr(assignment->assignment_key,",") = '\0';    // null-terminate key
    ptr=1 + strstr(ptr,",");
  }

It does appear to accept almost-random text excluding commas in the optional AID field, subject to the max line length 100 and some other restrictions. Thanks for that tip. Reference info is modified to reflect that. That mfaktc accepts almost any arbitrary text as AID input, and discards valid AIDs, not including them in result output, is ... just wrong, in multiple ways. But it is confirmed to be so. Probably the same applies to mfakto, since it was created from mfaktc source code. It would be good to get that corrected in both. The status quo makes it too easy to poach any TF assignment, or forge a fake result to terminate someone's assignment.

I usually open a command prompt and type "mfaktc" there. The rest is organized by the ini file, etc.

There is no facility documented in mfaktc.ini for specifying device number. There is apparently no provision for input of device number via mfaktc.ini present in the source code; strings "Device" or "device" do not appear in source module read_config.c. So any system with multiple CUDA GPUs will need the -d option on the command line for running mfaktc on GPU device number > 0.

[LaurV]

Well done, next step is to install misfit (if you run windows) to automatize what you did by hand (getting assignments and reporting results). If you run Linux, there are some python scrips doing the same as misfit, but without the graphic interface.
edit: crosspost, I was replying to OP. For the "optional" part, I may be confused... is the gpuowl or the cudaLucas the one requiring the N/A or AID to be present? I know for sure that assignments without it didnt work in the past. All my mfaktc lines contains dates (from gpu72/misfit), generally the date when the exponent was assigned, but not always.