I have a co-worker's HP ScanJet 6350 on my desk, connected to the office XP machine that is my "daily drive". I've not had to load any HP drivers—XP supported it from the moment I first plugged it in—and have been testing it with the built-in scanning support tools. It works very nicely.
Here's the Vista angle: the reason my co-worker is letting me use it is because her home system (running Vista) can't support it. When we tried it on a Vista test system at the office, the same thing happens: Vista can't find drivers for this unit, and HP isn't planning on writing any. This is stupid.
It was, and has been my understanding that the USB specification includes (as does SCSI) base drivers for specific classes of hardware. In practical, every day terms, this hardware class support permits the use of drives (solid-state and spindle-based) and interface devices (e.g., keyboard or mouse) without the need to install vendor-specific drivers. Of course, if you install the vendor driver you may find additional functionality, but the idea behind the class drivers is to gain the basic functionality that is expected from that class of hardware.
That said, the situation with the ScanJet implies that there isn't an "image capture" hardware class for USB (even though Windows lumps them together for use with the 'Scanner and Camera Wizard'). Here we have a perfectly good scanner (with document feeder!) that was acquired about 7 years ago for over $300 (in 2000 dollars; don't forget about inflation), and now we're forced into purchasing new hardware to get the same functionality under Vista.
(Note: This scanner is both USB and SCSI capable, but we've only tried it under Vista with the USB connection. The SCSI support in Vista may include scanner class drivers, but I don't have a SCSI-equipped Vista machine to check this out.)
Add to the annoyance: I have an HP ScanJet 6250 at home, which is the older sibling of the 6350. It is connected to my wife's XP machine using SCSI (which is faster than using the 6250's USB v1 port) and it has been functioning nicely for us since 1998. Of course, if the 6300 series isn't supported, it's a safe (and confirmed) bet that the 6200 series isn't.
This is a critical piece of hardware for my wife, so now I can't upgrade her system to Vista (which it would otherwise run well, as it is identical hardware to my Vista desktop test system) until I get a new scanner for her. Grrr!
Dribs and drabs of stuff that others might find useful, too.
Monday, December 17, 2007
Friday, December 14, 2007
Vista Movie Maker and DVD Maker
Okay, here's the deal.
I had been and still am unhappy with the frequent crashes that occur in the XP version of Movie Maker.
Back when Version 9 of Pinnacle Studio was the latest/greatest version, I paid real dollars for it, and found that it a) couldn't open the AVIs that I'd already captured using Movie Maker, and b) couldn't capture new video because the drive test failed. And no, I didn't get much help from Pinnacle support, as my system was using nVidia's RAID0+1 (which actually has phenomenal throughput), and they don't support hardware RAID. Phooey.
Fast forward to now. My office machine is still running XP because I have some Vista incompatibility issues on several important tools, especially Enterprise Manager for SQL 2000.
I've been working for several hours to capture, edit and publish videos for internal use, and Movie Maker keeps crashing on me. The main headache is the inability to save the final product as an AVI; it is fine for short chapters (5-6 min), but anything longer won't complete.
So I pull the source AVIs and the Movie Maker project over to my Vista laptop that I've brought into the office, and voila, the Vista version of Movie Maker doesn't even burp.
And rather than installing Nero to author a DVD based on the new AVIs I've generated, I used DVD Maker to do it. I'm a little disappointed that I was unable to give titles to the "chapters" I created, but the key thing is that it worked. Score another one for Vista.
Of course, I'm still hopeful that XP SP3 will include bugfixes for Movie Maker that will bring some stability and usability back to my XP boxes.
I had been and still am unhappy with the frequent crashes that occur in the XP version of Movie Maker.
Back when Version 9 of Pinnacle Studio was the latest/greatest version, I paid real dollars for it, and found that it a) couldn't open the AVIs that I'd already captured using Movie Maker, and b) couldn't capture new video because the drive test failed. And no, I didn't get much help from Pinnacle support, as my system was using nVidia's RAID0+1 (which actually has phenomenal throughput), and they don't support hardware RAID. Phooey.
Fast forward to now. My office machine is still running XP because I have some Vista incompatibility issues on several important tools, especially Enterprise Manager for SQL 2000.
I've been working for several hours to capture, edit and publish videos for internal use, and Movie Maker keeps crashing on me. The main headache is the inability to save the final product as an AVI; it is fine for short chapters (5-6 min), but anything longer won't complete.
So I pull the source AVIs and the Movie Maker project over to my Vista laptop that I've brought into the office, and voila, the Vista version of Movie Maker doesn't even burp.
And rather than installing Nero to author a DVD based on the new AVIs I've generated, I used DVD Maker to do it. I'm a little disappointed that I was unable to give titles to the "chapters" I created, but the key thing is that it worked. Score another one for Vista.
Of course, I'm still hopeful that XP SP3 will include bugfixes for Movie Maker that will bring some stability and usability back to my XP boxes.
Subscribe to:
Posts (Atom)