- Oct 9, 2002
- 28,298
- 1,235
- 136
TLDR:
@$%$# WINDOWS FILE & FOLDER SHARING!!!
Slightly longer:
25% of the time I try to do a simple sharing task in Windows, it fails miserably and demonstrates inexplicable behavior. There's nothing I hate more than a relatively-recent Windows install that is already behaving strangely. I'm obsessive, so I don't want to wonder if future problems in the future are related to this. I'd rather just reformat my Media PC (after weeks spent getting the tuner and guide listings set correctly) and re-install Windows.
Full overly-detailed insane rant:
(mostly for personal documentation)
2 PCs:
- "Performance PC" (Core i7 860, 16GB DDR3, Win7 Ult x64)
- "Media PC" (AMD Hudson E350 "Zacate," 4GB DDR3, Win7 Pro x64)
- Both have the same Windows username and password.
- Both are set to stay awake (never sleep).
- Both have shared folders on the root of their C: drives.
- Both can access each the other's shared folder with read/write access.
- Both are wired directly (100m) to a Linksys WRT54G running DD-WRT custom firmware.
I am trying to rip a full BD to files so I can make a movie-only backup onto BD-R. I was hoping to do this before going to a friend's house, so I can bring the backup copy instead of the original. I somehow convinced myself that, this time, there shouldn't be any complications to make it take all day long.
The Media PC probably can't handle BD re-mastering, but it has the only BD drive. On the Media PC, I ran AnyDVD HD and started ripping files directly to a shared folder on my Performance PC. This operation should be limited by the BD drive or the network transfer, not the CPU. Many, many, MANY hours later, it was barely 55% complete. CPU usage was really high until I closed some tabs in Google Chrome. I've never had a BD rip take so long, but I didn't let it bother me. It's the first time I've waited around while ripping one since I moved the BD drive to the new Media PC.
While waiting, I watched some online videos. One of the videos suddenly stopped and said "buffering," but clearly wasn't progressing. I feared my router had locked up and interrupted the rip to the shared folder. My router has almost never had a hitch since I installed custom firmware a couple years ago. However, I did recently over-clock it from 200mhz to 233mhz. Before I even looked at the rip progress, I tried to ping the router and could not ping it. The rip failed with a message that the destination was not accessible. #$%#$.
Then I switched to the Performance PC and it was still online and able to ping the router. I rebooted both PCs and the router for good measure. Because the first rip attempt had been taking WAY too long, I had to try a different approach. I already had a 1:1 ISO rip on the Media Center PC, located in C:\BD\. Both PCs already have shared folders that are fully accessible to each other, but they currently have unrelated files in them. I decided to just enable sharing on the C:\BD\ folder. The Performance PC says the newly-shared folder isn't accessible. I compared it with the other shared folder (also on the root) and they have identical share permissions. For some reason, any folder I create and share in C:\ on the Media PC shows a padlock on the icon. The previously-existing shared folder does not show a padlock. After another hour of fiddling and re-starting, I gave up and moved the ISO to the existing shared folder (with a bunch of unrelated files). On the Performance PC, I mounted the ISO in Virtual CloneDrive and started ripping to a local folder. It's going significantly faster than the earlier attempt.
After a bit of Google-fu, I found out how to resolve the sharing issue. I have to add the file security permission for "Authenticated Users." If I add "Authenticated Users" to a newly-created/shared folder in C:\, the padlock disappears and it's finally accessible to the Performance PC.
When I create a new folder in C:\ on the Performance PC, it already has security permission for "Authenticated Users." When I do the same on my Media PC, the permissions are missing. Obviously, it worked correctly when I created the original shared folder that has always been accessible. WHY DOES WINDOWS BOTCH ITSELF LIKE THIS?
Even though the install is only weeks old, I have to reinstall Windows due to this and other unexplainable BS. There's another issue where the mouse pointer won't disappear when typing. Because it's connected to a TV, I've chosen the "Extra Large" mouse pointer. It's almost always obscuring the field I'm typing in. I know there's a setting to control whether the pointer disappears when typing, and I've turned it off / on; but it makes no difference. Google fails me completely.
It has taken weeks to get the TV tuners and guide listings set up perfectly.
- Tuners had issues until another update was released
- Cableco moved QAM frequencies multiple times
- Had to assign guide listings and virtual channel numbers for several dozen QAM channels
Now I'll have to do it all over again.
...at least I didn't go through Windows activation yet!
@$%$# WINDOWS FILE & FOLDER SHARING!!!
Slightly longer:
25% of the time I try to do a simple sharing task in Windows, it fails miserably and demonstrates inexplicable behavior. There's nothing I hate more than a relatively-recent Windows install that is already behaving strangely. I'm obsessive, so I don't want to wonder if future problems in the future are related to this. I'd rather just reformat my Media PC (after weeks spent getting the tuner and guide listings set correctly) and re-install Windows.
Full overly-detailed insane rant:
(mostly for personal documentation)
2 PCs:
- "Performance PC" (Core i7 860, 16GB DDR3, Win7 Ult x64)
- "Media PC" (AMD Hudson E350 "Zacate," 4GB DDR3, Win7 Pro x64)
- Both have the same Windows username and password.
- Both are set to stay awake (never sleep).
- Both have shared folders on the root of their C: drives.
- Both can access each the other's shared folder with read/write access.
- Both are wired directly (100m) to a Linksys WRT54G running DD-WRT custom firmware.
I am trying to rip a full BD to files so I can make a movie-only backup onto BD-R. I was hoping to do this before going to a friend's house, so I can bring the backup copy instead of the original. I somehow convinced myself that, this time, there shouldn't be any complications to make it take all day long.
The Media PC probably can't handle BD re-mastering, but it has the only BD drive. On the Media PC, I ran AnyDVD HD and started ripping files directly to a shared folder on my Performance PC. This operation should be limited by the BD drive or the network transfer, not the CPU. Many, many, MANY hours later, it was barely 55% complete. CPU usage was really high until I closed some tabs in Google Chrome. I've never had a BD rip take so long, but I didn't let it bother me. It's the first time I've waited around while ripping one since I moved the BD drive to the new Media PC.
While waiting, I watched some online videos. One of the videos suddenly stopped and said "buffering," but clearly wasn't progressing. I feared my router had locked up and interrupted the rip to the shared folder. My router has almost never had a hitch since I installed custom firmware a couple years ago. However, I did recently over-clock it from 200mhz to 233mhz. Before I even looked at the rip progress, I tried to ping the router and could not ping it. The rip failed with a message that the destination was not accessible. #$%#$.
Then I switched to the Performance PC and it was still online and able to ping the router. I rebooted both PCs and the router for good measure. Because the first rip attempt had been taking WAY too long, I had to try a different approach. I already had a 1:1 ISO rip on the Media Center PC, located in C:\BD\. Both PCs already have shared folders that are fully accessible to each other, but they currently have unrelated files in them. I decided to just enable sharing on the C:\BD\ folder. The Performance PC says the newly-shared folder isn't accessible. I compared it with the other shared folder (also on the root) and they have identical share permissions. For some reason, any folder I create and share in C:\ on the Media PC shows a padlock on the icon. The previously-existing shared folder does not show a padlock. After another hour of fiddling and re-starting, I gave up and moved the ISO to the existing shared folder (with a bunch of unrelated files). On the Performance PC, I mounted the ISO in Virtual CloneDrive and started ripping to a local folder. It's going significantly faster than the earlier attempt.
After a bit of Google-fu, I found out how to resolve the sharing issue. I have to add the file security permission for "Authenticated Users." If I add "Authenticated Users" to a newly-created/shared folder in C:\, the padlock disappears and it's finally accessible to the Performance PC.
When I create a new folder in C:\ on the Performance PC, it already has security permission for "Authenticated Users." When I do the same on my Media PC, the permissions are missing. Obviously, it worked correctly when I created the original shared folder that has always been accessible. WHY DOES WINDOWS BOTCH ITSELF LIKE THIS?
Even though the install is only weeks old, I have to reinstall Windows due to this and other unexplainable BS. There's another issue where the mouse pointer won't disappear when typing. Because it's connected to a TV, I've chosen the "Extra Large" mouse pointer. It's almost always obscuring the field I'm typing in. I know there's a setting to control whether the pointer disappears when typing, and I've turned it off / on; but it makes no difference. Google fails me completely.
It has taken weeks to get the TV tuners and guide listings set up perfectly.
- Tuners had issues until another update was released
- Cableco moved QAM frequencies multiple times
- Had to assign guide listings and virtual channel numbers for several dozen QAM channels
Now I'll have to do it all over again.
...at least I didn't go through Windows activation yet!
Facebook
Twitter