• Announcements

    • LORAdmin

      S5 Beta Comments   07/16/2017

      Please keep all comments about S5 in the Open Beta General Comments section. This will help the developers by only have to look in one area of the forums for comments/questions/concerns about S5.
k6ccc

JRW12 - Unable to assign LOR default drive to network drive

4 posts in this topic

LOR Version:  5.0.0 beta

Operating system:  Windows XP (will confirm on Windows 7 later today)

When starting the S5 sequencer for the first time, it asks where the files will be located (the function that LORPost has done in the past).  I attempt to assign L:\ as the file location.  L:\ is a network shared drive (although on this computer it is actually a folder on the local hard drive).  The sequencer reports that "The folder name you have entered is not valid.", and instructs me to "Please go back and enter a valid folder name."

L:\ is the folder I use on all computers used for LOR.  In the case of this standalone computer, L:\ is actually C:\LightORama, however on the computers at home, it is actually a network folder on my server.  If I assign the actual location on the local drive (i.e. C:\LightORama), it does work.  I STRONGLY prefer to use the same location on every computer, so files don't need to be changed depending on which computer is running them.  Since the computers at home use the server, specifying a network location is required.

 

 

 

Share this post


Link to post
Share on other sites

Lor 5.0.0 Beta Windows 10 pro.

I can confirm this too,Jim. I am also using a mapped drive, also L:\.  It will not accept the "root" network folder. If you give it a subfolder of L:\ it will accept it.

Share this post


Link to post
Share on other sites

I confirmed what Phil said.  I created a sub-folder from L:\ and it worked fine when I assigned that sub folder.  So the issue is NOT a network drive issue, but rather a drive root issue.  Please fix this.

 

Thanks

 

Share this post


Link to post
Share on other sites

Thanks for chasing this down to find the root issue. We will get that fixed for the next beta release.

Matt Brown

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now