You know this is one of things that VMWare needs to
address in some kind of manual for users...,
Shared Folders is explained in the online help that comes with Fusion. Have you seen that? Pull down Fusion's Help menu and choose "VMware Fusion Help." Then go to "Moving and Sharing Files with Your Mac."
However, I do grant you that the online help doesn't explain the difference between VMware Shared Folders and Mac OS's /Users/Shared.
I misread something Pat Lee wrote once.. and was
thinking... oh, well, I'm going to need MacDrive...
to do that... and now I realize he wasn't saying that
at all.... So when Fusion virtualizes NTFS so you can
write to a Shared Folder... (Fusion's Folder)... and
its really layed over HFS+... isn't that kind of like
what MacDrive is doing...
Let me give you a better way to think about VMware Shared Folders. Imagine that you want to go to the airport, but you don't have a car (and there is no other way to get there). So you have two choices: you can rent a car, or you can hire a taxi.
If you hire a taxi, all you have to do is to say to the driver "To the airport!" and off you go. The driver takes responsibility for actually operating the car. But if you rent a car yourself, you take responsibility for driving it (and putting fuel in it, and returning it, and so on).
VMware Shared Folders is like hiring a taxi. Mac OS is the taxi driver; VMware Shared Folders says to Mac OS, "You deal with all the details of how this is actually stored on disk: NTFS or HFS+ or FAT or whatever. I just want to work with the files."
MacDrive is like renting a car. MacDrive accepts the duty of understanding the details of how data is stored on disk and to present the data to Windows as useful files and directories. It's driving the car, so to speak.
Now, can two people simultaneously drive the same car safely? NO (unless it's one of those unusual cars with two steering wheels that are used for driver training). In the same way, two operating systems cannot safely access the same HFS+ at the same time. This is why you don't want to use MacDrive in a Boot Camp VM.
Frankly, I think MacDrive isn't terribly useful to Fusion users. It seems dangerous in a Boot Camp VM, and it would have no access at all to your host Mac's file systems when run in an ordinary VM. If you want to share files between VMs and host, just use Shared Folders or network shares.
And then I get confused.. with the idea of using
Winclone... am I going to use it with MacDrive or
without MacDrive.. to NTFS or to HFS+ or to both...
I also don't think Winclone is very useful to Fusion users. The purpose of Winclone is to let you copy your Boot Camp partition to another disk. But the purpose of Fusion's support for running Boot Camp partitions as VMs is to make copying your Boot Camp partition unnecessary. And, if you really want to move your Boot Camp partition into an ordinary VM (the kind with virtual disks that are stored as files), VMware Converter will do that for you much more simply than Winclone will.