Using NDISWrapper in SLED10

After you run the installwifi script, all that is needed to do is to load the card manually into YaST yast2 lan. Making sure to use ndiswrapper as the module name for the card.

yast2-lan-ndiswrapper.png

After you run the installwifi script, all that is needed to do is to load the card manually into YaST yast2 lan. Making sure to use ndiswrapper as the module name for the card.

• Broadcom BCMWL5 Chipset
• Netgear WG311v3 Chipset

• Broadcom BCMWL5 Chipset
• Netgear WG311v3 Chipset

Even though the procedure to install and use NDISWrapper is very simple. I choose to use an RPM since it has the ability to download the driver files. I then had a simple script called installwifi which will load NDISWrapper with the downloaded Windows drivers.

So far I have created two different RPMs for the:

• Broadcom BCMWL5 Chipset
• Netgear WG311v3 Chipset

(:title Using NDISWrapper in SLED10:)

The objective of this project is to create a simple way of setting up wireless cards of multiple workstations. What I came up with was a RPM template that:

1. Loaded the correct Windows NDIS drivers into the Linux workstation.
2. Ran a script that loaded these drivers into memory using ndiswrapper.

Even though the procedure to install and use NDISWrapper is very simple. I choose to use an RPM since it has the ability to download the driver files. I then had a simple script called "installwifi"

Dual Boot SLED workstation where the second Operating System (most likely Windows XP) can also be run within SLED as a virtual workstation. When companies try to migrate their workstations to SLED they run into a number of problems (both technical and political). However if the end-user were to have the option of “having your cake and eating it too” the migration would be much smoother. Being able to run both Windows and Linux at the same time would solve a nearly all of the technical and political issues surrounding the migration.