Getting msieve to work
 

[quote=jasonp;150802]Now available:

[URL="http://www.boo.net/%7Ejasonp/msieve139beta2.exe"]win32 binary[/URL]
[URL="http://www.boo.net/%7Ejasonp/msieve139beta2.tar.gz"]source[/URL]

Highlights:

- fixed 64-bit NFS poly selection; it was completely broken

- added poly skew to the factor base file format, logfile, and internal structures (not used internally, yet)

- lowered the size of most A5 coefficients that are searched, and increased the time per coefficient

- fixed almost all compile warnings

- added forgotten typo to the NFS filtering

- added more MSVC tweaks from Brian Gladman; the MSVC project will now link with GMP and GMP-ECM by default. See the readme in the build.vc9 directory if you don't want them.

The shoddy state of this beta has me peeved, but hopefully this will be the last one before a full release later in the week.[/quote]


I don't know why msieve1.39 cannot run on my machine .
My operating system is windows XP.
I download msieve 1.38 from [URL="http://www.tuts4you.com/download.php?view.1252"]this[/URL],
msieve 1.38 can run on my machine with gui.

[QUOTE=aaa120;150920]I don't know why msieve1.39 cannot run on my machine .
My operating system is windows XP.
I download msieve 1.38 from [URL="http://www.tuts4you.com/download.php?view.1252"]this[/URL],
msieve 1.38 can run on my machine with gui.[/QUOTE]

Did you download the win32 binary? You can start it from the DOS-promt. Note that the filename is msieve139beta2.exe, not msieve.exe

Save msieve and extract it to a folder, e.g. "msieve139beta2".
Then right-click on that folder from the folder one level above it (e.g. Program Files) and click on "Command Prompt here". Then type:

msieve139beta2 <num>

where <num> is the number you want to factor. This does ECM up to 15 digits followed by QS/NFS. If instead you type:

msieve139beta2 -e <num>

msieve will run ECM up to the level where QS/NFS should be run. This is best for factoring a number completely.

Type

msieve139beta2 --help

to get a list of other options.

The output (including the factors) will be in a .txt file called "msieve".

have you got file extension hiding on 10metreh because the files name of the log is msieve.log not msieve

I thought it was "msieve.txt".

[quote=aaa120;150920]I don't know why msieve1.39 cannot run on my machine .
My operating system is windows XP.
I download msieve 1.38 from [URL="http://www.tuts4you.com/download.php?view.1252"]this[/URL],
msieve 1.38 can run on my machine with gui.[/quote]

Does the win32 1.38 binary here:

[URL]http://www.boo.net/~jasonp/msieve.exe[/URL]

work?

If you type on the DOS command line: "msieve_exe_name -m -v" (without the quotes), where 'msieve_exe_name' is the name of your msieve executable, does anything happen? It should respond with the prompt:

next number:

where you can then input, for example:

next number: (10^71-1) / 9

Can you do this with the 1.39 beta binary? If so do you get any error messages?

If you have an email address I can use, I can send you another win32 binary to try if you wish.

Brian Gladman

That works with beta1. I haven't taken the time to download beta2 yet. I would suppose that works with beta2 as well.

In fact, I didn't know this way of doing it. I used "msieve <num>" where <num> is the number to be factored. It also seems to resolve the problem that (10^71-1)/9 reads as (1071-1)/9. Only it was 4% slower than without -m -v and 6% slower than v1.38. :shock:

aaa120, what is the error you are getting?

Edit: I have downloaded beta2. There is no real QS time difference for R71.

Anyone who enters a number by formula at the command line, i.e. 'msieve "10^58-1" ', should realize that '^' is a reserved character on the DOS command line; it refers to concatenation. So just saying 10^58-1 will be rearranged by the shell as 1058-1 before msieve ever sees the number, but "10^58-1" (with the quotes) will hide the '^' character from the shell, and work correctly. This was news to me, and I've heard from [i]many[/i] people who reported this as an msieve bug. It isn't a problem in manual mode, i.e. with -m, because what you type there is not shown to the shell interpreter.

When I wrote the demo binary, I wanted something that could accept numbers in pretty much any form users could supply (from file, from the command line, in a pipeline, in batches, etc)