April 11th, 2009 Brian Herzog
One our regular patrons comes in with a ziplock bag full of flash drives, and then will spend hours copying text and images from websites into Word documents. He then saves these Word documents to the flash drives, and he also saves every email attachment he gets on the flash drives.
I trust this particular patron to know how to use a flash drive, so I was surprised one day when he comes up and said,
Your computer is giving me a flash drive error - it is saying it is full or write-protected, but it's not.
I went over to his computer, and sure enough, when I tried to save his file, I got the same error. I checked to make sure the drive wasn't physically locked, and also that it wasn't full - according to the properties, he had less than 30mb on a 1gb drive.
I was afraid the drive was corrupted somehow, so I took his drive back to the reference desk with me, telling him I'd look into it. A simple Google search for "can't save to flash drive" led to a thread on cnet forums.
The thread suggested this error can happen when you reach the upper limit on the number of files the root directory can hold. I had never heard of this before, so I took a look at his flash drive's root directory - sure enough, there were something like 700+ files in it.
I took the flash drive back to the patron and explained what I learned. The solution, I told him, is to temporarily cut/paste one file off of the drive to the computer, which will let us create a folder on the flash drive. Then, he can move files into the folder, and create additional folders, and start organizing files that way, instead of leaving everything in the root directory.
He did this, and it worked perfectly.
I had no idea disk directories had such limits, and I remarked to the patron that thanks to him, I learned something. This particular patron is always friendly and grateful for any help we give him. In this case though, he was extra cheerful - he spent the rest of the day letting everyone know that he taught me something.
Tags: directory, drive, drives, error, flash, full, jump, libraries, Library, memory, public, Reference Question, root, save, saving, stick, thumb, usb, write-protected
January 10th, 2009 Brian Herzog
We can learn a lot from our patrons.
One of our regulars spends most of his time surfing the internet and then copy/pasting things he likes from web pages and email messages into Word files. He carries around four or five flash drives, and his Word documents can sometimes be 200+ pages long.
And of course, he runs into problems. He called me over the other day, because he was seeing an error when trying to open one of his files. I had never seen it before, but (surprisingly) it gave very clear instructions on how to fix the situation - using something in Word that I had never noticed before.
The problem is that, when he copies things from a web browser, Word doesn't just copy the text and images. Word copies all of the underlying HTML code, too, and tries to recreate the tables. The chance of copying all of the necessary code is very slim, so when the file is saved and reopened, Word says the tables are corrupt.
But so far, Word's built-in "Open and Repair" option has worked every time. I find it annoying that Word tries to handle HTML, but at least they included a fix for it - I wonder how many other problems this can fix. And I wonder what other useful gems lie undiscovered (by me)
After I walked through this with the patron, he's been able to do it himself, and is very happy.
But the real fix might be to install the Copy Plain Text add-on for Firefox on our public computers and show him how to avoid the problem all together.
Tags: copy, copy/paste, error, firefox, HTML, libraries, Library, open and repair, paste, problem, public, Reference Question, word
October 2nd, 2008 Brian Herzog
Most of the talk about ALA's new website redesign has died down, but I noticed something this week I want to comment on.
On the whole, I think the new site is a vast improvement over the old one. And with any new site, I understand they're still shaking out the bugs, and dealing with lots of dead links.
But: for my previous post, I wanted to find information from the ALA about library activity rising in time of economic trouble. A search on Google linked to something sounding exactly like what I was looking for on the ALA site. However, the link was broken.
By searching the ALA site itself for the title displayed in the Google results, I ultimately found the article's new location. Which is fine, but I have to say I am disappointed with the new website's 404 page.
When the 404 "Page Not Found" page loads, the most dominate thing on the page is the search box right in the center. So of course I clicked on this to search for the page I wanted. But - surprise - it's not a functioning search box. It's just an image of what the search box at the top of the page looks like. Of course the text above this image tells you to use the one at the top, but who reads? I don't - especially when a dominate image draws my attention away from the text.
So ALA, how about making the search box in the center a functioning search box, instead of just teasing us? It would add utility to the page, and make the 404 page incrementally just that much more user-friendly.
But otherwise, I think this is a pretty good 404 page, as far as they go. It customized and nice-looking, and gives some tips for finding what you're looking for. It also includes an email address to contact a person for help, which is great. I think I only noticed this because I talked about library website 404 pages before, and gave my library a fancy-pants 404 page.
I don't understand why it doesn't show up all the time, but maybe that's in the works, too.
Tags: 404, ala, american, american library association, association, error, libraries, Library, missing, new, page, pages, public, redesign, revamp, website
March 28th, 2007 Brian Herzog
This picture is the error my computer has been displaying for the past week. It happened about a week ago, when my Verizon phone service also went out. I personally think that whatever knocked out the phone came in through the DSL line and also affected the computer, but Verizon's DSL helpline refused to even entertain such a notion. Ah, well.
The good news is that my phone service is back on. I've been searching the internet at work for information on this error, but everything I find has to do with Win2000. I have WinXP, so I'm still stuck without a computer at home. Which make blogging more difficult, but it certainly does force me outside to enjoy the warming Spring temperatures.
Anyway, if anyone has magical solution for fixing this error, please let me know. Thanks.
blue screen of death, computer, computer screen, damn microsoft, dsl, error, error c000021a, fatal system error, logon error, monitor, phone service, verizon, windows xp, winxp, xp
Tags: blue screen of death, computer, computer screen, damn microsoft, dsl, error, error c000021a, fatal system error, logon error, monitor, phone service, verizon, windows xp, winxp, xp