• Hail Guest!
    We're looking for Community Content Contribuitors to Stratics. If you would like to write articles, fan fiction, do guild or shard event recaps, it's simple. Find out how in this thread: Community Contributions
  • Greetings Guest, Having Login Issues? Check this thread!
  • Hail Guest!,
    Please take a moment to read this post reminding you all of the importance of Account Security.
  • Hail Guest!
    Please read the new announcement concerning the upcoming addition to Stratics. You can find the announcement Here!

About to lose my cool!

Storm

UO Forum Moderator
Alumni
Stratics Veteran
Stratics Legend
Awards
1
yes make sure and run as admin for everything
 
H

HongKongCavalier

Guest
only thing I can think to do now would be to uninstall again then go and make sure there is no folder for it at all and no saved files what so ever then run a registry cleaner to make sure there is nothing there ..
If I may recommend a registry cleaner, CCleaner is a free app that does a good job of cleaning up the registry and deleting your temp files. If you use it, make sure you scan and fix the registry twice; it always seems to find additional registry issues after fixing the issues from the first scan.

I had patching issues on my XP Pro machine once that I couldn't fix until i deleted all my temp files (temp folder, prefetch, etc.) and cleaned the registry (I also use Registry Mechanic in addition to CCleaner). Might be worth a try.
 
H

HongKongCavalier

Guest
Or simply disable the UAC completely and be without problems.
Good advice, IMO. But you'll still have the occassional permission/ownership issues (at least in Windows 7; I skipped the Vista era/error).

