Slow startup may be caused by 'problematic' disk drive (FRV queries all drive letters present in system for properties, than monitors all removable drives for media change), or by some broken drivers for other hardware (for example, one of our users has problems with Wacom Bamboo driver: if tablet was not connected to computer, driver initialization takes a long time; solved by driver update).
'Broken drive' may be, for example, drive letter connected to network storage, but NAS is not turned on, in this case drive query for properties will take a long time.
1. For disk drives query/monitoring problem we have this solution (mostly diagnostic, although you may work without Folders panel):
- Close FRV
- Navigate to "C:\Program Files\LibRaw\FastRawViewer\scripts" using Windows Explorer
- double click on DisableFoldersOnStart.reg script, confirm you're want to run Registry Editor/Enter changes into Registry.
- start FRV again
This script will disable opening Folders panel on program start and all logic behind this panel (disk drives/letters properties query, media monitoring, etc). This Folders panel still may be opened by F7 key (and will start all logic when opened).
If disabling Folders panel will help, the problem is definitely with drives query/monitoring logic (see section 3 below what may be done with it).
2. If it will not help, the problem is with other points. It may be not FRV itself, but some software (antivirus, etc) which monitors process memory (FRV allocates large memory chunks, so this monitoring may be slow). It also may be memory debugging settings if you're a software developer and use 'Debug Heap' settings (of MS Visual studio) in global environment settings (in this case MSVC runtime performs deep allocated memory analysis whitch is slow if large memory chunks are allocated.
To check against 3rd-party memory monitoring, please open Windows Task Manager window (Ctrl-Shift-Esc, select 'More details' in window bottom to show in details), than start FRV and see if any other process (antivirus, etc) will show big CPU usage.
If no suspicious activity is visible in Task Manager during FRV startup, we definitely will need dump file created during this delayed start. Without dump file we're unable to know what part of the FRV produces such delay.
To reduce Dump file size please
- change Preferences - File Handling - Start without filename to 'Empty screen', this will prevent recalling old folder
- in Preferences - Performance please make sure you have not increase cache sizes from defaults (12 for RAW and 20 for JPEGs).
With these settings, DMP file of just-started FRV should be about 300Mb, and will compress (by zip/7zip/rar) to 80-100Mb. Please send the DMP file to us using any file sharing service (WeTransfer.com, dropbox, google drive, MS One Drive, etc)
3. What to do if the problem is caused by disk drive
1st: enable standard folders behaviour back:
- Close FRV
- run EnableFoldersOnStart.reg script
- Open FRV
- open Folders panel by F7
- Close and open FRV again to see if Folders panel is in place.
Solution 1: if you know what drive letter causes the problem (it may be disconnected network drive letter, bad card reader, not connected A: floppy drive, etc), you may disable access to some drive letters/path prefixes by registry settings.
To do that, copy ResetDisabledFolders.reg script from FRV scripts folder to some place where it is editable, and change "DisableFolderPaths"="" line to something like
"DisableFolderPaths"="z:/;q:/"
(note the slashes, there are not Windows, but 'unix' slashes). Use drive letters of suspected drives instead of z: and q: in my sample.Than run this script. My sample will completely disables any access to z: and q: drive letters by FRV.
Solution 2: Simplified folders panel w/o any advanced features (context menus, media monitoring, etc):
Just run SimpleFoldersHandling.reg script while FRV is closed (NormalFoldersHandling.reg to revert it back).
Hope, your problem is with disk drives/network storage, not with other software/drivers. In this cases diagnostic (part 1) and one of solutions above will definitely help. If not, please send us DMP file created during slow FRV start.
Dear Sir:
Dear Sir:
(sorry for the long answer :)
Slow startup may be caused by 'problematic' disk drive (FRV queries all drive letters present in system for properties, than monitors all removable drives for media change), or by some broken drivers for other hardware (for example, one of our users has problems with Wacom Bamboo driver: if tablet was not connected to computer, driver initialization takes a long time; solved by driver update).
'Broken drive' may be, for example, drive letter connected to network storage, but NAS is not turned on, in this case drive query for properties will take a long time.
1. For disk drives query/monitoring problem we have this solution (mostly diagnostic, although you may work without Folders panel):
- Close FRV
- Navigate to "C:\Program Files\LibRaw\FastRawViewer\scripts" using Windows Explorer
- double click on DisableFoldersOnStart.reg script, confirm you're want to run Registry Editor/Enter changes into Registry.
- start FRV again
This script will disable opening Folders panel on program start and all logic behind this panel (disk drives/letters properties query, media monitoring, etc). This Folders panel still may be opened by F7 key (and will start all logic when opened).
If disabling Folders panel will help, the problem is definitely with drives query/monitoring logic (see section 3 below what may be done with it).
2. If it will not help, the problem is with other points. It may be not FRV itself, but some software (antivirus, etc) which monitors process memory (FRV allocates large memory chunks, so this monitoring may be slow). It also may be memory debugging settings if you're a software developer and use 'Debug Heap' settings (of MS Visual studio) in global environment settings (in this case MSVC runtime performs deep allocated memory analysis whitch is slow if large memory chunks are allocated.
To check against 3rd-party memory monitoring, please open Windows Task Manager window (Ctrl-Shift-Esc, select 'More details' in window bottom to show in details), than start FRV and see if any other process (antivirus, etc) will show big CPU usage.
If no suspicious activity is visible in Task Manager during FRV startup, we definitely will need dump file created during this delayed start. Without dump file we're unable to know what part of the FRV produces such delay.
To reduce Dump file size please
- change Preferences - File Handling - Start without filename to 'Empty screen', this will prevent recalling old folder
- in Preferences - Performance please make sure you have not increase cache sizes from defaults (12 for RAW and 20 for JPEGs).
With these settings, DMP file of just-started FRV should be about 300Mb, and will compress (by zip/7zip/rar) to 80-100Mb. Please send the DMP file to us using any file sharing service (WeTransfer.com, dropbox, google drive, MS One Drive, etc)
3. What to do if the problem is caused by disk drive
1st: enable standard folders behaviour back:
- Close FRV
- run EnableFoldersOnStart.reg script
- Open FRV
- open Folders panel by F7
- Close and open FRV again to see if Folders panel is in place.
Solution 1: if you know what drive letter causes the problem (it may be disconnected network drive letter, bad card reader, not connected A: floppy drive, etc), you may disable access to some drive letters/path prefixes by registry settings.
To do that, copy ResetDisabledFolders.reg script from FRV scripts folder to some place where it is editable, and change "DisableFolderPaths"="" line to something like
"DisableFolderPaths"="z:/;q:/"
(note the slashes, there are not Windows, but 'unix' slashes). Use drive letters of suspected drives instead of z: and q: in my sample.Than run this script. My sample will completely disables any access to z: and q: drive letters by FRV.
Solution 2: Simplified folders panel w/o any advanced features (context menus, media monitoring, etc):
Just run SimpleFoldersHandling.reg script while FRV is closed (NormalFoldersHandling.reg to revert it back).
Hope, your problem is with disk drives/network storage, not with other software/drivers. In this cases diagnostic (part 1) and one of solutions above will definitely help. If not, please send us DMP file created during slow FRV start.
--
Alex Tutubalin/FastRawViewer team