Not sure what you're asking but here's my best guess: both internal hard drives (C & D) are NTFS format. C contains my OS (XP) and came with the computer. D is a larger hard drive that I use to manually back up files, for extra storage, etc. I don't think you are asking about the two CD/DVD drives; however, for the sake of explanation - they are set up in the standard master/slave configuration.
Important note: If you've installed a Service Pack, you need to insert your Windows XP CD with Service Pack integration (called as the Slipstreamed Windows XP CD). If you don't have one, you may point to the %Windir%\ServicePackFiles\i386 folder for a recent version of the system files required during WMI repair. Or you may create a slipstreamed Windows XP CD and insert it when prompted.
Click Start, Run and type the following command, and press ENTER:
Insert your Windows XP CD into the drive when prompted. Repair process should take few minutes to complete. Then restart Windows for the changes to take effect.
Bottom line - computer booted faster than it has in a while; however, not only does V3 not recognise both my hard drives, now it does not recognise one of my dvd drives (it did before WMI rebuild).
Additionally, backup did recognise all my drives in V1 but to the best of my knowledge (memory) it has not yet worked properly with XP in either of V2 or V3.
I can't believe Norton's can't fix this hard drive problem. All programs, including Windows Explorer, see the drives. Why not Norton's? Maybe they have a priority is to sell more online storage space. I also think that it was fine in v1, and then lost all my drives in v2 and v3
Currently I have two desktops and a laptop running Norton's 360. With another child going off to college this fall, I'll be adding another laptop (thus another software purchase). If this problem is not fixed soon, I will be switching security packages, and going with Roxio's BackupMyPC. I hope Norton's is listening to the user community, because it seemed that their help desk was hoping Me and my problem would just go away. I'm not one to keep switching applications, but I'm not giving this situation much more hope.
This is a known issue. Let me give a brief explanation of what is happening here.
Beginning In N360 v2, we started using Microsoft's WMI architecture to detect system drives. Not many programs use this, but it provides more detailed drive information than otherwise available. Even windows explorer does not use WMI, so it makes sense that you would see no problems there.
WMI is a very fast and useful way of quickly retrieving information about the computer and the operating system.
However, it is possible for the WMI repository to become corrupted. Microsoft offers no explanations as to why this occurs, but they document several supported (and some unsupported) ways to repair a corrupt WMI database.
You can access WMI's user interface by right-clicking My Computer, and selecting 'Manage'. Then select 'Disk Management'. This screen should show all your drives, as well as their drive letters and volume names. In my experience, users having the same difficulty as you do not see all the correct information on this screen.
Some things to try, are the 'Action' menu items, 'Refresh' and 'Rescan Disks'. If they are not helpful, you could try bringing this issue to Microsoft, but their usual response is to reinstall the OS.
I'm sorry I don't have a more optimistic solution to this issue, but on the bright side, we are looking for alternatives to WMI for the next version of N360.
Thank you for the reply. Not sure why Norton's help line didn't do any followup with my call. Especially, since this is a known issue.
I tried your suggestions. My Disk Management window does currently show all drives correctly, I did the "refresh" and "re-scan" operations, and nothing really changed, so unfortunately, I still have the problem.
I would think that Norton's would come out very quickly with a fix for this problem by issuing a patch. The issue seems to be with the last two releases (v2 and v3). I do not want to wait to again purchase a new release for a potential fix to this problem. I need a guarenteed fix and a reliable backup program now.
Maybe you can put some presure on the development team, before myself (and others) find the need to switch to an alternate solution.