Discussion in   Tutorials   started     11 years ago   July 23, 2013, 08:13:38 PM   by   Haephestus

Fixing RAZOR Issues in Windows

Haephestus
Offline
1 Posts
Topic :   Fixing RAZOR Issues in Windows
11 years ago  July 23, 2013, 08:13:38 PM

     For the past few days, I'm seeing some people having trouble using Razor to connect to UOEvo. They're getting several error messages and sometimes Razor won't load up at all. This is due to the fact that Razor has stopped being supported when Windows Vista was released.
     Since Windows Vista got developed, the Windows system changed some of its registry entries paths, basically that change has to do with addressing 32 and/or 64 bits applications and their functions.
     The main problem with Razor is that its installation doesn't add the necessary registry entries to the system, making it not to work properly or just entirely crash. After some research and tests I've come with a fix that will ultimately overcome any trouble you might have when chosing Razor as your game assist.
     What you have to do is fairly simple, but may require some basic system knowledge. I'll break this tutorial into steps and try to make it as clear as possible, so everyone can follow it with little effort.

  • STEP #1 - Opening your Notepad as administrator:
Click the "Start" button and find your Notepad application. By default it's under: "All Programs > Accessories > Notepad". Click its icon with the right button of your mouse and chose "Run as administrator". If a message asking for permission pops up, click "Yes".

  • STEP #2 - Copying and pasting the core registry code into your Notepad:
Now you will have to insert the core registry code I'm providing you into your Notepad. For that, just copy (ctrl+c) the whole code and paste (ctrl+v) it into your Notepad application as it follows below:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Origin Worlds Online]
"HarvestStageNew"=dword:00000000
"UniqueInstanceId"=dword:484b15f1
"LastHarvestTime"=dword:484bf8d8

[HKEY_LOCAL_MACHINE\SOFTWARE\Origin Worlds Online\Ultima Online]

[HKEY_LOCAL_MACHINE\SOFTWARE\Origin Worlds Online\Ultima Online\1.0]
"ExePath"="...\\client.exe"
"InstCDPath"="...\\UOEvolution"
"PatchExePath"="...\\uopatch.exe"
"StartExePath"="...\\uo.exe"
"Upgraded"="Yes"

[HKEY_LOCAL_MACHINE\SOFTWARE\Origin Worlds Online\Ultima Online Third Dawn]

[HKEY_LOCAL_MACHINE\SOFTWARE\Origin Worlds Online\Ultima Online Third Dawn\1.0]
"ExePath"="...\\uotd.exe"
"InstCDPath"="...\\UOEvolution"
"PatchExePath"="...\\uopatch.exe"
"StartExePath"="...\\uo.exe"
"Upgraded"="Yes"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Origin Worlds Online]
"HarvestStageNew"=dword:00000000
"UniqueInstanceId"=dword:484b15f1
"LastHarvestTime"=dword:484bf8d8

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Origin Worlds Online\Ultima Online]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Origin Worlds Online\Ultima Online\1.0]
"ExePath"="...\\client.exe"
"InstCDPath"="...\\UOEvolution"
"PatchExePath"="...\\uopatch.exe"
"StartExePath"="...\\uo.exe"
"Upgraded"="Yes"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Origin Worlds Online\Ultima Online Third Dawn]

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Origin Worlds Online\Ultima Online Third Dawn\1.0]
"ExePath"="...\\uotd.exe"
"InstCDPath"="...\\UOEvolution"
"PatchExePath"="...\\uopatch.exe"
"StartExePath"="...\\uo.exe"
"Upgraded"="Yes"

  • STEP #3 - Editing the core registry code to meet your client installation settings:
