Posts tagged windows
What are Thumbs.db and .DS_Store files? Can I delete them? Do I need them and how can i make them stop coming back?
Apr 13th
James from Virginia wanted to know if it was safe to delete these Thumbs.db and .DS_Store files from his network. Check out our answer and step by step removal tips.
Running in a mixed Windows/Mac environment I find it annoying to deal with all the little artifacts the great OS’s leave behind. All of our mixed shares and network drives are full of these frickin ‘Thumbs.db and .DS_Store files.
Each folder with initiated thumbnail views (that is where they have displayed a Thumbnails or Filmstrip view in Windows Explorer) will have a Thumbs.db file.
They do nothing for me. I look at them like litter on the ground. I looked up what they do and started deleting them. But they came back…
Some times I get caught up in doing something after in enrages me enough. So I was now determined to get rid of these files from my shares here on out. I did some research on how to get rid of them permanently and how to prevent them from coming back!
Here is how you prevent Windows and OS X from creating these annoying files.
Prevent the creation of Thumbs.db in Windows:
Prevent the creation of .DS_Store files on Network volumes in MacOS:
- Open the Terminal application from the Utilities folder which is nested in the Applications folder
- Begin by first clicking on the Start Button
- Then click on Search and then Click on the All files and folders option
- In the All or part of the file name: box type in Thumbs.db
- Quickly ensure that the Look in: pull-down menu is set to whatever network drives you want to scrub
- Now Click on the Search button to search for all Thumbs.db files on your system
- In the All or part of the file name box type in Thumbs.db
- After the Search completes, click on the word Edit contained in your top tool bar area
This will pull down a menu for you to now click on Select All - Now Press the Delete key on your keyboard to delete all the Thumbs.db files on your system
- Then Close the Search Results window to return back to your Windows session
Now this doesn’t help you deleting the files that already may exist.
To accomplish that you may be interested in BlueHarvest to scrub your network of .DS_Store files and you can do a simple find and replace on Windows.
Find and Replace:
To delete all the existing Thumbs.db files on your computer you just:
For those of you who are scared to delete system files, the Thumbs.db and .DS_Store files are strictly cosmetic on network volumes and will have almost no impact on pretty much anything! Do you use them for something? Let us know in the comments.
_TheOCAdmiN_
Can I hide the Sceduled Tasks and Printers Folders in the Network view?
Apr 2nd
By default your windows XP machine shows the Printers and Faxes share along with the Scheduled Tasks folder. You can make use of the scheduled tasks folder like this or use a remote printer share to quickly install a remote printer.
Some people like this, most people don’t use it and a few people REALLY hate it. So here is a quick how-to on peacing it out:
To hide the Scheduled Tasks from the network share view, follow these steps:
- Click Start, Run and type REGEDIT
- Navigate to the following key:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Explorer \RemoteComputer \ NameSpace
- Backup the key by exporting it to a .REG file. (You need this to revert back!)
- To remove Scheduled Tasks, delete the following key:
{D6277990-4C6A-11CF-8D87-00AA0060F5BF}
- To remove the Printers folder, delete the following key:
{2227A280-3AEA-1069-A2DE-08002B30309D}
- Close Registry Editor.
By deleting one key or the other you are removing the folders from the network view and not disabling printing/scheduling in any which way. To restore the shares after removing them import the .REG file you saved in the third step above.
_ThePeaceYouOutAdmiN_
Last night Ubuntu saved my life – How I used Ubuntu to recover ALL my files…
Mar 30th
Commodore 64 here to bring you another horror story from binary-land. Lord knows I’ve been through hell and back with computers. Overheating CPUs, which were fixed by the cold of the winter outside my apt; crashing hard drives which were fixed or accessed by various means; faulty power supplies, which had me gutting and re-assembling my machine; and many more.
Up to this point, the only time I actually lost data, was to my ex-wife, who got to keep the computer with all my stuff in it, while I made away with a crappy laptop. Other than that, I’ve always been able to salvage my data somehow.
This time I had a new problem. Upon conferring with the Admin, to whom I have exclusive access (belonging has perks people, hit the comments if YOU want to belong as well) we came to the conclusion, based on past problems that were brought to his attention, that I have a power supply which is not supplying a steady stream of power to my hard-drives and various other internally powered devices. Now so far, to the best of my knowledge, a hard drive and ram are really the only components that can suffer from a faltering power supply. For the past 6 months, my computer has eaten through 3 Western Digital hard drives, which I’m sure were perfectly fine from the get-go. I will note here that I DO NOT blame Western Digital for these issues. I am a fair consumer which doesn’t point unnecessary blame where it is not due. I will however give them a call and will update this blog with their responses and whether they are able to help me at all along the lines of some replacements.
My problem started because of me. I let waaaay to much time go by before I blew the inordinate amount of dust out of my computer, and more importantly, my power supply. I have gotten into the bad habit of leaving my case open, as I am also inordinately lazy. This probably contributed to the systematic weakening of my power supply. My hypothesis is that the dust caked up on the power supply fan, causing the power supply to rise in temperature, and over time this started to affect it’s power output. This, in turn, caused my hard drives to fuzz in a very weird, intermittent way. At first we thought that my snazzy hard drive enclosure was the culprit. I had one of my drives, my all-important work drive with all my years of work, in an enclosure which, through an lcd display provided me spin-up and temperature info, but more importantly this enclosure allowed my drive to be cold-removed from my machine easily. My justification was, that in the case of a fire, or a world-wide Huxley style pron hunt, I would have the ability to simply slide my drive out of my machine, and make off with my all-important stuff. Karl and I had hypothesized earlier on, that this was the culprit to the failing of my first WD-320 drive. At the time this was my data drive on which I kept all my data, but I also had a recent copy of the data on another drive, so it was no big deal.
So I removed the offending enclosure and drive, and continued on with a slightly bruised ego and one less hard drive in my collection. For about a few months this was fine. Most likely there was now less power being drained from the power supply so this proved to be a stop-gap measure which lasted only a few months, which I only know now.
Then the unthinkable happened. Something that hasn’t happened to me in years. A full-out dead freeze in Windows, which upon rebooting, no longer existed according to the cryptic error message my BIOS was giving me. Windows was gone. Since I couldn’t deal with the problem right there and then, I popped in my newly burned Ubuntu 7.10 Live CD to leave some semblance of a usable computer intact on my PC.
A few days later I was actually able to spend some time recovering or repairing my machine, whichever came first. Since I had turned the machine off the night before, I booted up and noticed that Windows was beginning to boot. Hooray!
By some miraculous feat, Windows was booting up! However, my beloved work drive was not showing up. Upon checking BIOS I noticed that the hard drive was being detected, but Windows couldn’t see it! Before I could do much else, Windows froze again. At this point I realized Windows wasn’t coming back, and that I had to concentrate my efforts on damage control rather than repair. Recovering my work files became my top priority.
Enter Ubuntu.
At first, Ubuntu did not recognize my work drive. Then, after a few minutes, my work drive appeared in the My-Computer-esque Home window Ubuntu had given me. Eureka! The OS sees my drive. I quickly connected my LaCie external USB drive and double clicked on the WD-320 drive which contained all my precious work files. One more obstacle: I received an error which said something to the effect of (loosely translated) “Ubuntu needs you to give it the command, in the command prompt, to mount the drive with the force option activated.” I popped open Firefox and Googled just the first part of the error and was presented with some results to some blogs which contained the exact command, with switches, that I was to use to successfully get my drive accessible in Ubuntu. The command worked an I proceeded to copy the 130 Gigabytes of precious data from my half-broken, limping hard-drive to my ever solid external USB drive. A few hours later the operation was complete. I can rest easy now.
A later memory test, courtesy of the good people that brought the Ubuntu Live CD, revealed that my memory chips were fried too – looks like a job for Crucial.com.
It’s been a week now, and thanks to Ubuntu, getting my data accessible after a hard system crash like that was not something I had to lose sleep over. Since I was able to safely offload my data without having to overhaul my computer, I was able to get some sleep that night, and many other nights following the incident. Sleeping is not an issue when you know your data is safe, even if for the time being.
Now I can slowly work on getting the $500 together to buy 2 new hard drives, and 2 new ram chips, so that one day my computer will be restored to it’s former dual-screen, design station ala Commodore glory. But in the meantime, I can survive rather comfortably using my Mac, and my resuscitated PC running Ubuntu 7.10. In all fairness this was a harrowing situation, but the availability of a self-contained, graphical operating system, that can run off a CD on a PC with nothing in working order besides a power supply, a motherboard, and some limping hard drives and memory chips, enabled me to not have to put my life on hold again to ensure access to my important stuff.
Piece of mind, that’s what it came down to.
Can I disable the RESTART option after completing windows update? Is there any way to cancel a Reboot?
Mar 26th

