Windows 10 X360 China Xbox Controller Driver

Posted on 24.05.2020admin

sadus.netlify.app › Windows 10 X360 China Xbox Controller Driver ▼

The wired Xbox 360 controller is USB, so using it for PC gaming is easy–but things get a bit more complex if you have a wireless controller. Let’s take a look at how you can enjoy wireless gameplay on your PC while minimizing the headaches.

Xbox Controller Driver Windows 10
Windows 10 X360 China Xbox Controller Driver Windows 7
Windows 10 X360 China Xbox Controller Driver Download
Xbox Controller For Pc Driver Windows 10
Hp X360 Drivers Windows 10
Windows 10 X360 China Xbox Controller Driver Pc

The Three Prong Path to Wireless Freedom

When it comes to wireless Xbox 360 on Windows you have three options: the expensive and easy way, the cheap and somewhat frustrating way, and the grey market middle ground. If you’re sitting at your computer desk and not across the living room, for example–then you might just want to skip the whole hassle, just buy an official wired Xbox 360 controller for $27, and be done with it. A wired controller is pure plug and play with no hassle–but if you absolutely must have wireless play at your PC, you’ll need to buy a USB-to-wireless adapter.

Xbox 360 controller driver free download - XBOX 360 Controller For Windows, Xbox 360 Controller, VIA USB 2.0 Host Controller Driver, and many more programs Navigation open search. Hello Everybody, We come back with new Article Where You can fix Issue Of Xbox 360 Controller Driver Windows 10. If You are facing any Problem related Xbox 360 Controller Driver Then You are at Right Place.

That’s right, you can’t just connect a wireless Xbox 360 controller to your PC using Bluetooth, or anything like that. Xbox 360 controllers use a propriety 2.4Ghz communication method that need a specific a USB adapter made for the Xbox 360 controller–no substitutes allowed.

This is where the decision making process gets slightly complicated. Microsoft doesn’t sell the adapter by itself. They sell it in a bundle with a wireless controller–but if you already have a wireless controller, you probably don’t want to buy another one just to get the adapter.

If you want to buy the adapter separately, you can, but you’ll either be buying a Chinese knockoff product, or an official adapter that’s been separated from its kit by a third party. Picking from these potential options is the most important step in the project.

The Official Bundle: Expensive, But Headache-Free

If you don’t mind paying a premium (and potentially buying an extra controller you don’t need) then the most frustration-free and guaranteed-to-work method is to buy the official Xbox 360 wireless controller for Windows bundle. Despite the Xbox 360 getting a little long in the tooth, you can still find official Xbox 360 “For Windows” controller packs both on the shelves at many electronics retailers, online, and directly from Microsoft. And hey, if you only need the USB receiver, you can always sell the controller on Craigslist and try to get your money back.

RELATED:I Got Scammed by a Counterfeiter on Amazon. Here’s How You Can Avoid Them

The MSRP of the official bundle $59.95, and you’ll usually find it at close to that price at places like Best Buy. If you can find it cheaper from a reputable retailer, then by all means jump on it. If you must shop on Amazon, be sure you’re buying a product marked “fulfilled by Amazon” and be ready to return it if it ends up that the product is not an official model. (Remember, “fulfilled by Amazon does not guarantee a genuine product.)

The Dubious Aftermarket Clones: Cheap and Doable, but a Headache

On the opposite side of things, you’ll find piles upon piles of knockoff USB receivers sold separately all over Amazon, eBay, and other big online marketplaces. Typically, you’ll find them ranging in price from $7-15 and they’re either flawless clones that are indistinguishable from the official adapter dongle or they’re terrible knockoffs that will give you a headache setting them up.

The official Microsoft Xbox 360, seen above left, is always branded as “Microsoft” on the front and says “Microsoft Xbox 360 Wireless Receiver for Windows” on the back. The knockoffs are almost always branded “X360”, seen above right, and usually say “PC Wireless Gaming Receiver” or a variation on the back. Note the purposeful omission of any copy or trademarked names like “Microsoft”, “Xbox 360”, or “Windows”.

In general, we don’t recommend buying these. But if you already have one, we’ve got your back–scroll down for detailed instructions on getting it up and running, even when Windows doesn’t want to place nice.

The Official Orphans: A (Nearly) Sure Bet, as Long as You Can Find One

