Assertion failed

[endre70]

Hi!

A year have past since my last visit, hope everyone are doing well!

Got a issue with my luna z link a dest/source not loading, giving me assertion failed message and forces me to restart SC.

My system: SC5.1, win 7 - 64 bit, 2 boards (pulsar2, luna w/expansion), 2xa16 ultra. 32 channels going inn and out if my system - so i need all four zlink modules (2xpulsar + 2 luna),

The story so far: when updating the system a year ago I got the same problem loading the Luna z/link A module. The only way getting around the problem, was to use the old startup project from my old system disk.This made the modules loading as they should. This definately points away from hardware issues and towards software issues.

When trying to load some mixer modules recently I was forced to do a Scopeminstall (on top og the old one - excluding drivers) to sort out missing mixer modules (and then renaming startup project to make scope point out the right folder) . I backed up old projects and csi.ini.

When starting fresh, the same problem occures, failing to load z linkA module and scope stops working. I had to resolve to my old and trusted project, but managed to load mixers and other software modules after the reinstall mentioned.

If anyone got any logical pointers on how to solve this I would really like to know.

Thank you!

[garyb]

do you have a v4 folder and a v5.1 folder? if so, you need to remove or rename the older version's folder.

[endre70]

Hi garyb.

No V4 folder in system disk C. There is a V4 folder in another partition somewhere, on another physical disk. I will rename it just to be certain.

[garyb]

can you make a brand new project from scratch?

[endre70]

Yes. As long as I'm not loading luna z link module A source or destination. Pulsar A and B and Luna B loads as they should.

[endre70]

Im not alone.. http://forums.planetz.com/viewtopic.php ... on#p279368

[garyb]

as i told the other poster, it is probably not a software issue. there are no known bugs that would cause this. hardware failure or a bad firewire cable would cause it....

[endre70]

Thanks for your time again Garyb!

as i told the other poster, it is probably not a software issue. there are no known bugs that would cause this. hardware failure or a bad firewire cable would cause it....

But how come it loads when using the old startup project? A hardware issue is not logical..

[garyb]

then there's an issue in the file system....

[endre70]

Yes. There is that.. Could different scope systems, on different bootable systems mess it up? Does the scope projects contain data that refers to the scope location or is this handled by the sci.ini?

I will rename all other scope folders and try a fresh install when I'm in my studio again. I'll be back.. And thanks again!

[garyb]

yes, it could if both partitions are visable. the project file contains markers that point to the location, so....

[dante]

I have both Scope 5.1 PCI and Scope 5.1 XITE installed on C: (WinXP/32) with no issues, running them simultaneously.

EG when I start Scope XITE and load a Scope XITE project the load Scope PCI and load a Scope PCI project each finds its own paths/devices/cset.ini etc.

I save the two projects in the Cubase working directory - eg for the last song 'Millenium Girl' I will have one Scope project called 'Millenium Girl PCI.pro' and another called 'Millenium Girl XITE.pro'.

The only time I would get an issue using this system is if I load 'Millenuim Girl PCI.pro' into Scope XITE or load 'Millenium Girl XITE.pro' into Scope PCI.