Delphi Usb Drive Serial Number

by

128MB Flash Drive $3.55 Custom Logo USB 2.0 Flash Drives. Software program, whether it is written in Visual C, Visual Basic, Delphi, VBScript, Office macro,.

Is there a way to retrieve the USB path along which a USB flash drive is connected to? Acoustic alchemy american english rapidshare files 153773927. For example: in form of: USBFlashDrivePort(=ExternalHubPortIndex)-ExternalHubIndex(=RootPortIndex)-USBControllerIndex(=RootHubIndex) The reason I am asking is because I need to physically identify the USB flash drive when Windows report problem such as ‘this device can run faster if plugged in a high speed port’ or something like that. I sometimes plug in more than 20 USB drives (through hubs, of course) for file distribution purposes.

When Windows report a delayed write failed to a drive there is no way to know which physical drive it is refering. Is it possible at all? I’m using WMI for the first time and have seriously scratched my head at some things.

Per default, whenever something is weird I assume that I’m not getting it. But after seeing this page I’m convinced WMI is badly designed. Why is it necessary to do all this fancy extraction of DeviceID, replacing quotes, taking the thing after the = sign etc. Why isn’t there simply an attribute giving the DeviceID that you can use to do a simple query right after to get the device you are looking for. All the other stuff seems like something that is unstable if Microsoft ever changes the format of the 'Dependent' or whatever and it is a total waste of code.

It really amazes me how Microsoft could design a 'modern' API like this (it gets really ugly when you look at Win32_DiskDrivePhysicalMedia the sole purpose of which is to link Win32_DiskDrive to Win32_PhysicalMedia – which you can only take advantage of by doing the above weird parsing of the dage).

Here is my method. When answering a question please: • Read the question carefully. • Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. • If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome. • Don't tell someone to read the manual.

Chances are they have and don't get it. Provide an answer or move on to the next question. Let's work to help developers, not make them feel stupid.