Posts Tagged ‘Windows XP’
The Market are too Advanced for Your Computer
Posted by Parkzone Corsair in computer on March 29th, 2010
To illustrate the importance of accessorizing, we like to use the “plain dough” analogy. Let’s say that a brand new computer is a batch of plain dough – waiting to be flavored and baked into something useful. If we want to use this dough to make a delicious batch of chocolate chip cookies, we would need to “accessorize” this dough with chocolate chips and a little brown sugar. If we want to use this dough into in a warm loaf of sesame seed bread on the other hand, we’d need to “accessorize” the dough with yeast and sesame seeds.
Like “plain dough,” the brand new computer isn’t very useful by itself. It needs accessorizing.
Depending on what’s needed, accessorizing doesn’t need to be expensive. In fact, you can get away with paying a minimal amount for extra software and hardware if these accessories are for children. It’s when these accessories are work requirements or when they’re needed to produce works of quality for any other reason that they can become rather expensive. And this expense applies to microphones, digital cameras, PDAs, scanners, video cams, and more.
Regardless of cost, it’s important to understand that accessories can become “necessities,” and that the best time to get them is the moment you buy a new computer. Waiting too long to accessorize can cause more problems than necessary because while you wait, manufacturers continuously develop new technologies – technologies that your computer won’t be able to accommodate in the future. Once you’re ready to accessorize, the new products on the market are too advanced for your computer and they just won’t work. This is a typical problem experienced by those who want to use hardware designed for Windows Vista on a Windows XP or Windows 2000 machine.
USB Classes Included With Windows XP
Posted by Parkzone Corsair in USB on February 1st, 2010
Not every device requires its own INF file. Many devices that use the system’s class drivers can use the INF file that Windows provides for the class. These are some INF files for USB classes included with Windows XP.Because Windows XP and later prefer signed drivers, if you provide an unsigned driver for a device in a supported class, Windows XP and later won’t
use your driver and instead will select a compatible ID from the class’s INF file.
An INF file is considered part of the driver package, so Windows XP and later prefer a system-provided INF file for a system driver over an unsigned, vendor provided INF file for the same driver even if the vendor’s INF file contains a matching hardware ID. When the best match is an unsigned driver, operating-system settings can affect whether Windows blocks installation, installs the driver with a warning, or installs with no warning. To change the setting, in Windows Control Panel, select System > Hardware > Driver Signing.
A device that uses a class driver can have a custom, signed INF file with vendor specific strings that display in the Device Manager. For example, the entry for a HID can be a vendor-specific string instead of the default USB Human Interface Device. Many INF files provided with Windows contain sections with manufacturer specific information. When a device passes WHQL tests, Microsoft can add the device’s sections to an existing INF file or add a manufacturer-specific INF file to the files distributed with Windows.
