hide scope on startup
-
- Posts: 157
- Joined: Tue Aug 31, 2004 4:00 pm
if the above solution of putting a link in your startup menu doesn't work... you can always open regedit and go to:
local machine, software, microsoft, windows, current version, run
and add a new string value with the following:
name: SFP data: c:...sfp.exe -s
pretty much the same as above, only you are using regedit to create a key in the registry to have it run instead of the start folder... i only mention this because when i tried adding it to my start folder, it gave me errors and wouldn't run... i would have to open it manually everytime. hope this helps someone.
local machine, software, microsoft, windows, current version, run
and add a new string value with the following:
name: SFP data: c:...sfp.exe -s
pretty much the same as above, only you are using regedit to create a key in the registry to have it run instead of the start folder... i only mention this because when i tried adding it to my start folder, it gave me errors and wouldn't run... i would have to open it manually everytime. hope this helps someone.
i hope that does help Crisis,my SFP starts up automatically without an icon even being in the start-up folder so i was havig problems...does anyone know where the scope actually opens from on start-up????i'll try the regedit thing though, but i'm thinking that something has already opened it by the time this command runs from registry...
<font size=-1>[ This Message was edited by: minipax on 2004-10-26 12:38 ]</font>
<font size=-1>[ This Message was edited by: minipax on 2004-10-26 12:38 ]</font>
-
- Posts: 157
- Joined: Tue Aug 31, 2004 4:00 pm
the reason your sfp is starting without a shortcut in startup is because there is already a key in the registry telling it to start. sfp automatically inserts it's own startup key in the windows registry upon installation. if it isn't in;
local machine, software, microsoft, windows current version, run...
then try looking in;
current user, software, microsoft, windows current version, run...
the reason i say to put the key in local machine is because if you have different user accounts then it will only work on the account you are currently logged into.
putting it in local machine just assures no matter what it will initiate upon startup. if you already have a key in one of these directories, then just edit it and add the
-s at the end of it.
local machine, software, microsoft, windows current version, run...
then try looking in;
current user, software, microsoft, windows current version, run...
the reason i say to put the key in local machine is because if you have different user accounts then it will only work on the account you are currently logged into.
putting it in local machine just assures no matter what it will initiate upon startup. if you already have a key in one of these directories, then just edit it and add the
-s at the end of it.