clipped from specialed.about.com Pen scanners have been around for a number of years now, however, the current technology has had a positive impact on the accuracy of the pen scanners and they have improved tremendously. The pen scanner is used the same way you use a marker highlighter. Simply take the pen scanner across the text. The pen scanner will let you scan, store and transfer your printed text as well as smaller images to your computer. It's ideal for taking notes or scanning text for students that use a text reader. Many of the newer pen scanners also have synthetic voice and read the scanned text. Many teachers claim that the use of the scanner pens aids children with dyslexia. The student can benefit tremendously from the use of scanner pens for test taking, note taking, greater access to materials, auditory support and overall productivity.
|
Saturday, November 14, 2009
Pen Scanner
Thursday, April 16, 2009
Team Explorer Error
After I installed IE8 two weeks ago, I couldn't use Team Explorer anymore. I got the "Unable to cast COM object of type . . . {6D5140C1-7436 ...." error. The weird thing is it worked fine when running Visual Studio in user mode. It seems like a permission issue to me. Following the suggestion posted here by re-registering actxprxy.dll didn't fix the problem. I tried that in both system32 and syswow64 (I'm running Vista 64 SP1).
During that time I was so tied up with my work that I kind of lived with it by running 2 instances of Visual Studio; one in admin mode for my development and the other in user mode just for using Team Explorer. Until recently I needed Profiler and it crashed every time when it tried to load the report. Reinstalling Visual Studio 2008 SP1 didn't help. I had a feeling that it might be related to the initial problem so I tried re-registering actxprxy.dll again. But this time, I unregistered it first in both system32 and syswow64 before re-registering it. It worked! Both Team Explorer and Profiler are now back to live. (Visual Studio's devenv is a 32-bit process so doing so just in syswow64 should do the trick I guess).
During that time I was so tied up with my work that I kind of lived with it by running 2 instances of Visual Studio; one in admin mode for my development and the other in user mode just for using Team Explorer. Until recently I needed Profiler and it crashed every time when it tried to load the report. Reinstalling Visual Studio 2008 SP1 didn't help. I had a feeling that it might be related to the initial problem so I tried re-registering actxprxy.dll again. But this time, I unregistered it first in both system32 and syswow64 before re-registering it. It worked! Both Team Explorer and Profiler are now back to live. (Visual Studio's devenv is a 32-bit process so doing so just in syswow64 should do the trick I guess).
Labels:
programming,
technology,
Visual Studio
Sunday, January 11, 2009
Saturday, January 10, 2009
Hello World 2009!
It's time to extend my memory on the web.
Subscribe to:
Posts (Atom)