I hope you backed up the Virtual Machine or at the very least the User Data before attempting a resize.

Anyway you're going to have to provide more details as what you've presented so far is very general and ambiguous so have a look at HOWTO: Ask (and Answer) Questions and provide exact details and error messages etc.

This is still general and ambiguous because Fusion does not provide a mechanism to resize a running Virtual Machine and therefore Fusion would not be asking you to to restart the Virtual Machine since it can only resize the Virtual Hard Drive when the Guest OS isn't even involved in the process.

So if your using some 3rd party product to resize a partition after Fusion resized the virtual hard drive then provide the details! We are not mind readers so if you're not explicit and specific about exactly what you've done and how you've done it I'm not sure what help you expect to get

Is the screen totally absolutely black or is there as small white cursor, blinking or not in the upper lefty hand corner if the Virtual Machine's Display? Screenshot if necessary.

You can archive and upload the vmware*.log file from within the Virtual Machine Package and have a look at "Collect vmware.log files" section in Information Gathering for VMware Fusion

Sorry I'm not familiar with Norton Partition Manager. Is this a stand-a-lone program or part of a Norton or Symantec Product? Anyway this next part is critical... Fusion resized the Virtual Hard Drive however this does not change the size of the partition on the virtual hard drive and why one needs to use another program to either dynamically expand the existing partition or create a new partition within the free space on the newly resized virtual hard drive...

So which is it that you did? If one dynamically expands the existing partition there is no formating of the existing structure thus retaining existing OS/Applications/User Data intact and is only enlarging the existing partition to take up the additional space provided by the disk being resized. That additional space is formated whatever format the existing space was without touching the existing space and of course a reboot is required for the OS to recognize the changes.

I'm going to assume for the moment that this is what was done with Norton Partition Manager and not creating a separate partition in the free space.

Okay here is what I think happened... Because you have a black screen with a white non-blinking cursor in the upper left corner of the Virtual Machine's Display I believe if Norton Partition Manager didn't wipe your entire disk when formating that at the very least it has corrupted the MBR (Master Boot Record) and or Partition Table and one way to attempt to fix this after you first make a backup of the Virtual Machine Packaged with Fusion closed you would then boot the Virtual Machine with the XP Install Disc to the Recovery Console and run the FIXBOOT and or the FIXMBR commands in an attempt to repair this.

Make sure you make a backup copy of the Virtual Machine before doing anything else!

Description of the Windows XP Recovery Console for advanced users

To boot the Virtual Machine from the Windows Install Disc or ISO Image have a look at my reply in: Re: How can I repair XP in VMware Fusion 2

Message was edited by: WoodyZ

You originally said "Norton Partition Manager"... Anyway I'm familiar with Norton PartitionMagic because it used to be PowerQuest PartitionMagic before Norton/Symantec bought it from PowerQuest. I'm still using PowerQuest PartitionMagic 8.x and it still works fine.

Did you follow the directions in Re: How can I repair XP in VMware Fusion 2? Because if you do you should be able to boot the Virtual Machine from the CD or ISO Image if you follow the directions.

Well a hard lesson to learn however I bet you'll be backing up from now on.

If you didn't actually format the drive wiping it out then you can use VMDKMounter to mount the Virtual Hard Drive.

Ctrl-click the Virtual Machine Package and select Open With > VMDKMounter and then look on your Desktop for an icon of a white drive labeled "Untitled".