How to disable modification of hds_control.vbs?

[Samurai]

Excuse me for the issue.

Under Windows 7, Hard Disk Sentinel needs to use the Windows scheduler to schedule itself to run when you log in to the system because other ways (which worked in previous versions of Windows, for example using the registry) do not work.

So on startup (if the "load with Windows" option in Configuration -> Preferences page enabled) it creates this vbs file to
- check if its entry is present in Windows scheduler
- add its entry if required to start with Windows on next boot.
- remove its entry if required (for example if that option is disabled)

I'm sorry about conflict(s) with the other software. Is it possible to add that file as an exception, so that program should not check / issue warning on this VBS file? Most such programs have a such function.

The only way to disable the creation/use of this VBS file is to disable the above mentioned "Load with Windows" option in Hard Disk Sentinel.
However, then it will not load automatically on startup - unless you manually create a such entry to Windows scheduler, which will start the software (regardless of the setting in Hard Disk Sentinel). Maybe please check (and copy) the current settings for that, or let me know if I can provide further information about how to modify the settings of Windows Scheduler.

[hdsentinel]

Ps. sorry, it seems something happened with your original post and it is overwritten with the answer. Excuse me for the problem.

[Samurai]

Thank you for the quick reply even at the weekend!

Unfortunately the HIPS I'm using only allows excluding at the directory level and I cannot exclude the common Temp directory where the vbs file is created.

Yes, I do have the "Load with Windows" checked.

I also noticed a moment ago that when using a Standard user account (i.e. not an Administrator account) HDS will not start automatically at all regardless of the preference setting.

I do hope that there is at least some way to get HDS start automatically in Windows 7 under a Standard account, too.

[hdsentinel]

Thanks for your message. Of course, I try to help as soon as possible

I'm sorry, but administrator rights are required for HDS to access disk status information, so HDS can only work if you log in as Administrator.
This is true for both manual and automatic startup (and this is true for other sytems, like XP if you used that previously).

The other possibility is to use it as a service: Configuration -> Integration -> Use as service (when you logged in as Admin).
Then HDS will work as an NT service and runs even when standard rights user logged in (or even when no user logged in at all). But Windows 7 will not display the user interface as (compared to older Windows versions) it does not allow the use of interactive services. So that way you can only get information by using a web browser if you previously enable Configuration -> Integration -> Enable WebStatus.
Please check the Help for more information about these options.

[Samurai]

Ok, it sounds that the web interface may be the correct solution for me. I'll have a look on it. Thanks again!

[Samurai]

Do you think it could be possible to change the creation of hds_control.vbs in a future version so that it would be created in e.g. Users\User-x\AppData\Local\HDSentinel instead of the current common Temp directory?

That would make it easier to exclude it from a HIPS program which can operate only at the directory level with exclusion lists. I cannot afford to exclude ...\AppData\Local\Temp but I could exclude a HDS specific directory...

[hdsentinel]

Thanks for your attention, yes, to help the cooperation with HIPS program, that will be considered and probably it will be available in the next release.

[hdsentinel]

If you prefer, please try the latest beta version: 3.70.11
It is available from the "Download" page under Beta versions ( http://www.hdsentinel.com/dl.php )
or directly from http://www.hdsentinel.com/beta3/hdsenti ... p37011.zip

1) it uses C:\Users\%username%\AppData\Roaming\Hard Disk Sentinel folder (application-specific folder) instead of TEMP folder
2) it saves up to 3 different VBS files for different purposes when required, so the VBS files are not changed/modified/updated (unless really required)

Hopefully these changes will prevent problems with your HIPS program.
Thanks for your attention and excuse me for this issue !