In between the expense of buying an official Xbox 360 Windows controller bundle and cheap $7 eBay specials, you’ll find a sort of grey market happy medium if you’re willing to make a small gamble. If you look on Amazon and eBay, you’ll find hundreds of official Microsoft brand Xbox 360 PC dongles that have been separated from their controller mates.

Your best bet is to look for listings that include not just the dongle (with proper markings and tags, as we saw above) but also include an official driver CD and booklet. While you don’t need either of those things to use the controller (Windows will download the drivers automatically), it’s generally a good indicator that the listing is legitimate. It’s not really profitable (or legally wise) for companies to go to the extra hassle of creating fake Microsoft support materials.

Just remember that Microsoft does not officially sell these separately, so if you’re buying one separately, you are taking a bit of a gamble. While we recommend you carefully study each listing, read reviews, and make sure there is a good return policy for whatever online retailer you’re using, we can say that we’ve had great luck purchasing these official adapters for $15 a piece off Amazon (specifically fulfilled by RushHourWholesalers). Every one we’ve ordered has shipped with a driver disc, documentation, and is identical in terms of branding, construction, and labeling to those found in the official bundle.

How to Install an Official Microsoft Adapter

If you’ve purchased the official bundle, got your hands on an official adapter, or just happened to have purchased a knockoff adapter of exceptionally good quality, then the installation process is incredibly simple.

On Windows 8 and above, you can simply plug the adapter right into your PC. A few seconds later, it will be automatically detected and Windows will install the drivers. You can confirm this by opening up the Windows Device Manager–press the Start button and type “device manager” to access it. Look down at the bottom of the hardware list for the Xbox adapter entry:

On Windows 7 and earlier, you’ll be prompted by the “Add Hardware” wizard to add the USB adapter. You can select “Install the software automatically”, and if your version of Windows has the drivers the process will continue automatically. If you don’t have the drivers already on your PC, you can either use the included driver disc or download the appropriate drivers from the official website here.

Once the adapter is installed (and you’ve confirmed its presence on the Device Manger list) you can jump down the section “Pairing Your Controllers to Your PC”.

Xbox Controller Driver Windows 10

How to Install a Knockoff Adapter

If you’re stuck with one of the lower-quality knockoffs, we’re sorry–by comparison, it’s a huge pain. Fortunately for you, it’s not hard to get them up and running as long as you know the completely non-intuitive way to do it.

First, plug your device into your computer. We recommend plugging it directly into a port on the back. If you must plug it into a USB hub, make sure it’s a powered hub. We’d also recommend picking a port that you’ll be able to leave the device more or less permanently attached to. Whenever you unplug it, you’ll need to repeat the annoying steps we’re about to outline–so you’ll want to leave it plugged in at all times, if you can.

Let’s emphasize that last point again: with the majority of aftermarket adapters we’ve come across if you unplug the adapter you have to repeat the annoying multi-step installation process. In my experience, it was worth the extra money to buy another genuine adapter just to avoid this hassle.

With the adapter plugged in, navigate to the Windows Device Manager. Press the Start button and type “device manager” to access it. Look under “Other Devices” in the list of devices under the entry for your computer.

We know it’s quite nondescript, but unless you have multiple Unknown Devices on your PC, that little “Unknown device” entry is your knockoff Xbox 360 controller adapter. Right click it and select Properties.

Select the Driver tab in the Unknown device Properties box and then click Update Driver.

When prompted to select whether you want Windows to search automatically or for you to browse your computer for the drivers, select “Browse my computer for driver software”. Don’t worry, you don’t actually need any drivers, as they’re already included with Windows. (On the off chance that yours have gone missing, however, you can download the drivers here.)

You’ll be given the option to search for the drivers in a location you specify or you can pick from a list of device drivers already installed. We want the latter, so select “Let me pick from a list of device drivers on my computer”.

Scroll down the list until you see “Xbox 360 Peripherals”. Double click on it.

Note: These screenshots are from the setup process on Windows 8 and 10; under Windows 7 it’s possible that you may need to look under “Microsoft Common Controller” instead of “Xbox 360 Peripherals”.

On the next screen, select “Xbox 360 Wireless Receiver for Windows Version 6.3.xxxx”. Click Next. When prompted by the driver update warning, click Yes. The hardware signature of the knockoff doesn’t, in fact, match the driver signature, but it will work fine just the same.

