Short Story: Win7 is capitalizing a folder name in a share, and then changing it back, disrupting music play back. Long Story: There are 3 pcs on our network, HTPC, JJP and DURK. On HTPC, there is a music folder (the directory structure appears as \\HTPC\mammoth\Music). When I load up music from this folder on DURK (through Foobar, or any other program), it plays for about ten minutes, and then spits out the following error "Unable to open item for playback (I/O error (win32 #67)): "\\htpc\mammoth\Music\Daft Punk\TRON Legacy\12. End of Line.flac" Which after doing some research, seems to refer to 67 0x80070043 The network name cannot be found. ERROR_BAD_NET_NAME So I brought up my network drive in Explorer, and monitored that, sitting in the \\HTPC share directory. After the music stops playing, and Foobar spits the above error, I look at the \\HTPC folder, and mammoth is now Mammoth. After 30-60 seconds, this then remedies it self, changing back to mammoth, and everything is able to play again. The issue is that this is a non stop thing, and it does not occur on JJP, only DURK.

Hi, According to your description, it sounds like this is caused by software conflicts, maybe some processes modified the folder name when you were playing music, please boot DURK copmuter into clean boot mode to check if this issue persists. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hey Alex. I have done as you have suggested, but unfortunately the problem is still present. It appears though that the name of \\HTPC\Mammoth back to \\HTPC\mammoth has to do with me refreshing the \\HTPC folder. Or I just have weird timing.

I've gone into the HTPC and added the Music folder as a share, so I skip the \Mammoth folder entirely. So I suppose this will work. Though I am interested in continuing to find the solution to the problem, just in case someone else has this issue, and is not able to make the same fix as me.

Hi Dekthro, If this issue still persists, we can keep discussing in this post. Regards, Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.