I sent further information about the Service mode to your other topic
The problem is that if you decrease the Pre-start delay, then Hard Disk Sentinel tries to access the hardware, collect hard disk and disk controller device information and loads its files when other software is still initialising. As you can see, this even slows down things.
Other software which does not really communicate hardware this way may start very quickly, but HDSentinel needs to enumerate hard disk controllers, drivers, hard disks and connections, performance objects and so - which all require time from the OS, especially during startup of other software.
However, I can confirm that some parts of the software (which does not require so high communication with the hardware) already initialised before this pre-start delay, so some information (like the amount of transferred data) may be already checked during these seconds, even if the software does not yet visible (you can check that HDSentinel.exe is already active during that time in Windows Task Manager).
> I installed HDS on E:\ on my secondary HDD for testing whether I wanted it.
> I decided to keep it and registered it in that position.
> Would it start up much faster if I install HDS on the SSD I want to monitor
HDS does not load too much files. In theory yes, it could be a bit faster if you put it with all of its files to the SSD but the startup depends on lots of other factors, for example the OS and other software launched on startup.
> Could any of this delay be affected by my extremely recent removal of Pagefile.sys from the SSD to this same Secondary HDD E:\
This is a very good idea - I just recommend to set it to FIXED size.
Otherwise, yes, you may expect slowness of ANY software because all allocations/deallocations would cause Windows to allocate/shrink the swapfile which is a very time intensive operation. I'd also recommend to have the hard disk completely de-fragmented BEFORE placing the swapfile on it, to prevent fragmentation of the fixed size swapfile.
