A friend ran Norton Ghost 2003 for me to move XP SP1 and everything from the "C" SCSI boot drive to a "G" 120 GB WD drive. Unfotunately, he's out of town so I'm unclear what all the steps were and problems encountered. Also, unfortunately, the "G" drive that Windows and apps were moved to had other installed programs an data files which he said he'd back up first. That said, he didn't modify the boot sequence in BIOS, nor made "G" active first; so I've been fiddling with it to try and get things fixed. Here's the initial Q I posted to get him prepared to take these actions for me. G was NTFS, other 3 drives are 2 SCSI, one external IOMEGA were all Fat 32. When I checked things out this morning and encountered tons of errors and problems, noted all were Fat32... more below
Some problems now are:
1) External "H" drive is a Firewire connection to 120 GB external Iomega drive; this disappeared (not visible in disk management), though I can see it under hardware and device mgr.
2) At first boot and twice thereafter, chkdsk runs on C (old SCSI system drive) no problems found
3) Saw that sys was upgraded to XP SP2, but after reboot and some errors again on entry point not found and citing ntdll.dll for things like McAfee Firewall, shlwapi.dll and others too numerous to mention and another reboot, reverted back to SP1 .... HUH?
4) Know he did a lot of things to try and fix problems given what I've seen in terms of applications and interfaces which had moved; so restore points probably a disaster in terms of trying to recover old things.
5) unregmp2.exe entry point not found again, ntdll.dll
6) Event logs show svchost event 1000 ntdll.dll 0x00010d3, service control mgr event 7032 and on and on.
7) Update = generic host process for win32 services problems - winmgmt events 10 and 24, cites root and 0x80041010.
And more... Before I explain the nightmare of events so far and clutter everyone's mind, think I'll leave it here for insights.
ASUS MB, current BIOS, Adaptec 29160N SCSI card; 2400 Mhz P4 with 1024 RAM, changed the boot order in BIOS to the newly cloned G drive; changed disk management for G and System drive and made it active (which it wasn't).
The H, external firewire drive appears again (sometimes).... YIKES.