Paul, thanks for pushing me to respond - I kinda lost the will to live with this.

Setup Testing:

A] Win7 Combat Mode ON = Invisible MEDIA MANAGER.

B] Win7 Combat Mode OFF = Visible MEDIA MANAGER.

Stability(?):

Only time will tell, with Combat Win7 OFF (I need it off, to see MM) and the Tablet and Drivers removed that this will give me stability.

I think I've had 2 Vectors/Variables affecting this: The use/need for "grunt" when having MM engaged and then the other being a Graphic Tablet issue. I can alter/remove each and get a false positive of stability when in actual fact the issues of MM and Tablet still remain, which in turn reflects on stability. Stability is about Vegas choking. Remove some of the choking and VP will work, but hobbled. It is the programming and fit of the devices (GraphTab) and functions (MM) that need to be compliant with VP - OR, here's a novel thought, VP to be compliant with the device AND its own function.

In any event, this is all very tedious. But thanks Paul for the "nudge" . . . I've been enjoying the londO-lympics and that stunning opening ceremony. Totally inspiring, typical British Bonkers and unashamedly stirringly creative in putting over our tiny Country to the World.

Grazie

Graham, if i was in your situation with MM going invisible etc.. I'd be slashing my wrists too! .. Never mind mate, its all part of following a logical procedure to nail the issue. But yes, it IS tedious! But with some luck, you may just get a result. Chin up and all that :)
So, recap:
Wycom is totally disabled and uninstalled.
MM display still gone with compat mode ON
MM display is ok with MM mode OFF.

So its a trial now of whether the removal of the tablet has cured instabilities!
Good luck with your testing - lets hope so.

Yes, watched the opening of the games last night also, amazing!!! Proud to be British while watching it. What a production. Much debate if Sir Mac was miming at the end - some bad sync problem at the start.. hmmm...

Paul.

Crashing with Media Manager, and Compat. OFF.

So, after ALL I've gone through, I'm back to establishing with you guys, that I am needing to go:

Compat. Mode ON = MediaMgr BLIND

This is exactly where I started from, but you all now know that the "playing field" is flat and level.

Apart from reverting to my own "fix" - leaving an instance VP10, so I can get at MM - I haven't got any further forward.

Cheers

Grazie

At least you have ruled out the Wycom as having any effect. That's actually progress, even if it doesn't feel like it.
Its a bad one Graham, out of options here. Back to good old Vegas bug thinking.
May as well reinstall your Tablet software unless anyone else has any ideas.

Paul.

So compatibility mode is curing more problems than what's caused by Wacom tablets. Or put another way, the Wacom tablet isn't the only problem.

I guess the primary goal here is to get Media Manager working and that requires that you get Vegas to run without compatibility mode. I was kind of hoping that the Wacom tablet was the only issue, but at least you have that eliminated.

Now, you say that Vegas is still crashing and you need compatibility mode. What are you doing when it crashes? Anything specific, or is it just withering under your glare?

(BTW, one of the forum users has posted about an inexpensive third party tablet that he uses without any trouble. Maybe that would at least let you use a tablet in "normal" mode if that ever gets working.)

Rob

BTW, one of the forum users has posted about an inexpensive third party tablet that he uses without any trouble.

Or, I could just reinstall my Medion Grafik Tablet & Driver.

Grazie

When you're running Vegas in compat mode, can you check to see if the .medialib file (which is, I believe, the SQL database for Media Manager) shows read-only status or read/write? I saw on a Microsoft SQL forum that some users could not access databases created in Win7 through Vista because the flags had changed to read-only when accessed with Vista. Perhaps it's possible this could happen between SP1 and Win 7 compat mode as well? Just a thought. I can't offer any checks on my system because I haven't installed Media Manager for several versions now.

Larry

A very good idea Larry, but have checked it here by setting the .medialib to ReadOnly.
When starting Vegas you get a dialog box saying Default Media Library cannot be opened, then you click ok and MM is disabled in Vegas but you do see the controls in the window for MM just with no info.
So i think if this was Grahams problem, he too would be seeing an error message.

