usb_modeswitch Installs usb_modeswitch Installs the latest version of usb_modeswitch: Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. Packman Repository Packman package repository for openSUSE 11.2 Latest versions and additional packages in the most popular 3rd party repository http://packman.mirrors.skynet.be/pub/packman/suse/11.2 usb_modeswitch usb_modeswitch > usb_modeswitch Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch-debuginfo usb_modeswitch > usb_modeswitch-debuginfo Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch-debugsource usb_modeswitch > usb_modeswitch-debugsource Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch Installs usb_modeswitch Installs the latest version of usb_modeswitch: Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. Packman Repository Packman package repository for openSUSE 11.1 Latest versions and additional packages in the most popular 3rd party repository http://packman.mirrors.skynet.be/pub/packman/suse/11.1 openSUSE:11.1 openSUSE 11.1 distribution The openSUSE 11.1 distribution. http://download.opensuse.org/repositories/openSUSE:/11.1/standard/ usb_modeswitch usb_modeswitch > usb_modeswitch Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch-debuginfo usb_modeswitch > usb_modeswitch-debuginfo Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch-debugsource usb_modeswitch > usb_modeswitch-debugsource Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch Installs usb_modeswitch Installs the latest version of usb_modeswitch: Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. Packman Repository Packman package repository for openSUSE 11.0 Latest versions and additional packages in the most popular 3rd party repository http://packman.mirrors.skynet.be/pub/packman/suse/11.0 openSUSE:11.0 openSUSE 11.0 distribution The openSUSE 11.0 distribution. http://download.opensuse.org/repositories/openSUSE:/11.0/standard/ usb_modeswitch usb_modeswitch > usb_modeswitch Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch-debuginfo usb_modeswitch > usb_modeswitch-debuginfo Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes. usb_modeswitch-debugsource usb_modeswitch > usb_modeswitch-debugsource Several new USB devices (especially high-speed wireless WAN stuff, they're expensive anyway) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature "ZeroCD (TM)". Fortunately there are things like human reason, USB sniffing programs and "libusb". It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that does the switching, and to reproduce the same thing with Linux. USB_ModeSwitch makes the last step considerably easier by taking the important parameters from a configuration file and doing all the initialization and communication stuff. It does NOT check for success afterwards as of now. The right approach would be to consult /proc/bus/usb/devices (or the output of "lsusb") before and after execution to note any changes.