Startup and default projects

Cochise · Post by **Cochise** » Fri Sep 09, 2005 1:27 pm

Hi.

I've personalized startup and default projects, but now, trying to restore the initial one, I'm experiencing problems.

The startup/default project after a fresh Scope installation could be scopeappssfpappsfp.pro, so I have to load and then save it as startup and default; but loading it I got an error message, then system freezes

[ This Message was edited by: Cochise on 2005-09-09 14:29 ]

arela · Post by **arela** » Fri Sep 09, 2005 11:30 pm

hi
I' don't really know this, but maybe you could try step by step, add 1 device at a time, then save and restart.

Also you can try a different asio source.
(don't know why, but got a feeeling some is more stable

)

Or do as me, never turn off the PC
(because it is capable doing it by it self occasionaly)
....you know the blue ....

[ This Message was edited by: arela on 2005-09-10 00:41 ]

Cochise · Post by **Cochise** » Sat Sep 10, 2005 3:54 am

Hey Arela

The blue knows me

What's that story about your machine always set on ?

arela · Post by **arela** » Sat Sep 10, 2005 8:32 am

maybee it's a bad habbit, but i don't turn off my pc('s).
Just the displays and speakers.
But I do a restart every 2 - 4 week
(depends on how much work is done, clear cache and ram)

This pc, my surfing pc, has been working for 5 years these days.
No hardware issues yet, knock on wood.

Cochise · Post by **Cochise** » Sat Sep 10, 2005 12:34 pm

Hi stardust.
At present I can load everything but sfp.pro.

I could post cset.ini...

I went to take screenshots of the error message, but the software I used in these years won't work in dual desktop environment...

Cochise · Post by **Cochise** » Sat Sep 10, 2005 1:04 pm

OK, I've googled a shareware utility working in dual desktop (too busy disabling 2nd monitor and then reconfigure for that old CRT; I've not yet learnt to store settings).

I get this

In cset.ini I can see some paths using as separator and others using /
i.e. c:...... or c:/.../...

Paths usually have backslash...

[ This Message was edited by: Cochise on 2005-09-10 14:32 ]

arela · Post by **arela** » Sat Sep 10, 2005 1:41 pm

Is there another way of doing this.

As i recall (sorry, dust on my pick-up), just make your project and name it eg newstart.pro (at c:SFP4Projects*

Now, copy this file and rename the copy sfp.pro (or is it startproject.pro ??)
Exchange this file with the original one
(but save this one please

)

There should be some tips on this, because i had a "handmade" startup project some 2 years ago.

I found a safer way:

http://www.planetz.com/forums/viewtopic ... 69&forum=1

good luck

Cochise · Post by **Cochise** » Sun Sep 11, 2005 12:50 pm

Hey arela, very kind of you, but I've already set my startup and default projets.

Here anything seems to be out of order after a system restore and I wish to solve it before starting to work with music.
It should annoy me having problems while I'll be working around a project.

Cochise · Post by **Cochise** » Sun Sep 11, 2005 1:01 pm

Right, maybe I has to write the exeption window content as header of this topic

Cochise · Post by **Cochise** » Wed Sep 14, 2005 2:48 am

GURUS!

help please.

Cochise · Post by **Cochise** » Thu Sep 15, 2005 8:24 am

Sorry, I've 2 unanswered questions:

- Can everyone here load sfp.pro without error message?

- Does everyone else have slashes and backslashes in the cset.ini (is it a compression/decompression bug after restoring from a partition image)?

symbiote · Post by **symbiote** » Thu Sep 15, 2005 8:54 am

Can't check about SFP.pro as I'm not home, but I also have slashes and backslashes in cset.ini and it works fine, it's always been like that and always worked pretty well.

Cochise · Post by **Cochise** » Thu Sep 15, 2005 12:56 pm

Thank you.

I'm pretty sure I didn't have that problem before restoring..

symbiote · Post by **symbiote** » Thu Sep 15, 2005 9:53 pm

I've just tried loading that SFP.pro project you mention, and I get the same error (SetDynParent etc then SFP freezes.) I don't think that's the original default project like you seem to think.

If you want to restore the original project, you have a few options. First you can just load any project, delete all modules, and rebuild it. Second, you can try re-installing SFP. Third, and before you try re-installing everything (I should have put this at second but I'm lazy and drunk right now) is deleting the NewProject.pro and StartProject.pro projects (and the .0 .1 .2 etc backups -- make sure you back them up somewhere first) and let SFP rebuild them from scratch. I know the SDK works like this, so it's worth a try.

If you are forced to re-install, make sure you do a full backup of your SFP dir right after the installation. That way you can easily get back any file that might have gotten corrupted/lost/abducted by aliens.

Cochise · Post by **Cochise** » Fri Sep 16, 2005 1:55 pm

Thank you very much, Symbiote.

I've no need to really restore the original default/startup project, but I look at that error like at a symptom of something going wrong in my installation.

Right now I'm trying to build a modular III patch including a multisegment env bipolar feeding LPF and gated by a gate SEQ and it won't work. If I gate the ENV module by the MVC, it work. If feed the LPF with another ENV (I tried the AD vintage) it's possible to gate it by the SEQ.

About the SFP.pro, I'm pretty sure I was able to load it last month, when I wrote another post about default/startup. ( http://www.planetz.com/forums/viewtopic ... 84&forum=1 )

What is therefore the use of that SFP.pro?

symbiote · Post by **symbiote** » Fri Sep 16, 2005 2:07 pm

Probably some lowlevel stuff, similar to the SFPStartUpLogo.pro or whatever it's called, used by SFP internally. I don't think you are supposed to be able to load it. Like I mentioned, the Startup and Default projects are StartProject.pro and NewProject.pro.

I'm pretty sure I tried loading SFP.pro in a previous installation and it failed also, so I really doubt your installation is broken.

Cochise · Post by **Cochise** » Fri Sep 16, 2005 2:35 pm

I've uninstalled Scope, deleted the Scope folder, cleaned XP registry by an utility.

Going to reinstall, the setup process propose me to install in the path I used for the previous installation: C:program filesScope, and not C:Scope as on a clean XP installation.

All things go the same.

[ This Message was edited by: Cochise on 2005-09-16 15:37 ]

Cochise · Post by **Cochise** » Sat Sep 17, 2005 6:33 am

Sure. I've got it.
Do I maybe loaded newproject.pro a month ago and confused it with SFP.pro?
I should swear I successfully loaded SFP.pro..

About Scope reinstallation:
I forgot to delete temp files in the temp folders. Setup programs leave there files and information.
But I'll do a search for the string c:program filesScope inside the registry and inside the files contained in the OS partition