Assuming you're Scheduling those 25 profiles, the instance of SBFree you're looking at in the foreground is not the instance of the program that is running the profiles. If you're using Vista or later, the instance that is (running them) is likely not even visible:
http://www.2brightsparks.com/resources/ ... 011.html#3
Hence, no progress bar in the foreground instance.
It's not clear whether you are running the 25 profiles individually (and either potentially or deliberately in parallel), but the fact the last 3 profiles are apparently running in parallel now suggests it's probable. It's usually much more efficient to run them sequentially c/o a Group (not forgetting to delete the individual Schedules, if used, and rely on the Group's Schedule - otherwise they'll all conflict). That way, the various profiles are not contending with each other for resources (disk access, USB bus, network, whatever)
The other big issue is that if you're Scheduling them individually, every profile will be running (or was running) in its own individual instance of SBFree (compared to the Group mode, which uses one Scheduled instance of the program, and simply queues the profiles). Multiple instances of what is now a much larger program won't help...
It's possible the large profiles are hitting delays in performing the rename operation inherent in our Safe Copy process very slowly (some NAS devices do, for example), and your previous V3 freeware was either a version that didn't have Safe Copy or didn't have it set. Otherwise, not enough to go on, and we don't really offer an analysis service for the freeware, sorry (even if we did, you'd need to use a debug mode which currently isn't in force). You might want to stop those profiles, reboot and try again manually (one at a time). They'll need to scan again, but shouldn't need to re-copy anything. You may find they run much faster.
http://www.2brightsparks.com/resources/ ... 011.html#3
Hence, no progress bar in the foreground instance.
It's not clear whether you are running the 25 profiles individually (and either potentially or deliberately in parallel), but the fact the last 3 profiles are apparently running in parallel now suggests it's probable. It's usually much more efficient to run them sequentially c/o a Group (not forgetting to delete the individual Schedules, if used, and rely on the Group's Schedule - otherwise they'll all conflict). That way, the various profiles are not contending with each other for resources (disk access, USB bus, network, whatever)
The other big issue is that if you're Scheduling them individually, every profile will be running (or was running) in its own individual instance of SBFree (compared to the Group mode, which uses one Scheduled instance of the program, and simply queues the profiles). Multiple instances of what is now a much larger program won't help...
It's possible the large profiles are hitting delays in performing the rename operation inherent in our Safe Copy process very slowly (some NAS devices do, for example), and your previous V3 freeware was either a version that didn't have Safe Copy or didn't have it set. Otherwise, not enough to go on, and we don't really offer an analysis service for the freeware, sorry (even if we did, you'd need to use a debug mode which currently isn't in force). You might want to stop those profiles, reboot and try again manually (one at a time). They'll need to scan again, but shouldn't need to re-copy anything. You may find they run much faster.
