Volser 1.3 build: 9639 released: 2012-12-11 compiled with: Java 1.8.0_131 Jet jet12.0-pro-x86/1.8.0_131

Get 4-byte volume serial number of a drive.

Copyright: (c) 2007-2017 Canadian Mind Products.

Java application.
Download from: http://mindprod.com/products1.html#VOLSER

----

Notes:

You must install the Java JRE to use this program.
See http://mindprod.com/jgloss/jgloss/jre.html

This program can only be used from the command prompt, (or via an command
line style icon shortcut) e.g. under Windows command.exe or JPSoft
tcmd.exe, formerly called the DOS box. Just clicking the programs in a
directory listing will not do anything useful. Just typing the program
names at the command prompt will not either.

This program requires a manual install! See below.

This program works with vanilla text files, (e.g. ASCII files or UTF-8
Unicode files). You will need a text editor to create and view them, not a word
processor. e.g. notepad, Visual Slick Edit or other suitable text editor
http://mindprod.com/jgloss/editor.html. You must use a monospaced font
http://mindprod.com/jgloss/monospacedfonts.html (aka fixed pitch, aka
programmer font) to view your files, or they won't look properly aligned.

I put out an avalanche of free software into the world, and submit PAD
files to hundreds of distribution sites, but I rarely hear back from
anyone.  What's happening?  Does it all just work fine?  It is so
complicated nobody can figure out how to use it and they give up on it?
It is it useful?  Since everyone has the source, do people just fix the
programs to their liking themselves?  Did you have trouble installing?  Do
I presume you know too much?  I would be happy to hear from you about your
experiences, positive or negative and your requests for improvements.  A
one-line email to roedy@mindprod.com would be great.

===> Free <===
Full source included.
You may even include the source code, modified or unmodified
in free/commercial open source/proprietary programs that you write and distribute.
May be used freely for any purpose but military.
For more details on this restriction, see
http://mindprod.com/contact/nonmil.html
If you include any Canadian Mind Products code in your own applications,
your app too must be labelled non-military use only.
http://mindprod.com/contact/nonmil.html
All Java jars and source code are included. If you need the class files or Javadoc, you will have to build them yourself. To streamline the zip downloads, class files and Javadoc have been removed.

----

Prerequisites:

This program runs under any OS that supports Java,
(e.g.W2K/XP/W2003/Vista/W2008/W7-32/W7-64/W8-32/W8-64/Linux/LinuxARM/LinuxX86
/LinuxX64/Ubuntu/Solaris/SolarisSPARC/SolarisSPARC64/SolarisX86/SolarisX64/OSX/AIX...)
so long as you have
<><> Java version 1.8 <><> or later installed (32-bit or 64-bit Java).
See http://mindprod.com/jgloss/installingjava.html for details.

----

Installing on a PC:

Download source and compiled jar files to run on your own machine as an application.
First install a recent Java JDK or JVM.
See http://mindprod.com/jgloss/installingjava.html.
To install, extract the zip download with WinZip
(or similar unzip utility) into any directory you please,
often J:\ --  ticking off the <span class="click">use folder names</span> option.

This program uses JNI which requires an awkward manual installation step.
Copy volser.32.dll and volser.64.dll to a directory on the path/library.path.
Type PATH at the command prompt to discover the path directories.

To run as an application, type:
java.exe %JAVA_OPTIONS -ea -jar J:\com\mindprod\volser\volser.jar {put any parms here}

adjusting as necessary to account for where the jar file is.

----

Installing on a MacIntosh:

Use Safari to download source and compiled jar files to run on your own machine as an application.
Safari will automatically unpack the zip into ~/Downloads (version 10.5)
[or on the Desktop (version 10.4 and earlier)].
First install a recent Java JDK or JVM.
See http://mindprod.com/jgloss/installingjava.html.
You may optionally move the download tree to a permanent home.
I don't have a MacIntosh, just a PC, so I can't test my Java programs for Mac compatibility.
In theory they should work without problems, but in practice that does not always happen.
If you have problems please, let me know, preferably with screenshots and complete verbatim error messages.

