Vutrax PCB CAD     
OpenInformation
OpenSupport
OpenOpenLatest Changes
OpenOpenCurrent Log
OpenOpenPrevious Logs
OpenOpenOpenLog Index
OpenOpenOpenLog 12.0a
OpenOpenOpenLog 12.0b
OpenOpenOpenLog 12.0e
OpenOpenOpenLog 12.1a
OpenOpenOpenLog 12.1c
OpenOpenOpenLog 12.2c
OpenOpenOpenLog 12.3a
OpenOpenOpenLog 12.4a
OpenOpenOpenLog 12.5a
OpenOpenOpenLog 13.0a
OpenOpenOpenLog 13.1a
OpenOpenOpenLog 13.2a
OpenOpenOpenLog 13.3a
OpenOpenOpenLog 13.4a
OpenOpenSoftware Advice
OpenOpenUpdate Bulletins
OpenBroadband Download
OpenIndividual Downloads
OpenBookcase
OpenLinks
OpenMail & Contacts

Status of VUTRAX 12.0a Before Release of 12.0b (5 June 1998)

VUTRAX 12.0a

Note: To view the changes from Vutrax 12.0a to Vutrax 12.0b use your browser text search to look for sections including '12.0b' in the header.

  • Coordinate system resolution increased to 0.0001"/0.0025mm
    The changes have been applied in a manner that is forward compatible with existing Rule, NIB and similar files.
    (Customised PLOT control files will need modification)
  • Drawing board size increased to up to 200" (5 Metres).
  • Width is any value between 0 to 0.9999" in units of 0.0001" (24.978 mm in units of 0.0025mm). Each of the 9999 widths can be specified as Round or Butt capped.
  • Compact binary files are usually much smaller than for previous issues.
  • Picked points are preserved in the file.
  • Signal names, silk legends, etc. can all be up to 32 characters (16 when all overbarred).
  • VUTRAX 11 provided only limited support for 'long' file names in order to ensure interworking between 16 and 32 bit versions within the customer base. VUTRAX 12 supports file names up to 255 characters long with embedded spaces in the path.
    The final file name should be limited to 28 characters with no embedded spaces. Schematic analysis applies this restriction to avoid introducing invalid signal names.
  • The GROUNDPLANE settings are stored in the graphics file.
  • Dialogue box enhancements include adjusting the metric/ imperial display to suit the artwork, and adaptive Up/down (spin) controls.
  • Pad definition can include Thermal break and isolation pad specifications which can be used in preference to any general scheme specified. TOOLBOX 'POWERPLANE' supports their use.
  • Pad definitions can include a text description.
  • Special case for ROUND width one has been removed (unless the artwork is back-converted to VUTRAX-11).
  • Pin number styles have been extended to allow connector row 'Z' and larger PGA's
  • Comma separated list forms can be varied in format using the VTXCOMMA environment variable.
  • Network signal OPTIMISE adjusts multiple VIA handling according to the style of optimisation requested.
  • Memory management capabilities upped from 16MB to 256MB.
  • 16 bit only version discontinued.
    (Few users now use Windows 3.1, and 16 support inhibited developments. Further, 16 bit Beta testing was compromised by the lack of Windows 3.1 sites using VUTRAX intensively.)
  • Utility VTX12 11 Converts VUTRAX-12 graphics files to a form acceptable to VUTRAX-11. Some approximations are required. There are warnings for out-of-bounds coordinates, widths, and other potential problems.
    A 32 bit version is part of VUTRAX-12.
    A 16 bit version is freely available on the Web site.

