theworldofdreams.com

I downloaded the wodfiles, i did everything i should of but when i log in with my username and pass, i get the connecting thingy and then the cannot connect to server thing. any suggestions?

It seems i say this alot, but what version of UO, did you patch and did you download the login file found herehttp://www.theworldofdreams.com/files/index.html

I am having same issue, there is an error and WoD shuts down. I patched UO:AOS and play it as well. I tried to download and replace wodli.cfg in my UO folder and I get an error message:

Cannot copy wodli[1]: Access is denied.

Make sure the disc is not full or write-protected and that the file is not currently in use.

So how can I overcome this? I am running Windows XP.

DebbyAnne wrote:Cannot copy wodli[1]: Access is denied.
Make sure the disc is not full or write-protected and that the file is not currently in use.
So how can I overcome this? I am running Windows XP.

That is the WinXP default "simple file sharing", most likely.

How to Disable Simple File Sharing
Click Start, and then click My Computer.
On the Tools menu, click Folder Options, and then click the View tab.
In the Advanced Settings section, clear the Use simple file sharing (Recommended) check box.
Click OK.

You also can open "My Computer" navigate to your UO directory ( C:\UO ? ), then rightclick the directory, select Properties and see if "Everyone" has full privileges.

simon wrote:It seems i say this alot, but what version of UO, did you patch and did you download the login file found herehttp://www.theworldofdreams.com/files/index.html

I have UO Renassaince (sorry bout spelling lol) yes i did patch and download all the files needed, i have played WOD for 3 years, and i had to wipe my comp because of some problems with it so i had to download the stuff and everything and i get "Connecting" then "Cannot Connect to Ultima Online, etc"

this will sound odd to some people, but some times windows is just plain stupid, i done a reinstall of windows xp then it wouldn't run black and white, it would just crash, if it worked b4 it should work again.... sometimes a 2nd reinstall is needed for reasons unknown

but maybe just uninstalling UO and then clearing the UO folder(if anything is left) then defrag and give it a 2nd go

hey bayn, didn't i explain how to do that one before to someone else?

ok i can get other shards working, i even renamed WoD files to the UO ones (worked before) but i believe its the IP, the one in the login on files site may be wrong or something, any suggestions?

redownload the login file

i have many times

Draco wrote:ok i can get other shards working, i even renamed WoD files to the UO ones (worked before) but i believe its the IP, the one in the login on files site may be wrong or something, any suggestions?

someone else had this problem. could login to other shards but not WoD. It turned out to be a setting on the computer, or file protection, file sharing or something like that. Did you check simple file sharing, directory permissions and so on?

This doesn't Work in XP Home, only in XP Pro.

Bayn wrote:

DebbyAnne wrote:Cannot copy wodli[1]: Access is denied.
Make sure the disc is not full or write-protected and that the file is not currently in use.
So how can I overcome this? I am running Windows XP.

That is the WinXP default "simple file sharing", most likely.

How to Disable Simple File Sharing
Click Start, and then click My Computer.
On the Tools menu, click Folder Options, and then click the View tab.
In the Advanced Settings section, clear the Use simple file sharing (Recommended) check box.
Click OK.

You also can open "My Computer" navigate to your UO directory ( C:\UO ? ), then rightclick the directory, select Properties and see if "Everyone" has full privileges.

I probably need to put this on a permanent page, because more than a few people have had this problem and this has helped them, but here we go again... (Thanks to Daeric for originally helping me fix this problem on my machine)