I have 3 suggestions for Windows 7 users in general (and I'm pretty sure this all works for Windows Vista also):

1. Install any program you trust in folders in the root directory, not the Program Files directory (I have UO in c:\UO, for example). Anything in the Program Files directory is subject to additional permission restrictions (which is honestly usually not a problem, but a major annoyance when it does pop up).

2. Get familiar with the "takeown" and "icacls" commands; unfortunately, you will probably need them sooner or later.

3. Or forget about those 2 commands and Google this word (including quotes): "grantadminfullcontrol" and read the article at MyDigitalLife.

Of course, everything listed above is disabling what Microsoft feels is one of Windows 7's major assets, so only follow my advice if you are comfortable working without a net (a poorly designed net, but a net nonetheless).
 

ingsmsico

Visitor
Stratics Veteran
Stratics Legend
Good advice, IMO. But you'll still have the occassional permission/ownership issues (at least in Windows 7; I skipped the Vista era/error).

I have 3 suggestions for Windows 7 users in general (and I'm pretty sure this all works for Windows Vista also):

1. Install any program you trust in folders in the root directory, not the Program Files directory (I have UO in c:\UO, for example). Anything in the Program Files directory is subject to additional permission restrictions (which is honestly usually not a problem, but a major annoyance when it does pop up).

2. Get familiar with the "takeown" and "icacls" commands; unfortunately, you will probably need them sooner or later.

3. Or forget about those 2 commands and Google this word (including quotes): "grantadminfullcontrol" and read the article at MyDigitalLife.

Of course, everything listed above is disabling what Microsoft feels is one of Windows 7's major assets, so only follow my advice if you are comfortable working without a net (a poorly designed net, but a net nonetheless).
as far as I know, you don't need to worry about any of that to get UO to function properly. if you don't know what you are doing and you start messing with persmissions you are going to screw stuff up 100% guarantee.

I'm confused why re-installing UO isn't working for you people. you must be doing something wrong or have viruses. run MBAM before you do anything.
 
T

The_Traveler

Guest
Forgive me if I'm covering old ground here.

  • Uninstall UO.
  • Delete any folders left behind by the uninstaller.
  • Grab CCLeaner and run it to clean your registry. (Do this anyways, good tool to have)
  • Download the latest client.
  • Right click the installer and Run As Administrator.
  • Once install is complete set UO and uopatch to run as admin from their properties page.
 

Basara

UO Forum Moderator
Moderator
Professional
Governor
Stratics Veteran
Stratics Legend
Wiki Moderator
UNLEASHED
Campaign Supporter
Cal, Billy:

Here's an issue I've seen crop up on both my desktop and laptop (at different times), for patching the CC. This is with WinXP machines, but I don't see anything that would keep it from happening in a Vista or Win7 install, either.

It appears that the way the client patches is that it detects the version of a file being patched, then after detection of the old version (according to the description going on in the patch log) it writes the new file version, then deletes the old one.

This doesn't quite sound right, but if that's what it's doing, that may be the source of the glitch.

Now, some of the time when a person patches, something will glitch, and the old/new version of a file disappears DURING the patch process (both versions deleted, or the new one not written and the old deleted?), stopping the patch. With the file now MISSING, the patch then refuses to progress past the missing file.

If you don't have a backup of the installed program to copy the old file from, you then have to do a total reinstall, and hope you don't get the same glitch even earlier in the re-patch process after the reinstall. Strangely, this can occur at different spots in the same patch, on different machines, so it's not linked to the files being patch, but to the patcher doing something incorrectly.

If you DO have a backup (a copy of the directory, or - in my case - a copy of either the old or new version of the file from my other computer), you can just see in the patchlog what the offending missing file is, and copy it over from an install of the fully patched CC, or the version that is being patched up from.

I don't think files out of date by more than one patch will work (i.e. if the files were changed since the backup was made, but before the current patch).
 

Basara

UO Forum Moderator
Moderator
Professional
Governor
Stratics Veteran
Stratics Legend
Wiki Moderator
UNLEASHED
Campaign Supporter
Just for reference, in the patch log, this is what certain things look like...
(note that there is no space between an "End patch" line and the name of the next file being patched).

Most successful patches end/begin like this (the regular text is the end of the previous successful patch, and the ITALICS is the start of the new patch (not really italics in the patchlog - only made so here to show the break point).

Billy, something about the change in the patcher process between 7-0-2-1 & 7-0-2-2 made it to where it now OVERWRITES the end of the previous patchlog (prior, there were several line breaks separation clearly deliniating the breaks, and there was no line saying "Starting Patch session....")

Code:
----- Patch File Processing Complete -----
 
 
 
-----------------------------------------------------
 
-        Results of Application of Patch File       -
 
-----------------------------------------------------
 
File Patches Applied ......................... (  19)
 
   Files Modified .................. (  17)
 
   Files Renamed. .................. (   0)
 
   Files Added ..................... (   2)
 
   Files Deleted ................... (   0)
 
   Temporary Files Processed........ (   0)
 
File Patches Skipped: New Files Up-To-Date.... (  11)
 
File Patches Ignored: Old Files Missing....... (   0)
 
                      Old Files Invalid....... (   0)[I]Starting patch session...[/I]
[I]Transferring patch information[/I]
[I]Downloading patch uosa_win32_7-0-7-1.rtp( 551756 bytes )[/I]
[I]Downloading patch uosa_win32_7-0-7-1.pat( 13 bytes )[/I]
[I]Downloading patch uosa_win32_7-0-7-1.rtp( 551756 bytes, resuming )[/I]
[I]Downloading patch uosa_win32_7-0-7-1.pat( 13 bytes, resuming )[/I]
[I]Applying patch patch\uosa_win32_7-0-7-1.rtp[/I]
 
[I]-------------------------------------------------------------------------------[/I]
[I]PATCH  Version 7.00 - RTPatch(R) Professional - Software Update System[/I]
[I]                 DOS/16-bit Windows/32-bit Windows Edition[/I]
 
[I]    (C) Copyright Pocket Soft, Inc., 1991-2002.  All Rights Reserved.[/I]
[I]-------------------------------------------------------------------------------[/I]
 
 
[I]----- Processing Patch File -----[/I]
What it looked like before 7-0-2-2. Looking at the end of the patchlog file, it would seem that the truncating is occurring on the end of the save, meaning that the full recording of the patchlog is never completed, and the telling evidence of what is causing some of the missing-file bugs may not be getting written to the patchlog, when the issue occurs after 7-0-2-2. My data on what was going on originally were from older patchlogs that have long since been deleted.

Code:
----- Patch File Processing Complete -----
 
 
 
-----------------------------------------------------
 
-        Results of Application of Patch File       -
 
-----------------------------------------------------
 
File Patches Applied ......................... (  32)
 
   Files Modified .................. (  32)
 
   Files Renamed. .................. (   0)
 
   Files Added ..................... (   0)
 
   Files Deleted ................... (   0)
 
   Temporary Files Processed........ (   0)
 
File Patches Skipped: New Files Up-To-Date.... (   0)
 
File Patches Ignored: Old Files Missing....... (   0)
 
                      Old Files Invalid....... (   0)
 
-----------------------------------------------------
 
Total File Patches Processed ................. (  32)
 
-----------------------------------------------------
 
 
 
 
Transferring patch information
Downloading patch uosa_win32_7-0-2-1.rtp( 2091724 bytes )
Downloading patch uosa_win32_7-0-2-1.pat( 12 bytes )
Downloading patch uosa_win32_7-0-2-1.rtp( 2091724 bytes, resuming )
Downloading patch uosa_win32_7-0-2-1.pat( 12 bytes, resuming )
Applying patch patch\uosa_win32_7-0-2-1.rtp
 
-------------------------------------------------------------------------------
   PATCH  Version 7.00 - RTPatch(R) Professional - Software Update System
                    DOS/16-bit Windows/32-bit Windows Edition
 
       (C) Copyright Pocket Soft, Inc., 1991-2002.  All Rights Reserved.
-------------------------------------------------------------------------------
 
 
----- Processing Patch File -----


A successful add of a file that previously didn't exist

Code:
unifont9.mul
Applying ADD File Patch for 'unifont9.mul'
 
    Adding New File
 
    Verifying - Passed!
 
 
End patch
A successful update of a previously-existing file

Code:
walls.txt
Applying MODIFY File Patch for 'walls.txt'
 
    Writing New File
 
 
    Verifying - Passed!
 
    Deleting Old File
 
 
End patch

Here is an example of where a patch is resumed

Code:
client.exe
Applying MODIFY File Patch for 'client.exe'
 
    New Version of File 'client.exe' already exists.
 
End patch

Now, here are several examples of where the patch FAILS.

Code:
Cliloc.enu
Applying MODIFY File Patch for 'Cliloc.enu'
 
    Writing New File
 
 
    Verifying - Passed!
 
    Deleting Old File
 
 
End patch
Cliloc.jpn
Applying MODIFY File Patch for 'Cliloc.jpn'
 
    WriStarting patch session...
Transferring patch information
Downloading patch uosa_win32_7-0-7-0.rtp( 18072212 bytes )
Downloading patch uosa_win32_7-0-7-0.pat( 13 bytes )
Applying patch patch\uosa_win32_7-0-7-0.rtp
Code:
mobtypes.txt
Applying MODIFY File Patch for 'mobtypes.txt'
 
    Writing New File
 
 
    Verifying - Passed!
 
    Deleting Old File
 
 
End patch
options.enu
Applying MODIFY File Patch for 'oStarting patch session...
Transferring patch information
Downloading patch uosa_win32_7-0-5-0.rtp( 15293604 bytes )
Downloading patch uosa_win32_7-0-5-0.pat( 13 bytes )
Applying patch patch\uosa_win32_7-0-5-0.rtp
Code:
animdata.mul
Applying MODIFY File Patch for 'animdata.mul'
 
    Writing New File
 
 
    Verifying - Passed!
 
    Deleting Old File
 
 
End patch
art.mul
Applying MODIFY File Patch for 'art.mul'
 
    Writing New File
 
 
    Verifying - PaStarting patch session...
Transferring patch information
Downloading patch uosa_win32_7-0-5-0.rtp( 15293604 bytes )
Downloading patch uosa_win32_7-0-5-0.pat( 13 bytes )
Applying patch patch\uosa_win32_7-0-5-0.rtp
Code:
map1.mul
Applying MODIFY File Patch for 'map1.mul'
 
    New Version of File 'map1.mul' already exists.
 
End patch
map5.mul
Applying MODIFY File Patch for 'map5Starting patch session...
Transferring patch information
Downloading patch uosa_win32_7-0-3-0.rtp( 336186200 bytes )
Downloading patch uosa_win32_7-0-3-0.pat( 12 bytes )
Downloading patch uosa_win32_7-0-3-0.rtp( 336186200 bytes, resuming )
Downloading patch uosa_win32_7-0-3-0.pat( 12 bytes, resuming )
Applying patch patch\uosa_win32_7-0-3-0.rtp
Note the locations of where the patching text starts (especially the latter), and the start of the new attempt to patch later occurs (another reason to add line breaks before and after the patch sessions for logging).

I suspect that if the patch session fails at certain specific points in the Apply MODIFY/write/verify/delete process neither the new file is put in place, nor is the old file still present. IIRC, the art.mul and map5.mul files are ones I had to replace in cases of a file going missing in a patch, and not allowing patches past that point, but only older, pre-7-0-2-2 patchlogs that showed a missing file at the point of failure (that appears not to be getting written due to the patchlog pulling up short on its writing after that patch). (for these, I watched for where the patcher kept failing, then transferred the last file mentioned from the other computer, and restarted UO, and the patch continued)

Hopefully, this can at least give you an area to look at as to what causes some of the "unrecoverable" patch errors (that I've found can be recovered by copying a file or two over from another install).
 
H

HongKongCavalier

Guest
as far as I know, you don't need to worry about any of that to get UO to function properly. if you don't know what you are doing and you start messing with persmissions you are going to screw stuff up 100% guarantee.

I'm confused why re-installing UO isn't working for you people. you must be doing something wrong or have viruses. run MBAM before you do anything.
"You must be doing something wrong?" When something is not working the way it should, I wouldn't jump and put it on the user when any number of things can go wrong with a Windows PC (and not even be virus or malware related) that can't be fixed without reinstalling Windows from scratch.

And true, if you don't know what you're doing, you can mess things up. But even worse is, if you don't know what you are doing, you're not going to know how to recognize and fix a problem that you are running into because of restrictive permissions and ownership.

The fact you even have the options of disabling UAC and changing permissions/taking ownership of files is a tacit admission on Microsoft's part that Windows 7 won't always cooperate with you or your software and will not always behave how you like.
 
Top