Maybe there is still a communication problem.
Can you post the screenshot corresponding to the image on page 4 of 14 of the .pdf?
In that image you can see that there are THREE disk devices connected to the machine:
1) Hard Disk (IDE0:0) - that should be connected to your Virtual Disk - a .vmdk file - the one that boots as C:
2) CD-ROM (IDE1:0) - that should be either not connected to anything or connected to ETBOOT.ISO
3) Floppy - no need to connect it to anything
Now, when booting from ETBOOT.ISO, the Virtual Disk or .vmdk file should be as well connected.
What you are telling me is that once booted, ETBOOT.ISO cannot "see" the C: drive.
This is simply impossible
, even if it was formatted badly or not formatted at all, ETBOOT.ISO should see ANY entry in the partition table in the MBR of any connected hard disk (Virtual or physical).
The only possibility, would be if for any reason the VM fails to connect to the hard disk, something that you say it does not.
But this makes me wonder on another thing, you asked for assistance because you were not able to boot the VM from the .iso of ETBOOT, but then HOW did you managed to install windows within the VM as in step 3 of the tutorial (that assumes that ones boots the VM from the original XP/2003 Install CD or .iso image) ?
You can try using that CD/.iso instead of ETBOOT.ISO to boot and see if it can see the C: Virtual Disk/Hard Drive, starting (and not finalizing) a new or Repair install.
If the Windows install CD cannot see your Virtual Disk/Hard Drive, the problem is NOT in ETBOOT.ISO.
If it does, just reboot the machine after having changed just the .iso image to ETBOOT.ISO and it MUST see the drive.
If it does not, it must be some other setting you missed/set the wrong way.
Other than this, I'm really out of ideas....