You sure about that? I thought an XP recovery disc allowed an XP MBR to be made, oh well; best not to try it!
The only thing that would even remotely possibly make a XP MBR would be the recovery console. And that doesn't have a FDISK command; the proper way is FIXMBR.
In this case, it looks more like a DOS installation booting to run ghost, in which case FDISK (if present) would write a DOS MBR.
basically, for windows and DOS from windows 9x/ME and earlier, you would use FDISK /MBR; for Windows NT (including XP) you use FIXMBR. Except for Vista and Windows 7, since I've never had to run a recovery of any sort on those systems (it's probably part of the "repair" on the discs, though).
Of course, this little "recovery" disc is a bit strange- It's really just a shell around ghost. I was going to say I was surprised but then I saw this was an eMachines - (which also explains why they didn't create the menu properly, heh)
Another thing that half-confirms that this is a rather standard MS-DOS OS, rather then some sort of recovery console thingamajig, was the seemingly peculiar operation of "MORE". with Pre-NT "command.com" the pipe redirection character would be performed via the creation of some temporary files. Normally, these are created in the "TEMP" directory (that is, using the environment variable). However, when no TEMP variable is set, it just uses the current directory. In this case, since the installation is really running off of a read-only media, it can't.
Also, what on earth is this bit for:
My guess is the batch wasn't written by a human but by a program or something, which might explain that.
