This is a maintenance release of the MultiMac drivers. This package contains all the MultiMac drivers, however only the E1000B, MMIGB, MMLEM, MMAE, and MMRE drivers have been updated. The E1000B and the MMRE drives were updated to add new supported devices. The other 3 drivers are simply rebuilt and have no functional changes. This update is recommended for all users. ------------------------------------------------------------------------------------- NVIDIA PCIe NIC Driver for OS/2 Info ==== This is a driver for NVIDIA family integrated LAN adapters. It is based on the linux forcedeth driver and is supposed to support the same scope of adapters. This driver supports the following devices. nForce, nForce2, nForce3, CK804, MCP04, MCP51, MCP55, MCP61, MCP65, MCP67, MCP73, MCP77, MCP79, MCP89 More specifically, only the following device IDs are supported. All are Vendor ID 10DE. 0037, 0038, 0056, 0057, 0066, 0086, 008C, 00D6, 00DF, 00E6, 01C3, 0268, 0269, 0372, 0373, 03E5, 03E6, 03EE, 03EF, 0450, 0451, 0452, 0453, 054C, 054D, 054E, 054F, 07DC, 07DD, 07DE, 07DF, 0760, 0761, 0762, 0763, 0AB0, 0AB1, 0AB2, 0AB3, 0D7D Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. First check the Vendor ID. If the Vendor ID of your hardare is not 10DE, then your hardware is not supported by this driver. Then check the Device ID. If the Device ID is not in the list above, then your hardware is not supported by this driver. If the Vendor ID of your hardware is 10DE, and the Device ID is listed above, then this driver should work. The installation is very simple - just unpack this archive into your IBMCOM\MACS directory and, mpts.exe and set up driver as any other network driver. Then reboot. Copyright and License ===================== Copyright (c) 2012-2023 David Azarewicz <david@88watts.net> All rights reserved. Copyright (C) 2003,4,5 Manfred Spraul Copyright (C) 2004 Andrew de Quincey Copyright (C) 2004 Carl-Daniel Hailfinger Copyright (c) 2004,2005,2006,2007,2008,2009 NVIDIA Corporation (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. The distribution package also includes a version of the driver in the trace directory. This version has tracing enabled for debugging purposes. You would only use the tracing driver if you are debugging a problem in coordination with the developer. See https://www.arcanoae.com/wiki/multimac for more information. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = NVETH$, /A1 = NVETH2$, /A2 = NVETH3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM=n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. Options ======= There are several protocol.ini switches you can tune the driver work: MODE - the speed to work on, see nveth.nif for details OPTIMIZE - there are two modes of driver work - with throughput optimization and without, which results in different set of interrupts to enable. This modes came from forcedeth linux sources and you can study the sources for more info. I do not have the hardware to test the driver, so its you to try which setting suits best for you. TIMER - nvidia adapters have special interrupt driven by its own internal timer. This switch enables or disables the use of this interrupt. Switching off the timer will reduce the number of interrupts generating by the driver thus lowering system load, but it also could increase the latency in processing the rx/tx queues. Its up to you to find out whats is the best. LINK_TIMER - if set to "YES", driver periodically queries HW chip for the actual link speed and resetup the chip according to it. RXCHAIN - the os/2 ndis drivers have two methods to pass received data to the protocol drivers (tcpip and others) - receive chain and receive lookahead. The first one should be better. This option was introduced for testing purposes, now driver seems to work fine in both ways, so you can safely leave the switch intact. NETADDRESS - specifies the MAC address to use instead of the vendor supplied unique address. Must be exactly 12 hex digits long. Example: NETADDRESS = "4061865F3888" Getting Support and Reporting Problems ====================================== For more information and to report problems please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code is available at: http://svn.netlabs.org/repos/multimac Thanks ====== Thanks to Nickk for creating this driver. Thanks to Ruediger Ihle for RM code, explanations and testing. Thanks to all those brave guys who tested it. Changelog ========= 0.1.16 01-Jul-2023 through 0.1.14 08-May-2015 - David Azarewicz No changes to this driver. Recompiled for new package release, which links in system libraries which may or may not have changed. 0.1.13 23-Aug-2014 - David Azarewicz Corrected status checking in interrupt handler. 0.1.12 22-Jan-2014 - David Azarewicz Fixed a problem loading multiple instances of the driver. 0.1.11 13-Oct-2013 - David Azarewicz Converted to use the Drv16 kit. Fixed some errors in the NDIS setup. No functional changes 0.1.10 24-Apr-2012 - David Azarewicz New packet buffer allocation routines Changes to debugging routines. Added tracing functinality Changes due to MultiMac restructuring Added logging functionality 0.1.9 - David Azarewicz Minor changes to accomodate MultiMac restructuring 0.1.8 Fixed suspend/resume <-- Still to be done! Version 0.1.8 has not been released yet! Added support for ACPI suspend/resume removed the -r compiler switch 0.1.7 Fixed PCI config space save/restore for suspend/resume 0.1.6 Added NETADDRESS support 0.1.5 Added /Q switch. When present on the command line, indicates quiet mode and does not output normal messages. Error messages are still output normally. 0.1.4 Moved to the MultiMac project. 0.1.3 Changes to interrupt handler for older hardware. Changed link speed setup auto negotiate so it completes before binding. MODE= settings now work. 0.1.2 Fixed errors in link speed setup. Fixed reentrancy problem and block during interrupt in transmit. 0.1.1 Added APM support 0.1.0 First Mensys supported version. Changed ring setup. Minor interrupt handler changes. 0.0.7 When loading several drivers, the second driver instance name starts from NVETH2$ instead of NVETH1$. 0.0.6 Added support for newer NVIDIA chipsets (MCP73, MCP77, MCP79, MCP89). Added initialization for some Realtek & Vitesse PHYs. 0.0.5 ? Untested fix to load multiple driver instances for several nvidia NIC's on same machine. Unfortunatelly, the only tester with dual nvidia nic has his MB broken (not by this driver, by screwdriver, so dont worry ;)). So i have no hardware to test it on, but i hope, you have it! Please, test and report. 0.0.4 Added extended description for switches in readme. Fixed trap in OS2KRNL due to accident block during interrupt processing. 0.0.3 Added support for promiscous mode. 0.0.2 nveth.sys renamed to nveth.os2. Fixed bug with nforce1 adapter recognition. Compatibility fix for acpi's internal oemhlp$ driver. Added RM support. 0.0.1 Initial release, full of bugs. ============================================================================= GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>. Attansic Technology Corp. L1 Gigabit Ethernet driver Info ==== This is an NDIS driver for Attansic Technology Corp. L2 FastEthernet LAN adapters. The source code from the FreeBSD "ae" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. Attansic Technology Corp, L1 Gigabit Ethernet These correspond to the following Vendor:Device numbers: 1969:1048 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008 Stanislav Sedov <stas@FreeBSD.org>. All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMAGE$, /A1 = MMAGE2$, /A2 = MMAGE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Jun-2017 - David Azarewicz Initial release. ============================================================================= Intel(R) PRO/1000 NIC Driver for OS/2 Info ==== This is an NDIS driver for Intel(R) PRO/1000 LAN adapters. The source code from the FreeBSD e1000 "em" driver has been compiled to run on OS/2. This driver supports the following device IDs. All are Vendor ID 8086. 0D4E, 0D4F, 0D4C, 0D4D, 0D53, 0D55, 0DC7, 0DC8, 0DC5, 0DC6, 1049, 104A, 104B, 104C, 104D, 105E, 105F, 1060, 107D, 107E, 107F, 108B, 108C, 1096, 1098, 109A, 10A4, 10A5, 10B9, 10BA, 10BB, 10BC, 10BD, 10BF, 10C0, 10C2, 10C3, 10C4, 10C5, 10CB, 10CC, 10CD, 10CE, 10D3, 10D5, 10D9, 10DA, 10DE, 10DF, 10E5, 10EA, 10EB, 10EF, 10F0, 10F5, 10F6, 1501, 1502, 1503, 150C, 1525, 153A, 153B, 1559, 155A, 15A0, 15A1, 15A2, 15A3, 156F, 1570, 15B7, 15B8, 15B9, 15BB, 15BC, 15BE, 15BD, 15D6, 15D7, 15D8, 15DF, 15E0, 15E1, 15E2, 15E3, 15FB, 15FC, 15F9, 15FA, 15F4, 15F5, 1A1E, 1A1F, 1A1C, 1A1D, 294C, 550A, 550B, 550C, 550D, 550E, 550F, 5510, 5511, 57A0, 57A1, 57B3, 57B4, 57B5, 57B6, 57B7, 57B8 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. First check the Vendor ID. If the Vendor ID of your hardare is not 8086, then your hardware is not supported by this driver. Then check the Device ID. If the Device ID is not in the list above, then your hardware is not supported by this driver. If the Vendor ID of your hardware is 8086, and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 8086:109A hardware. Copyright and License ===================== Copyright (c) 2014-2023 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2001-2010, Intel Corporation All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = E1000B$, /A1 = E1000B2$, /A2 = E1000B3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code is available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.8 15-Sep-2023 - David Azarewicz Updated from BSD sources which added several new chips. Refreshed with updated system libraries. 1.1.7 11-Jul-2022 - David Azarewicz Updated from BSD sources to add several new chips. Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Updated from BSD sources to add several new chips. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Updated to current version from FreeBSD sources. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Minor update from FreeBSD. Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to latest FreeBSD source. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.7 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to current FreeBSD source. 0.1.6 03-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.5 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.4 08-Oct-2016 - David Azarewicz Refreshed release. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.3 21-Jul-2016 - David Azarewicz Updated to current FreeBSD source. (7.6.1-k) 0.1.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.1 06-Sep-2015 - David Azarewicz Updated FreeBSD driver to version 7.4.2. 0.0.2 03-Sep-2015 - David Azarewicz No changes to this driver. Recompiled for new package release, which links in system libraries which may or may not have changed. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 08-May-2015 - David Azarewicz Initial release. ============================================================================= Atheros AR813x/AR815x PCIe Ethernet NIC driver Info ==== This is an NDIS driver for Atheros AR813x/AR815x PCIe LAN adapters. The source code from the FreeBSD "alc" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. Atheros AR8131 PCIe Gigabit Ethernet Atheros AR8132 PCIe Fast Ethernet Atheros AR8151 v1.0 PCIe Gigabit Ethernet Atheros AR8151 v2.0 PCIe Gigabit Ethernet Atheros AR8152 v1.1 PCIe Fast Ethernet Atheros AR8152 v2.0 PCIe Fast Ethernet Atheros AR8161 PCIe Gigabit Ethernet Atheros AR8162 PCIe Fast Ethernet Atheros AR8171 PCIe Gigabit Ethernet Atheros AR8172 PCIe Fast Ethernet Killer E2200 Gigabit Ethernet Killer E2400 Gigabit Ethernet Killer E2500 Gigabit Ethernet These correspond to the following Vendor:Device numbers: 1969:1063, 1969:1062, 1969:1073, 1969:1083, 1969:2060, 1969:2062, 1969:1091, 1969:1090, 1969:10A1, 1969:10A0, 1969:E091, 1969:E0A1, 1969:E0B1 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2009, Pyun YongHyeon <yongari@FreeBSD.org> All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMALC$, /A1 = MMALC2$, /A2 = MMALC3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.7 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to current FreeBSD source. 0.0.6 03-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 08-Oct-2016 - David Azarewicz Refreshed release. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 21-Jul-2016 - David Azarewicz Updated to current source. 0.0.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= Attansic Technology Corp. L2 FastEthernet driver Info ==== This is an NDIS driver for Attansic Technology Corp. L2 FastEthernet LAN adapters. The source code from the FreeBSD "ae" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. Attansic Technology Corp, L2 FastEthernet These correspond to the following Vendor:Device numbers: 1969:2048 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2023 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008 Stanislav Sedov <stas@FreeBSD.org>. All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMAE$, /A1 = MMAE2$, /A2 = MMAE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.8 15-Sep-2023 - David Azarewicz Refreshed with updated system libraries. 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 02-Dec-2016 - David Azarewicz Fix to fixup bad MAC address from EPROM. 0.0.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= Atheros AR8121/AR8113/AR8114 PCIe Ethernet NIC driver Info ==== This is an NDIS driver for Atheros AR8121/AR8113/AR8114 PCIe Ethernet adapters. The source code from the FreeBSD "ale" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. Atheros AR8121/AR8113/AR8114 PCIe Ethernet These correspond to the following Vendor:Device numbers: 1969:1026 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 1969:1026 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008, Pyun YongHyeon <yongari@FreeBSD.org> All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMALE$, /A1 = MMALE2$, /A2 = MMALE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.6 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to current version of FreeBSD source. 0.0.6 03-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 08-Oct-2016 - David Azarewicz Refreshed release See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 21-Jul-2016 - David Azarewicz Updated to current version of FreeBSD source. 0.0.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= Attansic Technology Corp. L1 Gigabit Ethernet driver Info ==== This is an NDIS driver for Attansic Technology Corp. L2 FastEthernet LAN adapters. The source code from the FreeBSD "ae" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. Attansic Technology Corp, L1 Gigabit Ethernet These correspond to the following Vendor:Device numbers: 1969:1048 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008 Stanislav Sedov <stas@FreeBSD.org>. All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMAGE$, /A1 = MMAGE2$, /A2 = MMAGE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Jun-2017 - David Azarewicz Initial release. ============================================================================= Brodcom BCM57xx QLogic Gigabit adapter driver Info ==== This is an NDIS driver for Attansic Technology Corp. L2 FastEthernet LAN adapters. The source code from the FreeBSD "ae" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. HP NC370T Multifunction Gigabit Server Adapter HP NC370i Multifunction Gigabit Server Adapter HP NC380T PCIe DP Multifunc Gig Server Adapter HP NC371i Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5706 1000Base-T HP NC370F Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5706 1000Base-SX HP NC373T PCIe Multifunction Gig Server Adapter HP NC373i Multifunction Gigabit Server Adapter HP NC374m PCIe Multifunction Adapter QLogic NetXtreme II BCM5708 1000Base-T HP NC373m Multifunction Gigabit Server Adapter HP NC373i Multifunction Gigabit Server Adapter HP NC373F PCIe Multifunc Giga Server Adapter QLogic NetXtreme II BCM5708 1000Base-SX HP NC382i DP Multifunction Gigabit Server Adapter HP NC382T PCIe DP Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5709 1000Base-T HP NC382m DP 1GbE Multifunction BL-c Adapter HP NC382i DP Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5709 1000Base-SX QLogic NetXtreme II BCM5716 1000Base-T These correspond to the following Vendor:Device numbers: 14E4:164A, 14E4:16AA, 14E4:164C, 14E4:16AC, 14E4:1639, 14E4:163A, 14E4:163B, Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTE: This driver requires an exclusive interrupt to function. Normally this will be an MSI provided that you have a recent PSD. Otherwise, if an exclusive interrupt is not available this driver will fail to load. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 14E4:1639 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2006-2014 QLogic Corporation All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMBCE$, /A1 = MMBCE2$, /A2 = MMBCE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD:n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. 0.1.4 24-Sep-2018 - David Azarewicz Updated with current unix sources. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.3 17-Sep-2015 - David Azarewicz Initial release. ============================================================================= Atheros AR813x/AR815x PCIe Ethernet NIC driver Info ==== This is an NDIS driver for Atheros AR813x/AR815x PCIe LAN adapters. The source code from the FreeBSD "alc" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. Atheros AR8131 PCIe Gigabit Ethernet Atheros AR8132 PCIe Fast Ethernet Atheros AR8151 v1.0 PCIe Gigabit Ethernet Atheros AR8151 v2.0 PCIe Gigabit Ethernet Atheros AR8152 v1.1 PCIe Fast Ethernet Atheros AR8152 v2.0 PCIe Fast Ethernet Atheros AR8161 PCIe Gigabit Ethernet Atheros AR8162 PCIe Fast Ethernet Atheros AR8171 PCIe Gigabit Ethernet Atheros AR8172 PCIe Fast Ethernet Killer E2200 Gigabit Ethernet Killer E2400 Gigabit Ethernet Killer E2500 Gigabit Ethernet These correspond to the following Vendor:Device numbers: 1969:1063, 1969:1062, 1969:1073, 1969:1083, 1969:2060, 1969:2062, 1969:1091, 1969:1090, 1969:10A1, 1969:10A0, 1969:E091, 1969:E0A1, 1969:E0B1 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2009, Pyun YongHyeon <yongari@FreeBSD.org> All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMALC$, /A1 = MMALC2$, /A2 = MMALC3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.7 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to current FreeBSD source. 0.0.6 03-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 08-Oct-2016 - David Azarewicz Refreshed release. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 21-Jul-2016 - David Azarewicz Updated to current source. 0.0.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= Broadcom BCM4401 Fast Ethernet driver Info ==== This is an NDIS driver for Broadcom BCM4401 Fast Ethernet adapters. The source code from the FreeBSD "bfe" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. The Broadcom BCM4401 Fast Ethernet adapters. These correspond to the following Vendor:Device numbers: 14E4:4401, 14E4:170C Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 14E4:4401 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2003 Stuart Walsh<stu@ipng.org.uk> and Duncan Barclay<dmlb@dmlb.org> (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMBFE$, /A1 = MMBFE2$, /A2 = MMBFE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 11-Jan-2016 - David Azarewicz Initial release. ============================================================================= Atheros AR8121/AR8113/AR8114 PCIe Ethernet NIC driver Info ==== This is an NDIS driver for Atheros AR8121/AR8113/AR8114 PCIe Ethernet adapters. The source code from the FreeBSD "ale" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. Atheros AR8121/AR8113/AR8114 PCIe Ethernet These correspond to the following Vendor:Device numbers: 1969:1026 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 1969:1026 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008, Pyun YongHyeon <yongari@FreeBSD.org> All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMALE$, /A1 = MMALE2$, /A2 = MMALE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.6 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to current version of FreeBSD source. 0.0.6 03-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 08-Oct-2016 - David Azarewicz Refreshed release See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 21-Jul-2016 - David Azarewicz Updated to current version of FreeBSD source. 0.0.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= Broadcom BCM57xx(x)/BCM590x NetXtreme and NetLink family Ethernet driver Info ==== This is an NDIS driver for Broadcom BCM57xx(x)/BCM590x NetXtreme and NetLink family Ethernet adapters. The source code from the FreeBSD "bge" driver has been compiled to run on OS/2. This driver supports the following adapters. The Broadcom 57xx series adapters. These correspond to the following Vendor:Device numbers: 12AE:0003, 12AE:0004, 173B:03E8, 173B:03E9, 173B:03EA, 106B:1645, 14E4:1644, 14E4:1645, 14E4:1646, 14E4:16C6, 14E4:16A6, 14E4:1647, 14E4:16C7, 14E4:16A7, 14E4:1648, 14E4:16A8, 14E4:1649, 14E4:1653, 14E4:166E, 14E4:1654, 14E4:165D, 14E4:165E, 14E4:1668, 14E4:1669, 14E4:1678, 14E4:1679, 14E4:1655, 14E4:1665, 14E4:1656, 14E4:1657, 14E4:165F, 14E4:1659, 14E4:165A, 14E4:165B, 14E4:1643, 14E4:16F3, 14E4:1676, 14E4:167C, 14E4:1677, 14E4:167E, 14E4:167D, 14E4:1600, 14E4:1601, 14E4:16F7, 14E4:16FE, 14E4:16FD, 14E4:167A, 14E4:1672, 14E4:167B, 14E4:1673, 14E4:1674, 14E4:1681, 14E4:1680, 14E4:1688, 14E4:1689, 14E4:1687, 14E4:1684, 14E4:166A, 14E4:166B, 14E4:16DD, 14E4:1696, 14E4:1698, 14E4:16A0, 14E4:1699, 14E4:169A, 14E4:169B, 14E4:167F, 14E4:1693, 14E4:169C, 14E4:169D, 14E4:170D, 14E4:170E, 14E4:16FF, 14E4:1712, 14E4:1713, 14E4:1690, 14E4:16B0, 14E4:1682, 14E4:1642, 14E4:16B4, 14E4:1686, 14E4:1683, 14E4:1692, 14E4:16B1, 14E4:16B7, 14E4:16B5, 14E4:16B3, 14E4:1641, 14E4:1691, 14E4:1694, 14E4:16B2, 14E4:16B6, 1148:4400, 10B7:0003, 10CF:11A2, 10CF:11A1, 10CF:11CC Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was tested on the following hardware: 14E4:1600 (BCM5752) works - passed QA testing. 14E4:165A (BCM5722) works - passed QA testing. 14E4:16A7 (BCM5703) does not work 14E4:1648 (BCM5704) does not work Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008, Pyun YongHyeon <yongari@FreeBSD.org> All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMBGE$, /A1 = MMBGE2$, /A2 = MMBGE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Updated to latest FreeBSD source. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 09-Jan-2017 - David Azarewicz Initial release. ============================================================================= Brodcom BCM57xx QLogic Gigabit adapter driver Info ==== This is an NDIS driver for Attansic Technology Corp. L2 FastEthernet LAN adapters. The source code from the FreeBSD "ae" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. HP NC370T Multifunction Gigabit Server Adapter HP NC370i Multifunction Gigabit Server Adapter HP NC380T PCIe DP Multifunc Gig Server Adapter HP NC371i Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5706 1000Base-T HP NC370F Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5706 1000Base-SX HP NC373T PCIe Multifunction Gig Server Adapter HP NC373i Multifunction Gigabit Server Adapter HP NC374m PCIe Multifunction Adapter QLogic NetXtreme II BCM5708 1000Base-T HP NC373m Multifunction Gigabit Server Adapter HP NC373i Multifunction Gigabit Server Adapter HP NC373F PCIe Multifunc Giga Server Adapter QLogic NetXtreme II BCM5708 1000Base-SX HP NC382i DP Multifunction Gigabit Server Adapter HP NC382T PCIe DP Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5709 1000Base-T HP NC382m DP 1GbE Multifunction BL-c Adapter HP NC382i DP Multifunction Gigabit Server Adapter QLogic NetXtreme II BCM5709 1000Base-SX QLogic NetXtreme II BCM5716 1000Base-T These correspond to the following Vendor:Device numbers: 14E4:164A, 14E4:16AA, 14E4:164C, 14E4:16AC, 14E4:1639, 14E4:163A, 14E4:163B, Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTE: This driver requires an exclusive interrupt to function. Normally this will be an MSI provided that you have a recent PSD. Otherwise, if an exclusive interrupt is not available this driver will fail to load. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 14E4:1639 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2006-2014 QLogic Corporation All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMBCE$, /A1 = MMBCE2$, /A2 = MMBCE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD:n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. 0.1.4 24-Sep-2018 - David Azarewicz Updated with current unix sources. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.3 17-Sep-2015 - David Azarewicz Initial release. ============================================================================= Broadcom BCM4401 Fast Ethernet driver Info ==== This is an NDIS driver for Broadcom BCM4401 Fast Ethernet adapters. The source code from the FreeBSD "bfe" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. The Broadcom BCM4401 Fast Ethernet adapters. These correspond to the following Vendor:Device numbers: 14E4:4401, 14E4:170C Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 14E4:4401 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2003 Stuart Walsh<stu@ipng.org.uk> and Duncan Barclay<dmlb@dmlb.org> (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMBFE$, /A1 = MMBFE2$, /A2 = MMBFE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 11-Jan-2016 - David Azarewicz Initial release. ============================================================================= Broadcom BCM57xx(x)/BCM590x NetXtreme and NetLink family Ethernet driver Info ==== This is an NDIS driver for Broadcom BCM57xx(x)/BCM590x NetXtreme and NetLink family Ethernet adapters. The source code from the FreeBSD "bge" driver has been compiled to run on OS/2. This driver supports the following adapters. The Broadcom 57xx series adapters. These correspond to the following Vendor:Device numbers: 12AE:0003, 12AE:0004, 173B:03E8, 173B:03E9, 173B:03EA, 106B:1645, 14E4:1644, 14E4:1645, 14E4:1646, 14E4:16C6, 14E4:16A6, 14E4:1647, 14E4:16C7, 14E4:16A7, 14E4:1648, 14E4:16A8, 14E4:1649, 14E4:1653, 14E4:166E, 14E4:1654, 14E4:165D, 14E4:165E, 14E4:1668, 14E4:1669, 14E4:1678, 14E4:1679, 14E4:1655, 14E4:1665, 14E4:1656, 14E4:1657, 14E4:165F, 14E4:1659, 14E4:165A, 14E4:165B, 14E4:1643, 14E4:16F3, 14E4:1676, 14E4:167C, 14E4:1677, 14E4:167E, 14E4:167D, 14E4:1600, 14E4:1601, 14E4:16F7, 14E4:16FE, 14E4:16FD, 14E4:167A, 14E4:1672, 14E4:167B, 14E4:1673, 14E4:1674, 14E4:1681, 14E4:1680, 14E4:1688, 14E4:1689, 14E4:1687, 14E4:1684, 14E4:166A, 14E4:166B, 14E4:16DD, 14E4:1696, 14E4:1698, 14E4:16A0, 14E4:1699, 14E4:169A, 14E4:169B, 14E4:167F, 14E4:1693, 14E4:169C, 14E4:169D, 14E4:170D, 14E4:170E, 14E4:16FF, 14E4:1712, 14E4:1713, 14E4:1690, 14E4:16B0, 14E4:1682, 14E4:1642, 14E4:16B4, 14E4:1686, 14E4:1683, 14E4:1692, 14E4:16B1, 14E4:16B7, 14E4:16B5, 14E4:16B3, 14E4:1641, 14E4:1691, 14E4:1694, 14E4:16B2, 14E4:16B6, 1148:4400, 10B7:0003, 10CF:11A2, 10CF:11A1, 10CF:11CC Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was tested on the following hardware: 14E4:1600 (BCM5752) works - passed QA testing. 14E4:165A (BCM5722) works - passed QA testing. 14E4:16A7 (BCM5703) does not work 14E4:1648 (BCM5704) does not work Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008, Pyun YongHyeon <yongari@FreeBSD.org> All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMBGE$, /A1 = MMBGE2$, /A2 = MMBGE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Updated to latest FreeBSD source. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 09-Jan-2017 - David Azarewicz Initial release. ============================================================================= Intel(R) PRO/1000 Network Connection Driver for OS/2 Info ==== This is an NDIS driver for Intel(R) PRO/1000 Network Connection adapters. The source code from the FreeBSD e1000 "igb" driver has been compiled, unmodified, to run on OS/2. This driver supports the following device IDs. All are Vendor ID 8086. 10A7, 10A9, 10D6, 10C9, 150A, 1518, 10E6, 10E7, 150D, 10E8, 1526, 10CA, 150E, 150F, 1510, 1511, 1516, 1527, 043A, 0438, 0440, 043C, 1521, 1522, 1523, 1524, 1520, 1533, 1535, 1534, 157B, 157C, 1536, 1537, 1538, 1539, 1F40, 1F45, 1F41 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. First check the Vendor ID. If the Vendor ID of your hardare is not 8086, then your hardware is not supported by this driver. Then check the Device ID. If the Device ID is not in the list above, then your hardware is not supported by this driver. If the Vendor ID of your hardware is 8086, and the Device ID is listed above, then this driver should work. On multiport cards, only 1 port will probably work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2023 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2001-2012, Intel Corporation All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMIGB$, /A1 = MMIGB2$, /A2 = MMIGB3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code is available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.8 15-Sep-2023 - David Azarewicz Updated from BSD sources. Refreshed with updated system libraries. 1.1.7 11-Jul-2022 - David Azarewicz Updated from BSD sources. Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Updated common code from BSD sources. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Minor update from FreeBSD. Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to current FreeBSD source. 0.0.3 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 08-Oct-2016 - David Azarewicz Refreshed release. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 21-Jul-2016 - David Azarewicz Initial release. ============================================================================= JMicron Inc JMC25x/JMC26x Ethernet driver Info ==== This is an NDIS driver for JMicron Inc JMC25x/JMC26x Ethernet LAN adapters. The source code from the FreeBSD "jme" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. JMicron Inc, JMC25x Gigabit Ethernet JMicron Inc, JMC26x Fast Ethernet These correspond to the following Vendor:Device numbers: 197B:0250, 197B:0260 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2008 Stanislav Sedov <stas@FreeBSD.org>. All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMJME$, /A1 = MMJME2$, /A2 = MMJME3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.3 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.2 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.1 21-Aug-2021 - David Azarewicz Initial release. ============================================================================= Intel(R) PRO/1000 Legacy NIC Driver for OS/2 Info ==== This is an NDIS driver for Intel(R) PRO/1000 Legacy LAN adapters. The source code from the FreeBSD e1000 "lem" driver has been compiled, unmodified, to run on OS/2. Intel PRO/1000 CT Network Connection (82547) Intel PRO/1000 F Server Adapter (82543) Intel PRO/1000 Gigabit Server Adapter (82542) Intel PRO/1000 GT Desktop Adapter (82541PI) Intel PRO/1000 MF Dual Port Server Adapter (82546) Intel PRO/1000 MF Server Adapter (82545) Intel PRO/1000 MF Server Adapter (LX) (82545) Intel PRO/1000 MT Desktop Adapter (82540) Intel PRO/1000 MT Desktop Adapter (82541) Intel PRO/1000 MT Dual Port Server Adapter (82546) Intel PRO/1000 MT Quad Port Server Adapter (82546EB) Intel PRO/1000 MT Server Adapter (82545) Intel PRO/1000 T Desktop Adapter (82544) Intel PRO/1000 T Server Adapter (82543) Intel PRO/1000 XF Server Adapter (82544) Intel PRO/1000 XT Server Adapter (82544) This driver supports the following device IDs. All are Vendor ID 8086. 1000, 1001, 1004, 1008, 1009, 100C, 100D, 100E, 100F, 1010, 1011, 1012, 1013, 1014, 1015, 1016, 1017, 1018, 1019, 101A, 101D, 101E, 1026, 1027, 1028, 1075, 1076, 1078, 1079, 107A, 107B, 107C, 1077, 108A, 1099, 10B5 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. First check the Vendor ID. If the Vendor ID of your hardare is not 8086, then your hardware is not supported by this driver. Then check the Device ID. If the Device ID is not in the list above, then your hardware is not supported by this driver. If the Vendor ID of your hardware is 8086, and the Device ID is listed above, then this driver should work. On multiport cards, only 1 port will probably work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2023 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2001-2012, Intel Corporation All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMLEM$, /A1 = MMLEM2$, /A2 = MMLEM3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code is available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.8 15-Sep-2023 - David Azarewicz Updated from BSD sources to add several new chips. Refreshed with updated system libraries. 1.1.7 11-Jul-2022 - David Azarewicz Updated from BSD sources to add several new chips. Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Updated common code from BSD sources. Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.6 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 08-Oct-2016 - David Azarewicz Refreshed release See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 30-May-2016 - David Azarewicz Updated to current FreeBSD source (1.1.0) 0.0.1 30-May-2016 - David Azarewicz Initial release. ============================================================================= Marvell Yukon II Ethernet controller driver Info ==== This is an NDIS driver for Marvell Yukon II Ethernet controller. The source code from the FreeBSD "msk" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. SK-9Sxx Gigabit Ethernet SK-9Exx Gigabit Ethernet Marvell Yukon 88E8021CU Gigabit Ethernet Marvell Yukon 88E8021 SX/LX Gigabit Ethernet Marvell Yukon 88E8022CU Gigabit Ethernet Marvell Yukon 88E8022 SX/LX Gigabit Ethernet Marvell Yukon 88E8061CU Gigabit Ethernet Marvell Yukon 88E8061 SX/LX Gigabit Ethernet Marvell Yukon 88E8062CU Gigabit Ethernet Marvell Yukon 88E8062 SX/LX Gigabit Ethernet Marvell Yukon 88E8035 Fast Ethernet Marvell Yukon 88E8036 Fast Ethernet Marvell Yukon 88E8038 Fast Ethernet Marvell Yukon 88E8039 Fast Ethernet Marvell Yukon 88E8040 Fast Ethernet Marvell Yukon 88E8040T Fast Ethernet Marvell Yukon 88E8042 Fast Ethernet Marvell Yukon 88E8048 Fast Ethernet Marvell Yukon 88E8050 Gigabit Ethernet Marvell Yukon 88E8052 Gigabit Ethernet Marvell Yukon 88E8053 Gigabit Ethernet Marvell Yukon 88E8055 Gigabit Ethernet Marvell Yukon 88E8056 Gigabit Ethernet Marvell Yukon 88E8057 Gigabit Ethernet Marvell Yukon 88E8058 Gigabit Ethernet Marvell Yukon 88E8059 Gigabit Ethernet Marvell Yukon 88E8070 Gigabit Ethernet Marvell Yukon 88E8071 Gigabit Ethernet Marvell Yukon 88E8072 Gigabit Ethernet Marvell Yukon 88E8075 Gigabit Ethernet D-Link 550SX Gigabit Ethernet D-Link 560SX Gigabit Ethernet D-Link 560T Gigabit Ethernet These correspond to the following Vendor:Device numbers: 1148:9000, 1148:9E00, 11AB:4349, 11AB:4344, 11AB:4341, 11AB:4345, 11AB:4342, 11AB:4346, 11AB:4343, 11AB:4347, 11AB:4350, 11AB:4351, 11AB:4352, 11AB:4353, 11AB:4354, 11AB:4355, 11AB:4357, 11AB:435A 11AB:4361, 11AB:4360, 11AB:4362, 11AB:4363, 11AB:4364, 11AB:4365, 11AB:436A, 11AB:436B, 11AB:436C, 11AB:436D, 11AB:4370, 11AB:4380, 11AB:4381, 1186:4001, 1186:4002, 1186:4B00 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. Note that for adapters with more than one port, only port 0 will work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 11AB:4362 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 1997, 1998, 1999, 2000 Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. Copyright (c) 2003 Nathan L. Binkert <binkertn@umich.edu> (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMMSK$, /A1 = MMMSK2$, /A2 = MMMSK3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Updated to current version of FreeBSD sources. 0.0.3 03-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E PCI NIC driver Info ==== This is an NDIS driver for RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E LAN adapters. The source code from the FreeBSD "re" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. D-Link DGE-528(T) Gigabit Ethernet Adapter D-Link DGE-530(T) Gigabit Ethernet Adapter RealTek 8139C+ 10/100BaseTX RealTek 810xE PCIe 10/100baseTX RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet RealTek 8169SC/8110SC Single-chip Gigabit Ethernet Corega CG-LAPCIGT (RTL8169S) Gigabit Ethernet Linksys EG1032 (RTL8169S) Gigabit Ethernet US Robotics 997902 (RTL8169S) Gigabit Ethernet RealTek 8168 Gigabit Ethernet TP-Link TG-3468 v2 (RTL8168) Gigabit Ethernet These correspond to the following Vendor:Device numbers: 1186:4300, 1186:4302, 10EC:8136, 10EC:8139, 10EC:8161, 10EC:8167, 10EC:8168, 10EC:8169, 10FF:8168, 1259:C107, 1737:1032, 16EC:0116 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver might work. However, for this driver the PCI Vendor and Device ID are insufficient to determine if the adapter is supported. The driver also checks the chip revisions. This is because Realtek uses the same PCI Vendor and Device ID for different, incompatible NIC chips. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was personally tested by the developer on 1OEC:8168 hardware. Copyright and License ===================== Copyright (c) 2014-2023 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 1997, 1998-2003 Bill Paul <wpaul@windriver.com>. All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMRE$, /A1 = MMRE2$, /A2 = MMRE3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.9 15-Sep-2023 - David Azarewicz Added quirk for 8161 device. 1.1.8 12-Aug-2022 - David Azarewicz Added 2 new PCI IDs. Refreshed with updated system libraries. 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Switch to new system library. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.2 17-Sep-2017 - David Azarewicz Refreshed with updated system libraries (MSI fix). See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.7 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.6 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 08-Oct-2016 - David Azarewicz Refreshed release See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 21-Jul-2016 - David Azarewicz Updated to current FreeBSD source. 0.0.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= RealTek 8129/8139 PCI NIC driver Info ==== This is an NDIS driver for RealTek 8129/8139 PCI LAN adapters. The source code from the FreeBSD "re" driver has been compiled, mostly unmodified, to run on OS/2. This driver supports the following adapters. RealTek 8129 10/100BaseTX RealTek 8139 10/100BaseTX RealTek 8139 10/100BaseTX CardBus RealTek 8100 10/100BaseTX Accton MPX 5030/5038 10/100BaseTX Delta Electronics 8139 10/100BaseTX Addtron Technology 8139 10/100BaseTX D-Link DFE-520TX (rev. C1) 10/100BaseTX D-Link DFE-530TX+ 10/100BaseTX D-Link DFE-690TXD 10/100BaseTX Nortel Networks 10/100BaseTX Corega FEther CB-TXD Corega FEtherII CB-TXD Peppercon AG ROL-F Planex FNW-3603-TX Planex FNW-3800-TX Compaq HNE-300 LevelOne FPC-0106TX Edimax EP-4103DL CardBus These correspond to the following Vendor:Device numbers: 10EC:8129, 10EC:8139, 10EC:8039, 10EC:8138, 10EC:8100, 1113:1211, 1500:1360, 4033:1360, 1186:4200, 1186:1300, 1186:1340, 126C:1211, 1259:A117, 1259:A11E, 1743:8139, 14EA:AB06, 14EA:AB07, 021B:8139, 018A:0106, 13D1:AB06 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver might work. However, for this driver the PCI Vendor and Device ID are insufficient to determine if the adapter is supported. The driver also checks the chip revisions. This is because Realtek uses the same PCI Vendor and Device ID for different, incompatible NIC chips. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. This driver was tested by the Developer on 10EC:8139 hardware. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 1997, 1998-2003 Bill Paul <wpaul@windriver.com>. All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMRL$, /A1 = MMRL2$, /A2 = MMRL3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.3 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.1.2 17-Mar-2018 - David Azarewicz Switch to new system library. 0.0.6 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. 0.0.5 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. 0.0.4 08-Oct-2016 - David Azarewicz Refreshed release 0.0.3 21-Jul-2016 - David Azarewicz Updated to current FreeBSD source. 0.0.2 01-Feb-2016 - David Azarewicz No change to FreeBSD driver. Recompiled to use updated system libraries. 0.0.1 03-Sep-2015 - David Azarewicz Initial release. ============================================================================= SysKonnect SK-NET gigabit ethernet driver Info ==== This is an NDIS driver for SysKonnect SK-NET gigabit ethernet controller. The source code from the FreeBSD "sk" driver has been compiled, unmodified, to run on OS/2. This driver supports the following adapters. SysKonnect Gigabit Ethernet (V1.0) SysKonnect Gigabit Ethernet (V2.0) Marvell Gigabit Ethernet Belkin F5D5005 Gigabit Ethernet 3Com 3C940 Gigabit Ethernet Linksys EG1032 Gigabit Ethernet D-Link DGE-530T Gigabit Ethernet D-Link DGE-530T Gigabit Ethernet These correspond to the following Vendor:Device numbers: 1148:4300, 1148:4320, 11AB:4320, 11AB:5005, 10B7:1700, 1737:1032, 1186:4C00, 1186:4B01 Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. Note that for adapters with more than one port, only port 0 will work. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 1997, 1998, 1999, 2000 Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. Copyright (c) 2003 Nathan L. Binkert <binkertn@umich.edu> (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMSK$, /A1 = MMSK2$, /A2 = MMSK3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 1.1.7 11-Jul-2022 - David Azarewicz Refreshed with updated system libraries. 1.1.6 17-Mar-2022 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.5 17-Jan-2021 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.4 24-Sep-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.3 17-Mar-2018 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.1.2 15-Jan-2018 - David Azarewicz Version number changed to match numbering convention. 1.0.2 25-Oct-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. Fixed interrupt handler for OS/2 compatibility. 1.0.1 01-Sep-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 1.0.0 10-Aug-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.5 07-Jun-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.4 09-Jan-2017 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.3 02-Dec-2016 - David Azarewicz Refreshed with updated system libraries. See https://88watts.net/download/ReadMe-Bcl32.txt for details. 0.0.2 08-Oct-2016 - David Azarewicz Refreshed release. 0.0.1 28-May-2016 - David Azarewicz Initial release. ============================================================================= Driver for VirtIO network devices Info ==== This is an NDIS Driver for VirtIO network devices. The source code from the FreeBSD "virtio" driver has been compiled, unmodified, to run on OS/2. This driver supports VirtIO adapters with Vendor:Device numbers in then range of 1AF4:1000 through 1AF4:103F and an ABI value of 0. NOTICE: This driver is built from 2 major pieces: (1) The FreeBSD driver which is simply compiled to run on OS/2 (2) The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn't work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn't work properly on your hardware because we don't have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn't work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. Copyright and License ===================== Copyright (c) 2014-2021 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2011, Bryan Venteicher <bryanv@FreeBSD.org> All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = MMVTIO$, /A1 = MMVTIO2$, /A2 = MMVTIO3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM:n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. /BAUD=n Sets the BAUD rate for the selected COM Port. PROTOCOL.INI Options ==================== There are currently no options. Getting Support and Reporting Problems ====================================== Since the FreeBSD driver is simply compiled to run on OS/2, there is no development, no debugging, and no support for that part of the driver. There is only support for the interface between the FreeBSD driver and OS/2. For more information please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code will be available at: http://svn.netlabs.org/repos/multimac Change log ========== 0.1.1 28-May-2016 - David Azarewicz Initial release. ============================================================================= Intel PRO/1000 PCIe NIC Driver for OS/2 This driver is depreciated and will not receive any further updates. Info ==== This is an NDIS driver for Intel Gigabit PCI-Express LAN adapters. This driver is based on the source code of e1000e Linux kernel module and of nveth NVIDIA NIC driver for OS/2 developed by nickk. This driver supports the following devices. 82571EB, 82571PT, 82572EI, 82573V, 82573E, 82573L, 82574L, 82583V, 80003ES2LAN, 82562V, 82562G, 82562GT, 82566DM, 82566DC, 82566MC, 82566MM, 82567V-3, 82562V-2, 82562G-2, 82562GT-2, 82566DM-2, 82566DC-2, 82567LM-4, 82567LF, 82567LM, 82567V, 82567LM-2, 82567LF-2, 82567V-2, 82567LM-3, 82567LF-3, 82577LM, 82577LC, 82578DM, 82578D. More specifically, only the following device IDs are supported. All are Vendor ID 8086. 1049, 104A, 104B, 104C, 104D, 105E, 105F, 1060, 107D, 107E, 107F, 108B, 108C, 1096, 1098, 109A, 10A4, 10A5, 10B9, 10BA, 10BB, 10BC, 10BD, 10BF, 10C0, 10C2, 10C3, 10C4, 10C5, 10CB, 10CC, 10CD, 10CE, 10D3, 10D5, 10D9, 10DA, 10DE, 10DF, 10E5, 10EA, 10EB, 10EF, 10F0, 10F5, 10F6, 1501, 1502, 1503, 150C, 294C Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. First check the Vendor ID. If the Vendor ID of your hardare is not 8086, then your hardware is not supported by this driver. Then check the Device ID. If the Device ID is not in the list above, then your hardware is not supported by this driver. If the Vendor ID of your hardware is 8086, and the Device ID is listed above, then this driver should work. Copyright and License ===================== Copyright (c) 2014-2015 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2001-2010, Intel Corporation All rights reserved. (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. The distribution package also includes a version of the driver in the trace directory. This version has tracing enabled for debugging purposes. You would only use the tracing driver if you are debugging a problem in coordination with the developer. See https://www.arcanoae.com/wiki/multimac for more information. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = E1000E$, /A1 = E1000E2$, /A2 = E1000E3$, etc. /V Turns on the version banner when the driver loads. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /COM=n Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2, or the port address. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. PROTOCOL.INI Options ==================== There are the following switches you can tune the driver work: MODE Intel Gigabit PCIe network adapters support the following operation modes 10HALF - half duplex operation at 10 Mb/s 10FULL - full duplex operation at 10 Mb/s 100HALF - half duplex operation at 100 Mb/s 100FULL - full duplex operation at 100 Mb/s 1000FULL - full duplex operation at 1000 Mb/s The default mode is Auto-Negotiation. RXCHAIN The way of transferring received packets to the protocol drivers: receive chain and lookahead. The recommended setting is the receive chain. NETADDRESS Specifies the MAC address to use instead of the vendor supplied unique address. Must be exactly 12 hex digits long. Example: NETADDRESS = "4061865F3888" Getting Support and Reporting Problems ====================================== For more information and to report problems please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code is available at: http://svn.netlabs.org/repos/multimac Change log ========== 0.2.8 03-Sep-2015 through 0.2.7 08-May-2015 - David Azarewicz No changes to this driver. Recompiled for new package release, which links in system libraries which may or may not have changed. 0.2.6 23-Aug-2014 - David Azarewicz Corrected status checking in interrupt handler. 0.2.5 22-Jan-2014 - David Azarewicz Fixed a problem loading multiple instances of the driver. 0.2.4 13-Oct-2013 - David Azarewicz Converted to use the Drv16 kit. Fixed some errors in the NDIS setup. No functional changes. 0.2.3 24-Apr-2012 - David Azarewicz Changes due to MultiMac restructuring Added logging functionality Added promiscuous mode capability 0.2.2 08-Apr-2012 - David Azarewicz Misc debugging changes New packet buffer allocation routines Reentry issue fixed Tracing support added Fixed a locked resource issue 0.2.1 - David Azarewicz Minor fixes due to MultiMac restructuring 0.2.0 - David Azarewicz Resynced with the sources from the Linux 3.2.4 driver. 0.1.7 - David Azarewicz fixed suspend/resume Added support for ACPI suspend/resume removed the -r compiler switch 0.1.6 - David Azarewicz Fixed PCI config space save/restore for suspend/resume 0.1.5 - David Azarewicz Added NETADDRESS support 0.1.4 - David Azarewicz Added /Q switch. When present on the command line, indicates quiet mode and does not output normal messages. Error messages are still output normally. 0.1.3 - David Azarewicz Moved to the MultiMac project. 0.1.2 Fixes were made for ICH8LAN chipsets support. 0.1.1 Initial release. ============================================================================= GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>. Realtek Gigabit PCIe NIC Driver for OS/2 This driver is depreciated and will not receive any further updates. Info ==== This is an NDIS driver for Realtek Gigabit PCI-Express LAN adapters. This driver is based on the source code of r8169 Linux kernel module and is supposed to support the same scope of adapters. This driver supports the following devices. RTL8169, RTL8169s, RTL8110s, RTL8169sb/8110sb, RTL8169sc/8110sc RTL8102e, RTL8101e, RTL8168b/8111b, RTL8100e, RTL8168cp/8111cp, RTL8168c/8111c, RTL8168d/8111d, RTL8168dp/8111dp, RTL8105e, RTL8168e/8111e, RTL8168evl/8111evl, RTL8168f/8111f, RTL8402, RTL8411, RTL8106e, RTL8168g/8111g These correspond to the following Vendor:Device numbers: 10EC:8129, 10EC:8136, 10EC:8167, 10EC:8168, 10EC:8169, 1186:4300, 1186:4302, 1259:C107, 16EC:0116, and certain subsets of 1737:1032 and 0001:8168) Use the PCI.EXE command to find the Vendor ID and Device ID of your hardware. If the Vendor ID and the Device ID is listed above, then this driver should work. Copyright and License ===================== Copyright (c) 2014-2015 David Azarewicz <david@88watts.net> All rights reserved. Copyright (c) 2002 ShuChen <shuchen@realtek.com.tw> Copyright (c) 2003 - 2007 Francois Romieu <romieu@fr.zoreil.com> (c) Copyright IBM Corporation 1990,2000. All rights reserved. Important! By downloading or using this software, you acknowledge that you have read and consent to the license agreement at the end of this file, that you understand it, and that you agree to be bound by its terms. Installation ============ You can install the network driver during operating system installation. Or you can install the driver using the Warpin package. This Warpin installer only copies the driver files to your system. After you install the files, run mpts.exe and set up the network driver as usual. Then reboot. If you are already using one of these drivers, then this package will update the files on your disk and there is no need to run mpts.exe again. The new driver will be used when you reboot. The distribution package also includes a version of the driver in the trace directory. This version has tracing enabled for debugging purposes. You would only use the tracing driver if you are debugging a problem in coordination with the developer. See https://www.arcanoae.com/wiki/multimac for more information. If your hardware requires a firmware file and you re-install the same or an updated WPI package when the driver is loaded, you will get an error that the installer cannot overwrite the firmware file. You can safely skip updating this file since the firmware typically does not change. Command line options ==================== /An Selects a specific PCI adapter to use. If not specified, the driver will use the first unused PCI adapter that is supported by the driver. For example, /A1 will select the second PCI adapter that is supported by the driver. If the specified PCI adapter does not exist, the driver will produce an error. /A0 = R8169$, /A1 = R81692$, /A2 = R81693$, etc. /V Turns on the version banner when the driver loads. /Fdirectory Specifies the location of the rtl_nic directory that contains the firmware files. The default \IBMCOM. Options only in the trace build ------------------------------- /Tn Sets the minor trace number for controlling trace output. Only applies to the trace build of the driver. Ignored in the retail version. Options only in the debug build ------------------------------- The debug build is not included in the distribution package and is only for developer use. /Dn Sets the debug output level to n. The default is 5. Only applies to the debug build of the driver. Ignored in the retail version. /On Sets the serial port for debug output. Valid values are 1 and 2 for COM1 and COM2. The default is no serial port output. Only applies to the debug build of the driver. Ignored in the retail version. PROTOCOL.INI Options ==================== There are the following switches you can tune the driver work: MODE Intel Gigabit PCIe network adapters support the following operation modes 10HALF - half duplex operation at 10 Mb/s 10FULL - full duplex operation at 10 Mb/s 100HALF - half duplex operation at 100 Mb/s 100FULL - full duplex operation at 100 Mb/s 1000FULL - full duplex operation at 1000 Mb/s The default mode is Auto-Negotiation. RXCHAIN The way of transferring received packets to the protocol drivers: receive chain and lookahead. The recommended setting is the receive chain which is the default. NETADDRESS Specifies the MAC address to use instead of the vendor supplied unique address. Must be exactly 12 hex digits long. Example: NETADDRESS = "4061865F3888" Getting Support and Reporting Problems ====================================== For more information and to report problems please visit: https://www.arcanoae.com and click on SUPPORT. Or go directly to the MultiMac support wiki at: https://www.arcanoae.com/wiki/multimac/ Source Code =========== The source code is available at: http://svn.netlabs.org/repos/multimac Change Log ========== v.1.0.2 03-Sep-2015 through v.1.0.1 08-May-2015 - David Azarewicz No changes to this driver. Recompiled for new package release, which links in system libraries which may or may not have changed. v.1.0.0 16-Feb-2014 - David Azarewicz Initial version based on v3.13 Linux source. ============================================================================= GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>. ------------------------------------------------------------------------------------- Debugging Guide Known Issues MultiMac drivers (except NVETH, E1000E, and R8169) are built from 2 major pieces: The FreeBSD driver which is simply compiled to run on OS/2 The system library which is the interface between the FreeBSD driver and OS/2 While we will always try our best to support these drivers, please realize that there is not much we can do about (1). We simply do not have the manpower, or even the technical information necessary to debug or enhance this portion of the driver. If this driver doesn’t work on hardware that it is supposed to, the limit of what we can do is verify that it is loading properly. Other than that, we simply cannot debug problems in the FreeBSD code and we cannot add support for more chipsets. We cannot even fix problems if it doesn’t work properly on your hardware because we don’t have the hardware data that would be required. Development is continuing on (2) so there might be improvements to the OS/2 interface as time goes on. This generally will not affect whether the driver works or doesn’t work on any given hardware, but might affect things like traps, hangs, and interfacing to existing features in the FreeBSD driver. The interface speed shown by the “netstat -n” command always shows 100000000 regardless of the actual interface speed. This is because most of the FreeBSD drivers do not report the interface speed, so a default number is used. Currently the only FreeBSD drivers that report link speed are E1000B, MMIGB, and MMLEM. Before Opening a Ticket Things to check before opening a ticket if you have problems Make sure your issue is not listed in the Known Issues section above. Make sure you are using the latest version of a supported driver. Only drivers distributed by Arca Noae are supported. The E1000E, R8169, and any other builds from other sources are not supported. Make sure you are using an official supported kernel. Only the official IBM 14.104a debug, 14.105, 14.106, and the Arca Noae kernels 14.104b, 14.104c, and 14.20x are supported. Make sure you are using an official supported loader for the kernel you are using. If you have ACPI.PSD installed, make sure it is the latest version and that you are not using any unnecessary switches. Recent versions of the MultiMac drivers will not work with ACPI.PSD older than 3.23.04 and may cause traps. Make sure you don’t have any load order violations in your CONFIG.SYS. Specifically make sure that all IFS statements come before all MAC drivers. If you open a ticket, please attach a TestLog log file when you open your ticket. Always make sure you capture the TestLog log file when the problem exists. If you cannot create a TestLog log, please include the bldlevel output for the driver you are using and the PCI Vendor ID and Device ID of your hardware in the ticket (ie. the section from PCI.EXE that relates to your NIC). If the driver traps, please, include the trap screen.