## Setup a Virtual Drive (optional)

SDKs have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.

#### Setup a Virtual Drive for SDKs

1. To subst a drive, type on a command line:
   > subst drive_letter: path_to_kit
   For example:
   > subst M: C:\Symbian\S60_5_0_201012
2. On the command line type:
   >subst

   You should see the new virtual drive pointing to your kit. If the debugger tries to load a file it can’t find, it will look for it on the virtual drive. You can see this in the stack crawl. The stack crawl should give the full path of the file on the virtual drive the file was built on. The debugger will not be able to load the file until the correct virtual drive is specified.

   If this happens you can redo the virtual drive to use the drive specified in the stack crawl or navigate to the file using the existing virtual drive. From that point the IDE will add that path and recursively check folders for files it needs.

3. Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.

##### Other references

- Verify System Setup (Run-mode) Tutorial