MJ writes to us that her machine runs updates around lunch time and she keeps getting the prompt do you want to restart now?
Not only is it annoying – sometimes she clicks yes by accident and her whole world comes crashing down. (See the fix for this at the bottom of the post – not for the faint of heart or slow typers!!!)
Not only will we show you how to disable the automatic restart option after updates via Group Policy we will show you how to quickly cancel a reboot.
- Go to Start –> Run, type “gpedit.msc”.
- Go to Computer Configuration –> Administrative Templates –> Windows Components –> Windows Update.
- Look for option “No Auto Restart For Scheduled Automatic Update installation” and Enable that option.
- This will make sure that your computer is not rebooted automatically, instead it will just notify you for a reboot. It will be users choice as to when to reboot your computer
- If in case you want it to notify you again and again, after a specific interval of time, then look for option “Re-prompt for restart with scheduled installations”. Enable that option and specify the time.
Everything above is all easy, its just editing some policies which you can perform easily. [TechiesDen]
Now to cancel a reboot:
- Start
- Run
- Type Shutdown -a and hit enter
Thats it, that will cancel your impending doom if you hit it fast enough!
I cant format my hard drive that has strange partitions on it help!
Mar 25th
If you have a hard drive of unknown origins there are times when you just can’t format it using the normal methods like an OS’s installer or Windows built in Disk Configuration Utility. NTFS’s good old security tries to do you dirty as well. It can be a real pain in the ass.
But AtA has been through this MANY MANY times and we know of an old school solution to blowing away almost any fussy hard drive.
Is Dos 6.22 old enough for you? Fdisk and format are your friends… You didn’t forget about them did you? 6.22 is before NTFS so it doesn’t worry about the security – isn’t that special?
Don’t worry loyal AtA fan we won’t make you go scurrying back to your domicile looking for your old dusty box of floppy disks because we have an image for you right over here…
You can use this with a blank floppy disk to boot into 6.22 and get down and dirty (You do know what a floppy disk is don’t you?).
How do you deal with formating issues? Hit us up in the comments.
_TheFlashBackAdmiN_
Display a Start Up Message in Windows XP before logging in.
Mar 12th
Before someone logs into your machine a message can be displayed. This is meant to inform you that you are being monitored or you are bound by some formal code of conduct.

You can use it to display a message in your absence to remind your buddies you are an all knowing Admin. You can do it pretty easily by displaying what Microsoft refers to as a legal notice at system start up.
- GO TO RUN
- REGEDIT
- Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system]
- Change legalnoticecaption”=”Legal Notice“
- legalnoticetext=”AskTheAdmin is watching you.”
obviously you can replace Legal notice or AskTheAdmin is watching you with any text you want. The editors over here are pretty sure you can find some Funny Practical uses for this on your, or a public, PC…