You’ll receive a confirmation that the device was installed properly.

If you get the error “Xbox 360 Controller for Windows / This Device Cannot Start. (Code 10)”, then you’ve accidentally selected the drivers for the controller, not the receiver. You’ll need to go back into the device manager, delete the erroneous entry and repeat the tutorial from the start.

Aug 30, 2016 - Available as an audiobook for the first time, read by band members Fat Mike, Eric Melvin, Erik 'Smelly' Sandin, and Aaron 'El Hefe' Abeyta. Nofx hepatitis bathtub audio download torrent.

Back in the Device Manager, scroll down to the bottom and double check that there is now an entry for the Xbox receiver:

If you see that entry, you’re in business–it’s time to add your controllers to your PC.

How to Pair Your Controller(s) to Your PC

The only thing left to do at this point is to sync your controller to the new wireless receiver. If you’re an Xbox 360 user porting some or all of their old controllers to their PC, then this process will seem very familiar, as its only a hair different than the process of pairing controllers with the actual Xbox 360.

Press the button on the receiver (the light will blink) then, immediately after, press the connect button on your wireless controller (located at the top of the controller just above the battery pack).

The green ring of lights on the Xbox controller will rotate around and then the controller will signify which controller it is by lighting up the appropriate quadrant (the wireless receiver will support up to 4 controllers for those rare multiplayer PC games).

One final step you may wish to take, even though it’s not required to get the controllers to work, is to download the 360 for Windows controller software, it adds in a really convenient function: you can tap and hold the Xbox logo on the controller to get a battery status check.

That’s all there is to it! Before you dash off to play, however, we strongly recommend bookmarking, Evernote clipping, printing, or otherwise saving this tutorial if you have an aftermarket dongle. As we mentioned at the start, if you unplug the receiver you have to go back into the Device Manager and install the drivers again.

Windows 10 X360 China Xbox Controller Driver Windows 7

My controller doesn't work!
Developer Info

About

This driver supports the Microsoft Xbox series of controllers including:

Original Xbox
- Original Xbox controllers are supported by using a USB adapter.
Xbox 360
- Wired Xbox 360 controllers are supported directly.
- As of macOS 10.11, Wireless Xbox 360 controller support causes kernel panics. This issue cannot be resolved with minor changes to the driver, and requires that the driver be re-written from scratch to resolve the issue. Due to an excess of caution, we have disabled Wireless Xbox 360 controller support as of 0.16.6. If you want to use a wireless controller, download 0.16.5 or earlier and disable the driver before the computer enters a 'sleep' state in order to prevent kernel panics. Alternatively, you can revert to a macOS version before 10.11 to avoid this issue.
Xbox One
- Xbox One controllers are supported when connected with a micro USB cable. Using the controller with the Wireless Adapter is not currently supported.
- Bluetooth capable Xbox One controllers (released after August 2016) are natively supported by macOS without the use of this driver. However, installing this driver will allow you to use the controller via USB.

The driver provides developers with access to both force feedback and the LEDs of the controllers. Additionally, a preference pane has been provided so that users can configure their controllers and ensure that the driver has been installed properly.

Controller support includes ALL devices that work with an Xbox series piece of hardware. All wheels, fight sticks, and controllers should work. This includes things like the Xbox One Elite controller. If your hardware does not work with an Xbox console we cannot support it. Sorry.

This project is a fork of the Xbox360Controller project originally created by Colin Munro.

Installation

See the releases page for the latest compiled and signed version of the driver. Most users will want to run this installer. If you are using macOS 10.13.4 or later, then you will have to allow the signing certificate of 'Drew Mills' in order for the software to run. Usually, the installer will prompt you to complete this process:You can either click 'Open Security Preferences' to quickly fix this. If you didn't see this prompt, you can navigate to the same window using the Apple menu in the top left hand corner of your screen, navigating the 'System Preferences' and then clicking on 'Security & Privacy.' This will open up the following page. All you need to do is click the 'Allow' button near the bottom right.This prompt has been known to have issues with software or hardware that interferes with mouse movement. If you are using software that impacts the movement of your mouse, such as MagicKeys, or are using a special interface device, such as a Wacom tablet, please using a standard input device, such as a mouse, to click this button. This is a security feature of macOS and is out of our control.

Uninstallation

