Using _DIREXISTS with BitLocker encrypted drives

[hanness]

When checking for the existence of a drive letter, I have been using the _DIREXISTS function.

For example:

IF _DIREXISTS(D:) then
   PRINT "Drive letter D: exists on this system"
END IF

However, if a drive is BitLocker protected AND that drive is currently locked, then the _DIREXISTS for that drive letter will return false leading to the erroneous conclusion that the drive letter is available.

To work around this, if _DIREXISTS returns false, I always follow up by running a "manage-bde -status D:" (or whatever drive letter) via a SHELL command and capturing / parsing the output.

So, this leads me to my question: Is there any more foolproof way to determine a drive letter's existence? There is the _DIREXISTS function, as well as the _FILEEXISTS function, but no _DRIVEEXISTS function or anything similar as far as I can tell. My workaround works, just wondering if there is a more direct test of the existence of a drive letter.

[RhoSigma]

Using the WinAPI (I assume you are on Windows OS),

Code: QB64: [Select]

1. DECLARE LIBRARY
2.     FUNCTION GetLogicalDriveStringsA& (BYVAL bufSize&, buffer$)
3. END DECLARE
4.  
5. '--- get available drives once during your program init procedure ---
6. DIM SHARED allDrives$
7. buffer$ = SPACE$(112)
8. length% = GetLogicalDriveStringsA&(LEN(buffer$), buffer$)
9. allDrives$ = ""
10. FOR position% = 1 TO length% STEP 4
11.     allDrives$ = allDrives$ + MID$(buffer$, position%, 1)
12. NEXT position%
13.  
14. '--- in your program flow test drives whenever needed (returns false(0) or true(-1)) ---
15. PRINT DRIVEEXISTS%("A")
16. PRINT DRIVEEXISTS%("B")
17. PRINT DRIVEEXISTS%("C")
18. PRINT DRIVEEXISTS%("D")
19. END
20.  
21. '--- a quick test function ---
22. FUNCTION DRIVEEXISTS% (drv$)
23. DRIVEEXISTS% = (INSTR(allDrives$, UCASE$(drv$)) > 0)
24. END FUNCTION
25.  

[hanness]

Thanks, much appreciated.

I have to admit that I've never done anything using the WinAPI so I guess I better start educating myself on this :-)

[Pete]

Thanks, much appreciated.

I have to admit that I've never done anything using the WinAPI so I guess I better start educating myself on this :-)

You won't be disappointed, but if you make your own routines, be advised there is lag when you poll the Windows libraries, so if you don't get the results you expected, put a _delay .3 ( or some other suitable value) in your code, to let the API return a value before polling for that value in your code.

Pete