Two different things are being discussed.

1. The install option refers to expanding on the host (the guest always sees the same size drive).
2. The process this thread talks about refers to changing the guest's view of the disk. This is difficult because in real life, you can't just change the size of your disk (well, not without cloning it to a larger drive), and so guests aren't able to adjust; the extra work is necessary to get them to recognize the new space.

Well, I couldn't find an easier way to do this, so I just followed the directions in the PDF file. It did work, but it was not without a few quirks. I post them here in case someone else runs in to these problems in the future.

First -- back up your virtual machine before you do anything! You'll regret it if you don't and something goes bad...

Next, the vdiskmanager GUI crashed on me during the resize the first time I ran it. When I ran the 2nd time, it would not work. It give me some cryptic error saying the file already existed. With nothing left to lose, I got adventurous. I right clicked on the virtual machine and clicked the show package contents link. I then deleted some oddly named file that ended in .tmp and tried again. This time vdiskmanager GUI worked.

Finally, the newly resized virtual machine would not run after I finished all the steps in the PDF. Windows kept crashing on me during the boot. I had to insert me Vista Install CD, and do a Repair. Once I did that, Windows did start up and everything seems to work.

I hope this helps!

Yes. This is the Fusion subforum, and Fusion is for Macs.

I would suggest RDPetruska's DiskManager GUI

Search for vdiskmanager in http://www.vmware.com/pdf/ws6_manual.pdf

However the Utility Eric pointed you to is the easiest way to do it and it's pretty self-explanatory one you take a good look at it.

Robert D. Petruska's DiskManager GUI

Yes I also used this method, and I agree it is easier. As you said this thread is for Fusion (Macs) but I would recommend the other method for increasing a virtual hard disk on Windows.

FYI: That link was already posted about 5 months ago by zyx100 further up in this thread.

Never mind... It turns out I needed to actually "power down" my VM. d'oh!

That's who I was trying to quote, but it seems that I'm not figuring out quite how to quote on this board. Glad to have run across it, the method works great, on Windows at least.