symbolic links are gone after reboot
Started by Walter
Walter
symbolic links are gone after reboot 03 September 2013, 21:46 |
I've just few days experience with RAM disks so maybe there is already solution to my problem but I just can't find it.
I have a freshly installed Win7 x64 system with 16GB of RAM
For start I've dedicated 2GB of RAM for RAM Disk and it's mounted on boot
I've moved IE temp files to it, Win and User temp files also
I have 2 questions:
Will "mounted on boot" option resolve problems with updates and software that require restart during installation?
I'm trying to move Flash player and windows media player temp files to by creating symbolic links but those links are gone after reboot.
I've used junction and "mklink" with no avail
Is there any solution to this?
example of commands:
junction "Y:\Flash Player" "C:\Users\*me*\AppData\Roaming\Macromedia\Flash Player"
mklink /D "Y:\Flash Player" "C:\Users\*me*\AppData\Roaming\Macromedia\Flash Player"
I didn't create any image on RAM Disk because of speed during boot and shutdown.
Best regards,
Walter
symbolic links are gone after reboot 03 September 2013, 22:19 |
Admin Registered: 18 years ago Posts: 3 568 |
QuoteWill "mounted on boot" option resolve problems with updates and software that require restart during installation?
No. However, there aren't many applications that require temporary files to be present after a reboot. I myself have been using a volatile RAM disk for Windows temporary files for a couple of years without any major issues.
QuoteI've used junction and "mklink" with no avail Is there any solution to this?
I have just tried this and it worked okay. I created a boot-time RAM disk on E:\, then created a symbolic link with mklink /D as mklink /D test E:[/b] and the test folder kept pointing at E:\ after a reboot.
Make sure you're using the latest version of RAM disk (3.4) which came out yesterday as it may be a fixed issue.
Walter
symbolic links are gone after reboot 03 September 2013, 23:21 |
-------------------------------------------------------
> Will "mounted on boot" option resolve problems
> with updates and software that require restart
> during installation?
>
> No. However, there aren't many applications that
> require temporary files to be present after a
> reboot. I myself have been using a volatile RAM
> disk for Windows temporary files for a couple of
> years without any major issues.
>
True, but windows update is one of those applications and one that cannot be skipped easily.
> I've used junction and "mklink" with no avail Is
> there any solution to this?
>
> I have just tried this and it worked okay. I
> created a boot-time RAM disk on E:\, then created
> a symbolic link with mklink /D as mklink /D test
> E:\ and the test folder kept pointing at E:\ after
> a reboot.
>
> Make sure you're using the latest version of RAM
> disk (3.4) which came out yesterday as it may be a
> fixed issue.
Hi,
thank you for a swift reply!
I'm using 3.4.
Since I'm playing with this version since yesterday, I've tried many variants.
One thing I've noticed is that I get BSOD on windows boot if machine was shut down.
BSOD doesn't apear if I only restart the machine.
I noticed that I get BSOD on this version, using "mount on boot" option
On a previous installation using 3.3.3 and without "mount on boot" there was no BSOD.
I'll try to make a disk without "mount on boot" and post results.
Maybe this BSOD is a culprit for mklink not working.
Best regards,
Walter
symbolic links are gone after reboot 03 September 2013, 23:36 |
Admin Registered: 18 years ago Posts: 3 568 |
Walter
symbolic links are gone after reboot 04 September 2013, 19:29 |
I've done some more testing so at this point I can confirm that I get BSOD on startup only when I have RAM Disk mounted on boot.
RAM Disk mounted on logon doesn't have this issue
I know that I've opened this topic with a different issue so I will open another for this problem.
Regarding mklink
Whatever I do, I can't get symbolic links to stik to RAM Disk after reboot
I've tried with disks mouted on logon and mounted on boot disks and with HDD emulation ticked
My idea was to move as many temp files and folders to RAM Disk since I have enough RAM to play with but it seems that it doesn't work for me.
Any ideas on how to deal with this?
Best regards,
Walter
Walter
symbolic links are gone after reboot 04 September 2013, 22:09 |
just tested on RAMDisk 3.3.3, same problem, symbolic link is gone after reboot, no matter if RAMDisk is mounted on boot or mounted on logon
Just in case I'm doing something wrong, this is syntax I use:
mklink /D "Y:\Flash Player" "C:\Users\*me*\AppData\Roaming\Macromedia\Flash Player"
y = RAMDisk
*me* = I put my username here
I've also tried with something simple as a test folder created on c:\root
mklink /D Y:\Test C:\Test
Unfortunately same results.
Any help would be greatly appreciated!
Best regards,
Walter
Walter
symbolic links are gone after reboot 10 September 2013, 18:24 |
QuoteAndrew
I have just tried this and it worked okay. I created a boot-time RAM disk on E:\, then created a symbolic link with mklink /D as mklink /D test E:\ and the test folder kept pointing at E:\ after a reboot.
Hi,
I presume this is on a RAMDisk with image mounted?
Did you try it on a RAMDisk without image mounted?
I presume that it won't work that way because, if I understood the way volatile RAMDisk works is that it gets created every time machine gets powered up.
Basically, symbolic links are deleted on power down along with all other data on volatile RAMDisk.
Except using image or a log on script, is there any other way this would stick?
Thank you!
Best regards,
Walter