NOTE The instructions on this page are for the latest WinDriver version released for the target operating system. To install an older version of WinDriver, refer to the installation instructions in the WinDriver User’s Manual for your WinDriver version. Below you will find instructions for,, and.

Free jungo 10.2 download download software at UpdateStar.

Installation Instructions for Windows System Requirements • Any x86 32-bit or 64-bit (x64: AMD64 or Intel EM64T) processor. • Any compiler or development environment supporting C or.NET • Windows XP requires at least SP2.

NOTE • The WinDriver installation defines a WD_BASEDIR environment variable, which is set to point to the location of your WinDriver directory, as selected during the installation. This variable is used during the DriverWizard code generation — it determines the default directory for saving your generated code and is used in the include paths of the generated project/make files. This variable is also used from the sample Kernel PlugIn projects and makefiles. • If the installation fails with an ERROR_FILE_NOT_FOUND error, inspect the Windows registry to see if the RunOnce key exists in HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion. This registry key is required by Windows Plug-and-Play in order to properly install drivers using INF files. If the RunOnce key is missing, create it; then try installing the INF file again. The following steps are for registered users only: To register your copy of WinDriver with the license you received from Jungo Connectivity, follow these steps: • Start DriverWizard: Start Programs WinDriver DriverWizard.

• Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo Connectivity. • Click the Activate License button. • To register source code you developed during the evaluation period — • For USB, refer to the documentation of WDU_Init() in the. • For PCI, refer to the documentation of WDC_DriverOpen() in the.When using the low-level WD_xxx API instead of the WDC_xxx API (which is used by default), refer to the documentation of WD_License() in the. Installation Instructions for Windows CE System Requirements • An x86 or ARM target platform running Windows CE (a.k.a. Windows Embedded Compact) 4. Mx Player Serial here. x–8.x (including Windows Mobile) OR a MIPS target platform running Windows CE 4.x–7.x (including Windows Mobile) • Windows 10/8.1/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP host development platform.

• IDE: • For Windows CE 4.x–5.x (including Windows Mobile): • Microsoft eMbedded Visual C++ or Microsoft Visual Studio 2005/2008 with a corresponding target SDK • Microsoft Platform Builder with a corresponding Board Support Package (BSP) for the target platform • For Windows Embedded CE 6.x: Microsoft Visual Studio 2005/2008 with a corresponding target SDK or with the Windows CE 6.0 plugin. • For Windows Embedded CE 7.x: Microsoft Visual Studio 2008 with the Windows Embedded Compact 7 plugin • For Windows Embedded CE 8.x: Microsoft Visual Studio 2012 or higher with the Application Builder for Windows Embedded Compact 2013 plugin Installation Installing WinDriver CE when Building New CE-based Platforms. NOTE • The following instructions apply to platform developers who build Windows CE kernel images using Windows CE Platform Builder or using MS Visual Studio 2005/2008 with the appropriate Windows CE 6.0 plugin. The instructions use the notation “Windows CE IDE” to refer to either of these platforms. • We recommend that you read Microsoft’s documentation and understand the Windows CE and device driver integration procedure before you perform the installation. • Modify the project registry file — WinDriver samples wince_install project_wd.reg — to add an entry for your target device.

NOTE When defining ID values, take care to use the correct format, as specified in the project_wd.reg comments — decimal for USB devices and hexadecimal for PCI devices. • Compile your Windows CE platform (Sysgen stage). • Integrate the driver into your platform: • Run the Windows CE IDE and open your platform. • Select Open Build Release Directory from the Build menu. • Copy the WinDriver CE kernel file — WinDriver redist windrvr1221.dll — to the%_FLATRELEASEDIR% subdirectory on the target development platform (should be the current directory in the new command window). • Append the contents of WinDriver samples wince_install project_wd.reg to the%_FLATRELEASEDIR% project.reg registry file. • Copy the contents of the WinDriver samples wince_install project_wd.bib file to the FILES section of the binary image builder file —%_FLATRELEASEDIR% project.bib.

