I just upgraded to Slack 12.1, and now I cannot get ndiswrapper to work. Did anything change with this? Thanks.

If you just upgraded, I would guess your kernel was also upgraded. In which case you will need to recompile ndiswrapper against the new kernel.

I did a fresh install of Slack. So, ndiswrapper is being compiled against the new kernel. Sorry, I should have said that in my first post.

How far do you get through the install of ndiswrapper and what errors do you get? And which version are you using?

Just in case you're using something else, your best bet for getting ndiswrapper to work would be to use the SlackBuild at slackbuilds.org. If you want a pre-built package and are using the default generic-smp kernel you could also use Alien Bob's package (1.52) here (he also includes a SlackBuild): http://www.slackware.com/~alien/slackbuilds/

I forgot all about the slackbuilds. The only thing that I am curious about is that I am trying to setup a dualboot on my laptop between Slackware and Ubuntu (I need ubuntu for something for work). How exactly would I accomplish this, and where can I read up on it? Thanks.

Ubuntu has its own packages for ndiswrapper so use those and use the slackBuilds for slackware. You can probably use the same source, though. Ndiswrapper is really easy to setup. You don't need any special instructions other than the documentation that comes with the source.

Also, since you are dual-booting with Ubuntu I recommend that you configure your main boot loader (installed on the MBR) to chain load to the other OS's boot loader installed on its root partition. That way you can keep them separate which will make upgrading kernels a lot less of a hassle.

I wasn't even aware that Ubuntu had ndiswrapper packages. Thanks for that info. As far as the MBR, doing that will keep the two OS's completely separate from eachother? Cause I think I am having some trouble with each OS looking at the others' SWAP partition. How can I ensure that each OS has it's own SWAP partition and not even look at the others? And finally, which OS do you suggest I install first? Ubuntu, or Slackware? Thanks for all the info, guys. It's really appreciated.

On my laptop i have a dual boot beetween Slackware 12 and a Debian 4.0. The swap partition is the same for both of them and after 4 months from the Debian install, i still have no problem (if you have a lot of RAM, usually the swap remains empty all the time, and after a poweroff/reboot, the swap clears)

First install Slack with the lilo in the MBR. Next install Ubuntu and when it installs the Grub, make sure it installs it in the first sector of the partition where ubuntu is installed.
Afterwards modify the lilo something like these:

(sda8 is the partition where my Debian is installed. Modify the value for the partition where you will install Ubuntu).

Why does it matter if they share a swap partition? Are you planning on using it for suspending/hibernation? Otherwise, it shouldn't matter. If you are using those features and need separate swap partitions, then do that. Use something like a gparted liveCD and add another swap partition which is only used for one of the OSs.

You don't have to install your bootloader on the MBR, but I usually do (If you don't make sure your root partition is active/bootable). Whichever is your main OS (or the one that will stay the longest) I recommend to install its bootloader on the MBR (if you Windows install that first, and then the main Linux OS on the MBR). While you are in your main Linux distro, configure your bootloader to chainload the other linux parition. For your other Linux OS, install its boot loader onto its root partition. Now, when you boot your computer, if you choose the other Linux distro it will go to its bootloader.

If you don't want to keep them separate I recommend using Ubuntu's bootloader, since Ubuntu updates it's kernel images frequently and this automagically updates the grub configuration. So, in this case, either install Ubuntu last or don't install LILO when you install Slackware.

Again, something I was not aware of. I was always told that the two distros had to work off of different swap partitions. If this is not the case, then I will fix that. Should I make the swap space bigger though? Or is double the RAM still ok?

As far as the actual ndiswrapper issue I was having, it is all resolved now. Using the build script from slack builds, it works perfectly. Had some DNS issues because my /etc/resolv.conf file did not have any DNS settings. And even now, the DNS servers are statically assigned, rather than having the computer pull the DNS settings from the DHCP server. But other than that, my wireless is working perfectly. Thanks for all the help everyone. Much appreciated.

No, you should not need to. In fact, you may not even need 2XRAM for your swap. It really depends on your specific needs (ie. what you are running) and how much RAM you have. More than likely if you have a lot of RAM (1GB+) and don't have virtual machines running all the time, you probably will rarely use swap, if ever. In these cases it is safe to use less. On this current machine I have a swap of 512MB and my RAM is about 1.3GB. Even if I have tons of apps open I never use swap. Even when using vmware I rarely use swap, and if I do it is very little (less than 64MB).

I have an older machine that has 288MB RAM (400MHz PII) and I set my swap partition to 500MB. It has been enough for me thus far (and I definitely use it occasionally on that machine). The point is that 2X/1.5X rule is only a guideline and you should determine what you actually need by running your system under what you think would be a "max memory load" and check the machine stats using something like htop, top, etc.

I generally try to avoid using swap in the first place as it is slow. You can setup vmware, for instance, so that it tries not to use it, and if your resource hungry apps are causing you to use it then look for lighter alternatives. Even on my old machine I can usually avoid using swap with my setup.