Page 2 of 2

Posted: 23.10.2007, 21:08
by Marek
The difference is probably Windows (Vista - Win2000).
For XP is possible to deactivate the ZIP:
regsvr32 /u zipfldr.dll

Geoff, you can try if it works for Vista.

Posted: 24.10.2007, 00:18
by Geoff
Hi Marek,

I tried the reg thing with no luck, it complains about no entry-point on the .dll and probably just as well (read below)

For what it's worth I wouldn't spend much time on this, as I have a work-around in place (don't close FC with the focus on a folder which contains any large .zips)



From what I've established, on my PC (aka Vista)
(and no this is NOT an all encompassing applies to everyone statement!!!)

- the number of files in the .zip affect the FC load time, not so much the size of the .zip file

- tree view affects the FC load time

- Windows explorer doesn't seem to be affected by the .zips in the same way


I would hazard a guess and speculate, that because Vista has lzw support already built into the operating system, that somehow the OS is doing a read-ahead cache trick and trying to interrogate the content of the .zip file in an attempt to increase performance for when the user wants to access the .zip file?? Refer: LZInit() and Lz32.lib on MSDN

I would also hazard a guess and speculate that Windows Explorer must some how mask or block this functionality during loading???

Even still, the more I think about it... Depending on the way the threading has been designed in FC, this could be contributing to the problem.

With the apps I write, I try to keep the UI 100% responsive and shielded from the worker threads, communicating via queued messages. Depending on how FC is threaded, it could be made to appear instantaneously with the panel inactive whilst reading from the disk or display the "loading..." screen

Ahh. The more I think about this, the more certain I become. I've observed this in a number of folders where FC displays stale data even after clicking on another folder, which would ideally cause a screen refresh.

Also, when I use FC I generally only work with one panel 100:0 layout for the panes. However, I notice if I extend the UI, that the second panel is revealed. This may be effectively doubling the work the machine has to perform during load time??

Food for thought.

As I've mentioned earlier, I think FC is great and I am trying to help.
I understand that FC is your baby. If you would like me to, I would be happy to look at the source code and offer any suggestions.

Regards,

Geoff

Posted: 24.10.2007, 01:13
by ian
I would hazard a guess and speculate, that because Vista has lzw support already built into the operating system, that somehow the OS is doing a read-ahead cache trick and trying to interrogate the content of the .zip file in an attempt to increase performance for when the user wants to access the .zip file?? Refer: LZInit() and Lz32.lib on MSDN

I would also hazard a guess and speculate that Windows Explorer must some how mask or block this functionality during loading???

That would explain everything, and knowing microsoft would be something they would do...

Even still, the more I think about it... Depending on the way the threading has been designed in FC, this could be contributing to the problem.

With the apps I write, I try to keep the UI 100% responsive and shielded from the worker threads, communicating via queued messages. Depending on how FC is threaded, it could be made to appear instantaneously with the panel inactive whilst reading from the disk or display the "loading..." screen


I've has the same issue with a few other FC things - but FC is effectively a single thread program at the moment - so Marek would have to do a lot of work to change that! And I agree with you re the UI, I do the same and have written my own thread based (and thread safe) classes to manage it all..

Posted: 21.06.2009, 11:47
by jpretori
Hi, I see this is an old thread - I'm seeing the same symptoms as Geoff did back in 2007.

I use Windows XP, with all the latest service packs & updates, I have no particularly enormous zip files that I'm aware of (certainly not in any folders that I frequently start FC in), I don't use the tree view (anymore, I used to have it on), and yet, each time I start FC I have to sit there looking at the desktop for about 10-15 seconds before it pops up.

I work on a Dell Latitude D820.