Then uncomment the line that matches the target platform (see the “TODO” comments in the copied text). NOTE This step is only necessary if you want the WinDriver CE kernel file ( windrvr1221.dll) to be a permanent part of the Windows CE image ( NK.BIN), which is the case if you select to transfer the file to your target platform using a boot disk. If you prefer to have the file windrvr1221. Shareit Download For Windows 7 64 Bit. dll loaded on demand via the CESH/PPSH services, you do not need to perform this step until you build a permanent kernel. • Select Make Image from the Build menu, and name the new image NK.BIN.

• Download your new kernel to the target platform and initialize it either by selecting Attach Device from the Target menu, or by using a boot disk. For Windows CE 4.x, the menu is called Download/Initialize rather than Attach Device. • Restart your target CE platform.

The WinDriver CE kernel will automatically load. • Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see the for an explanation on how to check your installation). Installing WinDriver CE when Developing Applications for CE Computers. NOTE Unless otherwise specified, “Windows CE” references in this section include all supported Windows CE platforms, including Windows Mobile. The following instructions apply to driver developers who do not build the Windows CE kernel, but only download their drivers, built using MS eMbedded Visual C++or MS Visual Studio 2005/2008 to a ready-made Windows CE platform. • Run the WinDriver installation — WDCE.EXE (for example, WD1221CE.EXE) — on your host Windows PC, and complete the installation. • Copy WinDriver’s kernel module — windrvr1221.dll — from the WinDriver redist WINCE directory on the Windows host development PC to the Windows directory on your target Windows CE platform • Add WinDriver to the list of device drivers Windows CE loads on boot: • Modify the registry according to the entries documented in the file WinDriver samples wince_install project_wd.reg.

This can be done using the Windows CE Pocket Registry Editor on the hand-held CE computer, or by using the Remote CE Registry Editor Tool supplied with MS eMbedded Visual C++ or MS Visual Studio 2005/2008. Note that in order to use the Remote CE Registry Editor tool you will need to have Windows CE Services installed on your Windows host platform. • On many versions of Windows CE, the operating system’s security scheme prevents the loading of unsigned drivers at boot time, therefore the WinDriver kernel module has to be reloaded after boot. To load WinDriver on the target Windows CE platform every time the OS is started, copy the WinDriver redist Windows_Mobile_5_ARMV4I wdreg.exe utility to the Windows StartUp directory on the target PC. • Restart your target CE computer. The WinDriver CE kernel will automatically load. You will have to do a warm reset rather than just suspend/resume (use the reset or power button on your target CE computer).

• Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see the for an explanation on how to check your installation). Windows CE Installation Note: The WinDriver installation on the host Windows PC defines a WD_BASEDIR environment variable, which is set to point to the location of your WinDriver directory, as selected during the installation. This variable is used during the DriverWizard code generation — it determines the default directory for saving your generated code, and is used in the include paths of the generated project/make files. Note that if you install the WinDriver Windows toolkit on the same host PC, the installation will override the value of the WD_BASEDIR variable from the Windows CE installation. Installation Instructions for Linux System Requirements • Any of the following processor architectures, with a 2.6.x or higher Linux kernel: • 32-bit x86 • 64-bit x86 AMD64 or Intel EM64T (x86_64) • PowerPC 32-bit or 64-bit (PCI only).

NOTE Jungo Connectivity strives to support new Linux kernel versions as close as possible to their release. To find out the latest supported kernel version, refer to the. • A GCC compiler NOTE: The version of the GCC compiler should match the compiler version used for building the running Linux kernel. • Any 32-bit or 64-bit development environment (depending on your target configuration) supporting C for user mode • On your development PC: glibc2.3.x • libstdc++.so.6 and libpng12.so.0 — required for running GUI WinDriver applications (e.g., DriverWizard; Debug Monitor) Preparing the System for Installation In Linux, kernel modules must be compiled with the same header files that the kernel itself was compiled with. Since WinDriver installs the kernel modules, it must compile with the header files of the Linux kernel during the installation process. Therefore, before you install WinDriver for Linux, verify that the Linux source code and the file version.h are installed on your machine: Install Linux kernel source code: • If you have yet to install Linux, install it, including the kernel source code, by following the instructions for your Linux distribution. • If Linux is already installed on your machine, check whether the Linux source code was installed.

