SCOPE needs a hard restart (force quit) on bootup

UsedManateeSalesman · Thu Dec 14, 2006 11:52 am

Hey guys,

Oddly enough on my squeaky clean DAW boot (use the other boot for work, junk, etc) although everything comes up and you can hear the DACs click on when the drivers are loaded for scope, I cannot view the scope environment. If I right click on the tray icon I get the normal menu for "Show" and "Exit", however although I can drag that little menu around, both options are unselectable.

The solution is to force quit on scope and restart it manually via the icon. Any ideas on this one? Maybe I could just figure out a way to stop it from autoloading, and do it manually each time?

Thanks,
UMS

astroman · Post by **astroman** » Thu Dec 14, 2006 12:17 pm

to prevent Scope from auto-starting
edit the file cset.ini in the sfp\app\bin directory
change the entry DontRestart=0 (which means start automatically)
to DontRestart=1

cheers, Tom

Post by **garyb** » Thu Dec 14, 2006 3:40 pm

possibly you are not giving it enough time to load?

UsedManateeSalesman · Post by **UsedManateeSalesman** » Thu Dec 14, 2006 3:43 pm

garyb wrote:possibly you are not giving it enough time to load?

No, I thought this too so the next time I booted into the DAW I let it go a long time, left the room, came back, unable to access. What's weird is it autoloads fine on the really junked up boot from another disc. Such is life.

UsedManateeSalesman · Tue Dec 19, 2006 12:53 pm

astroman wrote:to prevent Scope from auto-starting
edit the file cset.ini in the sfp\app\bin directory
change the entry DontRestart=0 (which means start automatically)
to DontRestart=1

cheers, Tom

Just got around to looking at this. I don't currently have DontRestart set in cset.ini. Does it need to go under a particular [HEADING] ?

Thanks,
ums

valis · Post by **valis** » Tue Dec 19, 2006 3:04 pm

Also, the better your PSU the less the clicks will be from the DAC's on startup (learned this when I put a 460W in my scope box).

UsedManateeSalesman · Post by **UsedManateeSalesman** » Tue Dec 19, 2006 3:08 pm

valis wrote:Also, the better your PSU the less the clicks will be from the DAC's on startup (learned this when I put a 460W in my scope box).

The clicks aren't bad really. My PSU is alright, though if I add another scope card I'll be making sure to put in a more powerful one. Since I pulled everything else off the PCI bus, it's managing it and the clicks aren't any more or less than I'd expect from suddenly having them turn on.

The necessary force-quit is the problem :/ If it were happening on my jacked up work boot of XP then I'd understand it. I may uninstall the drivers and reinstall the card if I can't figure out where to put this DontRestart param.

Janni · Post by **Janni** » Wed Dec 20, 2006 2:59 pm

I usually have this problem when scope opens a pop up (device not found), but as its not fully loaded, its not possible to bring it to the top of the desktop.
Try to load your startup project like any other project...
Perhaps this helps...
Cheers,
Jan

astroman · Post by **astroman** » Wed Dec 20, 2006 4:18 pm

UsedManateeSalesman wrote:...I may uninstall the drivers and reinstall the card if I can't figure out where to put this DontRestart param.

oops, I thought it would be there and you'd just have to set it from 0 to 1
on my system it's under
[runpep]
DontRestart=1
to prevent autostart - but it's under Win98, maybe XP deals with this as a service (?)

cheers, Tom

UsedManateeSalesman · Post by **UsedManateeSalesman** » Wed Dec 20, 2006 6:20 pm

Janni wrote:I usually have this problem when scope opens a pop up (device not found), but as its not fully loaded, its not possible to bring it to the top of the desktop.
Try to load your startup project like any other project...
Perhaps this helps...
Cheers,
Jan

I can't load a startup project, or any project, because I can't actually see the scope interface. The only thing there is the scope tray icon, which is only draggable but not clickable.

Post by **irrelevance** » Wed Dec 20, 2006 11:36 pm

For me it seemed the only way to stop this from happening was to edit the system startup under msconfig. I don't know why but it just seemed to me that scope didn't like starting up while windows was sorting itself out.

On my multi boot system I have scope installed twice. The non music boot has an anti virus program (bit defender) and steam which is a service used by valve games run on startup. In this environment scope doesn't seem to mind auto starting? While on my stripped back music boot I sometimes get this hanging.

UsedManateeSalesman · Wed Dec 20, 2006 11:50 pm

Sounds like we have the same weird situation. I also just unchecked it in msconfig. Nice usable autostart for windows sounds and games... funny but annoying.

irrelevance wrote:For me it seemed the only way to stop this from happening was to edit the system startup under msconfig. I don't know why but it just seemed to me that scope didn't like starting up while windows was sorting itself out. On my multi boot system I have scope installed twice. The non music boot has an anti virus program (bit defender) and steam which is a service used by valve games run on startup. In this environment scope doesn't seem to mind auto starting? While on my stripped back music boot I sometimes get this hanging.

astroman · Post by **astroman** » Thu Dec 21, 2006 8:17 am

http://www.r2.com.au/
they have a startup delay freeware (and some other stuff), could be worth a try

cheers, tom

Janni · Post by **Janni** » Thu Dec 21, 2006 12:20 pm

You can´t start scope after your "force quit"?
If you can, just start scope and load your startup-project and there will be an error during loading up, I think...
If not, I didn´t get you right...
Hope you get it cleared!
Cheers,
Jan

UsedManateeSalesman · Thu Dec 21, 2006 12:24 pm

Janni wrote:You can´t start scope after your "force quit"?
If you can, just start scope and load your startup-project and there will be an error during loading up, I think...
If not, I didn´t get you right...
Hope you get it cleared!
Cheers,
Jan

Yes, that's what I was doing in the first place. I just can't load a project, or access the scope interface, after the autostart. Once I get it going it's fine.

Janni · Post by **Janni** » Thu Dec 21, 2006 12:48 pm

No error while loading startup-project?
Hmm, really strange...
Perhaps it works if you delete or rename your startup project.
A new "clean" one will be generated, afaik...
Cheers,
Jan

UsedManateeSalesman · Post by **UsedManateeSalesman** » Thu Dec 21, 2006 3:26 pm

Janni wrote:No error while loading startup-project?
Hmm, really strange...
Perhaps it works if you delete or rename your startup project.
A new "clean" one will be generated, afaik...
Cheers,
Jan

Going to give that a try depending on what happens on the next boot (I'm in my work boot now). Yesterday I overwrote the startup project with another. I notice that the winconfig line runs the sfp.exe with the -s param, presumably to load the startup. I wish I could edit the line directly and take that out.

But no, no error on startup. It's absurd

It isn't a showstopper it's just an annoyance.