Filezilla fails to start for no apparent reason

[Zbyněk Winkler]

After installing 3.2.1 I get only one dialog window with OK button telling me to report all bug I encounter. After clicking OK the dialog disappears but nothing else happens. The process keeps running but I get no top level window.

[Zbyněk Winkler]

Ok, it just takes very very long time (I've managed to create account, read the "NewTicketForm" file, submit the ticket, loose interest and start doing something else - over all about 15min).

[Tim Kosse]

Do you have slow or disconnected network drives? Do you have antique hardware (such as floppy drives) which take a long time to respond each and every time Windows forgets that there's no media inserted?

[Zbyněk Winkler]

Yes, I have disconnected network drives. It works fine when I turn on the vpn client and the drives are accessible. It also works fine when connected to the internal network directly. I also tried winscp and it has the same problem. OTOH totalcmd starts and runs just fine even with the inaccessible network drives so there probably is a way to deal with this.

[Tim Kosse]

FileZilla just queries Windows for drive labels and icons. Nothing I can do to fix it if Windows decides to block.

Regarding TotalCommander, last time I tried it (been a while though), it only had generic stock icons and no labels.

Just unmap your network drives when you don't need them.

[Zbyněk Winkler]

Unfortunately it is not reasonable to unmap about 10 drives after work only to remap them the next morning in the office :(. BTW: I do not know about icons but the labels are just fine in totalcmd.