Jump to content

Recommended Posts

Posted

We have Cubase 7 artist running on a Windows network. We have come across a problem that if a user logs off without closing Cubase first, another user will log on and Cubase will then crash when trying to run it until the PC has been rebooted.

Its as if there is still a Cubase service still running in the background for the previous user that's stopping the new logged on user from accessing it.

Any ideas for a fix or a work around? Making sure pupils close Cubase before logging off is easier said than done.

 

Thanks

Posted

Cubase stores data in the my settings folder which on our system is on the network.

Cubase doesn't support this, and causes all sorts of problems (very slow closing of cubase, and file corruption)

This may be related to the issue you have.

To overcome it, on our stations with cubase we have a program that writes to the user registry hive (HKCU), to change the re-direction to a specified directory on the local machine.

This means that all of cubase's disc access is on the local disc.

This means that when a user logs out, cubase can write it's data out before it shuts down.

Posted

Unfortunatly, it's a custom program I wrote for our school. It is very tailored to this particular school.

It replaces explorer.exe so that it runs at login, before the user hive is read, and changes a bunch of things that we dont do via GPO, before calling explorer.exe.

 

You could probably do it with GPO preferences with tagging to identify users logging into machines with cubase, and change the redirection just to those.

  • 4 weeks later...
Posted

HKCU#\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders#AppData =

HKCU#\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders#AppData =

HKCU#\Volatile Environment#AppData =

Point these keys at a local drive/folder (I create a folder for the user based on username)

 

To prevent GPO refresh (by default 90 minutes on our system) from overwriting these set this key...

 

HKLM#SOFTWARE\Policies\Microsoft\Windows\Group Policy\{35378EAC-683F-11D2-A89A-00C04FBBCFA2}#NoBackgroundPolicy = 0x00000001 as a DWORD

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...