Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Local library: unable to map a directory to a network share #1569

Open
OrdoConcept opened this issue Mar 19, 2024 · 2 comments
Open

Local library: unable to map a directory to a network share #1569

OrdoConcept opened this issue Mar 19, 2024 · 2 comments
Labels
bug This issue identifies a bug in Nuclear. help needed - Windows We're stuck and we need someone with access to Windows to help debug this

Comments

@OrdoConcept
Copy link

Platform: Windows 10

Nuclear version: 0.6.30.0

Description of the issue:
Impossible to map a directory to a network share (a NAS for example). Why?
@OrdoConcept OrdoConcept added the bug This issue identifies a bug in Nuclear. label Mar 19, 2024
@nukeop
Copy link
Owner

nukeop commented Mar 19, 2024

I don't know, what happens and what do you expect to happen? Can you simply mount it somewhere in the local filesystem?

@OrdoConcept
Copy link
Author

Thank you for this quick response.
If I put my library on a physical disk on my machine everything works. If I put it on my NAS, even if I mount the directory in the file system, no file is detected...

@nukeop nukeop added the help needed - Windows We're stuck and we need someone with access to Windows to help debug this label Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue identifies a bug in Nuclear. help needed - Windows We're stuck and we need someone with access to Windows to help debug this
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nukeop @OrdoConcept