As soon as the attribute was returned to read/write, all was fine again.
Still worth checking though.

Paul.

Well, Larry, there IS a difference. The first piccie shows MM behind my interrogation of the MM Default file, and you can SEE MM filling its pane.

Compat OFF:-




Compat ON:-



Here it is saying "READ only". Is that the same as "seen" only? Who knows?

Larry, could we be onto something? And again, this is not affecting the use of VP10. Is this a particular VP11 issue? - Can't be that as others have reported success WITH and WITHOUT Compat ON or OFF.

But yes, most certainly, the Compat mode suggests a manipulation of the underlying security set by M$.

What now?

Cheers

Grazie

Well, I don't know whether I've done the right or wrong thing, but . . . . having read READ only I went ahead and unchecked as Administrator, and the WHOLE of Vegas appears to be on STEROIDS! I'm serious . . . The Splash Screen on Building the Video Factory thingies didn't get time to breath and it was up and gone; it flashed through ALL the other initialization screens and the GUI was up and there before I knew it!?!?

However . . . . Compat mode still makes MM Blind.

UGHHH....... However, I've got a feeling that I may not now NEED compatability mode as Vegas is blindingly fast.

Could it be that those files I've now let loose, it did go away and rummage through ALL my system and stuff now making available for view, has made my system more open and responsive?

Now this is very interesting.

Even my Keyboard as I type this is keeping up the pace of my typing . . . and THAT's been a long time coming.

Something HAS changed . . Larry thanks for maybe breaking a log jam I've been having.

Grazie

Well, not wanting to endanger your library file that's working, perhaps renaming the file to something that relates to compat OFF, creating a new copy that you give the original name to, and unchecking "read-only" on the attributes and see if it works in compatibility mode? I'd hate to suggest anything that would compromise your ability to use it in compat off, but maybe it's worth a try.

Other than that, (and I only have limited skills at SQL and don't know the way it's implemented in Media Manager) using a command line interface or a SQL GUI to create a copy of the database contents into a new database while in compatibility mode may give you a file you can use. If I've helped determine a potential problem, great, but I know just enough to be dangerous. Perhaps some others can weigh in on better solutions than I can offer.

I'll keep an eye on this post and if I feel I can offer more help, I certainly will. Good luck.
Larry

Wow. Just saw your last post, Grazie. I'm going to read through carefully to make sure I understand, but this may be the first time in memory I've seen anyone refer to Vegas "being on steroids." That's seriously encouraging. Hope this is a lasting breakthrough.

Larry

Lazzie, for the past 10 minutes I've been HAMMERING Vegas and is some box of tools!

No really, it would appear the files that Vegas needed - and it would seem some OTHER parts of my PC - were blind to its own operation.

What could I have done?

Why didn't I get to know about this before?

Too excited.

Grazie

From the two images you posted, i see these are from different locations, and their properties are different for a reason.
The first image shows your database FILE properties, and the 2nd image is the FOLDER properties.
Now these are different, because they themselves are different objects.
The one to check is the actual database file, not folder.

Put another way, the folder may be write protected, whereas the actual file inside may be read/write enabled.

Graham, even though for some unexplained reason you are experiencing faster operations, i do think you would be seeing the error splash (as i do) if this was indeed the problem, i can reproduce the read only scenario here and i get the error dialog, whereas you do not. Something else is going on.

Paul .

When your excitement subsides, please start a new thread that lists everything you've done in detail. I've been fairly successful at keeping V11 running, but I'd love to see some steroid action here. My work habits have slowed down greatly because V11 seems happiest when you give... it ...time. Like to get back to old habits.

Larry

From the two images you posted, i see these are from different locations, and their properties are different for a reason.

Paul, which would be what? And yes, I see the different locations too. However the Library files are the same in each folder.

Anyway, when I rengaged Compat, the Read only gets pinged back on.

G

Your top image (FILE) should show as Read Only = unticked. (it can be written to)

Second image (FOLDER) can be either depending on what the operating system is trying to do. Mine is currently set to Read Only = ticked. [not really, see below]

Paul.