CommonTater,
Sorry I missed that..after reading 6 pages on this issue, I was probably jumping to conclusions. my apologies .. (I am complexed about this issue)
No need to apologize. This thread has gone places I didn't expect and still no real solutions in the offing. Perhaps I should clarify...
The original question --which quickly became a family problem-- was why would windows 7 wake every computer on my lan whenever I locally accessed a folder that just happened to be shared? For example: I share my downloads folder, if I click on it on my desktop it will bring the computer in my son's bedroom out of sleep, the one in the rec room spins up, my better half's machine wakes up and the HTPC spins up... The XP machines do not do this, only the two Win7 machines (mine and my wife's)
To this point we had problems with occasional spinups that started about a month ago and hadn't connected them to shared folders on the Win7 machines... It seems Win7 wants the entire network to be active all the time...
This became a family problem when my youngest was on night shift and was sleeping during the day... he was just getting asleep when I hit a folder here and his machine spun up, the monitor came on and of course the disturbance woke him up... I don't blame him for being upset... I would be too...
So, as the thread details I tried several experiments trying to see if there was a feature or service I could shut down to prevent this... and there isn't.
Subsequently I've realized that it's not just shared folders... it's ANY folder. But, if I turn off the navigation pane on the Win7 Explorer it only does it on shared folders... It's actually Win7's "network tree" in the navigation pane enumerating the network that's causing the spinups.
I've managed to stop the problem by jerry rigging the HTPC to never sleep (monitor off, disk drives off... otherwise fully awake) and disabling the Network Browser service in the other machines.
Now... this whole Win7 thing has grown into a big family debate... Some time ago we decided that we really should be updating the lan to something newer than XP... so we decided to spend the bucks and get all the kids a copy of Win7 Ultimate as a gift and get the thing up to modern specs. Well... it's been a month since I put it in my machine and started trying to sort it out so the kids would have "drop in" installs on theirs and in this last month I've done very little other than mess with this computer and fish this forum for answers to questions... It's really becoming a problem for us... the family wants their stable network back, my BH wants Win7 for a new venture she's rolling out in May... I don't much care what OS I'm on but I'm the one that's got to make this whole thing work...
Last week I had no choice but to XP back in the HTPC machine --or face a family rebellion-- after Win7 proved to be totally useless for playing multimedia files. It's an ASRock ION 330 box (Intel Atom dual core, 2gb ram, 500mb hd, Nvidia ION chipset)... Under 7 it couldn't even play mp3s, they would stutter make weird noises and change speeds for no apparent reason. Avi playback was bad, with frames being dropped and the sound sputtering. 1080p was impossible on that machine. Now that I put XP back in it, it can play 1080p from blueray, stream avis out the network and defrag the disks all at the same time...
So that's kinda where we are... The whole clan will be here later today for supper and to discuss this issue... I'm sure it will be an interesting conversation but not so sure what's going to come from it... I'm not too fond of having 6 copies of Win7 ultimate sitting unused in a box in the garage... Thats a total waste of $1200. But that's likely where this is heading.
In all my years in computing, nothing we've done has ever been so contentious as this Win7 upgrade...