NasmEdit Version 1.0 for Java 


 Getting Started

These instructions are the only form of help included with this release of NasmEdit. It is important that you read them as they contain information that will help you to avoid problems with NasmEdit. These instructions have been tested only on the Win32 platform. Users of other systems may need to consult their operating system and Java documentation.

  1. Installation
  2. These instructions assume that you have already downloaded and extracted the NasmEdit archive onto your system. You should have the following directory structure:

    NasmEdit The root directory for NasmEdit (the name of this directory is up to you). This directory contains the main NasmEdit class file and a Windows icon.
    com Contains the class files for NasmEdit.
    docs Contains documentation.
    examples Contains three sample NASM programs.
    kiwi Contains class files for the Kiwi Toolkit.
    nasm The recommended location for the NASM executable.
    resources Contains images and configuration files.

  3. Running NasmEdit
  4. This section assumes that you have extracted NasmEdit into a directory called ‘NasmEdit’ and that the ‘java’ executable is in your search path.

    To run NasmEdit, change to the ‘NasmEdit’ directory and type ‘java NasmEdit’. Note that this will only work if you change to the ‘NasmEdit’ directory before running. To run NasmEdit from any location I suggest using a batch file and include a classpath setting, for example:

    java –cp c:\NasmEdit NasmEdit

    Where ‘c:\NasmEdit’ is the directory where NasmEdit has been installed.

  5. Setting options
  6. On the ‘Options’ menu, select ‘Directory…’. This should display the Directory Options dialog.

    In the ‘NASM path’ input box you should type the full path name (but not the filename) of the NASM executable (e.g. ‘c:\NasmEdit\nasm’).

    By default, NasmEdit expects the executable to be called ‘NASMW.EXE’ however this can be changed by manually editing the NasmEdit properties file (in the ‘resources\properties’ subdirectory).

    If you are using Win32 it is important that you use a version of NASM compiled for Win32 console mode. Java behaves unpredictably if a 16 bit executable is used.

    If you wish to run DOS .COM files on the Win32 platform, you must make sure that the ‘RunWrap.bat’ file (by default this is in the ‘nasm’ subdirectory) is in the NASM path.

    Hopefully you should now be able to use NasmEdit to edit, assemble and run code.

  7. Feedback
  8. As NasmEdit has been produced for my degree project, I would be grateful for comments that are constructive enough to be included in my report. If you have questions or comments then email me.

    I am particularly interested in the following:

    I will be releasing the source code to NasmEdit towards the end of May, and would like to hear from anyone who would like to help with future versions.

  9. Test systems
  10. NasmEdit has been tested on the following systems.

    Test system 1 - Main development system

    Processor Intel Pentium III @ 500MHz
    Memory 128Mb
    Graphics Diamond Viper V550 with DirectX 6.1
    OS Windows 98 with Symantec JIT version 3.10.100
    NASM Version 0.98 pre-release J3

    Test system 2

    Processor Cyrix P166+ @ 133MHz
    Memory 64Mb
    Graphics Hercules Terminator 64 with DirectX 6.0
    OS Windows 95 OSR2.1 with Symantec JIT version 3.10.100
    NASM Version 0.98 pre-release J3

    Test system 3

    Processor Cyrix MediaGX @ 200MHz (Compaq Presario laptop)
    Memory 32Mb
    Graphics NVidia Riva 128ZX
    OS Windows 95 OSR2.1 with Symantec JIT version 3.10.078
    NASM Version 0.98 pre-release J3

  11. Licenses
  12. Please read the license files in the ‘docs’ directory. This directory also contains OROSyntax.html that describes the regular expression syntax used by NasmEdit.

  13. Credits
  14. Most of the NasmEdit icons are from an icon collection by Dean S. Jones, available from http://www.gallant.com/icons.htm

    The regular expression facilities are provided by OROMatcher™ from Daniel F. Savarese, available from http://www.oroinc.com/

    NasmEdit also uses the Kiwi Toolkit by Mark Lindner of PING Software Group, available from http://www.nerosworld.com/ping/kiwi/index.html

    Java is trademark of Sun Microsystems, Inc. Corporation. All other product names mentioned are the trademarks of their respective owners.