Version:    DRAFT 38.00c (VUTRAX 12.0a)
Entry Date: 14 July 1997 - 25 March 1998
Problems:

  • GROUNDPLANE thermal ties wider than the fill width may cause violations. DESRULE detects the error normally.
    SAN 165 provides details and avoidance.
  • Isolated areas of a Groundplane will not be indicated or deleted if a ground signal surface mount pad or blind/buried via appears on another layer in a position where it would overlap the isolated area.
    SAN 167 provides details and a command file workaround.
  • GROUNDPLANE may place thermal ties too close to signals with certain combinations of tie width, clearance and resolution. Avoidance: Design check as usual, and remove any detected.
  • GROUNDPLANE isolated area removal just might leave a spurious join line. DESRULE will detect any such occurance.
    Use[Width ...] 0 (SEG WIDTH 0) to remove it.
  • The PAD dialogue erroneously allows setting of [Layers] for Assumed pad shapes. The effect is temporary, not being saved to file. DESRULE checks, and PLOT outputs, the original pad.
  • If you DRAFT a file, change the coordinate system, and [Exit] DRAFT doesn't save the change. Avoidance: Explicitly [Save].
  • After examining coincident points with the Esc key, the point selected by the left mouse button may not be what you expect.
    Avoidance: Use local menu [Reselect] (double right click).
  • Pad shape summary tables to file or printer are missing a line break where unused pads are skipped. [Save As] (F2) the file and insert them if the format needs to be fixed.
  • The PAD setting dialogue for 45 degree rectangular pads displays nonsense values for the metric equivalent.
    Workaround: Set up an axial rectangle, note the THOU values, change to 45 degree axial, insert these values, and save.
    Checking: The listing outputs show the intended value.
  • CHECK calls detect violations accurately, but when there is no violation the report of the maximum clearance that accompanies an explicit CHECK may be inaccurate if the value output is more than 5 THOU (0.0125mm) over the minimum gap.
    Workaround: Explicitly check for the maximum gap you care about. e.g. [Check ...] from (Route > Check clearance) or type command CHECK <bigger gap>.
  • The option to allow DRAFT to open Read-only files will let you save a changed version just once. SAN 168 describes the operating system problem, and workarounds.
  • OPTIMISE uses up memory at each use (not settings) until DRAFT is exited. If your system becomes slow after repeatedly optimising a large artwork, [Save], [Exit] and restart DRAFT.
  • Hatching (e.g. obsolete Groundplanes) or Dashing embedded within a signal may cause OPTIMISE to take so long that it effectively hangs. Restart DRAFT, and either [Erase Route], or alter the signal using [Clear Optimise Marker].
  • Defining a surface mount pad with [Drill on] as 'No Layers' is refused. Avoidance: SM pads (FIXED NODES) don't get drilled anyway - set the entry to 'All Layers'.
  • [Move Component] and [Flip Component] might remove existing VIAs used for powerplane connections. The sequence of points influences whether the fault occurs - for VUROUTE output it does not. SAN 179 provides workarounds and patch.
  • When DRAFT explicitly or automatically 'saves' an artwork it becomes confused about which is the current noted point.
    DRAFT may crash if auto-SAVE occurs with a command used while banding (e.g. POS, PAN), & you then continue that operation.
    To avoid side-effects after an explicit or automatic save:-
    Select a new command or [Reselect].
    If DRAFT become deranged, restart from the just saved file. (This many years old fault has only just been reported.)
  • PAD U (list unspecified pads) produces a silly list.
  • The point count wrapped at 32767.
Enhancements:
  • Any colour can be selected for items. Colour schemes can be saved and restored. Background colour can be selected. The computer palette system can be used or not as desired.
  • Clicking on the Layer/Colours list invokes the Layers and Colours selection and colour palette dialogue.
  • Clicking on the command line invokes a command setting and history dialogue. The command history has been extended to 32 items.
  • The PAD setting dialogue makes provision for copying an unchanged entry to another pad number. The assumed Goto/Copy to value is automatically one greater than the current pad.
  • The LISTSTRUCT dialogue offers [Flash All] when more than one structure has the selected name.
  • GROUNDPLANE stores it current settings in the graphics file.
  • GROUNDPLANE warns if thermal tie width exceeds outline/fill width.
  • OPTIMISE now sets the final point of the signal to a non-zero width to simplify modification.
    This also prevents problems with powerplane signals marked as networked when using OPTIMISE EDIT or OPTIMISE PLOT.
  • Relative Origins are support in a variety of ways.
  • DRAFT 'WIREGEN' accepts schematic file name up to 28 characters long. Embedded spaces, and a variety of exotic characters are rejected. The underscore characters is conventionally used to replace spaces. The long name is used to derive names for unassigned signals.
  • Schematic symbols can normally be constructed without regard to the data point or silk point order.
  • The Toolbar is now user configurable. The settings for the 4 primary modes are configured independently.
  • Menu commands, Toolbar commands, and Toolbar buttons graphics can all be user configured. SAN 177 provides details of the more complex varieties of such changes.
  • EXEC command files (.DEX) can generate custom dialogue boxes for choices, text input, or file browsing.
  • PICK SHUFFLE offers to update the CHECK clearance (if configured) to the clearance in use for track shuffling.
  • Creation of new file prompts for default settings and mode.
  • While assigning pins during library building, if you press the [Finish] button with a changed pin number or fixed signal name, you are warned that the pin will not be included unless you first select [Next >].
  • The command line forms TEXT/.../.../, SILK/.../.../ and DATA/.../.../ now match either letter case.
  • Auto-save on command count (WARNAFTER directive) is replaced by auto-save determined by elapsed time since the oldest unsaved change, and the user pausing (directive AUTOSAVE).
