Creating and Removing Virtual Drives

Its Friday morning, the weekend is sparkling in front of you and you boot up your work computer only to find that something in the system has hiccuped and nuked all your virtual drive settings.

Even if you don't have an environment batch file or what have you to save the day, it's an easy fix (as long as you know what the virtual drives were linking to!)


Creating a Virtual Drive:


1-Work out what folder you want the drive to link to- eg: c:\projects\myProject\art\
2-Open the command prompt
3-Type in:

subst z: c:\projects\myProject\art\

Presto! z: now links directly to that folder! You can use any drive letter as an assignment as long as it is not currently in use by the system. Good candidates are x:, y: and z: drive letters.

Removing Virtual drives...

Oops... I made a mistake in my path and now it links to c:\whoops\this\is\wrong, and when I try to fix it it keep telling me 'Drive already SUBSTed'

Once again, easy fix! To remove a virtual drive after it has been made, type this into the command prompt...

subst z: /d

And your virtual drive will be removed. This won't delete the data in the drive, just the link to the drive itself. Now z: is free to be linked to the correct folder.

-Pete

Comments

Post a Comment

Popular posts from this blog

Calling Python from Substance Painter

Here is a quick code snippet for calling a Python script from Substance Painter and parsing the results. The in/out is very simple, but serves as an example of using the alg.subprocess.check_output function to bridge the JS api and your own Python scripts. // This can be called from the QML UI, or elsewhere in the plugin code. function GetAllFilesInDirectory(root) { if (root == undefined) return; // I put my scripts in a relative path to keep my plugin tidy. var script_path = "Scripts/FileUtils.py"; // Gathering files var ret = "NOSTRING"; try { // The arguments are used as parameter inputs to the Python script. This requires some planning // and well communicated conventions, but works well enough. ret = alg.subprocess.check_output( [ pypath, // Absolute path to interpreter. script_path, // Relative path to the py script. "log_files_of_type", // sys.argv[1], in this case the python ...
Read more

A Quick Checkin- Clion, Unreal and Mac

Image
Super quick check-in. Hello world! For the last year or so, I've been working with Echtra Inc. on a great project as a Tools Engineer/Technical Artist guy. The project is using the Unreal Engine, which I like more and more every day. On Windows, C++ plus Visual Studio Pro and Visual Assist is a great combo, and I happily churn through my daily tasks without fighting the tools too much. Not so on my Mac at home. Programming in Unity on a Mac is great! Mono Develop isn't amazing, but it isn't terrible. But Unreal on a Mac. I want it to be fun, I want it to be possible, but I just can't get myself to like, let alone enjoy, XCode. On that, for anyone thinking "well, you could just use blueprints..." etc, I feel it's too much of a shackle to not be able to just dive into the guts of it. C++ or bust. So anyway, I recently adopted PyCharm at work and really enjoyed using it for my Python tools. I noticed that JetBrains also made an IDE called CLion , and they ...
Read more