Each module or package should be compiled for compatibility with the Linux kernel currently in use. Derivatives NoteOS Note OS is 'a lightweight system' based on Slax. It shares Slax features, such as KDE 3 and a quick boot time. It fully supports Slax modules and the ability to save 'changes' to writable media.

Topic moved to 'General Chat', as HOWTO's and resources is for posting resources and documentation, rather than help requests. Welcome, gsthompson277! Hamza is correct, you can convert your sq3 modules to sq4.

Some modules may not work--especially if you're running 64-bit porteus. With that as my segue, I have a couple more questions for you -- What version of Porteus are you running? I'm assuming version 0.9, rather than version 1.0 (currently in testing/beta).

32-bit or 64? For your wireless, please try opening a terminal and running the command 'pns-tool' without the quotes. Your wireless card may already be detected by the kernel.

Follow the script, and let us know if that gets your wireless up and running. If not, let us know what information it gives you. Also, if it fails, enter the command 'lspci' and post the output here. Yes I am currently running.9 on 64 bit system. I will run the two commands and then post my results and let you know. Thank you very much for your support.

Posted after 2 hours 19 minutes 1 second: I met with no success under the pns-tool. My keyboard display shows that my wifi is disabled and I could not use the key to enable it. The information I received under the LSPCI tool. I received the following information: Network Controller: REALTEK SEMICONDUCTOR CO, LTD Device 8171 (Rev 02) Ethernet Controller: RTL8101E / RTL8102E PCI EXPRESS FAST ETHERNET CONROLLER (REV 02) I tried configuring under Eth0 and Wlan0 and got nothing both times. I would like to not the my actual device driver under Windows 7 Ultimate is an:'RTL8191SE' of which I do have the drivers for Linux in a.tar file. Thank you in advance for the helpd.

The industry average of $0.66.

Obk, so take this post with a grain of salt, because I don't have much experience myself with hardware issues (I'm only a moderator here because the admins realized early on that they couldn't get rid of me, and I'm pretty handy in a street fight). Two methods for you: 1) you could try using the windows driver via ndiswrapper. See the FAQ (item 10) in the 64-bit section for more info. 2) you can compile the linux driver in the tarball. Google sketchup. See the tutorial here: That tutorial may work for you 'out of the box' if you are using saved changes in porteus, but you're better off building a module with the driver, as saved changes are prone to corruption if saved directly to a FAT or NTFS partition. To build a module, you'll need to follow the tutorial up through 'make install', and then copy the driver, which will be in /mnt/live/memory/changes/lib/modules/2.6.XX.smp/kernel/drivers/net/wireless/ to a new directory that will serve as the root of the module. For example, on your desktop, make a directory 'wifidriver' (the path to this file will be /root/Desktop/wifidriver/).

Inside this directory, you have to make nested directories that are the same as the path to where the driver goes in your system: lib/modules/2.6.XX.smp (copying what you get from the 'make install' process)/kernel/drivers/net/wireless/). Copy the driver from your live filesystem to the wireless directory you just made.

Then, you are ready to build a module from this directory. Open a console, and enter: 'cd /root/Desktop' then: 'dir2lzm wifidriver wifidriver.lzm' All, without the quotes.

That will create a module with the full path to the driver, and you can put that module in your /porteus/modules folder, so that it will be inserted into your filesystem at startup, even in 'always fresh' mode. Maybe read through some of the module documentation on the website (porteus.org) first, to get an idea of how this process works. If anyone has anything to add, feel free. If I have a chance tomorrow, I'll take a stab at building this module, and if I can get it to work, I'll upload it for you. Once I have a module up, it will go in /poerteus/modules on your usb stick.

For beny's file, you would copy it into your live filesystem, with saved changes. So you would boot into porteus, open dolphin (file manager), and navigate through /usr/.to the specified folder, and paste the file. It takes a little getting used to, because you have two worlds -- the files that create the live system (modules, saved changes, and rootcopy) and the live system itself. You'll get there Posted after 3 hours 39 minutes 39 seconds: here's the module: download that, and move it to the folder on your flash drive: /porteus/modules/ this can be done from windows or linux. Modules that are put in /porteus/base makeup the files that are used to build porteus at each bootup. Any add-on modules that should be inserted every time you boot up (like drivers or modules with config files, or applications you always want) go in /porteus/modules/, and modules that you want to have available but not always active (such as applications you don't use that often) go in /porteus/optional.