mixing routing projects corupted when saved

Realtime · Post by **Realtime** » Mon Jan 15, 2007 3:50 am

and won't re open.

Everything was working beautiful and then a crash, and we can't get the projects to open up again.

Realtime · Post by **Realtime** » Mon Jan 15, 2007 4:11 am

here is part of the error report enclosed as a text file.

Not sure if this means or says anything important

We have tried everything, on planetz.

We are running a pulsar 2, and a scope srb on a pentium 4 2.8 prescott, we checked irq and there where no conflicts, we moved the cards around we uninstalled and reinstalled scope, we made sure the srb was the primary card, and tried multiples savings under different names and folders, and they all projects that are saved open with the error rport above.
we disabled all unecessary hardware, moved the cards around,

Post by **irrelevance** » Mon Jan 15, 2007 5:28 am

Are you able to open any other saved projects? If not, what about projects saved before the crash?

Realtime · Post by **Realtime** » Mon Jan 15, 2007 12:28 pm

only the example presets that come w/ the card will load. we'll use one of those to start building our project window and save it to see if it gets strange. when we try and open the newly saved project, it starts loading then immediatelly shuts off. when you click on 4.5 again and then try and open that same project, you get the error message. some of the changes we made to the original presets before we save as a new name are very mundane(ie. we just unplugged a asio channel from a mixer) so it can't be us loading something in a way that scope doesn't like.

Post by **irrelevance** » Mon Jan 15, 2007 3:22 pm

Does the I/O in the example projects correspond to the 1st card? I'm not so sure that the srb should be your set as the 1st card as it doesn't have any I/O of it's own.

valis · Post by **valis** » Tue Jan 16, 2007 4:21 am

The srb wasn't initially master (I had him add the numboards etc info to make his large card master) but he's trying to find out why projects are saving corrupt. To me it basically looks like the process of writing to disk is corrupting & I haven't had a chance to vnc into his box to check it out so I asked him to post up here hoping someone might have an idea.

Post by **garyb** » Tue Jan 16, 2007 1:09 pm

sounds like your computer itself has issues if this is the same machine that took all night to install scope, a process that should only take a few minutes....