vb.net barcode library GETTING E VERYTHING UP AND RUN NING in Java

Creator Code-39 in Java GETTING E VERYTHING UP AND RUN NING

If you find both component parts of the PCI ID in the line, as in this example, then you ve found the .inf file you need. (In fact, you ll probably find many lines matching what you need, which is fine.) You must now transfer the .inf file, along with the .sys and .bin files (if any .bin files were included with the driver) to the computer on which you want to install the drivers. This can be done by putting them onto a floppy disk, by burning them onto CD, or by using a USB memory stick. Create a new directory called driver on the desktop and save them there. Your procedure from this point depends on if Ubuntu recognized your wireless networking device when you first booted but was unable to make it work correctly. If it did then you will need to blacklist the built-in driver, so that NdisWrapper can associate with the hardware. If the device wasn t recognized, you can skip straight to the Using NdisWrapper to Install the Drivers section. Blacklisting Existing Drivers To blacklist the existing built-in driver that didn t work with your wireless device, you need to find out the name of the kernel module and then add it to the /etc/modprobe.d/ blacklist file. Here are the steps:

the entry in the list for your wireless network device. This is the one you discovered in steps 1 and 2 earlier, in the Identifying Your Wireless Network Hardware and Sourcing Drivers section.

look for the line that begins info.linux.driver. Then look in the value column, and make a note of what s there. For example, on our test notebooks, the value column read rt2500usb. Close Device Manager.

following to open the blacklist configuration file in the Gedit text editor:

gksu gedit /etc/modprobe.d/blacklist 4. At the bottom of the file, type the following on a new line: blacklist modulename

Replace modulename with the name of the module you discovered earlier. For example, on our test system, we typed the following (as shown in Figure 8-5):

You should now find that the wireless network device is no longer visible when you click the NetworkManager icon, and all you see is a Manual Configuration option. This is good, because it means the hardware no longer has a driver attached, and you can now tell NdisWrapper to use the hardware. Using NdisWrapper to Install the Drivers On the Ubuntu computer on which you wish to install the drivers, you should now have the .inf file from the previous steps, plus the .sys and possibly .bin files that constitute the driver. You should have copied these files from the removable storage device into a new folder on your desktop named driver.

Note If you ve used a USB memory stick to transfer the files, it should appear automatically on the desktop as soon as it s inserted. When you ve finished with it, right-click the desktop icon, and select Unmount. You must do this before physically removing any kind of USB memory device, as explained later in this chapter.

To install the driver using NdisWrapper, follow these instructions:

2. Click the Install New Driver button. 3. The Install Driver dialog box appears, prompting you to select the .inf file for your

driver folder on your desktop. Double-click the desktop folder, and then doubleclick the driver folder listed in the right column. Select the .inf file you copied in the driver folder and then click the Open button.

5. Back in the Install Driver dialog box, click the Install button. 6. At this point, you should see the driver listed at the left column of the Wireless

Network Drivers dialog box. It specifies the name of the driver installed and whether the hardware is installed. If it says the hardware isn t installed, you ve probably selected the wrong .inf file, or might be using the wrong driver file. Return to the previous sections and try to get an alternative Windows driver.