Only to (hopefully) contribute to the communication, dencorso never stated he actually attempted to boot from the new thingy, he attempted to access it as a secondary drive from an already booted XP SP3.
Sure! I think that if I cannot actually recognize and use the disk normally in an already booted XP, then all attempts at booting from it ought to be futile. Therefore, I set my goal at getting the disk working on XP before even thinkinh of attempting anything more complex, of course!
... he attempted to access it as a secondary drive from an already booted XP SP3, which - with no offence whatever implied to dencorso - very likely it is not a fresh installed XP SP3, but rather an existing installations where hundreds or possibly more drivers, programs and what not installed and removed, registry hacks, original or modified updates, etc. has been run.
No offence taken. And, sure, this installation is from Jan 1st, 2014, which makes it one of my newest installations. As you may remember, I never reinstall an OS, unless the initial installation went wrong. By contrary, I make partition images obsessively, and when anything starts to blork, I redeploy the latest (or, rarely, an older) backup. That's also my preferred method for removing something I decide to install but, then, regret havng done so. Therefore it surely is a very complex tweaked install, with many drivers and countless possible conflicts with the new driver and/or hardware. And the same is true of the Win 7 SP1 installation in which the drive worked. Now, if I don't get it to work on this XP SP3, I may move the drive to another machine or decide to sell it. I have, after all, no real need for it, and installed it just for the lulz. But, for now, I think it's too soon to give up, so I intend to try to get it to work some more.
that on my x58 board it was also not possible under XP
to have a nvme disk as codevice, same message (Code 10).
PS: I noticed, that some PCIe slots are connected with each other.
This can also give the "This device cannot start. (Code 10)" message.
EDIT: Asus P8Z68-V LX
Der PCIe x16_2-Steckplatz teilt die Bandbreite mit dem PCIe x1_1- und dem PCIe x1_2-Steckplatz.
It may be the case here, too. And yes, I had seen that. I initially installed the adapter on PCIe x16_2 (which is actually a x4 in a x16 slot), but it refused to work (because I have an USB 3.0 card in PCIe x1_2, I presume). So I moved the adapter to PCIe x16_1 (which is truly x16 and does not share bandwidth with any other slot, it's the one intended for a graphics card), and then it started working, at least on Win 7 SP1.