JIm,
>I trust the drive. It has performed flawlessly under SAFE MODE.
>It took a while but I finally figured out how to change it from Simple/Dynamic to Basic with a primary partition.
>I still believe that it's an OS problem. Something has gone awry and is screwing access in normal operaating mode.
>Its a 10,000rpm drive, just over 2 years old and one of those that comes with a 5yr warranty. I'd like to hang on to it rather than replace it with a slower 5000GB unit. Its low capacity also enforces a certain discipline on my usage.

your attitude resonates quite a bit with me - main difference probably I decided to employ redundant many disks JBOD'ed.
The tenacity to find that !§$%& bug eluding most others is working in the personal HW setup as well.
Also, there is the chance that it was NOT a HW failure but some OS screwup waitig to happen again...

>I continue to get intermittent availability in normal operation but full access/performance under Safe Mode.
>I wish I knew what OS components are involved and how to "refresh" them.
>I'll keep plugging away. I've done 3 formats and 2 re-populates already. one or two more isn't a real problem. I just need to have a good reason to do it again < s >

The line between having fun poking at HW and being in serious trouble can move FAST. I understand your hesitation of using a 10000 RPM as failsafe equipment sitting in your drawer - but I still believe the basic idea/reasoning is sound. Make a deal with yourself: at the first time the disk behaves badly after config to as a non-dynamic disk, get a new one.

PERIOD. (think of it as insurance and compare to time spent)

Work on the new disk for 2 weeks up to a month WITHOUT the Raptor to make sure it is NOT an OS twitch. (You are stil doing diagnostics, you haven't failed <bg>) If everything is working flawlessly, use the Raptor in a redundant or temporary manner. Hints:

If you are using *large* vfp cursors, set only vfp's temp dir to that disk, separating data and cursor. Creating cursors from your backdrop data is helped A LOT. Spoil your fox!

create a multi-boot machine using xxClone to copy your OS back to the raptor and work from there as long as no toubles surface. In case of trouble, just switvh to the slow new HD <g>. But leave your important personal data OFF the raptor.

I am sure in your case this will not be totally applicable, but a variant based on the same principle will be. Don't focus on not loosing the "battle" but to pick the "battles" wisely.

regards

thomas