Version History v136.txt Driver File Contents (BCS2_Wedge_Application_v136.zip)

BCS2 Keyboard Wedge Application.

v136
- Added in an alert warn that IrDA is disabled when enabling the wedge.
- Added comment in help file about the IrDA being disabled.
- Handling application launch after conditional resets better now. 
- Changed the application name from BCS2KeyboardWedge, to BCS2Wedge.
- Changed the application icon

v135
- Corrected bug when setting scanner to defaults.
- Disabling IrDA library when scanner is activated. User is given the option to deactivate it when the IrDA library is invoked. The IrDA has to be disabled because the auto trigger IR LED on the scanner interferes with communications.

v134
- Corrected bug where sometimes the module may complain that it can't be configured when being enabled for the first time.
- Made sure that scanner is reset afer each scanner configuration so as to make it more reliable each time.
- Corrected bug where the scanner config string was appearing in the main title string after the About box was clicked.
- Corrected bug where the custom Date format was hanging off the screen for the longest string.
- Corrected bug where the custom Date format was not being updated next time the form was loaded.
- If the user tries to delete the wedge application when it is enabled, everything will now properly shutdown, and then get deleted.
- After a soft reset, the scanner will reinitialise automatically without a prompt if it was turned on before the reset.			
- When doing a HotSync, wedge is disable in case it needs to be updated. It is reenabled after HotSync is finished.					
- Corrected bug where Up and Down arrow keys were not registering.
- When the scanner has been deactivated (due to timeout) and launching the wedge application UI, now prompting to reactivate it.


v133
- Incorporated a message box to pop up when scanner functions are stalling the system.
- Added support for barcode type IDs, for easier software filtering on barcode types.
- Fixed bug when changing from Auto IR triggering to manual triggering. The immediate manual trigger didn't seem to register the barcode, but subsequent triggers did. Now cycling scanner power when the scanner is updated.
- Fixed bug where two barcodes were being enqueued back to back under some circumstances.
- When the user taps on the prompt to enable the scanner after a reset, it used to launch the wedge application by default. This is no longer the case, as it is inappropriate in some circumstances. 


v132	
20-Mar-06
- Incorporated a API interface via launch codes to give access to 3rd party software for enabling, disabling, getting and setting wedge preferences, setting to defaults, and also triggering.
- The wedge now checks for the physical presence of the BCS2 module before proceeding.
- Added support for trasmitting code ID when the barcode is read. However only the code ID supporting barcodes (EAN8,13, UPCA,E, Interleaved 2of5, Codabar, Code 128) are supported due to the laser module's limitations. Note that barcodes other than these ones will display a Generic Code ID. 
- Added more flexibility to custom string generation which now replaces the previous method. This system allows the user to specify special character fields which will generate the output string according to what they represent. Also included is a checker to make sure that the string is valid at the point that it is created.
- Added the ability to now have more than 1 trigger method simultaneously. This however can't be extended to have auto IR triggering as well as manual triggering as the scanner doesn't support this.
- Added checkboxes for selecting if a good read or bad read sound is to be heard.
- Made it possible to set the min and max barcode lengths.
- Changed the key queue to be accept 100 chars, instead of the 40 or so that is the system default. It is restored to its previous size afterwards.
- The Main screen now updates itself automatically when the scanner deactivates from timeout.		
- Incorporated new configuration windows, via tabbed button interface.
- Add page up/down buttons to the trigger mix.
- Found that when scanning multiple barcodes very quickly, some barcodes would only appear partially and sometimes garbled. Corrected this issue.
- Increased the size of key queue to 200 elements now, so that more entries can be made before the queue is full. This is so that when scanning multiple barcodes really quickly, the barcodes aren't lost - or at least more of the barcode are properly recorded, rather than being lost.
- Made the update of the scanner settings more robust, in that if it failed, it would better inform the user, and also try again. If user selects not to try again, the wedge will be disabled. The scanner settings will be updated again the next time the wedge is enabled.
- Developed a programmers interface for enabling, disabling, triggering and changing the internal preferences of the wedge application.
- Made it so that the repeating keys for left and right buttons do not generate new scans if held down. Instead, the system will now hold the processor still if the keys remain pressed down, and will only continue when the keys are released. 
- Enqueuing ACEECABarcodeReceivedKey=0x1D01 with the keyCode as the total lenth of the barcode about to be received. 

v112
20-Dec-05
- When enabling scanner for the first time, the scanner engine is configured to the application preferences. This prevents the BCS2 module being out of sync with the wedge application. 
- This version supports the BCS2 driver natively and doesn't require the BCS2 shared library. It can however be reverted back to using the BCS2 shared library method using a conditional compile.

v100
14-Dec-05
- Initial beta release, relies on BCS2 shared library.
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: ftp, load: 2.01