File editor option bug

I had custom file editor with path "C:\Program Files\Notepad++\notepad++.exe"
After reinstalling windows I saved all FlashFXP user files, so they are the same. Now I`ve installed last build of FlashFXP (1535).

Installation folder
D:\FlashFXP 4
Settings folder
D:\FlashFXP 4\4

I`ve changed path of file editor in settings to "C:\Program Files (x86)\Notepad++\notepad++.exe" but FlashFXP displays an error when I try to edit sime file saying that "C:\Program Files\Notepad++\notepad++.exe" is not found.
I can write in Settings anything and it`s been saved(!), but in config file (FlashFXP.ini) there are now changes

[Viewers]
*.html;*.php;*.xml=111;C:\Program Files\Notepad++\notepad++.exe

Win7 x64

Please post the details from within FlashFXP > Help > About > Details tab

Perhaps FlashFXP doesn't have proper write access to the data folder.

Windows:
Windows 7 x64 Service Pack 1 (6.1.7601)

FlashFXP version:
4.0.0 (build 1535)

Installation type:
All User - Custom data folder

Program folder  [Access: Read / Write]
D:\FlashFXP 4\

Data folder  [Access: Read / Write]
d:\FlashFXP 4\4\

Shared data folder  [Access: Read / Write]
C:\ProgramData\FlashFXP\4\

Temp folder  [Access: Read / Write]
C:\Users\NeoN\AppData\Local\Temp\

I conducted several tests and I was not able to reproduce the issue, Changing the application saves the changes to the flashfxp.ini and the new application is correctly used for editing.

Reinstalling didn`t help, so I deleted editor`s path from FlashFXP.ini and applyed new path.
But I don`t get where was stored path in settings if in config file was another entire?

I also tested this and cannot find fault.

I suggest user caused bug by changing the default install path for FlashFXP

Mine is

Windows:
Windows 7 x64 (6.1.7600)

FlashFXP version:
4.0.0 (build 1535)

Installation type:
All User - Common data folder

Program folder  [Access: Read / Write]
C:\Program Files (x86)\FlashFXP 4\

Data folder  [Access: Read / Write]
C:\ProgramData\FlashFXP\4\

Temp folder  [Access: Read / Write]
C:\Users\X3\AppData\Local\Temp\

users is using path D:\ and d:\ please note this may be case sensitive.

And I have no issues, its clear something is amiss with users setup which causes bug.

I ran some more tests and determine this to be user caused bug

There's no way this fails if user had installed flashfxp properly to begin with.

And again using a unstable service pack for the OS.

And again using a unstable service pack for the OS.

It is RTM build.

Originally Posted by NeoN_Roma

It is RTM build.

Sorry no its not, if you check the official site, even MSDN it is still RC candidate, the RTM was a leak that is buggy and Microsoft pulled from release because it is very buggy, this is valid for all countries.

You did not get that file from Microsoft you downloaded it from a 3rd party unsupported site like a zillion other people, I did too but its on a Virtual machine and not as my main, I can tell you its quite disappointing, from a quite experienced user point of view.

Check yourself buddy, don't take my idle words for it.

http://www.microsoft.com/oem/en/down...ows_7_sp1.aspx

That says it all

But thx for info.

See ya around man..

I have RTM-Escrow build 7601.17514.101119-1850 sign-off
But maybe it is already not RTM)))

Na its not RTM

Escrow is the engineer or dipstick,numb nuts idiot who signed off on crap because believe it or not MS does employ engineers who know less then you or me about this stuff.

I give you a fine example

remember XP sp3 and the LLTD fiasco?

I came up with a fix 6 months before Microsoft released a fix, its on my blog.

http://x3webworx.wordpress.com/?s=lltd

its the bottom article and the top is MS lovely fix which to get you had to sign in to accept a disclaimer get your OS WGA scanned then you were redirected to a page with the download.

After that I swore never to fix any MS crap.

Anywho this bug cant be reproduced...

your custom install paths are wrong, Em pretty sure the data and program install paths cant be same unless your using a flashfxp.portable file. Essentially an empty file with no extension with that name

Nonono, I remembered that now! There was buggy SP, but this is another one
But lets finish tis discussion)

you betcha...

Just trying to help you out cause I cant reproduce bug you reported at all...