Incorrect drive index order

Qvae · **Joined:** Tue Sep 23, 2008 3:52 am **Posts:** 58

Or maybe that is just how you set it up for some reason. But the index order of the drives seems to be incorrect. Ex. My application grabs the order of the CDROM in the same order as the computer's System Information -> Components -> CD-ROM has it. Drive E on index 1 then Drive F on index 2. However, when I grab the CD-ROM drive list with my app, I have to reverse the array so it lists the drives as F on index 1 then E on index 2, for things to match up and work correctly. Was the order purposely reversed in "X", or is this a bug?

anton (staff) · **Posted:** Tue Nov 25, 2008 12:23 pm

It is not a bug it's the way Windows works. Devices symbolic links like Cdrom%d, Tape%d and PhysicalDrive%d can have "gaps" in numbering (PnP result). So 0,1,5,10 indexes are absolutely normal.

Qvae wrote:

Or maybe that is just how you set it up for some reason. But the index order of the drives seems to be incorrect. Ex. My application grabs the order of the CDROM in the same order as the computer's System Information -> Components -> CD-ROM has it. Drive E on index 1 then Drive F on index 2. However, when I grab the CD-ROM drive list with my app, I have to reverse the array so it lists the drives as F on index 1 then E on index 2, for things to match up and work correctly. Was the order purposely reversed in "X", or is this a bug?

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Hello,

We have implemented sorting for the list of devices. So .. the next version of the StarburnX (10.5) should return list of devices in the correct order!

Regards,

Dmitry

#1 Burning Software

Incorrect drive index order

Who is online