You can do this by looking for ‘linux’ in the /usr/src directory. If the source code is not installed, either install it, or reinstall Linux with the source code, by following the instructions for your Linux distribution. Install version.h: The file version.h is created when you first compile the Linux kernel source code. Some distributions provide a compiled kernel without the file version.h.

Look under /usr/src/linux/include/linux/ to see whether you have this file. If you do not, follow these steps: • Become super user: $ su • Change directory to the Linux source directory: # cd /usr/src/linux • Type # make xconfig • Save the configuration by choosing Save and Exit. • Type # make dep • Exit super user mode: # exit To run GUI WinDriver applications (e.g., DriverWizard; Debug Monitor) you must also have version 6.0 of the libstdc++ library — libstdc++.so.6 — and version 12.0 of the libpng library — libpng12.so.0. If you do not have these files, install the relevant packages for your Linux distribution (e.g., libstdc++6 and libpng12-0).

Before proceeding with the installation, you must also make sure that you have a ‘linux’ symbolic link. If you do not, create one by typing /usr/src$ ln -s linux For example, for the Linux 3.0 kernel type /usr/src$ ln -s linux-3.0/ linux Installation • On your development Linux machine, change directory to your preferred installation directory, for example to your home directory: $ cd ~/.

NOTE The path to the installation directory must not contain any spaces. • Extract the WinDriver distribution file — WDLN.tgz or WDLNx86_64.tgz (for example, WD1221LN.tgz or WD1221LNx86_64.tgz): $ tar xvzf /WDLN[x86_64].tgzFor example, to extract WD1221LN.tgz run this command: $ tar xvzf ~/WD1221LN.tgz • Change directory to your WinDriver redist/ directory (the tar automatically creates a WinDriver/ directory): $ cd /redist/ • Install WinDriver: • For USB: /redist$./configure For PCI: /redist$./configure --disable-usb-support. NOTE • The configuration script creates a makefile based on the running kernel. You may select to use another installed kernel source, by executing the script with the --with-kernel-source= option, where is the full path to the kernel source directory — e.g., /usr/src/linux. • If the Linux kernel version is 2.6.26 or higher, the configuration script generates makefiles that use kbuild to compile the kernel modules. You can force the use of kbuild on earlier versions of Linux, by executing the configuration script with the --enable-kbuild flag.

For a full list of the configuration script options, use the --help option:./configure --help • /redist$ make • Become super user: /redist$ su • Install the driver: /redist# make install • Create a symbolic link so that you can easily launch the DriverWizard GUI: $ ln -s /wizard/wdwizard /usr/bin/wdwizard • Change the read and execute permissions on the file wdwizard so that ordinary users can access this program. • Change the user and group IDs and give read/write permissions to the device file /dev/windrvr1221 depending on how you wish to allow users to access hardware through the device. Due to security reasons, by default the device file is created with permissions only for the root user. Change the permissions by modifying your /etc/udev/permissions.d/50-udev.permissions file.

For example, add the following line to provide read and write permissions: windrvr1221:root:root:0666 • Define a new WD_BASEDIR environment variable and set it to point to the location of your WinDriver directory, as selected during the installation. This variable is used in the make and source files of the WinDriver samples and generated DriverWizard code, and is also used to determine the default directory for saving your generated DriverWizard project.

