Access data on RAID0 HD from old computer?

Nope. Thats the risk you take on when you use raid 0. If something happens that data is gone forever. Its sometimes possible to recover some data with recovery software, but I doubt you will get much if anything.

Thank you. I will trying this out tomorrow.

SUB MESA IS MY NEW HERO!

By booting with Linux, I was easily able to view the contents on my RAID 0 drives, which were from another chipset entirely. (See my OP.)

I understood that I would not be able to boot up the old system in toto (given what I had done), but I did wonder about this idea that the data on the drives were totally inaccessible. In my case, there was not a question of damage or corrupt drives. Simply, that I had naively thought that I could transfer the drives from my previous system, which was an AMD CPU & MSI mobo, to my new Intel CPU/Asus mobo without a thought about compatibility or methods of coupling them.

However, though I have little knowledge, the idea that these drives (no matter how they are configured) are simply the same magnetic material in the same mechanism left me baffled as to how they were complete inaccessible through non-esoteric means, i.e., "data recovery methods."

Anyway, thank you, Sub Mesa for your knowledge of theory and practice and I hope your message becomes more well known. I know that I will pass it on.

Now that I have access to these RAID 0 disks (which were set using NVRAID/AMP chipset/MSI mobo/Vista), is there anyway to have them recognized by new set up (Intel/Asus mobo/Vista) without a standard reformating? (Which erases all the previous data, no?) When I access it with my current system, it asks if I want to format the drive, which is to be expected.

I cannot figure out what file is the raid file for my drive in the /dev directory for the mdadm package --detail command (where your example has sudo mdadm --detail /dev/md0 and md0, I assume, stands for the filename. There's nothing obvious immediately in /dev. I tried /dev/mapper/NVIDIA_dbjabbcb and /device/[the long ID number]. The message I got for both was does not appear to be a md disk. So, I don't know if this is a legit message or if I am just not using the proper file in the /dev.