Now that you have the basic code copied to your Notepad, you will need to edit some lines so they point to the path where you've installed your game client. Into your Notepad locate every line starting with "ExePath", "InstCDPath", "PatchExePath" and "StartExePath" then change the suspension points (...) to whatever path you have your game client installed. Make sure you use double backslashes (\\) when separating folder names and leave everything else as it is.
     Example: "ExePath"="...\\client.exe" becomes "ExePath"="C:\\games\\UOEvo\\client.exe"
     Example: "InstCDPath"="...\\UOEvolution" becomes "InstCDPath"="D:\\user\\johndoe\\UOEvolution"

  • STEP #4 - Saving your file and changing its extension:
After editing all the necessary info in your registry code, save it with whatever name you want. Locate the file and you will notice it has a .txt extension. What you want to do is rename that .txt extension to a .reg one; for that just rename the file as you normally would. A warning message will appear saying that action might corrupt the file, just click "OK" and the icon should change.

  • STEP #5 - Applying the newly set code to Window's registry tree:
Here, all you have to do is double click your newly created .reg file. A couple permissions and/or warnings messages might come up, but you can safely click "OK" and "Yes" every time. A message saying the code was succesfully added to the registry should come up in the end.

  • STEP #6 - Changing the compatibility mode of your Razor application:
Now that you have your registry updated with the proper code, you might want to change Razor's compatibility mode so it'll run clear of any other possible glitches, like having a "blinking" window or temporary freezes. For that click the "Start" button and find Razor, by default it's under: "All Programs > Razor > Razor". Click the icon with the right button of your mouse and choose "Properties". Inside the window that opened, click the "Compatibility" tab and check the box that says "Run this application in compatibility mode"; in the drop-down box choose "Windows XP (Service Pack 3)". Click "Apply" and then "OK".

     Now you should have a sound and safe working Razor with no more issues of any kind. I hope I've made all the procedures clear enough for everyone and that this tutorial serves you good.
     If you have any doubts or questions regarding this matter, let me know either by replying to this post or sending me a PM in-game. Suggestions and/or corrections are also welcome.

Have fun!  :D

Haephestus

Kali
Offline
11 Posts
#1 Re :   Fixing RAZOR Issues in Windows
11 years ago  July 23, 2013, 11:25:40 PM

Awesome information!  Thanks for posting this.

*pretends to understand what she read*

DarkSilence
Offline
189 Posts
#2 Re :   Fixing RAZOR Issues in Windows
11 years ago  July 24, 2013, 07:44:58 AM

Nice post +1 Karma for you good work.

Kyn
Offline
336 Posts
#3 Re :   Fixing RAZOR Issues in Windows
11 years ago  July 24, 2013, 08:17:22 AM

Registry edits may be a bit complicated for some people. However I do approve that this is a correct fix and will not cause any harm to your registry pending you do this correctly.


As I always say, trial and error is not something you want to be doing with your registry. If you don't know. Don't do it and simply ask for staff assistance.


Also, since we do not officially support razor (due to the severe lack of updates/patches) we recommend that if your razor is not working, it may be a good time to switch over to UO Steam


www.uosteam.com
www.uorazor.com

Crawford
Offline
43 Posts
#4 Re :   Fixing RAZOR Issues in Windows
11 years ago  July 24, 2013, 09:10:40 PM

Hmmm,


         If razor is not supported then perhaps it should be removed from the wiki and the download links. That is where I got it from to use with this shard.
We use AssistUO and Razor also, but Razor is a 3rd party client program and does not have support from the company.  They dont seem to update or fix errors.  We support it the best we can, it does have flaws from way back.  It still works, but players are moving over to the newer AssistUO with support.


http://www.uorazor.com/
http://www.uorazor.com/documentation/

http://www.uosteam.com/
http://www.uosteam.com/uo-steam-faq/
http://www.uosteam.com/uo-steam-guide/

Kyn
Offline
336 Posts
#5 Re :   Fixing RAZOR Issues in Windows
11 years ago  July 24, 2013, 10:20:28 PM

Hmmm,


         If razor is not supported then perhaps it should be removed from the wiki and the download links. That is where I got it from to use with this shard.


http://uoevolution.com/?page_id=2


It is noted that we don't officially support razor anymore, but it is something players can still use.