You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I change the "Download Path" to any drive other than the primary drive, I get the error stating that it cannot access the network drive. It's NOT a network drive, it is a local harddrive, the program GPT4ALL is installed on my S drive, the exact drive GPT4ALL says that it cannot access because the network name is not found. I have changed the drive to M and got the same results. I deleted the nomic.ai folder under AppData and it's immediately recreated upon running GPT4ALL again.
Steps to Reproduce
Change the path for the "Download Path" to any local drive other than default
Expected Behavior
Your Environment
GPT4All version: 3.5.1
Operating System: Windows 10 Pro
Chat model used (if applicable): cannot find any of the installed models
The text was updated successfully, but these errors were encountered:
Speaking of which, I wonder if Anyone is, u know, erm, testing this program before launching an update, and if yes, then do they See the things that are wrong.
How can a program confuse a locally connected harddrive with a network share? I cannot even figure out how that is possible without specifically calling out in the code that any drive letter other than "C" is a network name, but that makes no sense to make that call.
Bug Report
If I change the "Download Path" to any drive other than the primary drive, I get the error stating that it cannot access the network drive. It's NOT a network drive, it is a local harddrive, the program GPT4ALL is installed on my S drive, the exact drive GPT4ALL says that it cannot access because the network name is not found. I have changed the drive to M and got the same results. I deleted the nomic.ai folder under AppData and it's immediately recreated upon running GPT4ALL again.
Steps to Reproduce
Expected Behavior
Your Environment
The text was updated successfully, but these errors were encountered: