No longer minimized on computer startup - how to fix?
No longer minimized on computer startup - how to fix?
For some reason my Scope 4.0 no longer starts minimized when the computer is first started. Can anyone tell me how to set it to start minimized like it used to?
Didn't work. I'm looking to have SFP come on in "Hide" mode when I boot up. As it is, I have to click on "Hide" in the SPF icon in the tray bar to dismiss it every time I reboot the computer, which is a lot. It's annoying, and I didn't used to have to do this.stardust wrote:Minimize it and than save the startup project when closing down scope.
It's probably a setting in App\bin\cset.ini but I can't figure out what it would be.
-
soylent.green
- Posts: 97
- Joined: Sun Jan 04, 2004 4:00 pm
- Location: Munich, Germany
The "-s" option
This is such a damn time consuming, pain in the arse problem.
Oh, I'm sorry, I'm getting upset.
I (and I think plenty of other users) had this multiple times. I had to figure out the solution multiple times...until pain became to big and solution burnt into my brain. I know you solved it, but for the reason of documantation (Anyone volunteering a FAQ on this)...
Use Start > Run > Programm > msconfig
Scroll down to find Entry "SFP"
What does it say in column "command"? is it "...\SFP.exe -s"?
No?
Go to regedit, use the Path from msconfig (Column "Path")
Find the Entry which ends in "SFP.exe". On my system this is key "InitPulsar"
Add " -s" to the value (don't forget the blank between ".exe -s"!
Only leave one SFP.exe entry below "Run", remove all others. I once had two entries...
Close Registry and reboot.
BTW: Is there any installation FAQ? List of common pitfalls + solutions.
A similarly painfull installation problem is one which simply results from "no write access" to some files that the installer itselfe writes to harddisk. I remember that the failure messag that pops up was no help in no way. It was just planetz that helped...Was it the step were you could provide a file with registration keys???? Hopefully some of the pitfalls will be removed in SFP 5.
(Nevertheless I enjoy the overall quality of scope software - If microsoft had done it, it would have been worse, belief me...)
Oh, I'm sorry, I'm getting upset.
I (and I think plenty of other users) had this multiple times. I had to figure out the solution multiple times...until pain became to big and solution burnt into my brain. I know you solved it, but for the reason of documantation (Anyone volunteering a FAQ on this)...
Use Start > Run > Programm > msconfig
Scroll down to find Entry "SFP"
What does it say in column "command"? is it "...\SFP.exe -s"?
No?
Go to regedit, use the Path from msconfig (Column "Path")
Find the Entry which ends in "SFP.exe". On my system this is key "InitPulsar"
Add " -s" to the value (don't forget the blank between ".exe -s"!
Only leave one SFP.exe entry below "Run", remove all others. I once had two entries...
Close Registry and reboot.
BTW: Is there any installation FAQ? List of common pitfalls + solutions.
A similarly painfull installation problem is one which simply results from "no write access" to some files that the installer itselfe writes to harddisk. I remember that the failure messag that pops up was no help in no way. It was just planetz that helped...Was it the step were you could provide a file with registration keys???? Hopefully some of the pitfalls will be removed in SFP 5.
(Nevertheless I enjoy the overall quality of scope software - If microsoft had done it, it would have been worse, belief me...)
