http://www.winpenpack.com/ it-it Copyright © winPenPack 2005-2023 - All rights reservedPowered by e107 website system | winPenPack License AgreementTerms of Use | Privacy Policy winpenpack@nospam.com (winPenPack) winpenpack@nospam.com (winPenPack) Mon, 16 Mar 2026 10:07:47 +0100 Mon, 16 Mar 2026 10:07:47 +0100 http://backend.userland.com/rss e107 (http://e107.org) hourly 1 60 http://www.winpenpack.com/main/e107_images/logo.png http://www.winpenpack.com/ 88 31 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409
thank you very, very much for X-Launcher. I like it very much.

Here's a little problem, I've noticed. This seems to be a bug in X-Launcher (all versions). The below samples show that X-Launcher does not interpret its command-line parameter (filenames) the right way.
I'm not sure about it. But I think that X-Launcher should always give the full path of filenames to the executed application (see examples below). Another way: Maybe it can be done by setting the working directory. But I don't know what happens if you're using two files from different directories.

Have a nice day.
zoi


---------------------------------------------------------------------------
Test 1:
---------------------------------------------------------------------------
x-WinMerge
taken from http://www.winpenpack.com/main/download.php?view.27
15 ottobre 2009 - 00:25:54

1. x-WinMerge started from CommandLine (Cmd, FarManager, ...)
'Dir: C:\X-WinMerge\'
'Cmd: X-WinMerge.exe X-WinMerge.ini X-WinMerge2.ini'

2. Result:
x-WinMerge does not start right.
- it opens "File Open"-Window
- Showing
'Left: C:\X-WinMerge\Bin\WinMerge\X-WinMerge.ini X-WinMerge2.ini'
in "File Open"-Window for Left side. This is terrible because
WinMerge cannot handle this single kind of filename.
Should be:
'Left: C:\X-WinMerge\Bin\WinMerge\X-WinMerge.ini'
'Right: C:\X-WinMerge\Bin\WinMerge\X-WinMerge2.ini'

3. No Problem when using winmerge directly:
'Dir: C:\X-WinMerge\'
'Cmd: C:\X-WinMerge\Bin\WinMerge\WinMerge.exe X-WinMerge.ini X-WinMerge2.ini'



---------------------------------------------------------------------------
Test 2:
---------------------------------------------------------------------------

X-FoxitReader launcher 1.4.2 [rev10]
taken from http://www.winpenpack.com/main/download.php?view.1042
13 ottobre 2010 - 13:40:23

1. X-FoxitReader started from CommandLine (Cmd, FarManager, ...)
'Dir: C:\X-FoxitReader\'
'Cmd: X-FoxitReader.exe td_1.pdf'

2. Result:
X-FoxitReader does not open file 'td_1.pdf'.

3. No Problem when using X-FoxitReader directly:
'X-FoxitReader.exe td_1.pdf C:\X-FoxitReader\td_1.pdf'
]]> Tue, 26 Oct 2010 07:30:22 +0200 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 At first sight, the solution to your problem should be quite easy.
Just add

[FileToRun]
(...)
WorkingDir=@WorkingDir@

in the X-WinMerge.ini and X-FoxitReader.ini files, and see if this changes their behaviors as you desire...
Please, try and let us know if it works for you!
Best Regards
ZioZione]]> ZioZione Wed, 27 Oct 2010 21:30:37 +0200 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409
'X-FoxitReader' works fine now. I do not really understand that. I've played around with so many parameters, changing directories and filenames in every single way. But there were no lacks. What does the working dir has to do with files in different locations? But, at last, it does work.


'X-WinMerge' still has it's problems:

Test:
Direct start of 'X-WinMerge.exe' in 'C:\WinMerge\'
Cmd: X-WinMerge.exe X-WinMerge.ini X-WinMerge2.ini
-> same error

Cmd: X-WinMerge.exe C:\WinMerge\X-WinMerge.ini C:\WinMerge\X-WinMerge2.ini
-> same error

Direct start of 'WinMerge.exe' in 'C:\WinMerge\'
Cmd: C:\WinMerge\Bin\WinMerge\WinMerge.exe X-WinMerge.ini X-WinMerge2.ini
-> ok

Maybe there are different causes for the problems?

]]> zoi Thu, 28 Oct 2010 07:40:04 +0200 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409
X-WinMerge launcher is version 1.4, with the new version 1.4.2 the problem is solved.
It will be updated as soon as possible.
]]> Energy Thu, 28 Oct 2010 16:20:16 +0200 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 X-WinMerge is now in download with the new launcher 1.4.2, please check if the bug is finally solved.

Thanks for your help.

Best regards]]> zandet2 Sat, 30 Oct 2010 15:07:33 +0200 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409
cmd: X-WinMerge.exe X-WinMerge.ini X-WinMerge2.ini
-> X-WinMerge.exe tries to locate those files in the directory of the original exe.

I've added the following lines (like ZioZione said)

[FileToRun]
....
WorkingDir=@WorkingDir@

Now it works fine.
X-WinMerge.exe has to be re-released one more time, i think.

Thank you all for you help.



]]> zoi Mon, 01 Nov 2010 07:11:05 +0100 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409 the last released X-WinMerge package is already correct for normal use.
The only difference betweeen this one and previous is the correction of management of paths with spaces in their names.
The solution I depicted above is for using X-WinMerge in batch processing, that is surely less diffuse (and required), and allow the interested users (like you) to perform particular jobs. Anyway, I hope you appreciate it
Best Regards
ZioZione]]> ZioZione Mon, 01 Nov 2010 12:06:21 +0100 http://www.winpenpack.com/main/e107_plugins/forum/forum_viewtopic.php?46409