In order to uninstall the driver: navigate to the preference pane by opening your 'System Preferences,' navigating to the 'Xbox 360 Controllers' pane, clicking on the 'Advanced' tab and pressing the 'Uninstall' button. This will prompt you to enter your password so that the uninstaller can remove all of the bundled software from your machine.

Usage

The driver exposes a standard game pad with a number of standard controls, so any game that supports gaming devices should work. In some cases, this may require an update from the developer of the game. The preference pane uses the standard macOS frameworks for accessing HID devices in addition to access of Force Feedback capabilities. This means that the preference pane is a good indicator that the driver is functional for other programs.

It is important to note that this driver does not work, and can never work, with Apple's 'Game Controller Framework.' This GCController framework corresponds to physical gamepads that have been offically reviewed by Apple and accepted into the mFi program. Due to the fact that we are not Microsoft, we cannot get their gamepad certified to be a GCController. This is an unfortunate oversight on Apple's part. If you would like to discuss this, please do so at this location.

Users have been maintaining a partial list of working and non-working games. Please contribute your findings so that you can help others debug their controller issues.

My controller doesn't work!

I'm using a driver from the Tattiebogle website

The Tattiebogle driver is NOT the same driver as this Github project. We do NOT support that driver. Under NO circumstances will we support that driver. If you download the latest version of this driver from the releases page we will do our best to help you out. This driver will install over the Tattiebogle driver. You don't have to worry about uninstalling the Tattiebogle driver first.

My controller doesn't work with a game!

We cannot fix game specific issues. This driver does its absolute best to put out a standardized format for games to use. If they don't take advantage of that, there is ABSOLUTELY NOTHING we can do. The best we can do for you is give you the 'Pretend to be an Xbox 360 Controller' option in the 'Advanced' tab. This will make any wired Xbox 360 or wired Xbox One controller appear to games as if it were an official Microsoft Xbox 360 Controller. That way if the game is only looking for Xbox 360 controllers and isn't looking for other devices like third party Xbox 360 controllers or Xbox One controllers, you should be able to trick the game. If you experience an issue with a game that this toggle does not fix, we cannot help you, sorry. That is just the nature of drivers.

How do I find my Vendor ID and Product ID?

Navigate to the Apple menu at the top left corner of your screen. Select the About This Mac option. This will open a new window, where you need to select System Report.. in the Overview tab. This will open another new window. On the left hand side of this window, there will be a number of options. Select USB. It will be somewhere near the bottom of the Hardware section. This will show you the USB device tree. Find and click on the entry that corresponds to your controller. This will provide you with the information needed at the bottom of the window. If you cannot find your device, make sure that all devices are properly connected to the computer. Try different cables if the controller still is not found.

Original Xbox Controllers

Make an issue describing your problem.

Wired Xbox 360 Controllers

Wireless Xbox 360 Controllers

As of macOS 10.11, Wireless Xbox 360 controller support causes kernel panics. This issue cannot be resolved with minor changes to the driver, and requires that the driver be re-written from scratch to resolve the issue. Due to an excess of caution, we have disabled Wireless Xbox 360 controller support as of 0.16.6. If you want to use a wireless controller, download 0.16.5 or earlier and disable the driver before the computer enters a 'sleep' state in order to prevent kernel panics. Alternatively, you can revert to a macOS version before 10.11 to avoid this issue.

Xbox One Controllers connected with USB

Always check your controller with the preference pane found at: Apple Menu -> System Preferences -> Xbox 360 Controllers before creating an issue. If the controller works in this menu, then the driver is operating as intended. If your controller works with this menu, but not with a specific game, then read the My controller doesn't work with a game! section.If your controller is recognized by the preference pane, but you aren't getting any response from button presses, this is likely due to an issue with macOS 10.11 and later. Apple changed some of the underlying USB code with this release and broke compatibility with some controllers. This is specifically found in controllers from PDP and PowerA. If you revert to macOS 10.10 or earlier, these controllers will work.If the preference pane can't find your controller, make sure that it is listed in Apple Menu -> About this Mac -> System Report -> Overview -> Hardware -> USB. This menu should list a device called 'Controller.' If it isn't listed there, then you likely have a 'charge' Micro USB cable instead of a 'data' cable. If the cable isn't sending data, then you can't use the driver. Try a different cable.If you have a third party controller, make an issue following the template with the 'Product ID' and 'Vendor ID' of the controller. Follow How do I find my Vendor ID and Product ID? for instructions on how to find this information.At this time, PDP and PowerA controllers are unsupported by this driver as of macOS 10.11+ thanks to a rewrite of the macOS USB kernel. We cannot resolve this issue. It is a bug in Apple's core OS code.

