Running YAFU via Aliqueit doesn't find yafu.ini

EdH · 2013-04-28, 17:36

My normal setup for running Aliqueit/YAFU includes separate directories for each. I'm using an absolute path in the aliqueit.ini file for the YAFU call. YAFU is called properly, but it appears to look for its yafu.ini file in the Aliqueit directory instead of its home directory. I can copy yafu.ini into the Aliqueit directory and it is read appropriately.

I suppose I could consider this a feature, whereas I can have two different setups for YAFU, depending on where it is run from, but in my case, the two would be identical. This is not a pressing issue, just one I thought I'd bring up for discussion.

Thanks for all.

shortcipher · 2018-03-13, 04:09

This bit me as well on Windows 10.
It's a problem whenever you invoke yafu.exe from a different directory than where yafu.exe and yafu.ini reside.

Dubslow · 2018-03-13, 12:58

You'll find the same of any similar program. The only directory it "knows" about is the one that it's started in. How is it supposed to know where "its" directory is?

EdH · 2018-03-13, 14:09

Quote:

Originally Posted by Dubslow

You'll find the same of any similar program. The only directory it "knows" about is the one that it's started in. How is it supposed to know where "its" directory is?

Wow! It only took 5 years for some discussion. And I thought no one cared.

To play Devil's advocate, you tell YAFU where to find gnfs-* and ECM, maybe it could reference its own directory, when it's called from there.

As to me, personally, I moved on long ago and now copy both YAFU and its .ini into wherever I'll be using it.

Dubslow · 2018-03-13, 14:12

Quote:

Originally Posted by EdH

you tell YAFU where to find gnfs-* and ECM, maybe it could reference its own directory, when it's called from there.

You tell it where to find gnfs-lasieve*, and *ecm, via the ini file (or command line arguments). How is it supposed to know where to find the .ini file if not in the current directory? Because yafu a priori doesn't know anything about the file system structure other than its current directory. (The answer is either via the command line, or not at all.)

RichD · 2018-03-13, 14:32

Perhaps an -i flag is needed, like in Msieve.

LaurV · 2018-03-13, 16:49

in windoze, using "start" command, a "working dir" can be set; however, due to laziness, we keep all in the same folder (yafu and aliqueit) with their inis together.

shortcipher · 2018-03-14, 08:48

@Dubslow
Some Windows apps can find a .ini in their .exe directory when started from a different directory. For example, Resource Hacker 4.2.5. Not sure how they do this.

Dubslow · 2018-03-14, 17:22

Quote:

Originally Posted by shortcipher

@Dubslow
Some Windows apps can find a .ini in their .exe directory when started from a different directory. For example, Resource Hacker 4.2.5. Not sure how they do this.

Presumably by some sort of installation process, where running the program is more involved than simply starting the .exe. yafu is less sophisticated, having no installation process.

2013-04-28, 17:36	#1
EdH "Ed Hall" Dec 2009 Adirondack Mtns 3×7×263 Posts	Running YAFU via Aliqueit doesn't find yafu.ini My normal setup for running Aliqueit/YAFU includes separate directories for each. I'm using an absolute path in the aliqueit.ini file for the YAFU call. YAFU is called properly, but it appears to look for its yafu.ini file in the Aliqueit directory instead of its home directory. I can copy yafu.ini into the Aliqueit directory and it is read appropriately. I suppose I could consider this a feature, whereas I can have two different setups for YAFU, depending on where it is run from, but in my case, the two would be identical. This is not a pressing issue, just one I thought I'd bring up for discussion. Thanks for all. Last fiddled with by EdH on 2013-04-28 at 17:37

2018-03-13, 04:09	#2
shortcipher Mar 2018 21₈ Posts	Me too This bit me as well on Windows 10. It's a problem whenever you invoke yafu.exe from a different directory than where yafu.exe and yafu.ini reside.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Yafu batch running	ThomRuley	YAFU	15	2021-08-31 16:44
Aliqueit Failing to Find Msieve Factors	EdH	Msieve	14	2016-09-05 21:52
YAFU-1.34	bsquared	YAFU	119	2015-11-05 16:24
Hopefully this user doesn't find M49...	NBtarheel_33	PrimeNet	15	2014-08-19 06:14
Running YAFU	lorgix	YAFU	9	2012-03-28 03:37

2018-03-13, 12:58	#3
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 1C35₁₆ Posts	You'll find the same of any similar program. The only directory it "knows" about is the one that it's started in. How is it supposed to know where "its" directory is?

2018-03-13, 14:32	#6
RichD Sep 2008 Kansas 3,923 Posts	Perhaps an -i flag is needed, like in Msieve.

2018-03-13, 16:49	#7
LaurV Romulan Interpreter "name field" Jun 2011 Thailand 2⁴×643 Posts	in windoze, using "start" command, a "working dir" can be set; however, due to laziness, we keep all in the same folder (yafu and aliqueit) with their inis together.

2018-03-14, 08:48	#8
shortcipher Mar 2018 17 Posts	@Dubslow Some Windows apps can find a .ini in their .exe directory when started from a different directory. For example, Resource Hacker 4.2.5. Not sure how they do this.