What does "init rewrite locked" mean?
Built a new computer around Windows 7 Pro 64 and now I can't edit (make any changes at all - not even move modules around) any of my patches in any of the recent RCs. I constantly get this "init rewrite locked" message in the console. I can't even quit HH (I need to shut it down from Task Manager). Everything seems fine on my other computers (W8.1 and W7 Pro 64).
Help!
Help!
Regards,
Scott
Scott
maybe have tried to run as admin? looks like some autorosiations errors. or hold shift and type PROTECT to disable/reenable , maybe was trigged by error if ya can't edit anything looks possible.
You can also check where you have install Usine, for example try an external disk or a second partition, avoid your C: partition or the desktop
Thanks for your replies. I am running hh as an administrator and from the same volume and folder (precisely) as on 3 other computers which don't have this problem. This is something I've never seen before. Perhaps Olivier can shed some light on this warning message.
Regards,
Scott
Scott
I've asked Olivier precisely and he point on this C; and system partition.
Have you try to move the folder to help the diagnostic?
Have you try to move the folder to help the diagnostic?
Thanks Nay. Unfortunately I have only one hard drive on my computer. Would you like me to move it to another folder on the same drive? Maybe I can find a USB key to run it from for troubleshooting. The current folder is in c:UserssleporesterdownloadsDropboxhh_beta in case that helps. The problem occurs regardless of whether Dropbox is running, or not.
Regards,
Scott
Scott
ok,
can you try to move the folder out of the dropbox, for example in the download folder ?
you can also try a fresh unzip version ( don't import your settings first) in this same download folder to check if you have the same issue
can you try to move the folder out of the dropbox, for example in the download folder ?
you can also try a fresh unzip version ( don't import your settings first) in this same download folder to check if you have the same issue
I'll give it a try in a few minutes and let you know what happens.
Regards,
Scott
Scott
That looks like an Apache message... Are you running an Apache server?
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
should just try creating a C:HH folder and placing your patches in this at the moment.
Then you can verify if it's a permission problem with Windows 7.
-S
Then you can verify if it's a permission problem with Windows 7.
-S
"Every act of creation is first an act of destruction." -Picasso
Ok. Looks like moving the app folder out of the DB folder did the trick.I can now edit patches and exit hh. Reverting to 71b seems to have resolved the other weirdnesses in my patches.
What stumps me is why hh is working fine from the same DB folder on my other 3 systems. I checked permission on the folder and I have full permissions and I am also the owner. I have had file contention issues of workspaces and patches stored in DB, but never an issue with hh.
Thanks for everyone's input. Long live the community!
What stumps me is why hh is working fine from the same DB folder on my other 3 systems. I checked permission on the folder and I have full permissions and I am also the owner. I have had file contention issues of workspaces and patches stored in DB, but never an issue with hh.
Thanks for everyone's input. Long live the community!
Regards,
Scott
Scott
Who is online
Users browsing this forum: No registered users and 20 guests