Xbox One Controllers connected with Wireless Adapter

Xbox One controllers connected with the Wireless Adapter are currently not supported. Please be patient as we figure out this complicated protocol.

Xbox One Controllers connected with Bluetooth

The Xbox One controller works with macOS automatically when connected over Bluetooth via System Preferences. Only specific Xbox One controllers released after August 2016 have Bluetooth capability. See Microsoft's support page for determining if your controller supports Bluetooth. Due to the fact that this controller works by default, it will not be supported by this driver. If you choose to plug this controller in via USB, you will need this driver. If you do not wish to connect the controller via USB, then you do not need this driver. Any problems with game compatibility in Bluetooth mode are completely out of our control and are up to you to solve in conjunction with the game developer.

Xbox One Adaptive Controller

The Xbox One adaptive controller can connect to your macOS machine through either a Bluetooth or wired connection. In Bluetooth mode, it is not controlled by the driver in any way, and will not show up in the 'Xbox 360 Controllers' preference pane. If you are having issues with a wired connection, where the preference pane is recognizing your controller, but isn't recieving inputs, please connect it to a PC or VM running Windows in order to recieve a crucial firmware update. This update may also be possible through an Xbox One console.

Adding Third Party Controllers

First, disable signing requirements so that you can run your custom build with your third party controller added. Then edit 360Controller/360Controller/Info.plist. Add your controller following the pattern of pre-existing controllers by adding your vendor and product IDs to a new entry. After this, follow the information in the building section, following the 'If you don't have a signing certificate' path to build your new .kext. Then, place your shiny new 360Controller.kext in to /Library/Extensions over the old one. You may need to take ownership of the driver in order for it to operate properly. You can do this with sudo chown -R root:wheel /Library/Extensions/360Controller.kext. Then, to make sure everything went according to plan, run sudo kextutil /Library/Extensions/360Controller.kext. This will load your kext into the OS and you should be able to use your controller. Once you reboot, your custom driver should be loaded automatically.

Developer Info

Drivers inherently modify the core operating system kernel. Using the driver as a developer can lead to dangerous kernel panics that can cause data loss or other permanent damage to your computer. Be very careful about how you use this information. We are not responsible for anything this driver does to your computer, or any loss it may incur. Normal users will never have to worry about the developer section of this README.

Building

Apple has recently changed how drivers work in Xcode 7. In order to build the driver, you will need Xcode 6.4 or earlier.

Additionally, to use the included build scripts, you will need to change your preferred Xcode installation using xcode-select.

You must have a signing certificate to install a locally built driver. Alternatively, you can disable driver signing on your machine, however this is a major security hole and the decision should not be taken lightly.

You will need a full installation of Xcode to build this project. The command line tools are not enough.

The project consists of three main parts: The driver (implemented in C++, as an I/O Kit C++ class), the force feedback plugin (implemented in C, as an I/O Kit COM plugin) and the preference pane (implemented in Objective C as a preference pane plugin). To build, use the standard Xcode build for Deployment on each of the 3 projects. Build Feedback360 before 360Controller, as the 360Controller project includes a script to copy the Feedback360 bundle to the correct place in the .kext to make it work.

To debug the driver, sudo cp -R 360Controller.kext /tmp/ to assign the correct properties - note that the Force Feedback plugin only seems to be found by OSX if the driver is in /System/Library/Extensions so it can only be debugged in place. Due to the fact that drivers are now stored in /Library/Extenions, this means that you must create a symlink between the location of the driver and /System/Library/Extensions so that the force feedback plugin can operate properly.

Building the .pkg

In order to build the .pkg, you will need to install Packages.app.

If you don't have a signing certificate

Open 360 Driver.xcodeproj using Xcode.
Select the 360 Driver project in the Navigator.
Select the 360Daemon target from the top right corner.
Select the Build Settings tab from the top of the screen.
In the Code Signing section, find Code Signing Identity section and expand it.
In the Release section, change the selection to Don't Code Sign.
Set the code signing identity for 360Daemon, Feedback360, 360Controller, DriverTool, Pref360Control, Wireless360Controller, WirelessGamingReceiver and Whole Driver.
Run ./build.sh to build the .pkg. This .pkg can be found in the Install360Controller directory.

