Skip to content
This repository has been archived by the owner on Sep 14, 2024. It is now read-only.

Releases: BrickBot/Archive

Official Renesas (Hitachi) H8/300 Resources

14 Sep 13:37
5c81a2c
Compare
Choose a tag to compare

Official LEGO® MindStorms RCX Multimedia

15 Jun 14:40
c975f7e
Compare
Choose a tag to compare

com0com Null-Modem Emulator and Utilities for Windows

27 Jan 03:53
bc6531d
Compare
Choose a tag to compare

A suite of drivers and tools offering virtual serial ports, serial port redirection, and more.


Known Driver Signing Issues

Due to driver signing issues reported with the releases posted on the legacy SourceForge project site when installing on Windows 10, version 1607, or newer, multiple different com0com versions are posted here.

Problem Synopsis

Per Windows Driver Signing Policy, “Starting with Windows 10, version 1607, Windows will not load any new kernel-mode drivers which are not signed by the Dev Portal.”

Permitted Exceptions to the Driver-Signing Policy

Per that same policy page, there are three exceptions to the “signed by the Dev Portal” requirement:

  • The PC was upgraded from an earlier release of Windows to Windows 10, version 1607.
  • Secure Boot is turned off in the BIOS.
  • Drivers were signed with an end-entity certificate issued prior to July 29th 2015 that chains to a supported cross-signed CA.

(For a more in-depth consideration of driver signing, please refer to Practical Windows Code and Driver Signing.)

For most end users, the only practical exception option would likely be turning of Secure Boot in the BIOS, but of course there are tradeoffs to doing so. Given these issues, there are multiple different ways to attempt installation.

Alternative Driver Signing Workaround

Driver Signature Enforcement Overrider: A permanent solution to load unsigned kernel-mode drivers by using TESTSIGNING mode with a test-signed digital certificate (suggested only as a last resort).

Available Downloads

Name Description
com0com v3.0.0.0 - Signed These drivers were signed by the "signed-drivers" project on SourceForge and are not from the com0com downloads page on SourceForge for v3.0.0.0
com0com v3.0.0.0 - Manual Install - Signed These drivers were also signed by the "signed-drivers" project on SourceForge, but the difference with this download is that installation must be performed manually. Two executables—setupc.exe and setupg.exe—are also provided to assist with this, but please refer to the bundled ReadMe.txt for usage details and instructions.
com0com v3.0.0.0 - AltSigned These drivers were signed by another SourceForge user back in 2012 and so might help some users avoid the July 29, 2015, certificate issuance date cutoff
com0com v2.2.2.0 - Signed Some users have reported success using the earlier v2.2.0.0 release of com0com, potentially because this signing would have predated the July 29, 2015, cutoff. These files are from the com0com downloads page on SourceForge for v2.2.2.0.   NOTE: Please be sure to fully remove v3 before attempting to install v2.2.2.0

The com2tcp and hub4com releases do not bundle their own drivers, so driver signing has not been an issue with these.


Forks of com0com

As the com0com SourceForge project has not been updated in quite some time, below is a curated list of links to forks of com0com or one or more of its sub-projects (including com0com, hub4com, and com2tcp).


Related Projects

The hubub project (archived here under the BrickBot organization) can potentially offer additional TCP communication capabilities.

Windows Backwards Compatibility Support

27 Jan 02:47
f4dcbac
Compare
Choose a tag to compare

Windows backwards compatibility support, including the latest-and-greatest versions for Windows 9x of third-party dependencies and related software for the Robotics Invention System (more recent than the versions included on the RIS CD):

Explicit Dependencies

 

Optional Software

 

Help System for *.hlp Files on Newer Windows Versions

Windows Vista and newer do not support *.hlp files

 
The following are alternative options for opening *.hlp files, though these methods will not support help support built into older applications or {F1} help.

NetBeans 8.2 for Windows

27 Jan 03:19
bc6531d
Compare
Choose a tag to compare

The last release of the original NetBeans IDE (v8.2), as used to be available bundled with the JDK (pre-Apache).

Was used in the development of some open source software designed for the RCX (e.g. VisualNQC)

NetBeans 8.2 for Windows

Official LEGO® MindStorms Robotics Invention System Releases

27 Jan 05:01
65737ee
Compare
Choose a tag to compare

Official releases from LEGO are gathered here.

Official LEGO® Firmware and ROM Releases for the RCX:

Official LEGO® Software Releases and Guides for the RCX:

Official LEGO® Master Builder Guides for RCX Projects

LEGO USB Tower Driver Update Instructions

By installing these drivers you signify that you have read and accept the conditions outlined in the included LICENSE AGREEMENT (LICENSE.TXT).

For 32-bit Windows XP and Windows 98/ME

  1. Unzip LEGO USB Tower Driver 1.0.50.164 for 32-bit Windows onto a directory on your hard drive
  2. Unplug the Tower from the PC.
  3. Open up the file and click on "Setup"
  4. After the tower drivers are updated, plug in the tower.
  5. Your system should now not freeze when the tower is plugged in.

For 32-bit Windows 2000

  1. Unzip LEGO USB Tower Driver 1.0.50.164 for 32-bit Windows onto a directory on your hard drive
  2. Ensure the tower is plugged in your computer
  3. Right-click the "My Computer" icon and select "Properties" in the context menu
  4. In the My Computer properties window, select the "Hardware" tab
  5. Click on "Device Manager"
  6. Click on "LEGO Devices" and then double-click "LEGO USB Tower"
  7. Select "Driver" tab
  8. Select "Update driver"
  9. Click "Next"
  10. Select "Display a list of known drivers for this device so that I can choose a specific driver"
  11. Click "Next"
  12. Click "Have Disk..."
  13. Navigate to the directory where you unzipped the driver files and click OK
  14. Click "Next"
  15. Click on "Next" again to install the updated driver