Problems with cwd when starting a program through a .info file in WB

[8bitbubsy]

I have a issue with a program I'm working on (ProTracker 2.3E) where it can't find the config file if it's executed from double-clicking a .info icon file, but it works just fine if you cd to the binary's directory in a shell and start it from there.

It's as if the current working directory is not set to the current open drawer in WB when you start programs through icons, how would I solve this issue? If I could somehow get the path to the current process' executable, I could change the current working directory to that...

[meynaf]

Initial dir is bogus when a program is run from WB.
You can use PROGDIR: assign to get the directory from which the program has been run.
It is also possible it is available somewhere in the WB startup message.

[8bitbubsy]

Originally Posted by meynaf

Initial dir is bogus when a program is run from WB.
You can use PROGDIR: assign to get the directory from which the program has been run.
It is also possible it is available somewhere in the WB startup message.

I tried to add PROGDIR: in front of the filename it tries to open, and it didn't work. Also just to test, if I try to open "PROGDIR:" inside ProTracker's directory lister, it can't open that directory... I used SnoopDos, and now it says that it tries to open PROGDIR:PT-Config.00, which ought to work, but no. I'm on Workbench 3.1.

	MOVE.L	#ConfigName2,D1
	MOVE.L	#1005,D2
	MOVE.L	DOSBase,A6
	JSR	LVOOpen(A6)

[meynaf]

As an alternative, have you tried calling dos.library/GetProgramDir (and then changing directory to the returned lock) ?

[8bitbubsy]

EDIT: Ok it works now, it was my mistake. I called CurrentDir instead of SetProgramDir. Thanks!
EDIT2: Spoke too soon. Seems like SYS: is returned from GetProgramDir() when ran from an icon in WB (or that the call fails), argh!

[ross]

You can use my code (removing the floppy stuff..):
http://eab.abime.net/showpost.php?p=1331387&postcount=5

Cheers.

[8bitbubsy]

Thanks for the code, but I managed to put something together myself. Apparently ProTracker is already doing something similar to your code, but it seems like it got broken in some PT2.x version by Noxious. Anyway, my method only works for kickstart 2.x and later, so I need some help - how can I easily detect if the kickstart version is V36 or above?

[ross]

Originally Posted by 8bitbubsy

Thanks for the code, but I managed to put something together myself. Apparently ProTracker is already doing something similar to your code, but it seems like it got broken in some PT2.x version by Noxious. Anyway, my method only works for kickstart 2.x and later, so I need some help - how can I easily detect if the kickstart version is V36 or above?

Posted code works in every KS.

To check for KS version:

lib_Version	EQU	$14
KS20		EQU	36

		movea.l	$4.w,a6
		cmpi.w	#KS20,lib_Version(a6)
		bhs.b   _ks20code		;fork