If you do not define this variable you will be instructed to do so when attempting to build the sample/generated code using the WinDriver makefiles. • Exit super user mode: # exit • You can now start using WinDriver to access your hardware and generate your driver code! TIP Use the WinDriver/util/wdreg script to load the WinDriver kernel module. To automatically load WinDriver on each boot, add the following to the target Linux boot file ( /etc/rc.d/rc.local): /wdreg windrvr1221 The following steps are for registered users only: To register your copy of WinDriver with the license you received from Jungo Connectivity, follow these steps: • Start DriverWizard: $ /wizard/wdwizard • Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo Connectivity. • Click the Activate License button. • To register source code you developed during the evaluation period — • For USB, refer to the documentation of WDU_Init() in the. • For PCI, refer to the documentation of WDC_DriverOpen() in the.When using the low-level WD_xxx API instead of the WDC_xxx API (which is used by default), refer to the documentation of WD_License() in the.

• Easy user-mode driver development. • Friendly DriverWizard allows hardware diagnostics without writing a single line of code.

• Automatically generates the driver code for the project in C, C#, Visual Basic.NET, Delphi (Pascal), or Visual Basic 6.0. • Supports any USB device, regardless of manufacturer. • Enhanced support for specific chipsets frees the developer of the need to study the hardware’s specification. • Applications are binary compatible across Windows 10/8.1/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP. • Applications are source code compatible across all supported operating systems — Windows 10/8.1/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP, Embedded Windows 10/8.1/8/7, Windows CE (a.k.a. Windows Embedded Compact) 4.x–7.x (including Windows Mobile), and Linux. • Can be used with common development environments, including MS Visual Studio, Borland C++ Builder, Borland Delphi, Visual Basic 6.0, MS eMbedded Visual C++, MS Platform Builder C++, GCC, Windows GCC, or any other appropriate compiler/environment.

• No WDK, ETK, DDI or any system-level programming knowledge required. • Supports multiple CPUs. • Includes dynamic driver loader. • Comprehensive documentation and help files. • Detailed examples in C, C# and VB.NET.

• WHQL certifiable driver (Windows). • Two months of free technical support.

• No run-time fees or royalties. WinDriver’s Top Features • Fast: Shorten driver development cycle and time to market. • Simple: No OS internals or kernel knowledge required. • Stable: Field-tested on thousands of HW and OS configurations. • Enhanced Chipset Support: Silicon partners libraries to jump-start your driver development. Special samples for various PCI/USB chip vendors, such as and. WinDriver generates a skeletal driver code, customized for the user’s hardware.

• Multiple OS support and cross platform: WinDriver product line supports?Windows 10/8.1/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP, Embedded Windows 10/8.1/8/7, Windows CE/Mobile, and Linux. The same driver will run under all supported operating systems without any code modifications. Just recompile! • Immediate Hardware Access and Debugging: Test your hardware through a graphical user-mode application, without having to write a single line of code.

Monitor kernel level activity throughout the driver development process. • Performance Optimization: Use WinDriver’s Kernel PlugIn technology to develop your driver in the user-mode — then run performance critical sections of it in the Kernel Mode (Ring 0) to achieve optimal performance. • WHQL Certifiable Driver: WinDriver’s Windows drivers are WHQL ready — you will not need to invest time and efforts on making your driver WHQL compliant. Jungo also can prepare the WHQL submission package for you. • Field-proven quality: WinDriver’s technology enables you to concentrate on your core business and successfully create first-rate drivers without having to invest redundant resources in driver development from scratch.

• User-mode programming: WinDriver’s architecture enables driver development in the user mode, while maintaining kernel-mode performance. • 64-bit Support: Allow utilizing the additional bandwidth provided by 64-bit hardware and enable 64-bit data transfer on x86 platforms running 32-bit operating systems.

Drivers developed with WinDriver will attain significantly better performance results than drivers written with the DDK or other driver development tools that do not support this feature. • Complete.NET Framework Support: Easily incorporate WinDriver’s C# or VB.NET code into your existing.NET application using the powerful object oriented managed extensions for C++ library.