Error when using Windows Paths for drives. Maybe the directory redirect?

[eddie-moser]

Version

1.38.6

Operating system type + version

Windows 10

Behavior

When installing Slic3r into a folder that is actually a drive mounted as a windows path it will not open several images keeping people from being able to save new profiles etc...

_Is this a new feature request? no

[bubnikv]

What exactly does not work? I tried to extract Slic3r onto a network drive and at the first sight everything seems to be working.

[eddie-moser]

It has nothing to do with a network drive, the issue is actually 2 physical drives. Within windows you can change the mountpoint of a physical drive to a folder that is under another physical drive. When I had it installed to the folder that was actually a different PHYSICAL volume it would error out reading in the icon paths and wouldn’t allow you to use the app. When you look at the error you can clearly see that the path is wrong due to what looks like a variable being used $VOLUME. If you want to setup a time I can work with you on how to repeat the issue because I validated twice that if you use the above mapping the app crashes. From: bubnikv [mailto:[email protected]] Sent: Monday, February 12, 2018 4:25 AM To: prusa3d/Slic3r <[email protected]> Cc: eddie-moser <[email protected]>; Author <[email protected]> Subject: Re: [prusa3d/Slic3r] Error when using Windows Paths for drives. (#711) What exactly does not work? I tried to extract Slic3r onto a network drive and at the first sight everything seems to be working. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#711 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/Aii-W61R84hY52h_cov-1aEniK5r1eAFks5tUBFngaJpZM4R8VUc> . <https://github.com/notifications/beacon/Aii-WzTSouTyGFdto2zRHl78cmRJai9Sks5tUBFngaJpZM4R8VUc.gif>

[bubnikv]

Frankly your use case is quite rare and if the error happens inside the Perl part, we will likely not fix it quickly. We are working on rewriting the remaining Perl parts into C++, and then your issue will get the attention it needs. Which icons are missing? From the screenshots I may judge which part of the application fails. Thanks.

…

On Mon, Feb 12, 2018 at 11:28 AM, eddie-moser ***@***.***> wrote: It has nothing to do with a network drive, the issue is actually 2 physical drives. Within windows you can change the mountpoint of a physical drive to a folder that is under another physical drive. When I had it installed to the folder that was actually a different PHYSICAL volume it would error out reading in the icon paths and wouldn’t allow you to use the app. When you look at the error you can clearly see that the path is wrong due to what looks like a variable being used $VOLUME. If you want to setup a time I can work with you on how to repeat the issue because I validated twice that if you use the above mapping the app crashes. From: bubnikv ***@***.*** Sent: Monday, February 12, 2018 4:25 AM To: prusa3d/Slic3r ***@***.***> Cc: eddie-moser ***@***.***>; Author ***@***.*** > Subject: Re: [prusa3d/Slic3r] Error when using Windows Paths for drives. (#711) What exactly does not work? I tried to extract Slic3r onto a network drive and at the first sight everything seems to be working. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < #711 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe- auth/Aii-W61R84hY52h_cov-1aEniK5r1eAFks5tUBFngaJpZM4R8VUc> . < https://github.com/notifications/beacon/Aii-WzTSouTyGFdto2zRHl78cmRJai9Sks 5tUBFngaJpZM4R8VUc.gif> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#711 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFj5IwygbQIpPUzn5Uf2r8jDX-MC4DhHks5tUBJNgaJpZM4R8VUc> .

[eddie-moser]

It is the PERL crashing IIRC. The icons at the top for saving changes to filaments/printers etc… are missing. From: bubnikv [mailto:[email protected]] Sent: Monday, February 12, 2018 5:06 AM To: prusa3d/Slic3r <[email protected]> Cc: eddie-moser <[email protected]>; Author <[email protected]> Subject: Re: [prusa3d/Slic3r] Error when using Windows Paths for drives. (#711) Frankly your use case is quite rare and if the error happens inside the Perl part, we will likely not fix it quickly. We are working on rewriting the remaining Perl parts into C++, and then your issue will get the attention it needs. Which icons are missing? From the screenshots I may judge which part of the application fails. Thanks.

On Mon, Feb 12, 2018 at 11:28 AM, eddie-moser ***@***.*** ***@***.***> > wrote: It has nothing to do with a network drive, the issue is actually 2 physical drives. Within windows you can change the mountpoint of a physical drive to a folder that is under another physical drive. When I had it installed to the folder that was actually a different PHYSICAL volume it would error out reading in the icon paths and wouldn’t allow you to use the app. When you look at the error you can clearly see that the path is wrong due to what looks like a variable being used $VOLUME. If you want to setup a time I can work with you on how to repeat the issue because I validated twice that if you use the above mapping the app crashes. From: bubnikv ***@***.*** Sent: Monday, February 12, 2018 4:25 AM To: prusa3d/Slic3r ***@***.*** ***@***.***> > Cc: eddie-moser ***@***.*** ***@***.***> >; Author ***@***.*** ***@***.***%0b> > Subject: Re: [prusa3d/Slic3r] Error when using Windows Paths for drives. (#711) What exactly does not work? I tried to extract Slic3r onto a network drive and at the first sight everything seems to be working. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < #711 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe- <https://github.com/notifications/unsubscribe-%0b> auth/Aii-W61R84hY52h_cov-1aEniK5r1eAFks5tUBFngaJpZM4R8VUc> . < https://github.com/notifications/beacon/Aii-WzTSouTyGFdto2zRHl78cmRJai9Sks 5tUBFngaJpZM4R8VUc.gif> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#711 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFj5IwygbQIpPUzn5Uf2r8jDX-MC4DhHks5tUBJNgaJpZM4R8VUc> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#711 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/Aii-W8VtfCi5F5o2M5-f7EDabqeF8wMxks5tUBsZgaJpZM4R8VUc> . <https://github.com/notifications/beacon/Aii-WyKRQ5H-zxuwrcfpB9nPQecTl84xks5tUBsZgaJpZM4R8VUc.gif>

[bubnikv]

It is the PERL crashing IIRC. The icons at the top for saving changes to filaments/printers etc… are missing.

Thanks. I will keep this issue open for reference, so we can test it once we have the UI code ported from Perl to C++.

[bubnikv]

Isn't your issue the same as #732 ?

[lukasmatena]

This issue is apparently outdated for a long time. Closing.