This problem (and fix) only works on Windows XP Home. The same problem can happen on XP Pro, but Pro comes with the tools to fix it built right in, nice and easy to use. Home edition is not so lucky. This is a problem that happens sometimes with other files in XP Home, but for some reason, it seems to happen rather often with UO (it happens to me all the time, because I'm constantly fiddling with UO files, so much so that I made a batch file to fix it.)

A few things that you should try before the stuff below:
Try to delete all the wod*.* files. If you can't delete them, restart the computer and try to delete them again. If you're using Windows XP Home, do what Bayn said. If you're using anything other than XP Home, then I'm not sure at this point. If you are using XP Home, then this is what you need to do to fix it...

First you need the program cacls, which you can download from the Microsoft site (God help you there, though - its impossible to find ANYTHING on the Microsoft website.) Download it and install it/unzip it/put it in your windows directory.

Next, you need to find your username in Windows. This is pretty easy: Press the Start button - at the top of the menu that pops up, there should be a picture followed by your username. You need to have the exact capitalization, spacing, etc.

Start a DOS command prompt. Change to the Ultima Online directory. Make absolutely certain that you are in the Ultima Online directory. Double-check that you are in the Ultima Online directory. If you are not in the Ultima Online directory, what happens will be very, very bad. You will likely need to reinstall Windows if you are not in the Ultima Online directory, so make sure you are in the Ultima Online directory (am I being clear here? )

Type the following:
cacls *.* /G "(username)":f

Replace (Username) with your windows login name that I discussed above, being sure to use the right capitalization and/or spaces, as appropriate. It should ask you if you want to continue, Y/N - <b>make sure you are in the Ultima Online directory</b> and select Yes. That should fix the problem, then.

Drocket wrote:Try to delete all the wod*.* files. If you can't delete them, restart the computer and try to delete them again. If you're using Windows XP Home, do what Bayn said. If you're using anything other than XP Home, then I'm not sure at this point. If you are using XP Home, then this is what you need to do to fix it...

Should that paragraph have read:

Try to delete all the wod*.* files. If you can't delete them, restart the computer and try to delete them again. If you're using Windows XP Pro, do what Bayn said. If you're using anything other than XP Home, then I'm not sure at this point. If you are using XP Home, then this is what you need to do to fix it...

I changed one Home to Pro.

Drocket wrote: This is a problem that happens sometimes with other files in XP Home, but for some reason, it seems to happen rather often with UO (it happens to me all the time, because I'm constantly fiddling with UO files, so much so that I made a batch file to fix it.)

For those of you that are interested in the "Where's and why fors" and those of you who would like to adjust your practices so that this occurs less frequently.

First, this is an unintended side effect of a NTFS feature. Because the NTFS permissions are masked from the user in Windows XP Home it can be extremely annoying.

Here is a step by step of the process most users go through when downloading the wodli.cfg file followed by an explaination of where the permissions were confused and why.

1. User Snuffy Downloads wodli.cfg file to his Desktop

2. User Snuffy opens Windows explorer and drags and drops the wodli.cfg into the Ultima Online folder.

Obviously these steps will vary somewhat per user but generally the common thread among people suffering this problem is "User downloads to desktop/or My Documents" then copies the file into the UO folder.

Now as most of you know when relocating a file you have two options, you can move the file or you can Copy the file. Windows handles these two operations differently with regards to file permissions.

Copy: Windows duplicates the file exactly, to include file security or ACL's (You did ask for a Copy) and places this newly created copy into the directory you specified with it's file permissions intact.

Move: File is moved to the new location however the File security (DACL) structure associated with the file is removed and it instead accepts the default permissions in the folder it has been moved too.

So the logical question is: "I can open/move/copy and delete the file on my desktop, so if the permissions are copied exactly how is it that I cannot delete it when I've moved it to the new folder?"

The answer: The desktop (in fact most Windows folders) use what is called inherited permissions, this means you set the permissions at the top level (C:\) and these permissions are allowed to be passed down to subsequent files. When you copy a file which has inherited permissions the Copy process records only the ACL's specific to that file which are "None".

Because the copy you created of the file has it's own DACL(Security Permissions) associated it does not inherit permissions from the folder it is placed in so it has a blank set of security permissions and this is why you cannot delete or access the file properly.

Best Practices: The best way to get around this "Feature" is to ensure that each time you relocate a file on your system you know exactly which procedure is taking place Copy or Move. The easiest way to accomplish this is, when you're planning to drag a file from one location to another, instead of holding down the left mouse button. Use the right mouse button, Drag and drop just like you normally would.. when you release the mouse button you will see a small popup menu appear with the following options "Copy Here", "Move Here", "Create Shortcut", and "Cancel".

It's a very useful habit to get into. How many times have you dropped a folder in the wrong place? This gives you the option to "Cancel" the action before it starts and armed with your new knowledge of NTFS Copy/Move you'll know when you're duplicating ACL's and when you aren't, so at least you'll be able to quickly identify and resolve future ACL Move/Copy problems.

GM Daeric

Not
Too
Friggin
Smart

refreshing honesty from microsoft.