Windows Vista Thread, Cubasis VST, Dance EJay and "non admin" rights - refusal to start...? in Technical; We're making alterations to our new network, tightening things up from the ground state of things we were left with.
Cubasis VST, Dance EJay and "non admin" rights - refusal to start...?
We're making alterations to our new network, tightening things up from the ground state of things we were left with.
One of these is that kids/staff were "admin rights enabled". Don't ask. We don't quite get it either.
However, now we're locking everything up tight. Everything on my test PC in the modified "non admin" OU with a new user seems to work fine (hurrah!), with the exception of Dance EJay 2005, and Cubasis VST.
Cubasis runs through the initial "startup splash" once, then vanishes. Subsequent startups give me an hourglass for a few seconds and that's it. No errors, no nothing.
EJay keeps prompting for admin user and password to run "reg_start.exe". If I decline, it dies.
OS on the workstations is Vista Business SP1 (fully updated), Servers are a mix of Win2k3R2 and Win2k8 x64, if it helps.
Any suggestions? EJay seems to have gone for a burden - the sites are down, and according to Wikipedia the company is in liquidation.
Failing that, any alternative suggestions for packages to do the same thing?
I got this from r-e-m for the "for schools" version
Dance eJay for Schools – Network Instructions to aid permissions issues
Install the program to a read-only drive on the server. Within
this "Dance eJay" folder there is an executable "Dance2005_start.exe"
which is what you would expect to run - but this causes the problem.
We have found that if, instead, Administrator runs "Dance2005.exe"
which is within the "eJay" subfolder of the "Dance eJay" folder, you
can then create a shortcut to this "Dance2005.exe" executable and users
can run this without problems on this workstation. For a network, you need to package this operation since running
"Dance2005.exe" as Administrator creates a variety of files in the
Windows and System folder which must be on the workstation for it to
work as a user.
the info was not in it's self very usefull (as i think WriteAccess.ini has to do with RM networks) but it prompted me to find a solution.
Basically I ran the network shortcut on the client machine as an admin which presumably adds files to the c:\ drive of the client machine. After this running over the network as a standard (non admin) user works fine.
No need to create a package - Install to a central location and create a WriteAccess.ini file with the following entries to apply to the workstations