Directory Linker

New Post: linking in one direction only?

mlg — Tue, 30 Oct 2012 17:25:50 GMT

I am trying to install Google Chrome on a drive other than their only option, which is C:. My C drive is a relatively small SSD which I don't want to have constantly written to, and filled up with browser data.

I have been able to get the actual application moved to my E drive, although the application files still remain on C as well.

My real problem is that usage files constantly grow: cache, bookmarks, history etc. These files are located in the user directory of C and the path is long and windy. I've tried using mklink in the command prompt but usually land up with some error about its not liking the path.

Using dirlinker and telling it to delete and/or overwrite the files on the target, I was able to create the data, which Google has on C:/users/ etc. on my E/users etc. according to the link. However, when I use Chrome, the user files are written to BOTH on C/users/ etc. and on the target E:/users/etc.

Is there a way to ONLY have the user files updated on the target (E) and have the folders stay on C so that Google finds them there - or should they be deleted from the subdirectory folder where the link resides, forward?

Hope this is clear and that someone can help me clarify it further. Thanks in advance.

MLG

Created Issue: Dirlinker deleted entire directory [4]

deejaynyc — Sat, 02 Jul 2011 02:23:10 GMT

I was attempting to set up a symbolic link between two directories using dirlinker. The operation indicated that it had failed, and asked if I wanted to undo the operation. I said "yes," and it appeared to reverse itself. When I went back, the original directory seems to have completely disappeared. It was not even sent to the Recycle Bin. Where might it have gone?

DJ

New Post: it doesn't work on storage server 2008 R2

pfei — Wed, 22 Dec 2010 15:38:41 GMT

Description:

Stopped working

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: dirlinker.exe

Problem Signature 02: 2.1.1.0

Problem Signature 03: 4d0e57a3

Problem Signature 04: DirLinker

Problem Signature 05: 2.1.1.0

Problem Signature 06: 4d0e57a3

Problem Signature 07: 66

Problem Signature 08: b

Problem Signature 09: System.IO.FileNotFoundException

OS Version: 6.1.7600.2.0.0.272.7

Locale ID: 1033

New Post: it doesn't work on storage server 2008 R2

pfei — Wed, 22 Dec 2010 15:36:31 GMT

dirlinker it doesn't work on storage server 2008 R2.

Commented Issue: does not work with network paths [3]

WillC — Mon, 20 Dec 2010 08:52:22 GMT

Great app. But I'm trying to link to a newtork location:
eg. \\netdisk\share\Pictures
but the app puts a small red icon saying "Please enter a valid path"
The path IS valid!! In fact, the textbox field automatically populates suggested locations as I type the pathname, so windows is recognizing it properly.
Sadly, I have to use cmd and enter the mklink command-line which works fine. So I KNOW the path and syntax is correct. This app doesn't work for it. Bummer because this is the perfect tool to simplify the operation.
Comments: Hi, Thanks for pointing that out, I've just uploaded a new version that should relax the validation and allow network paths. Regards Will :)

Edited Issue: does not work with network paths [3]

WillC — Mon, 20 Dec 2010 08:52:22 GMT

Updated Release: Directory Linker 2.1.1 (Dec 20, 2010)

Willc — Mon, 20 Dec 2010 08:43:06 GMT

Directory Linker 2.1 with one bug fix:

Relaxed validation in the UI to allow network paths to be entered.

Released: Directory Linker 2.1.1 (Dec 20, 2010)

Mon, 20 Dec 2010 08:43:06 GMT

Directory Linker 2.1 with one bug fix:

Relaxed validation in the UI to allow network paths to be entered.

Updated Release: Directory Linker 2.1.1 (Dec 20, 2010)

Willc — Mon, 20 Dec 2010 08:42:29 GMT

Directory Linker 2.1 with one bug fix:

Relaxed validation in the UI to allow network paths to be entered.

Source code checked in, #05fa3414c6cf

Will — Sun, 19 Dec 2010 14:33:40 GMT

relaxed validation rules

Commented Issue: does not work with network paths [3]

mkdoggett — Fri, 17 Dec 2010 20:34:24 GMT

Created Issue: does not work with network paths [3]

mkdoggett — Fri, 17 Dec 2010 20:31:36 GMT

Edited Feature: Problem with kernel32.dll [2]

WillC — Wed, 05 May 2010 06:30:18 GMT

Im using Windows Xp, and i was creating a symbolic link from a desktop folder to another folder in the Application Data folder.

the program is able to reproduce all the steps, but in the end it a message box appears:
"An error occured:Unable to find an entry point named "createsymboliclink" in dll 'kernel32.dll'... do you want to und any changes made?"

And if i click in yes it erases my target folder ( which wasn't empty)....

I would deeply appreciate any comments on you this could be solved please!!

BR

Commented Issue: Problem with kernel32.dll [2]

WillC — Wed, 05 May 2010 06:29:44 GMT

Created Release: Directory Linker 2.1 (May 04, 2010)

Willc — Wed, 05 May 2010 06:26:12 GMT

This release introduces XP support, more information about all features can be found at http://www.humblecoder.co.uk/?p=141

Released: Directory Linker 2.1 (mai 04, 2010)

Wed, 05 May 2010 06:26:12 GMT

This release introduces XP support, more information about all features can be found at http://www.humblecoder.co.uk/?p=141

Updated Wiki: Home

WillC — Wed, 05 May 2010 06:22:24 GMT

Project Description
Directory Linker is a small Winforms application that allows the user to quickly and easily create symbolic links in Windows Vista and Windows 7 for files and folders. (Note XP is not supported)

The process for creating a symbolic directory link for a folder that already exists is a bit clunky, you have to:

Create the target
Copy any existing content to the target
Delete the folder you want to be a link
Start cmd.exe and then enter the mklink command along with the full paths of the folders you want to link

DirLinker helps with this, it is very basic UI that allows you to enter where you want the link and where you want to link to. You can just delete the link place or copy the contents over first. Use these options at your own risk, I will not be held responsible for any data loss.

As of version 2.1, DirLinker also supports the creation of symbolic file links and creating folder links on Windows XP

Features

Create symbolic folder links
Create symbolic file links (Only on Vista or later)
Move or delete a file/folder before creating a link, making it easier to create a link for a file/folder that already exists
Undo support, if anything goes wrong we can put it back.

Requirements:

XP or later (It has been tested on Vista x86 and Win7 x64)
.NET 3.5
Admin rights

(This is an adaptation of my original blog post about dirlinker, http://www.humblecoder.co.uk/?p=50)

Source code checked in, #24c5a1da6489

Will — Wed, 05 May 2010 05:57:58 GMT

Completed

Source code checked in, #ef235682745e

Will — Wed, 05 May 2010 05:57:18 GMT

Merged XP support back into mainline

Source code checked in, #beb63c4566c5

Will — Wed, 05 May 2010 05:56:05 GMT

Made XP folder links work, added validation to stop it trying to link files