Citizen Bob <spam@uce.gov> wrote
> Rod Speed <rod.speed.aaa@gmail.com> wrote

>> THERE ARE NO SEPARATE DEVICE DRIVERS.

> Here's the facts as I see them.

> 1) If I open a defragger (NT Defrag or Perfect Disk), I see two
> entries per partition. Both have a drive letter and one has the
> volume label, whereas the other is blank after the drive letter.

Says nothing useful about whether there are
separate device drivers for those two entrys.

> 2) This does not show up in Disk Management. However there
> are hidden devices sometimes because when I format a partition,
> it won't let me assign the drive letters for the hidden devices.

Says nothing useful about whether there are
separate device drivers for those two entrys.

> 3) In DiskPerfect I can expose the GUID for the device drivers,

Those arent separate device DRIVERS either, they are just separated DEVICES.

> and they are different for the two entries per partition.

Says nothing useful about whether there are
separate device drivers for those two entrys.

> 4) Every time I change the disk signature (using Win98SE fdisk /mbr) I get
> a message that I have to reboot because Windows has detected a new device.

Says nothing useful about whether there are
separate device drivers for those two entrys.

>> You've stuffed something up, presumably in the process of
>> using that abortion of a RAID, but it could just as easily have
>> been you use of whatever it was you used to clone the drive too.

> The problem was present before I used clones.

I didnt meant the clones for backup, I meant the cloning you did in
the process of setting that system up with that abortion of a RAID.
Using the hard drive manufacturer's ute from memory.

> That problem (corrupt NTFS partitions) was
> the reason I got rid of the RAID contraption.

The corruption may well be an entirely separate issue to the
extra entry for each partition since changing to FAT32 fixed
the corruption but not the extra entry for each partition.

>>> Also, in the Registry there is key that shows Mounted Devices.
>>> It has an entry for the hidden drive letter that can't be used.
>>> If I clear out that key, it becomes available.

>> Presumably something else keeps putting it back.

> If I could find what it is, I might be able to fix this problem.

> One poster suggested that I use RegMon (a Registry monitor that
> displays everything that goes on in the Registry) to track down the
> problem. The trouble with that is there would be literally thousands
> of records to sort thru.

Thats what the search function is for.

>>> I contacted the Product Line Manager in Taiwan and she was
>>> eager to work with me to find the source of the problem. But
>>> after a short period she turned cold - I suspect she discovered
>>> that there was something radically wrong with her product.

>> Or she decided that you were too bone headed to bother with.

> Why would you say that?

Because of the evidence I have seen of your bone headedness.

> If you knew me, you would know I am the complete opposite.

Pity about the evidence of your boneheadedness in your posts.

An absolutely classic example of that is that obsessive claim
that you have separate device drivers for those extra entrys
for each partition when there are no such separate device drivers.

> Are you sure you are not projecting.

Completely sure.

>> Kony clearly has.

> Kony doesn't appreciate what I am up against.

Yes he does.

> Anyway, there may be a misunderstanding about what he
> means by a "fresh install". I took it to mean that I have to
> reinstall all my applications, which is clearly a nightmare.

And we both kept rubbing your nose in the fact that that isnt necessary.

> Now he tells me in his last post that there is a way to do a fresh
> install without having to reinstall everything - and it is not an IPU.

And I told you that well before that, using the files and settings transfer wizard.

>> A retrospective abortion may well be the only solution.

> That is not a nice thing to say about my son.

That was a joke, Joyce.