Checking for Drive Media

Screen-shot

This program checks the removal and CD-ROM drives for Diskettes, you can either specify a drive or let the program checks all drives on the computer.

The idea of checking disk existance depends on changing the current path to the path of the drive, if an error occurred (with the code 75), that means the computer isn't able to change the path. Consequently, there is no disk in the drive.

The project consists of:
  1. A module where all the functions , declarations and constants are found
  2. A form to demonstrate how to use the module.

The programs input is either the letter of the drive you want to check or just let the program check all drives.

The output is a msgbox specifing whether there is a disk in the drive or not. The program checks the removal or CD-ROM drives only.

The attached zip file contains all neccessary files, the ScreenShot file is a screen shot of the program in case you need it.

Download zipped Project file (3k)



Comments

  • Help From You

    Posted by Legacy on 05/10/2001 12:00am

    Originally posted by: Asif

    I want to have security to my priject
    for the purpuse of external security i want Key Disk
    I am unable to locate code for that your website is not working properly so please send the code through e-mail if possible do me this faver. i will be grateful to you

    Thank you

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

Top White Papers and Webcasts

  • On-demand Event Event Date: April 22, 2014 Database professionals -- whether developers or DBAs -- can often save valuable time by learning to get the most from their new or existing productivity tools. Whether you're responsible for managing database projects, performing database health checks and reporting, analyzing code, or measuring software engineering metrics, it's likely you're not taking advantage of some of the lesser-known features of Toad from Dell. Attend this eSeminar with Dell Software's …

  • 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