Changes:
  • In line with modern usage, the word LIB (Library Copy) is replaced by the word COPY, giving commands COPY ..., BOX COPY and PICK COPY. For those used to the old form, and with existing .DEX files, the work LIB is synonomous.
  • The form ENV LIB has been replaced with ENV STYLE to more reflect the effect on which part of the environment is copied. (ENV LIB is still accepted in your command files.)
  • Graphical Fonts now interpret any non-zero width of 1 THOU or less to be drawn at the default width. Previously only width of 1 THOU (the minimum non zero width) was treated this way.
  • Script font design is modified to keep it at usable scales. Existing fonts continue to work.
Clarification:
  • To use overbars with fonts from FONTKIT.FNT you need to specify a suitable non-escaping symbol for '' (Ascii 170).

Version:    DRAFT 38.01 (VUTRAX 12.0b)
Entry Date: 23 Apr 1998 - 28 May 1998
Problems:

  • [Move Component] on a non-axial device produces diagnostic "You have not selected a PCB Component". A workaround and patch fix is in SAN 187.
  • Building physical libraries from schematics using LIKEPAD names over 12 characters may grey out the [Next >] button. See SAN 186 for workaround and fix.
  • Drawings over 3000 sq. inches (2.24 sq. m) may fail on use of WIREGEN or signal OPTIMISE. See SAN 182 for avoidance and fix.
  • TRACE pads defined to use wide (over 25'5) lines were stored with the wrong width (See SAN 188 for details & workarounds).
  • Very long paths + filename combinations may cause graphical library builds to skip the final display and append phase.
    Workaround 1: Append MAKELIB!.LIB to the library yourself.
    Workaround 2: Set a long directory as the project directory.
Limitation:
  • User defined menu and Toolbar commands can not be induced to display a parameter dialogue. We are researching an extension (which has to control the selected Browse scheme).
Enhancement:
  • SIGNAL and LABEL commands provide warnings earlier, and more helpfully describe the problem.

Version:    VTX12 11 1.00a (VUTRAX-12)
Entry Date: 25 Mar 1998
Purpose:

  • Converts VUTRAX-12 graphics file to form usable by VUTRAX-11.
  • The 32 bit Windows version is bundled with VUTRAX-12.
  • The 16 bit Windows version is available on request or from the Internet site for use with Vutrax-11.

Version:    VTX12 11 1.01a (VUTRAX 12.0b)
Entry Date: 25 Mar 1998
Enhancements:

  • More help on what to do when things go wrong, tailored for 32 bit versions (with VUTRAX-12) and 16 bit (with only 11). The actual functionality of the program is unchanged.
Documentation:
  • SAN 184 provides the detail for handling conversion problems.

Version:    TOOLBOX 11.00c (VUTRAX 12.0a)
Entry Date: 22 Dec 1997 - 25 Mar 1998
Problem:

  • Some error message fail to appear when TOOLBOX is used from the system menu. e.g. POWERPLANE notifying missing pads.
    Avoidance: Select [Show Prompts] from (File > Setup) and run the function again. Once your problem is resolved revert to [Display Banners] (default) or [Hide Banners].
  • In TOP-DOWN-MODIFY, hatching (e.g. obsolete Groundplanes) or Dashing embedded within a signal may cause OPTIMISE to take so long that it effectively hangs. DRAFT the (usually 'old') file, [Erase Route] on the signal, and modify again.
Enhancements:
  • POWERPLANE can be instructed to use isolation and Thermal break pads specified in the pad shape table.
  • VTXTODXF can be told to generate DXF output for just one layer, or a selected set of layers, and choose layer/absence or each pad catagory.
  • DXFTOVTX allows you to vary the import scale without recourse to editing the defaults definitions DXF.VTX.
  • DXFTOVTX numeric limit on FLAGS and similar has been extended to 4095.
  • Existing and mismatching .MRF and .URF files now offer the option to continue when controlled from the menu system.
  • The TOOLBOX 'ANNOTATE' default settings file has changed its interpretation of dimensional fields.
    Warning: impacts personalised files and possibly libraries.
  • GLUESPOT has a newly introduced comma separated list output.
  • TESTPOINT comma list output has been updated.
  • New tool VUTRAX TO COMMA generates the complete graphics as a comma separated list. Options include complete analysis of pad shapes, fonts and rounds to draw lines.
    See also decoder COMA2VTX

Version:    TOOLBOX 11.01a (VUTRAX 12.0b)
Entry Date: 24 Apr 1998 - 27 May 1998
Problems:

  • Drawings over 3000 sq. inches (2.24 sq. m) may fail on use of GENPINLIST, GENDEVLIST, BACKMODIFY and STATISTICS.
    See SAN 182 for avoidance and fix.
  • If POWERPLANE reports a pad substitution, the minumum radius listed in units of 0.0001" rather than a coordinate value.
  • If STATISTICS reports multiple drill sizes at a coordinate, the sizes are in units of 0.0001" rather than a coordinate value.
  • TRACE pads defined to use wide (over 25'5) lines were stored with the wrong width (See SAN 188 for details & workarounds).

Version:    COMA2VTX 1.00a (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
Purpose:

  • Reads files written by VUTRAX TO COMMA and generates a standard VUTRAX graphics file.
    An option imports constructed pads, script and rounds as the drawn items from the list, rather than natural forms.

Version:    AUTOPLACE 8.00a (VUTRAX 12.0a)
Entry Date: 30 July 1997 - 25 Mar 1998
Problem:

  • Hatching (e.g. obsolete Groundplanes) or Dashing embedded within a signal may cause OPTIMISE to take so long that it effectively hangs. Use DRAFT to [Erase Route] first.
Temporary Restriction:
  • Grid and similar sizes had to be specified in THOU.

Version:    AUTOPLACE 8.01a (VUTRAX 12.0b)
Entry Date: 27 May 1998
Problem:

  • TRACE pads defined to use wide (over 25'5) lines were stored with the wrong width (See SAN 188 for details & workarounds).

Version:    PLOT 15.00b (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
Enhancements:

  • Windows GDI printer support the Negative image (pseudo colour (letter) 'I' ).
  • Various options converted from integer coordinate units to Imperial or metric units.
  • Support for Gerber RS274X output, including automatic aperture building. Includes new control file GERB274X.HXY and utility GERB274X.
Changes
  • NIB files description and pen selection fields can be up to 32 characters long.
  • All control files have been updated. Users wishing to update personal files should obtain SAN 176.

Version:    PLOT 15.01a (VUTRAX 12.0b)
Entry Date: 30 Apr 1998 - 27 May 1998
Problem:

  • Rings used for drawn drill chart centres appear as dots.
    Workarounds and patch in SAN 185.
  • TRACE pads defined to use wide (over 25'5) lines were plotted with the wrong width (See SAN 188 for details & workarounds).

Version:    GERB274X 1.00b (VUTRAX 12.0a).
Entry Date: 25 Mar 1998
Purpose:

  • Tool to build artwork specific Gerber RS274X aperture definitions, the associated .HNB and .RNB files, and visible aperture table. Normally used automatically by PLOT, but can be used explicitly as a tool to prepare your own lists.

Version:    GBTOVTX 10.00a (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
Enhancements:

  • The .RNB file width can be in Metric (as well as part thou)
  • In n.4 format full resolution can be viewed.
  • In Metric format rounding error is negligable.
Changes:
  • The scale factors have changed. See the program help.

Version:    EMTOVTX 4.00a (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
Enhancements:

  • The .RNB file width can be in Metric (as well as part thou)
  • The full Imperial resolution can be viewed.
  • In Metric format rounding error is negligable.
Changes:
  • The scale factors have changed. See the program help.

Version:    DESRULE 34.00a (VUTRAX 12.0a)
Entry Date: 29 Jul 1997 - 25 Mar 1998
Clarification:

  • Reports of items too close may erroneously report that they touch. Distinction of violations and 'OK' remains accurate.

Version:    DESRULE 34.01a (VUTRAX 12.0b)
Entry Date: 24 Apr 1998 - 27 May 1998
Problem:

  • Drawings over 3000 sq. inches (2.24 sq. m) may fail.
  • See SAN 182 for avoidance and fix.
  • TRACE pads defined to use wide (over 25'5) lines were stored with the wrong width (See SAN 188 for details & workarounds).
Clarification
  • SAN 183 describes analysis of 'Isolated Sections', and why VUTRAX-11 and VUTRAX-12 may produce different reports.

Version:    EMCRITIC 2.00a (VUTRAX 12.0a)
Entry Date: 28 Nov 1997 - 25 Mar 1998
Problem:

  • [Windows 3.1, 3.11 and Win32s only] Complex outlines used in POWEROUTLINE split powerplane checking may malfunction or be refused. SAN 172 provides explanation and workarounds.

Version:    EMCRITIC 2.01a (VUTRAX 12.0b)
Entry Date: 29 Apr 1998 - 27 May 1998
Problem:

  • Multiple pads found while Split Powerplane checking were needlessly reported even when they were the same size.
  • TRACE pads defined to use wide (over 25'5) lines were stored with the wrong width (See SAN 188 for details & workarounds).

Version:    AUTOTRAK 23.00b (VUTRAX 12.0a)
Entry Date: 11 Jan 1998 - 31 Mar 1998
Problem:

  • Hatching (e.g. obsolete Groundplanes) or Dashing embedded within a signal may cause OPTIMISE to take so long that it effectively hangs. Start DRAFT, and either [Erase Route], or alter the signal using [Clear Optimise Marker].

Version:    AUTOTRAK 23.01a (VUTRAX 12.0b)
Entry Date: 27 May 1998
Problem:

  • TRACE pads defined to use wide (over 25'5) lines were stored with the wrong width (See SAN 188 for details & workarounds).

Version:    VUROUTE 8.00b (VUTRAX 12.0a)
Entry Date: 11 Jan 1998 - 31 Mar 1998
Problem:

  • Hatching (e.g. obsolete Groundplanes) or Dashing embedded within a signal may cause OPTIMISE to take so long that it effectively hangs. Start DRAFT, and either [Erase Route], or alter the signal using [Clear Optimise Marker].

Version:    VUROUTE 8.01a (VUTRAX 12.0b)
Entry Date: 27 May 1998
Problem:

  • TRACE pads defined to use wide (over 25'5) lines were stored with the wrong width (See SAN 188 for details & workarounds).

Version:    WIRE 67.00b (VUTRAX 12.0a)
Entry Date: 5 Nov 1997 - 25 Mar 1997
Problem:

  • Some forms of silk screen name for devices using 'Named Groups' could confuse WIRE. The symptom will usually be failure to use existing placements, and related complaints.
    SAN 169 provides all the details and avoidance.
  • WIRE libraries that include cross or cyclicly referenced libraries (using USE, LIKE or LIKEPAD) which are then built into a Physical Library index (FOOTLIB.LIX) may cause WIRE to crash trying to resolve the sequencing.
    Workaround 1: Avoid indexing, name the libraries explicitly, and normal WIRE syntax checks will find the problem.
    Workaround 2: Select [Build List] from (Tools > Library > Rats Nest Index), go to the end of the list (F9), and print the section from the row of hyphens to the end. The indented libraries are referenced by the preceding left justified library name. Check the references until you find the cross or circular reference. Re-index before trying your fix.
Enhancements:
  • Signal aliasing is introduced, primarily to mix and match different names for power signals in different libraries.
  • The GLOBAL directive can be multi-line.
  • The comma separated form engineering file (.EXG) is extensively upgraded:-
  • Allows for full length names.
  • The comma separated lists outputs coordinate information as controlled by VTXCOMMA.
  • Pad type, size and offset is added in new field.
Compatibility:
  • The columnised format engineering file (.ENG) is retained with the VUTRAX-11 name length limits and coordinate formats. It is expected to work correctly with existing third party utilities. AVOID THIS FORMAT for new or updated interfaces.
  • The PADSHAPE directive accepts (or will ignore the absence of) two extra parameters for powerplane pads.

Version:    WIRE 67.01a (VUTRAX 12.0b)
Entry Date: 8 May 1998
Problem:

  • Wire-wrap output formats were usable, but not as intended:-
  • Lengths were in 0.001" units rather than 0.1".
  • Columns were misaligned, and inconveniently long.
  • Check-list absent unless 'TRAY' deleted from placements.
    Manual wire-wrap is seldom used. 12.0b will provide a fix.
    If you are stuck ask the office for an update of WIRE.

Version:    PARTGEN 8.00a (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
Enhancements:

  • Reformatted for larger field length.
  • Normally output width is reduced as far as possible.
    Option /W forces full width with consistant columnisation.

Version:    CONNECT 27.00a (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
General:

  • Name lengths extended for VUTRAX-12.

Version:    CONNECT 27.01a (VUTRAX 12.0b)
Entry Date: 30 Apr 1998
Problem:

  • Input line length was limited to 80 characters.
    Importing new placements caused an error message loop.
    Stop CONNECT by using Ctrl+Alt+Del and selecting [End Task].
    Avoidance: Before importing, remove multiple spaces from the placements using a SEE editor 'Find' (Ctrl+F) sequence like
        Find: <space><space>
        Erase: 1 (erase 1 of the spaces)
        Dirctv: 0 (Keep going until no more to do)

Version:    SEE 10.00b (VUTRAX 12.0a)
Entry Date: 18 Aug 1997 - 25 Mar 1998
Problem:

  • Using the mouse to select an area which overflows the right edge of the window may induce very fast scrolling.
    Workaround 1: Reposition and mark right to left.
    Workaround 2: Use [Mark End Section] (Esc), move to the other end (don't expect highlight markers), and [Copy] or [Cut].
Enhancements:
  • [Join Line] (Ctrl+N) strips all but one space at the join so that joining indented lines is more natural.
  • File dialogue selection is allowed to select a read-only file in more appropriate situations.
  • Files up to 8MB can be edited without overflowing to disk.

Version:    SEE 10.01a (VUTRAX 12.0b)
Entry Date: 28 May 1998
Problem:

  • Very long file paths could cause SEE to malfunction, particularly if [About] from (Help) (Typed Ctrl+L) is used. [DOS version not faulty].

Version:    PRINTFRM 41.00a (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
Enhancements:

  • Support for multiple copy output, including quantity, optional collation, and alternating sides for double-sided.

Version:    MENUVTX 10.00b (VUTRAX 12.0a)
Entry Date: 25 Mar 1998
Enhancements:

  • Support for separate 'current directory' and 'project name' concepts.
  • Use of special temporary directory, and improved cleanup.
  • Installation update from old menus, and conversion.
  • Tip of the Day Introduced

Version:    MENUVTX 10.01 (VUTRAX 12.0b)
Entry Date: 23 Apr 1998 - 1 May 1998
Problem:

  • If you select a project directory with embedded spaces, and later re-select that radio button, the quoted name is displayed as subdirectory of the current path.
    Avoidance: Click the edit box at the left of the first quote, and backspace (delete) all characters to the left.
  • Possible crash when selecting a directory name over 13 characters long on a Novell network drive. No known problems with other types of network.
    Workaround: Don't select from the list of directory names - type the name into the edit box at the top, and then [OK].

Version:    SQUASH 10.00a (VUTRAX 12.0a)
Entry Date: 22 Sep 1997 - 25 Mar 1998
Problems:

  • Attempting to compress and simultaneously pack an already compressed file creates a double entry in the packed file that confuses unpacking and de-compress.
    Workaround: Unpack using copy (-c) and de-compress (-d) separately.
Enhancements:
  • Handles 'long' files names (including embedded spaces) in normal and packed files.
  • Option -h allows archives of Hidden and System files.
  • Option -comp allows 'unpack & compare' to verify archives.
  • The original time stamp, and attributes Hidden, System and Read-only are now normally applied to the new file.
    Option -t suppresses this feature at write or read.
  • -b (Batch) option extended with -by to continue after encryption decode mismatch (the file can not be decoded).
  • -x<string> option introduced to enclude files from processing.

Version:    VTXSETUP 10.01a (VUTRAX 12.0b)
Entry Date: 1 May 1998
Problem:

  • Possible crash when selecting a directory name over 13 characters long on a Novell network drive. No known problems with other types of network.
    Workaround: Don't select from the list of directory names - type the name into the edit box at the top, and then [OK].

Version:    VTXSHELL 4.00c (VUTRAX 12.0a)
Entry Date: 25 July 1997 - 25 Mar 1998
Problem:

  • Windows 95 only: 2 concurrent 16 bit VTXSHELL's may both wait for both programs they are running to exit before either re-activates. Avoidance: Use the intended 32 bit version.
  • 32 bit only: If you XCOPY, REN etc. to a wildcard destination with source name having consecutive dots, one the dots may not be included in destination filename. The only likely effect is on XCOPY of Windows files of shortcuts such as "Email Message..." which has name "Email Message....lnk".
  • 32 bit only: XCOPY source name specifier '\' doesn't work, and 'X:\' looks in the current directory of X: (often the root anyway). All other forms (e.g. which include directory or network names) work fine.
    Workaround: Add *.* to the name e.g. X:\*.*
  • When more than one VTXSHELL is running, termination codes from simultaneously running programs may be passed to the wrong control shell. The only likely effect on VUTRAX is that if you run Vutrax menu systems concurrently then automatic display of results may occassionally be skipped or take place when a job has been aborted.
  • Each time 32 bit VTXSHELL starts a program, it wastes a few hundred bytes of memory, recovered on VTXSHELL termination. (Not significant in normal use.)
Enhancements:
  • 'DIR' command support attribute '*' - all attributes.
  • New filter command TABLE can take a comma separated list (or other separator) and generates tabulated output from it.
  • Command CALLEXEC is used in place of CALL when the command is unknown at the time of writing.
  • Command OPEN finds the application associated with a supplied file, and attempts to display the document with it.
  • You can determine the window state for programs you start (provided that the application takes any notice).
  • The command history list and command line can be displayed in a dialogue for selection, cut, paste, and file browsing.
  • Command (.BAT) files can generate custom dialogue boxes for choices, text input, or file browsing. They can also change the window title and alter their window state.
  • New command SLEEP <seconds>.
  • The current time can be captured in virtually any format.
    Using this with SLEEP, job schedulers can be written.
  • Drive sizes in bytes listed by DIR supports drives up to 999,999GB (previously limited to 2 GB). The fields used by DIR are longer and may effect sorting.
  • New environment variable EXECTICKCOUNT timestamps the time an application is started.
  • HINT command dialog and font adjusts to the screen size.

Version:    VTXSHELL 4.01a (VUTRAX 12.0b)
Entry Date: 19 May 1998
Problem:

  • Programs taking more than a few seconds to create a top level window (visible or not) expired any wait expected.
    Symptoms: Misbehaviour of the menu system, and premature attempts to display results.
    Avoidance: Select [Display Banners] in (File > Setup).

Version:     VTX2000 1.01a
Date:        27 Mar 1998
Enhancements:

  • Frozen or very slow clocks detected.
  • Windows 98 formally supported.
  • Web site reference updated, + other cosmetic changes.
Note:
  • Can directly replace 1.00c without formal installation.