Issues with the program

[harmgsn]

I recently upgraded to 3.4 and purchased a new license separate from my work, and now I'm seeing some oddities with the program. Specifically I cannot connect to any of the sites I have saved (but I can via command line) and when I open quick connect, I see some oddities in the dialog window. I have provided a screenshot of the 'oddities'. Here's the link:

http://img388.imageshack.us/img388/9355/flashfxp1bw8.jpg


Any help? Please? :(

[MxxCon]

we need this info http://www.inicom.net/forum/showthread.php?t=4275

[harmgsn]

Forgive me... here's the information:


* FlashFXP v[ 3].[ 4.0], build [1145 ], [ x]registered, [ ]unregistered, [ ]pirated
* OS [ x] WinXP, [ ] Win2K, [ ] Win98, [ ] WinME, [ ] Other
* Running behind NAT/router [ x] Yes & Model [freebsd ipfilter ], [ ] No, [ ] Not sure
* Running firewall [ ] Yes, Name [ ], Ver. [ ], or [ x] No
* Running Antivirus [x ] Yes, Name [Norton Pro 2k3 ] or [ ] No
* Network [ ] xDSL, [x ] CABLE, [ ] Dail-Up, [ ] Other

additional info if related
* FTP server(s) name [freebsd ftpd], version [6.00LS]


It's a WinXP machine fully patched running FlashFXP 3.4.0b1145 (registered) behind a FreeBSD box with ipnat/ipfilter (flashfxp has worked up until 3 days ago) on a Cable modem. I do run Norton 2k3 Pro, but all traffic scanning is diabled. I do not run a firewall on the local system as that's what the freebsd box is for.

When I go to Help -> About it says "This version is licensed to N/A", but I have a valid registration key sitting in my inbox right now from a few hours ago. :\ I have also noticed that I am getting the oddities everywhere in the menus. Site Manager, Quick Connect, About, Preferences.... I've completely uninstalled the program and started from scratch but it does not seem to want to go away. Any help is more than welcome at this time. Thanks!

[bigstar]

I am going to contact you privately regarding this issue

[bigstar]

This issue was resolved by deleting the english.elg language file from the FlashFXP\Language folder.

We're still looking into the problem to determine why this error occured in the first place.