[General Topics] Menneisyys:
Fortunately, there is a very easy way of fixing this: the free EasyBCD. Just make sure you follow THIS guide. A screenshot showing it configured to access my OS X setup:

1.4 Security and its implications; loosening security restrictions

1.4.1 File system

If you're a newcomer to Vista / W7, you'll notice it uses an entirely new file system security approach.

In XP, it's just the subfolders of Documents and Settings that were protected (by default) so that other users couldn't just step into them to examine the contents of other users. In Vista / W7, this has been taken further – now, among other things, c:\Program Files is entirely write protected.

There are some implications of this. For example, if you run some "hacker" tools (like Driver Heaven's "Mobility Modder" hack) needing to have full write access to the given (sub)directory so that they can patch / copy files, they'll fail. Also, if you need direct write access to a subdirectory of c:\Program Files, you may run into problems.

An example of this is running Apache Tomcat (or any other Web server) from inside c:\Program Files. If you develop Web pages (JSP's etc.) in its webapps/ROOT directory, you will run into problems when you try to edit the individual files. Sure, if you use the plain Notepad to do this, all you'll need to do is either creating it or saving under a different name so that, later, you can re-edit it. Third-party tools like JCreator (even as of the latest, 4.5 version), however, may run into severe problems doing the same. In my practice, they reported my files having been saved; however, they were nowhere to be seen. That is, JCreator was simply unusuable to edit my Java files under c:\Program Files.

Fortunately, it's pretty easy to fix problems like this. Right-click the directory where you keep your files (for example, ROOT under webapps), select Properties and, then, the Security tab:

There, select "Users" in the upper "Group or user names" list as is depicted in the above screenshot. Now, click Edit under the "Group or user names" list and, again, select "Users":

Finally, tick in the "Allow" checkbox in the "Full control" row (it's selected in the next screenshot):

Now, click Apply and two times OK.

Note that you'll only want to do this when you're absolutely sure you must write into a given directory a lot of times. Otherwise, being read-only is part of the tighter security model. That is, always make sure you only allow free writing to a the bottom-most directory, not a more generic one closer to the root directory.

1.4.2 User Account Control (UCA)

You may also want to hide the User Account Control prompts, which can be quite a nuisance, particularly if you install a lot of software. For this, you'll need the free TweakUAC tool. Please consult the online documentation for more info.

1.5 Mobility: iPhone, Windows Mobile, Symbian, BlackBerry

Now, let's have a look at how W7 supports the (outside the U.S. – sorry, I still don't have a real, genuine Android machine – I don't want to use Android hacks on WinMo ones – so I can't comment on Android yet) four major mobile operating systems.

1.5.1 Apple iPhone

I haven't really run into problems accessing or synchronizing my iPhone (firmware version 2.2, yellowsn0w-unlocked and jailbroken) under W7. Even T-PoT worked (please see THIS and THIS for more info), which is great news for all iPhone freaks wanting to access the file system right from Total Commander on the desktop, without having to run an SSH server on the phone (and having to stick to an SSH / SFTP client under Windows.)

1.5.2 Windows Mobile

Accessing (and synchronizing) Windows Mobile (WinMo for short), on the other hand, have turned out to be a little more cumbersome. It hasn't always managed to recognize my WM5+ Windows Mobile models easily. In some, I had to switch to the other USB connection approach.