PlanetZ forums - scopeusers.com

The really sad thing is, it's fucking true!



Anyway, after a cursory glance, the lines you mention appear to all relate to XTC mode... which I disabled during setup! Should I not have done that? Is there anything there that doesn't relate to XTC, and that I should definitely add given that I don't use XTC mode?

Cheers!

Chris

Never mind the XTC stuff, your cset.ini file should definately have the [Host] & [Host-Config] entries.

Okie dokie!

Is there anywhere in particular, then, that I should paste the following?

[Host]
Scoperev=128

[Host-Config]
Numboards=1
Board0=Host


Is CSET.ini sensitive to line breaks and such?

Cheers,

Chris

Just paste it at the bottom, but you may need different value entries, since I've pasted that from this system which has 2 cards, not 1.

Curiouser and curiouser... I can't find those lines anywhere in the cset.ini file that relates to my internet installation! That said, the project on my internet install is pretty basic (Wave -> Channel Strip -> Analogue Dest).

I'll give it a try though, hopefully I'll be able to ammend your lines to suit,

Many thanks again, t'is appreciated muchly.

Cheers,

Chris

mmm....

Well, on the bright side... at least we're working thru some things that will hopefully lead to fixing the issue eventually..

Try to add:
[board0]
boardid=0
rest looks good.
add that under host

At this point I would completely remove the Scope installation including registry (after making a backup) and do a fresh install. Doesn't take that long.


/dave

yeah, weird problem with no obvious solution? reinstall and save time and trouble.

if the computer is set up properly, it should be stable and run properly, assuming no hardware issues. there are so many hundreds of thousands of lines of code involved and it only takes one character to become corrupted and then.....

Ah, good point Gary... re - corruption.

Chris, don't know what you're installing from, but if it's a downloaded installer, download it again!!!

Mark

Definitely dont mess about with the BIOS if one windows is working fine. its a windows problem.

Check that you have the same drivers for all your chipset stuff,
you could have got a windows update or something that fixed a problem with a low level driver.
I had good luck with SP3 some people with non intel chipsets had problems though.


I am kind of lazy what i would do is ghost the one that works. uninstall all the games and other crap from it and use it for my DAW

All good suggestions!

The graphics card driver is something I haven't thought of - it seems unlikely to me that it would cause such a problem, but that's definitely something that differs between the two installs.

Thanks for all the help guys, I'll keep you posted!

Cheers,

Chris

Hello all!

Still not fixed but I've found a glimmer of hope...

On your advice, I uninstalled Scope (which was originally installed from the CD that came with the card), removed the SFP entry in the registry, uninstalled the card drivers in the device manager, and decided to install Scope again, but this time using the SFP 4.5 zip which I downloaded from the SC FTP.

It kept crashing again, in exactly the same way. So...

I renamed the folder 'to Scope1', just so that the shortcuts wouldn't know where to point to, and copied the entire Scope folder from my internet install (which, as I explained appears to be working fine). And guess what? It didn't crash!

However...

It was behaving rather oddly. For example, none of the menus seemed to be working - the one that says 'Show' or 'Exit Scope Platform' wouldn't let me click on it, and if I right-clicked in the Live bar to add a device, the menu didn't expand. Now, my best guess as to why this happened is that, since I copied the Scope folder from another location, all the drive lettering is wrong, so it doesn't know where any of the devices are.

This, I believe, leaves me with two options:

1) Only copy part of the working Scope installation into the old one (which I named 'Scope1'), though I wouldn't know which bits to copy and which ones not to (if this is the best idea, I'd like to know please!) Or...

2) Keep it all exactly as it is, do a search in the Scope folder for all files containing the text 'H:', and replace it with 'D:' (the root drive of this new install).

Any ideas?

Cheers!

Chris

Chris, try just swapping the cset.ini files back. IE go get the one which will have the correct path entries in it.

Mark

Awesome - I'll try it right away (I'm guessing that's the only file with all the file path names and that in it?)

Cheers!

Chris

It's the main one to get sorted because with the wrong path entries in the cset.ini Scope will definitely be screwed up.

Mark

Well, I don't want to tempt fate, but it seems to be a lot happier...

I tried just swapping the cset.ini files over, but that caused identical lock-ups to before. Just to check, I replaced it with the other one, and it didn't crash, but those anomalies with the menus kept happening. So, I did a find and replace for H: and replaced all instances with D: and all the devices are there, the menus are fine it hasn't crashed so far...

I can only guess that for some reason, the cset.ini file keeps getting corrupt - possibly something to do with my computer, because the same happened whether i installed from the CD, or from the downloadable zip file, and that through some kind of fluke, the install on my internet-enabled Windows boot worked just fine.

Well, I'm off to put it through its paces... It's a right fucking nuisance though, all of this, because (provided the crashes stop - touch wood), there'll be a while yet where every click I do is tainted with the fear that it locks up again! Not good for creativity...

Thank you all for your most helpful help! If you don't see me here for a few hours, you'll know it's working.

Safe!

Chris

Glad you get it going.

I guess you probably don't want to mess around with it now that it's working, but FWIW it could have been as simple as a messed up value in that cset file. I noticed for example that in the [SFP] section you had an entry 'SFPBar_TopLevel=100000' which I think was odd. Should have been more like 'SFPBar_TopLevel=3000' I think. If it wasn't that, then there definitely must have been something else wrong with the cset.ini file. ...mmm, that's kinda stating the obvious now.

Mark

It appears to be working perfectly!

This makes me very happy indeed - once again, thanks for the help. I think I'll try and keep that cset file somewhere handy in case this ever happens again.

Cheers!

Chris