Basic Steps for Dual Booting NT;2K;XP with something else (like Win98 Recovery):
Please don't be fooled by the number of words here. Once you understand the process this is incredibly simple.
Small C: (5-20Gb) for System, Programs, and user settings. Large D: (10-60Gb) for ALL user data. Small (100Mb) Win98 Dos partition for recovery boot.
Boot to main operating system, or recover partition via NT Loader boot menu.
1. Install main operating XP (or NT;2K) system - selecting to make C: partition NTFS, and only ~25% of total disk size.
(I use a 10Gb C: on a 30Gb drive, or 15-20Gb c: on an 60-80Gb drive. Depends on how big you think your C: will need to be. Only YOUR experience will tell).
1a. If C: is already taking up entire hard disk use PartitionMagic;BootIT;Acronis; to shrink as required. Note: We've had the odd laptop fail to boot after resizing. In this case expand c: back to original size, confirm successful boot, and try a different resizing tool. Possibly someone else will have an answer for why the occasional PC fails after a shrink of c: I'm assuming it has something to do with SWAP file relocation/corruption?
2. Boot main operating system, and use Disk Manager (Right-Click My Computer => Properties) to create & format (quick format - or you'll be waiting an hour or more) the user data drive (d: NTFS - and a Primary partition - Name=Data).
Make the size of this partition "everything that is left minus ~100Mb"
3. Create the 3rd PRIMARY partition - 100Mb or whatever is left. Format this as FAT32 Name=Recovery
Drive Letters: (This is the way I do it, however it's up to you)
C: - always allocated to Windows System partition.
D: - 2nd partition - User data
No Drive Letter: - 3rd partition (Fat32). Left without a dive letter to stop either virus or users mucking around in there!
Z: - CDROM. We make this Z (instead of E:) to allow USB keys/camera's/Cell Phones to be allocated e: (F: is our 1st network drive). If we use e: for CDROM then removable media often is not allocated a drive letter as f;g;h are already taken by Network mappings. As our users are "restricted users" there's not much they can do to fix the problem - so Z: it is....
4. If you're following my instructions for doing GHOST backups of c: to file on d: then create a directory d:image for storage if ghost images.
This directory can be hidden to stop users from mucking around with it. I have not played with permissions to stop users getting in there - but that might be worth a try. I don't think that will affect the ghost process. Not sure without testing.
5. Boot from a Win98 floppy (Sorry... Dos 6.22 is not capable of booting further up the drive than 2Gb, so you need Win98 boot floppy).
6. Confirm that c: is empty, and only around 100Mb. Should be, as Win98 DOS won't see the NTFS partitions.
7. Format c: as system - ie format c: /s (that was 'slash s' however this forum removes the slash).
8. Type the following... (don't muck this bit up.. These instructions assume that the Win98 partition is the 3rd partition, and others are NTFS - see footnote 8a).
Note: Assume <enter key> at the end of each line. Anything looking line '0' is a number (not a letter).
L 100 2 0 1
8a. Note: in the line "L 100 2 0 1" the 2 (hex) refers to the drive that you're dumping the boot sector of. 2=C, 3=D, 4=E etc. Since we booted via a 98 floppy, the NTFS partitions are hidden, and the Win98 partition will appear as c:
This will create a file called "bootsect.dos" from the boot sector on the Win98 partition in the root of that partition.
9. This file needs to be copied to the root of your nt;2k;xp system drive. I'll leave the how up to you.
10. reboot the PC (into NT;2K;XP) and In the hidden & readonly file C:BOOT.INI, add the line:
c:bootsect.dos="Win98 Recovery" (or whatever you wish to call it).
We also usually change the timeout from 30 down to 5 sec, so that if a user isn't specifically looking for the boot menu under our instruction then they'll usually miss it.
Credits... (and another safer? way of creating the bootsect.dos file):
11. Test it... On startup, you should now be able to boot successfully to either Windows (NT;2K;XP) or DOS (Win98).
You can now use this Win98 recovery partition for an automated GHOST backup/restore of your system (c:) from an image file located in d:image.
P.S. Important Note:
All our users are Domain users who's passwords change regulally. When you or they create a backup image, it's important that the user records what their current password is . Otherwise - on restore you have a good PC, but the user can't log on (we're assuming that the user is away from the network, on the other side of the world).
An addidtional issue - If the restore image is fairly old, the PC will no longer talk to the domain when the user plugs into the LAN. I assume that machines periodically change their machine account passwords - and that what we've done is to restore the machine with an old password.
This is not an issue while the user is still overseas. However once back on our network we occassionally need to remove the machine from the domain, and re-join manually. (Possibly we could just reset the machine account in AD).
This is a small price to pay for getting the user up and running after a fatal op system failure while they're overseas.