tag:blogger.com,1999:blog-50964783942647907962012-02-16T01:30:30.386-08:00boyhitsworldhttp://www.blogger.com/profile/09474626930205329689noreply@blogger.comBlogger21100tag:blogger.com,1999:blog-5096478394264790796.post-68145708378726748872011-01-29T10:34:00.000-08:002011-01-29T10:34:52.734-08:00I have recently been using Windows 7, and have found an irritation with the way it handles network drives. I have all my music and media on a <a href="https://secure.wikimedia.org/wikipedia/en/wiki/NSLU2">NSLU2</a>-driven network drive, which under XP was configured to reconnect at startup. Which it did.<br /><br />With Windows 7, it appears as though it tries to reconnect network drives before the network connection is available, leading to a perpetual start-up error of "network drives failed to reconnect". You then have to manually go to explorer and double click the drive to bring it up. This is irritating.<br /><br />My workaround is to use a batch script at startup that pauses for a 15 seconds, letting the network connection come up, and then map the drive.<br /><br />I created a script called "map drive.bat" and put this in the start-menu Startup folder. The contents are as follows:<br /><pre>@echo off<br />echo waiting for network...<br />timeout /t 15<br />net use z: "\\Nslu2\disk 2" /persistent:no<br /></pre>This maps my nslu2 share to the Z:\ drive, non-persistently, so it will disappear on reboot (but this script is run at startup so that's fine).<br /><br />The downside is that you have to run the script manually if the share comes up after you boot windows, but that's no worse than having to open explorer to load the drive if you do drive mapping the normal way.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5096478394264790796-6814570837872674887?l=boyhitsworld.blogspot.com' alt='' /></div>boyhitsworldhttp://www.blogger.com/profile/09474626930205329689noreply@blogger.com0tag:blogger.com,1999:blog-5096478394264790796.post-47534935006545289312011-01-27T13:36:00.000-08:002011-01-27T13:36:28.039-08:00So, running my site was all fine when I <strike>had the time to</strike> wasn't lazy about keeping the software up to date. I clearly was that lazy, so I got hacked. After a morning clearing up and upgrading back to the latest, I still didn't learn my lesson and got hacked again.<br /><br />Long story short, I probably spent more time keeping everything up to date than writing posts, so I've jumped over to blogger, which should hopefully encourage me to be a bt more verbose. I've got the latest backups of my wordpress database, so I may attempt to repost some of the old stuff if I can. We'll see...<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/5096478394264790796-4753493500654528931?l=boyhitsworld.blogspot.com' alt='' /></div>boyhitsworldhttp://www.blogger.com/profile/09474626930205329689noreply@blogger.com0