Ph9214
Members
-
Joined
-
Last visited
-
When using the following in my Windows 10 xml... <numatune> <memory mode='strict' nodeset='1'/> </numatune> ...the option is ignored and memory access is still split across NUMA nodes
-
Linus tech tips found this one in this video, but its 100$, yikes
-
So-Very-True!!! I would agree that both you have identified the problem. However, I did fix it (using the "documents" as a share name) by creating a new share (identical config) using Documents2, then verified it worked, then deleted the documents share, then renamed Documents2 to Documents. And everything is working. Given I agree with your assessments on the 'default' names, why would it now work? Seems like as soon as I renamed Documents2 to Documents, the conflict should show-up again... Thoughts? it may be that the actual path and not the name is still Documents2 I really have no idea, it could also be that somehow your share config just got messed up somehow
-
nope what are those
-
32 gb (thinking of upgrading)
-
yep it's probably the fact that the name is identical to a windows user folder name so try naming it Docs or whatever you feel like other than the standard user folders which include: Desktop Documents Videos Pictures etc...