Enumerating CD Devices on Your System

This short code sample shows how to determine all the CDRom drives you have connected to your computer using the WinAPI.

Although this can now be done with the new FileSystemObject that comes with VB6 (and as an extra with VB5), this is how to get the drives through code when the target machine may not have the SSCRUN.DLL.


Screen-Shot

The code is quite simple and uses the GetDriveType and GetLogicalDriveStrings Windows API calls.


'
private Declare Function GetDriveType Lib "kernel32" _
        Alias "GetDriveTypeA" (byval nDrive as string) as Long
private Declare Function GetLogicalDriveStrings Lib "kernel32" _
        Alias "GetLogicalDriveStringsA" (byval nBufferLength as Long, _
        byval lpBuffer as string) as Long
private Const DRIVE_CDROM = 5
'
private Sub ListCDROMs()
    Dim sDrives as string
    Dim sDrive as string

    sDrives = Space(255)
    sDrives = Left$(sDrives, GetLogicalDriveStrings(255, byval sDrives))
    While InStr(sDrives, "\")
        sDrive = Left$(sDrives, InStr(sDrives, "\"))
        If GetDriveType(sDrive) = DRIVE_CDROM then
            List1.AddItem "(CDRom) " & sDrive
        End If
        sDrives = mid$(sDrives, len(sDrive) + 2)
    Wend
End Sub
'

Download Zipped Project File (3k)



Comments

  • More helpful for me

    Posted by Legacy on 07/25/2003 12:00am

    Originally posted by: Mohan

    Thanks lot to provide code. Your e-help is much appreciated.
    

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Hurricane Sandy was one of the most destructive natural disasters that the United States has ever experienced. Read this success story to learn how Datto protected its partners and their customers with proactive business continuity planning, heroic employee efforts, and the right mix of technology and support. With storm surges over 12 feet, winds that exceeded 90 mph, and a diameter spanning more than 900 miles, Sandy resulted in power outages to approximately 7.5 million people, and caused an estimated $50 …

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds