PlanetZ forums - scopeusers.com

My setup has been rock solid until.... this morning.

Last night it was all good. But today, SCOPE starts up with the MS runtime MVC..Dll termination error. Blue Screen then reboots into CHKDSK. Thousands of errors. Recovery can't fix them either. Finally the dreaded MBR not found. I recovered it to bootable. SCOPE's still the same. I'm sure somehow the drive got all scrambled up. A 4 month old SSHD. I renamed the project files and got SCOPE to load. If I load them automatically - runtime error. Have to rename or make a bare "New Project.pro" to start it and then I can load my project again! But no problems when I boot from another drive so I'm sure it's the drive. Did all the diags on the drive with recovery and sfc scannow and stuff is beyond repair mainly in the Windows folders. Ouch! Tried to manually copy the system from the good image but still problems in Windows. Definitely disk corruption issues.

Looks like I'm gonna have to bite the bullet and re-format the drive and re-install 7.1 64 and everything else. At least I have a good back-up of SCOPE on a good drive so I can put that back on when I re-do it or maybe get a new one if need be. It's good that I have all my native stuff on another machine so I just might go lean on this one with SCOPE and only add just the bare sequencer and native VST necessities and go back and forthwith ADAT (as I do anyway). In the meanwhile I can still use SCOPE on the good drive without the native stuff. I copied my folders and reinstalled 5.1 on it in like 5 minutes and it fired right up - no errors. I guess that says a lot because re-installing the native stuff will probably take days if I put it all back.

It wasn't a virus. Was it an update? I did a "critical" update a couple of days ago and I strongly suspect that must have been it or else a flakey drive or the combination thereof.

bad drive...
does windows see a smaller volume now?

Actually not.

It's weird but I started to get the Runtime termination error on the good drive, but only when the project is loaded anywhere else but "open" project. Load recent gives the error as well as setting it as the default project. Maybe that's fixable as it's happening on another drive... unless part of SCOPE is corrupted even though I re-installed?

a project can become corrupted, but if it's a fresh install, the software itself is not likely the cause.
it's bot common, but it's also not unusual for a project to become corrupted, especially if there was a problem like you describe.

Hmm, how long have you had the drive for? They tend to die after a few years (mine always did in the past).

Now I only use SSDs, but they can also go bad (had one start failing SMART check but it was still working. Got it replaced).

-Tom

I did a thorough test on the drive and it comes up perfect! I'm sure that the problems had to do with a Windows update that went south, maybe the machine rebooted in the middle or something that caused the OS to get messed up. It's actually running now but parts of Windows are screwed up. I'm going to try an in-place repair from the Win 7 SP1 DVD to see if I can just refresh the OS and then if I have any program issues, re-install only those needed. Maybe I can avoid a complete format/re-install. I used the best disk checker there is, Spinrite 6. I know the developer, Steve Gibson, since the Apple/Commodore days. The guy is tops.

Hmm,

Then Winblows got corrupted somehow. Not impossible.

-Tom

no, not impossible.

probably even

actually, hubird, about as likely as OSX becoming corrupted.

Yes, it's true.

I had Linux get corrupted on me. Once on a PowerBook G4 and once on a Beaglebone. It can happen to any OS.

-Tom

Heh, heh. Windoze has been brain dead since its inception. Instead of using memory properly it practically forces programmers to be lazy dumb-asses and it has a pre-disposition to perform auto self lobotomies every now and again and be a daily virus and update magnet. Now how many copies of the same MS runtime(s) do I need again? Oh, and I thought it was that DLL (Dreadfully Loaded Lavatory) version. My bad.

garyb wrote:actually, hubird, about as likely as OSX becoming corrupted.

with the emphasis on 'about'

But I was able to corrupt it by myself...by a stupid action.
I wanted to make a ghost copy of the system with Carbon Copy cloner and by accident I choose a partition of the disk carrying the system which I thought was as a separate disk.
Distracted attention, late at night, people around, shouldn't have done it.
The process hang, and the OS didn't start up anymore.
Now that's stupid eh?

Sorry for hacking the thread Ronnie, hoop you sort it out soon with the guys around here

Well, that's a human error, hubrid

-Tom

hubird wrote: Sorry for hacking the thread Ronnie, hoop you sort it out soon with the guys around here

No problem! How the heck did you "hack" Royston? Ohhhh... I just saw you're answer in that thread. Nice research!

tlaskows wrote:Well, that's a human error, hubrid

-Tom

Quod erat demonstrandum...it wasn't OSX itself doing it

Hubrid was a typo?
No problem, but it's hubird, pronounced as about hubert

Yeah, sorry. I'm not very good with nicknames lol

-Tom

it's always human error...

garyb wrote:it's always human error...

.... assuming Bill Gates is, uh, human?

I think something called MegaHard© would have more appeal than Microsoft© and function much more reliably.

garyb wrote:it's always human error...

you mean like the climate change?