BTW, suggestion to persons who routinely have trouble patching....
It's not like UO is spectacularly huge, and HD space is cheap these days.
1. After you successfully patch up, copy your entire UO client folder into a backup directory.
2. Repeat this after every successful patch.
3. When you have a failed patch session that can't be gotten past (As opposed to one that can be successfully resumed), check the patch log.
a. if you see where the patcher can't find a file, copy it over from your backup, clear your patch folder, and try again.
b. if you can't tell why it failed, copy the entire backup folder over to the original, empty the patch folder, and try again.
Either is a heck of a lot quicker than a reinstall.
One of the common catastrophic patch failure causes is that, instead of simply overwriting a file, the patcher seems to write the new file, then delete the old one. Sometimes the new file isn't written, but the old one is deleted. As a result, the patcher chokes, as it requires the old folder to be there, and to match the data (checksum? other version indicator??) of the version from the previous patch. Without the missing file, the patcher can't continue.
Devs, would it be so hard to come up with a modern patcher that, if it detects that a file is completely missing, it just replaces it, instead of going into catastrophic fail?