This program uses platform-specific JNI.
I do not yet have a Mac version of the C/C++ JNI code.
If you are technically savvy, you could create it yourself.

To run as an application, without parameters, just double click the jar file.

To run as an application with parameters, in bash shell type:
open Terminal.app
cd ~/Desktop
java.exe -ea -jar com/mindprod/volser/volser.jar {put any parms here}

adjusting as necessary to account for where the jar file is.

----

Rebuilding:

The zip already contains the necessary jar files, so unless you modify
the program, there is no need to recompile the source or rebuild the jar.
Configure.java basedir="E:/" in rebuild.xml to the drive where your files are.
Use ANT and rebuild.xml, not build.xml, to recompile and recreate the jar.

----

Use:

Gets the 4-byte 32-bit binary volume serial number of a Windows disk drive
assigned when it is formatted to provide an almost unique id.  Don't
confuse this with the volser(the string name, or the manufacturer's disk
serial number assigned to a hard drive at the factory.  Uses JNI and C++
native code.
Consists of  java and JNI you include in your own code.
You can test with
  C:
  CD \com.mindprod.volser
  java.exe -jar volser.jar
and ensuring nativevolser.dll is on the path, e.g. in the
current directory.  YOU MUST MANUALLY EXTRACT
 volser.32.dll
 volser.64.dll
AND PUT THEM ON THE PATH. See
http://mindprod.com/jgloss/path.html
To use getVolser, you need three pieces of code in your
class:
1. an import,
2. a static init to load the JNI library
3. a call to the getVolser native method
i.e.
  import com.mindprod.volser.Volser;
  ...
  static
        {
        // get DLL loaded from somewhere on java.library path.
        System.loadLibrary( "volser.32" );
        // if have troubles change this code to use
        // System.load( "E:\\com\\mindprod\\volser\\volser.32.dll" );
    /**
     * test harness
     *
     * @param args not used
     */
    public static void main( String[] args )
        {
        // Needs drive letter with colon and trailing backslash
        final int volser = Volser.getVolser( "C:\\" );
        System.out.println( "4-byte Volume serial number for drive C: is " + Integer.toHexString( volser ) );
        }
    }
To be more precise, here is how you must place the DLL. You
can use http://mindprod.com/products1.html#WASSUP, run as an
application to discover the java.library.path property.  The
nativevolser.dll must be manually placed in one of those
directories. I don't mean put the jar on the path. I mean
extract nativevolser.dll from the volser.jar and put it
separately on the library path.
If you use Java Web Start, then extracting the DLL from the
jar is not necessary, but you must insert the following:
   <resources os="Windows" arch="x86">
      <nativelib href="nativevolser.jar" />
   </resources>
into your JNLP file.
Volser does nothing  much by itself, other than a debugging
test harness to demonstrate getVolser method.
Why the purple cylinder icon?  It is supposed to represent a physical disk drive.
This program requires modules from the Microsoft C++ Express
12 run time library. Normally they should be automatically
statically included. However, if someone recompiled the JNI
C++ code without the /MT option, this code will not work
unless the vcredist_x86.exe Microsoft C++ Express 11 run time
library is preinstalled. You can download it from Microsoft
or CMP. see http://mindprod.com/jgloss/cpp.html
The symptom of this problem is an UnsatisfiedLinkError or a
side-by-side configuration error.
I could not get the 64-bit version to link.  If you know why, please let
me know.  I have not included volser.64.dll


----

Version History:

 1.0 2007-12-17 initial release

 1.1 2008-09-23 fix problem with Microsoft C++ runtime library

 1.2 2010-11-07 fix delete[] bug in C++ that could cause heap corruption.

 1.3 2012-12-11 add 64-bit support.

-30-