Yeah, I don't see anything called "regedit " on my start menuregedit on ur start menu if ure using win7
Yeah, I don't see anything called "regedit " on my start menuregedit on ur start menu if ure using win7
To be seeing those, you'd be in the registry folder:You'll find a key called "ExePath" that contains, by default, "C:\Program Files (x86)\Electronic Arts\Ultima Online Stygian Abyss Classic\client.exe"
Can't locate this..
All i see is
dEFAULT, GAME EXEUCTION, install DIR
Let it do that, then go back into the registry and add the space asterisk 32 after the client.exe name.I've tried your instructions S.P.A. and when I try to load assist it just says UO information missing, then asks me to find it. When I show it the UO directory it overwrites my registry changes! Any tips?
This also works for Windows Vista 64I just changed the uopatch.exe to client.exe in the registry. This will bypass the annoying patcher and launch uoassist just fine for Win 7 64. See pic.
View attachment 8566
Flutter,This also works for Windows Vista 64
Every time I try to load up UOA it comes up with that dialogue and overwrites the registry changes. I've tried doing it every which way but UOA just insists on changing the registry back.Let it do that, then go back into the registry and add the space asterisk 32 after the client.exe name.
Just change the patchexepath line from "UOPatch.exe" to "client.exe"Every time I try to load up UOA it comes up with that dialogue and overwrites the registry changes. I've tried doing it every which way but UOA just insists on changing the registry back.
Folks,
Here is the latest skinny on fixing problems.
64-Bit Windows
If you are on a 64-bit Windows operating system, you will still have problems, and I have solutions for you
The problem is process names. Tug's emergency fixes are watching for process names like "client.exe" and that's all fine and dandy in 32-bits, but of course on our newer 64-bit systems the process names are "client.exe *32".
So... the temporary soution is as follows:
Open your Registry Editor. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Origin Worlds Online\Ultima Online\1.0
You'll find a key called "ExePath" that contains, by default, "C:\Program Files (x86)\Electronic Arts\Ultima Online Stygian Abyss Classic\client.exe"
You have to tweak this a little to add a space and an asterisk and 32 at the end, so it reads:
"C:\Program Files (x86)\Electronic Arts\Ultima Online Stygian Abyss Classic\client.exe *32"
Whatever is in there on your machine, however you have configured your installation folder of UO, just put space asterisk 32 at the end and you'll be in business.
Once you've done that, make sure you set the UOAssist load method to "Load UOAssist Using: Method One (old - updated)" as Tug instructed here.
And then it works. I've tested it.
32-Bit Windows
If you are on a 32-bit Windows operating system, you should no longer be having problems if you:
- On Windows 7 and Windows Vista
- Ensure you are running UOAssist as an Administrator
- Follow Tug's instructions here.
I had tried that before - but for some reason it actually worked this time. Thanks!Just change the patchexepath line from "UOPatch.exe" to "client.exe"
If the patch screen still comes up after registry hacking the uopatch.exe to uotd.exe then you're hacking in the wrong placei tired these and its still not bringing up the UOA screen just the patch screen... running windows 7 64 bit... also changed the one to UOtd.exe and still isnt working..doing the same thing.. no UOA just the patch screen.
Why would you never want to see the patch screen again?If the patch screen still comes up after registry hacking the uopatch.exe to uotd.exe then you're hacking in the wrong place
As soon as you make that change, whether it be changing UOPatch.exe to Client.exe or UOtd.exe, you won't ever see the patch screen again.
If the patch screen still comes up after registry hacking the uopatch.exe to uotd.exe then you're hacking in the wrong place
As soon as you make that change, whether it be changing UOPatch.exe to Client.exe or UOtd.exe, you won't ever see the patch screen again.
Thanks for the screen shot. Made the changes and it worked on my machine running Windows 7 64 bit. Only problem is that none of my Assist macro are there, but at least I have Assist now.I just changed the uopatch.exe to client.exe in the registry. This will bypass the annoying patcher and launch uoassist just fine for Win 7 64. See pic.
View attachment 8566
I prefer to not see the patcher every time I load UO. I will of course patch the client when updates are pushed out.Why would you never want to see the patch screen again?
With UO Assist's fix, what happens is that the patch screen comes up, so UO can patch normally, then UO Assist and the UO 2d play screen come up after you've clicked "play" in the patcher.
-Galen's player
There is no reason to see the patch screen unless you are patching anyway. At least, none that I know of. It's evident that Bleak has been watching the forums and hasn't said anything to the contrary, so for the time being (ie: until a better "fix" is given to us) this work around works.I prefer to not see the patcher every time I load UO. I will of course patch the client when updates are pushed out.
All thanks should go to SPA, it was his original fix that got me to thinking that using the client.exe would work until uoassist is fixed. When tugsoft fixes uoassist I recommend everyone change the registry back as it will probably try to launch the client twice.
I don't mean to be a party pooper but if someone doesn't know what a registry editor is I feel kind of obligated to suggest maybe don't mess with the registry lol...or if you do, make sure you write down what you had there, and what you changed, in case UOA puts in a fix.What's a registry editor and how do I open it?
I understand completely. Frankly, I am glad I got a response to my question/comment. This has obviously become too complicated for me. I will check back in a few days to see if it's sorted.I don't mean to be a party pooper but if someone doesn't know what a registry editor is I feel kind of obligated to suggest maybe don't mess with the registry lol...or if you do, make sure you write down what you had there, and what you changed, in case UOA puts in a fix.
Windows Vista 32 bit here. Had to manually drop UOA files into directory because my patcher splash wasn't loading post-UO patch changes. Dropped the new UOA files, everything works. Haven't tried on my XP 32 or Windows 7 64.so far ive spoken with 3 people with this issue, they all seem to be running Windows XP, could this be a WinXP exclusive issue?
cause i got no issues on win7...
It's really not that difficult, but messing with the registry can be dangerous. If you make a mistake and delete something windows requires you'll be looking a formatting your computer. There are ways to backup your registry. The best bet is to google registry for whatever operating system you are using. You'll learn a lot more than what you would here.I understand completely. Frankly, I am glad I got a response to my question/comment. This has obviously become too complicated for me. I will check back in a few days to see if it's sorted.
If you made this above change to get UOA working for the day...you have to change it back with the new UOA patch.Using a variation of S.P.A. registry fix can get UOA working again today.
Follow all those steps but instead of changing UOPatch.exe to UOtd.exe.... change it to client.exe
Note this skips the patch thing but until all is fixed...I suppose that is not a bad thing.