If you have a signing certificate

Create a file named DeveloperSettings.xcconfig
Select the 360 Driver project in the Navigator.
In this file, add the following lines:
- DEVELOPMENT_TEAM = XXXXXXXXXX where XXXXXXXXXX is the development team on your Developer ID Application and Installer certificates.
- DEVELOPER_NAME = First Last where First Last is the name on the Developer ID Installer certificate.
- DEVELOPER_EMAIL = my.address@email.com where my.address@email.com is the email address of your Apple account that has your Developer ID Application and Installer certificates.
- NOTARIZATION_PASSWORD = abcd-efgh-ijkl-mnop where abcd-efgh-ijkl-mnop is a temporary password that you have generated for your Apple account for the purposes of notarization.

Disabling signing requirements

Since Yosemite (macOS 10.10) all global kexts are required to be signed. This means if you want to build the drivers and install locally, you need a very specific signing certificate that Apple closely controls. If you want to disable the signing requirement from macOS, you will need to do several things.

First, execute these commands in your terminal:

Next, you must disable System Integrity Protection. To do this, boot into recovery mode by holding down CMD + R while the computer is starting. Once recovery mode has been loaded, open the terminal from the Utilites menu item. Execute the following command:

Windows 10 X360 China Xbox Controller Driver Download

Re-Enabling signing requirements

From recovery mode, execute the following command:

Reboot into macOS like normal. You can reset the boot arguments by executing this command:

Xbox Controller For Pc Driver Windows 10

This will remove ALL boot-args. If you have previously manipulated your boot-args, those changes will be erased as well!

Notarization of the driver

This is only possible if you have a signing certificate, but it is a relatively straightforward process.

Build the driver as previously instructed and make sure to include the necessary information in your DeveloperSettings.xcconfig file, as they will be used during this process.
Make sure to cd into the Install360Controller directory and run ./makedmg.sh
Run ./notarize.sh
This should finish with the message: The validate action worked!

Then you can distribute the notarized and stapled version of the driver.

Debugging the driver

Debugging the driver depends on which part you intend to debug. For the 360Controller driver itself, it uses IOLog to output to the system.log which can be accessed using Console.app. Feedback360 uses fprintf(stderr, ..), which should appear within the console of the program attempting to use force feedback.

Debugging the preference pane

Most of these instructions are pulled directly from this blog post. Please visit it for futher information.

First, create a copy of System Preferences.app called System Preferences (signed).app. Then sign this new System Preferences with the command:

Hp X360 Drivers Windows 10

codesign -s 'Developer ID Application: First Last (XXXXXXXXXX)' -f /Applications/System Preferences (signed).app/

where Developer ID Application: First Last (XXXXXXXXXX) is the name of your Developer ID Application signing certificate.

Edit your build scheme for Pref360Control, and select the 'Run' scheme, and make sure you are editing 'Debug' (A). In the environment variables section, click on '+' to add a new environment variable (B). Name the new variable OBJC_DISABLE_GC, and set its value to YES.

Next, click the little disclosure triangle for the run scheme to reveal its detailed settings. Then select pre-actions. Click the '+' at the bottom to add a run script action. Enter /bin/sh as the shell, make sure that your target is selected to provide build settings, and type a shell command line to install the newly compiled pref pane in your personal Library folder:

cp -Rf ${CONFIGURATION_BUILD_DIR}/Pref360Control.prefPane ~/Library/PreferencePanes

Finally, select the run step, choose 'other' from the executable drop-down menu, and select System Preferences (signed) in the Applications folder. Verify that 'Debug executable' and 'Automatically' are both checked.

A note on Unity mappings

The issues with the button and axis mappings in the Unity game engine are outside of our control. Unity mangles the button and axis values provided by the controller and remaps them to different values. There is absolutely no way that we can introduce a shim to fix it. Complaints about this should be directed at Unity, not at us.

Licence

Windows 10 X360 China Xbox Controller Driver Pc

This driver is licensed under the GNU Public License. A copy of this license is included in the distribution file, please inspect it before using the binary or source.