We have a universal version number for a release. This is set in the module Bio::Root::Version which is universally applied to every module which inherits from Bio::Root::RootI. To check the version, just use the following one liner: perl -MBio::Root::Version -e 'print $Bio::Root::Version::VERSION,"\n"' Now when we use version tuples that are not just decimal numbers, Perl converts these silently to Unicode representations.

No, remote loading is discouraged. If you're really keen, you can set up a mirror of it and use that.

BioPerl is a toolkit of perl modules useful in building bioinformatics solutions in Perl. It is built in an object-oriented manner so that many modules depend on each other to achieve a task. The collection of modules in the bioperl-live repository consist of the core of the functionality of bioperl.

There is unfortunately no consistent nor single way to make this determination---this is one of the reasons that a move to PCSI installations is underway. On OpenVMS Alpha, you can use VMSINSTAL.HISTORY and PRODUCT SHOW PRODUCT to determine what packages have been installed via the VMSINSTAL and PCSI tools, respectively. To see which OpenVMS Alpha ECO kits have been applied, look in VMSINSTAL.HISTORY on OpenVMS Alpha prior to V7.1-2, and use PRODUCT SHOW PRODUCT/FULL on OpenVMS Alpha V7.

Some versions of the TransactNOW install display the version number at the bottom of any of the TransactNOW pages. You will see it in a bar at the bottom of the page and it will look something like 4.0.3.13.

Upon Reset, the original Apple II starts you in the system monitor looking at the "*" prompt. It allows step execution of machine code and has Integer BASIC in ROM. The major division between kinds of Apple II is Revision 0 and Revision 1. The Revision 1 motherboard adds a number of features including a few which are easily observed: More hires colors: To the Black, White, Violet, and Green available on a Rev0 machine, Rev1 adds Blue and Orange.

where <version> is found in the file VERSION and <n> is the number recorded in dist/hylfax.alpha. This string is also prominently displayed when you run the configure script to setup the software for compilation and each time the faxq scheduler process is started (look in the file where syslog messages are recorded).

Ewan Birney has answered this a few times on the Ensembl mail list. In short (in this thread): Ensembl doesn't make heavy use of Bioperl anymore - most of the critical things we re-wrote, mainly due to speed/memory issues. I think the short answer is that it _probably_ works with 1.5, but we don't have a strong desire to move up as certainly there are no problems with the 1.2.3 release we are using.

BioPerl is licensed under the same terms as Perl itself which is the Perl Artistic License (see http://www.perl.com/pub/a/language/misc/Artistic.html or http://www.opensource.org/licenses/artistic-license.html).

Use the module Bio::Tools::Run::StandAloneBlast. It will give you access to many of the search tools in the NCBI BLAST suite including blastall, bl2seq, blastpgp. The basic structure is like this.

bioperl-ext is a package of code for C-extensions (hence the 'ext') to BioPerl. These include interfacing to the staden IO library (the io_lib library) for reading in chromatogram files and Bio::Ext::Align which is a Smith-Waterman implementation.

The Microarray package provides some basic tools for microarray functionality. It was started by Allen Day and may need some more work before it is a mature product.

The GUI package provides a Graphical User Interface for interacting with sequence and feature objects. It is used as part of the Genquire project.

The Pedigree package was started by Jason Stajich and provides basic tools for interacting with pedigree data and rendering pedigree plots.

By repeatedly pressing the <UTILITY> button until you get to the "SYS INFO" page, you can tell what software is currently installed, what file system it's using, the EPROM version installed, and the model of the CD writer and hard drive installed. Back

Run the BCFPI software and choose, "Help | About" from the menu on the main BCFPI window. The About dialog will display either the "Outcomes Evaluation Software Version", or the, "Brief Child and Family Phone Interview Software Version". This tells you the version of the BCPFI software that you are running. You can compare the version here with the list of versions in our release history for more information.

Look at the case of the computer to determine which Apple II you have, then in the section on Apple II model information (sections 2.x) for that model. The methods of determining the versions of each model are integrated into the other information for that model.

We suggest the following. Post your idea to the appropriate mailing list. If it is a really new idea consider taking us through your thought process. We'll help you tease out the necessary information such as what methods you'll want and how it can interact with other BioPerl modules. If it is a port of something you've already worked on, give us a summary of the current methods.

Press MENU » MENU » 'Setup' » ENTR » 'System' » ENTR » MENU » 'Software Version' » ENTR. The current version of the firmware is shown. Unit ID is also listed.

Click the About button in the main menu to see what version of GAGEtrak you have. The latest version is always listed on the Software Updates page. Yes! You can easily export GAGEtrak data to most of the standard Windows programs, such as Microsoft Excel, Rich Text (Microsoft Word), HTML, or text. To export data, select the Import/Export option on the Tools and Utilities Menu.

In the browser's toolbar, click on "Help." You will see a menu option that begins "About..." Click on this menu option. You will see the type of browser you are using and also what version. Not at this time. Currently, if you log out of E-file before you complete and submit your IFTA return, you must reenter all the information when you log in again.

With the IIGS turned on, press CONTROL-Apple-ESCAPE And go to the Transwarp CDA The ROM version will be displayed on the screen.

When a Service Pack is installed using the normal method (e.g. not just copying the files to a build location) the service pack version is entered into the registry value CSDVersion which is under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion. The value is of the formal "Service Pack n", e.g. "Service Pack 4" but can have extra information if it is a beta or release candidate, e.g. "Service Pack 4, RC 1.99". alternative is to just run WINVER.

In the About Windows Movie Maker dialog box, note the version number. Version 2.1.4026.0 is Movie Maker version 2.1, and version 2.0.3312.0 is Movie Maker version 2.0. Install the latest Multilingual User Interface Packs (MUI) for Movie Maker 2.1. You can download the latest MUI packages from the Download Center.

If you're using any version earlier than Cosmo Player 2.0 (27191), or any beta version, you should definitely upgrade to Cosmo Player 2.1!

The following steps will determine which version of PowerNet is currently loaded in the Falcon RF unit. Safe boot the unit. If you are unfamiliar with this process, please refer to the Falcon Advanced User´s Guide, Chapter Seven: Resetting the Falcon. The TCPIP stack will try to load, however, an error message will appear because the RF card drivers and PCMCIA card drivers are not loaded. On the first line after typing SOCKETEP the message "DATLIGHT SOCKETS version XX" will display.

The PKTerm version number appears on the splash screen as you start PKTerm. You can also get the version number by clicking on Help, About from inside PKTerm.