Please Help Me Understand This Windows Partition Behavior....

Hi Guys,
 
I rebuilt an XP DAW and the main disk has 2 partitions. However when I use an older bootable version of Ghost it doesn't see things like XP does.  In XP they are seen as C:SYS_VOL and D:SAMP_VOL, both reflected as primary partitions.  All this is what I would expect.  However Ghost sees the system partition as NO_NAME while the other partition appears as expected (SAMP_VOL).   I don't believe this to be a problem within Ghost, rather there is likely something not properly written on the MBR/Partitions to enable Ghost to understand the system partition name/label.  Any ideas how I can get the system partition to be correctly reflected in programs outside of XP such as Ghost? 
 
Sonic

New hard drive.  It is SATA but the BIOS is set for Legacy emulation so all software uses it as a conventional ATAPI/IDE type interface.  (Hope I said that right, but I'm sure you can at least understand what's going on)
 
It is formatted with FAT32.  System partition is 10GB and sample partition 50GB.  In my initial testing of the DAW rebuild process I ended up used different tools and approaches to partitioning and formatting the drive.  So this current case is not a "virgin" partition scenario.  In some instances I let XP OS installer do the job, in others I used a Western Digital tool, or DOS command line. And of course the disk manager inside XP. So I can't say for sure how this specific instance was partitioned & formatted.  Only that whatever was used was in the realm of industry-standard stuff.  I'm pretty sure in this specific situation I used the DOS command prompt from within XP recovery mode to format the system volume in order to blow away the preceding XP test-OS, and then used the XP installer to format it again during re-install.  
 
Sonic
 
 

No, the issue isn't the drive being SATA, Ghost and everything else sees it just fine and the partitions are working fine.  But outside Windows, any DOS/Win98 type bootable utilities seem not to be able to recognize the NAME of the system partition.  It comes up as NO_NAME, while the other partition's label is seen just fine. So something is going on, but I don't understand what.  Not only do I need to see the system volume name for ease of use when imaging, etc I also want to understand what is behind this anomaly so I don't have some unanticipated surprise down the road once I put this machine into use.  I'm assuming there is something missing, or written incorrectly, in the MBR/partition table.
 
Sonic

That was my next "silly question". Occam's razor.

It seems there may be some issue in early disk-based utilities.  I found some threads on the web about this but couldn't find a resolution.  Seems people tried to use some utiliies to re-print the MBR/Partition but no-one ever responded back as to what they actually used to do it nor the details of how.
 
Somewhere in the 2000-2003 range there was a time where the Windows NT based PC's were laying down certain MBR/Partition & FS info that some utilities, including Ghost 2003, could not understand.  Or rather maybe were expecting something different, at least as far as the Volume/Label goes.  I actually found a neat little stand-alone program from that era that also reported the same "NO NAME" for the partition in question.  It's probably as simple as just getting a tool to read the sector, change the name, and save it back.  But I have no idea where to find such a thing, that is also user-friendly.
 
Did I mention I really hate computers....?   

Ok Guys, I figured this out, and it is useful information because this is a rather common issue believe it or not.  I'll do my best to describe all the research and solution, but it will be in somewhat layman's terms as I am not the most uber-technical, so for you super-geeks on the forum please cut me some slack if I say something not quite precise.
 
So, from what I gather, at some point Windows began changing the way it was storing the "Volume Name" that it portrays to users in Disk Manager.  In other words, it is apparently not stored any longer in the same FAT32 boot sector like used to be the case.  I didn't waste time finding where exactly, but it is apparently stored some place else.  This is why Windows and other more modern tools will reflect something different than what is in the actual boot sector.  But the reality is, depending on HOW the partition was formatted, it may even have "NO NAME" stored in the boot sector.  And this is why, when using tools that actually read the literal boot sector, it does NOT reflect the "Windows" Volume Name as you'd expect.
 
Ghost 2003 in particular is a PITA about this because it starts out asking to select a source partition from a provided list - but it uses the actual boot sector information.  So you will tend to see something like DRV1_VOL1 and DRV1_VO2, or the now infamous NO NAME.  Yet when it then next asks to select the target for the image file it portrays a list of volumes as Windows would normally represent them.  For example C:SYSTEM_VOL, D:AUDIO_VOL.  So it is very schizo and confusing.  And then if you also have a NO NAME volume thrown in the mix it really confuses matters even further for the user.  So you can now probably appreciate why it is important to have the boot sector volume names be something sensible & consistent, if not outright matching, the Windows volume names.  
 
Why sometimes does a volume end up with NO NAME in the boot sector you ask? Well, from what I can see, this happens when you use some utility that doesn't bother to ask about a volume name, or if you run the Format.exe command from the command line and don't bother to use the /v switch.  The default ends up as NO_NAME.  There are a variety of ways it might happen actually.
 
So then how do you fix this?  Well, I am still searching for a more tailored stand-alone solution, but for now have managed to find a neat program called Active@ Disk Editor. It is free and can be found here: http://www.disk-editor.org/  It isn't very large, installs quickly and allows incredible control over the entire disk, quite an amazing piece of software.  But you need to take time to understand it since it can be very dangerous if you start making changes and saving them without understanding what you are doing.  To solve the particular problem under discussion is quite simple: Just load the FAT32 boot template and then Navigate to each of the boot sectors and look for the Volume Names.  Then set the Editor to Enable Changes, make the changes and save.  And be sure to also alter the boot sector copy as well.  Then repeat this for each partition that needs changing, or that you want to have match the Windows volume names.   This way, when you go into any disk or imaging tools in the future everything will always make sense.  As I said, I'm hoping to find a smaller, safer, simpler, standalone utility that will allow for volume name changes to the actual boot sectors.  So if any of you guys know of any such tool, please share. 
 
Hopefully I've managed to contribute something useful back to the forum after all the wonderful help people have provided on my DAW rebuild journey.  
 
Kind regards,
 
     Sonic