Welcome to RCF - WHF

Nightrider · Sep 25, 2004

Ok, after rebooting to get Explore displaying the text for the folders and drives again, I attempted to launch my Email client. But it will no longer open. I get a series of about 8 non-useful messages telling me that Eudora won't be able to run such as:

and

I am unable to capture the rest. This is what you should expect each time one of your installed programs has problems. I have had similar problems with several other previously working programs with an equal number of unhelpful M$ messages. So now I have to figure out how to prevent this problem from repeating each time I reboot. Notice as with a lot of the other problems, this is a permission issue...

Ok, what is happening is that W7 allows Eudora to create a temp file, but then it won't allow Eudora to use it immediately aftewards. W7 really struggles with permission issues. So I may be forced to reinstall Eudora from scratch since deleting the offending temp files does not resolve the problem. Eudora simply creates new temp files that W7 still won't give it access to and chances are, even if I reinstall, Eudora will run into the same problem again. There may not be a solution to this problem...

Brick wall

Nightrider · Sep 25, 2004

In its infinite wisdom, M$ decided to take the personal and application data and scatter it around in W7. Instead of having everything neatly in one place, M$ thought it was better to scatter it to many places. Then if you want to try to figure out where everything was moved to, you can run a program that shows all the Junction Points...

For example, you can no longer access the Documents and Settings folder since it really doesn't exist in W7. The reference is there for backward compatibility, but there is no way to view any contents because it really isn't there. M$ has decided that instead of a Docs and Settings folder, it needs two folders named ProgramData and Users:

Inside of the ProgramData folder, there are folers for installed programs as well as unaccessible Application Data, Desktop, Documents, Favorites, Start Menu, and Templates folders. Again, they don't really exist, but are simply listed for backwards compatibility. Their junction points can be found in the JunctionPoints.txt file that you might want to create to see where everything is actually stored now:

In the Users folder, it somewhat resembles the old Docs and Settings layout with folders for All Users, Default and Default User, Public, and yourself. But you cannot access the Default User folder because like those mentioned above, it doesn't really exist but is listed for "backward compatibility". If you open your User/<login name> folder, you will find an inaccessible Application Data folder along with a new AppData folder. There are also inacessible Local Settings, My Documents, Nethood, Printhood, SendTo, Start Menu, and Templates folders. Again, they are only listed for "backward compatibility" reasons and don't actually exist. This is the error message you would see each time you click on a non-existent folder:

Ok, when you click on your Users/<login name>/AppData folder, you will see 3 folders, Local, LocalLow, and Roaming. So far when I needed to modify program options, I could find them in the Roaming folder:

This seems to be where the important stuff, that you might want to backup, is stored. This seems like an extremely clugy way to handle things compared to the nice and neat method M$ used from W95 to XP. I cannot begin to understand why M$ thinks this is an improvement. All it seems like they are doing is moving the deck chairs around on the Titanic...

Brick wall

Nightrider · Sep 25, 2004

This is an example of what your W7 JunctionPoint.txt file might look like. You will need to create something like this in order to figure out where everything has been scattered to. This gives you a map that you can use to track everything down again if need be:

I would really love to hear from the genius who developed this why it is better than what we are used to seeing in the Docs and Settings folder. The explanation should be good enough for a laugh...

Brick wall

Katy · Sep 28, 2004

Thanks for the info NR & fish.. I am still using XP and am satisfied... Guess I'll stay here for a while.

Nightrider · Sep 25, 2004

Katy · Sep 28, 2004

Thanks

fishead · Feb 09, 2005

Nr, I'm not sure I understand what your saying but the permission problem, but, I think I had to create a second admin user, then delete it or something weird to fix the problem. I had to set up vista three times and remember doing something like that.

W7 sounds just like vista, nothing makes sense and certainly not easier. It was made by retards with no brains. They made things without testing it, they just threw in ideas and how ever the dice fell it fell without a care about the user. It is as user unfriendly as it can be. violent1

Nightrider · Sep 25, 2004

rb2d2 · Sep 25, 2004

Does this help?

How to Take Ownership & Grant Permissions to Access Files & Folder in Windows 7

Sounds like a lot of silly and (should be) unnecessary hoops to jump through.

Brick wall

rb2d2 · Sep 25, 2004

Here is something else: cacls is a handy tool to change permissions of files en masse.

Resetting NTFS files security and permission in Windows 7 RC

To reset files permissions:

1. Run “cmd” as Administrator

2. Go to the drive or folder in question, for example:

CD /D D:

3. To reset all the files permissions, type:

icacls * /T /Q /C /RESET

4. And that’s it!

dontknow