FlashFXP takes a long time starting

[rush]

I got the problem that Flash takes ages to load, its about ten seconds from clicking the link till the window shows up. This started a few days ago and i can't tell what i night have done to cause it.
What might Flash be looking for or trying to connect to before showing the main window?
Anybody got an idea?

[bigstar]

How many sites do you have in your site manager? the more sites you have the longer it takes to load them.

If you use anti-virus software that might be causing the long startup, try disabling it and then run FlashFXP and see if it makes a difference. Be sure to re-enable your anti-virus software.

[rush]

No its not my Antivirus, i just made sure. My Sites.dat isn't really big, and before this behaviour started Flash loaded within a second.
What i did do lately is redo my linux router, with new firewalling. But as you are saying that Flash does not have any network activity when starting i didn't look into this.
Or maybe i accidently removed something from the registry.

Anyways, when i start it FlashFXP.exe appears in the processes in the taskmanager and then sits there for its like ten seconds doing nothing until i see the window.

[bigstar]

Which version/build of FlashFXP are you using?

Do you have any network drives? On startup FlashFXP enumerates drives.

FlashFXP doesn't rely on any registry settings. All important information is stored in your FlashFXP folder.

[rush]

I am currently using the latest RC, but it is the same with the old 1.4.
But i do have networked drives through Samba. Yet i had this setup for ages and without any problems. Does Flash walk the whole directory structure on start?
But still wouldn't explain why i never had a problem before.

[bigstar]

No it does not. I don't know anything about Samba, perhaps that's it. I really don't know :confused:

[Linkster]

are you running flashfxp from a network share? is your default startup folder a network share? both these can cause delayed startup

[rush]

Thanks Linkster, you gave the right hint!
I actually have a network share set as default download path and when i redid stuff i changed the machines name. So there was a nonexistant startup path set.
I knew i was missing something. lol

Problem solved, thanks :)