Page 1 of 1

Botched Razor Update: Possible Solutions Here

Posted: Mon Oct 11, 2010 6:31 pm
by BlaZe
Since so many people here seem to have issues with the latest Razor update (Win7 users are the main victims) I decided to see if there was anyone posting on the RunUO forums with the same problems. Sure enough, there are plenty - one thread looks like it shows some promise of fixes.

Here's a link to the thread and here is an excerpt:
Shino90 wrote:If any of your macros/profiles are gone after the update:

* Open "C:\Users\<username>\AppData\Local\VirtualStore\Program Files\Razor"
* Copy all files to "C:\Program Files\Razor"


If you're unable to create new macros or take screenshots, you can either run Razor with administrator privileges, or change the Razor folder owner to your user account as follows:

* Open "C:\Program Files\Razor", right-click anywhere in the folder and click "Properties".
* Click the Security tab.
* Click Advanced.
* Click the Owner tab.
* Click Edit.
* Select your user account in the "Change owner to:" box.
* Press Apply, then OK about 3 times to close all previous windows.


If "C:\Program Files\Razor" already has subfolders, you may have to do the same for those too.

Re: Botched Razor Update: Possible Solutions Here

Posted: Tue Oct 12, 2010 12:54 pm
by BlaZe
Bump.

Re: Botched Razor Update: Possible Solutions Here

Posted: Tue Oct 12, 2010 4:05 pm
by dillingham
Thank you BlaZe for posting this.I used this and it worked. :D

Re: Botched Razor Update: Possible Solutions Here

Posted: Tue Oct 19, 2010 11:26 pm
by BlaZe

Re: Botched Razor Update: Possible Solutions Here

Posted: Fri Oct 22, 2010 11:09 pm
by Rebond
Razor, thanks again! This time Razor would not let me set up a macro, you had the answer........thanks

Re: Botched Razor Update: Possible Solutions Here

Posted: Sat Oct 23, 2010 8:37 am
by Undertaker
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.UnauthorizedAccessException: Access to the path 'C:\Program Files\Razor\Macros\BandSelf.macro' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter.CreateFile(String path, Boolean append)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path)
at Assistant.Macros.Macro.Save()
at Assistant.Macros.Macro.Play()
at Assistant.Macros.MacroManager.Play(Macro m)
at Assistant.Macros.MacroManager.HotKeyPlay(Macro m)
at Assistant.Macros.MacroManager.HotKeyPlay(Object& state)
at Assistant.KeyData.Callback()
at Assistant.HotKey.OnMouse(Int32 button, Int32 wheel)
at Assistant.ClientCommunication.OnMessage(MainForm razor, UInt32 wParam, Int32 lParam)
at Assistant.MainForm.WndProc(Message& msg)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4206 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Razor
Assembly Version: 1.0.12.15
Win32 Version: 1.0.12.15
CodeBase: file:///C:/Program%20Files/Razor/Razor.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4205 (VistaSP2GDR.050727-4200)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Ultima
Assembly Version: 2.0.3.0
Win32 Version: 2.0.3.0
CodeBase: file:///C:/Program%20Files/Razor/Ultima.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


This is the detail message error after the 2nd time i start my macro.... i have NO idea hah....

Re: Botched Razor Update: Possible Solutions Here

Posted: Sat Oct 23, 2010 2:46 pm
by BlaZe
System.UnauthorizedAccessException: Access to the path 'C:\Program Files\Razor\Macros\BandSelf.macro' is denied.
From the looks of it, your User doesn't have the proper privileges. Have you tried the Ownership fix on both the Razor folder and all the subfolders inside it (including the Macros folder)?
If you're unable to create new macros or take screenshots, you can either run Razor with administrator privileges (by right-clicking on the Razor shortcut, Run As Administrator), or change the Razor folder owner to your user account as follows:

* Open "C:\Program Files\Razor", right-click anywhere in the folder and click "Properties".
* Click the Security tab.
* Click Advanced.
* Click the Owner tab.
* Click Edit.
* Select your user account in the "Change owner to:" box.
* Press Apply, then OK about 3 times to close all previous windows.


If "C:\Program Files\Razor" already has subfolders, you may have to do the same for those too.

Re: Botched Razor Update: Possible Solutions Here

Posted: Sat Oct 23, 2010 6:10 pm
by Undertaker
ok by right clicking on Razor (shortcut) "Run as Administrator" i can run all my razor macros, but ALL my uo macros (F1-F12, etc) are gone, as well as all my spells, skills, etc lay'd out on my screen... what else ya got up your sleeve, seems like i cant win both ways yet lol

and thanks blaze :)

Re: Botched Razor Update: Possible Solutions Here

Posted: Sat Oct 23, 2010 6:25 pm
by BlaZe
Again..
* Open "C:\Program Files\Razor", right-click anywhere in the folder and click "Properties".
* Click the Security tab.
* Click Advanced.
* Click the Owner tab.
* Click Edit.
* Select your user account in the "Change owner to:" box.
* Press Apply, then OK about 3 times to close all previous windows.


If "C:\Program Files\Razor" already has subfolders, you may have to do the same for those too.
If you've already tried this then I don't know what to tell ya.

Re: Botched Razor Update: Possible Solutions Here

Posted: Mon Oct 25, 2010 12:32 am
by Undertaker
... Yes, blaze... 3x .... Thx... Again...

Re: Botched Razor Update: Possible Solutions Here

Posted: Mon Nov 01, 2010 4:36 pm
by Highroller
I am having problems with frame network trying to bomb out. Not sure if its a connectuo problem or the frame network itself or even a razor problem. Any ideas?