VUTRAX 12.1b (Issued 22 June 1999)
Entry Date:   22 - 24 June 1999
Known Problems (also in 12.1a):

• [Windows NT & Windows 2000 Only] Various file selections remove one \ (backslash) character when \\ (double backslash) is used to access networked files or devices (e.g. \\remote\penplotter).
  Workaround 1: Use local mappings - e.g. network drive letter.
  Workaround 2: In the 'Filename' group box select [Raw] from (File > Setup > Stored). Ensure that filenames entered with no path will only be used from current directory.
  
• A final '.' in a filename may prevent network addresses working. If one appears it can usually be suppressed by typing a '.' for the name - an explicit 'no extension'.
  
• Configuration file OPTIONS setting 8 works in reverse - value 0 locks for reading only. In most configurations this works fine - adjust if necessary.

VUTRAX 12.1c (Issued 4 Sep 1999)
Enhancements:

• Optional suppression of Recent Files [Delete] (Key: RcntDel) in DRAFT, MENU and SEE.
  
• The Lavenir Viewmate provided on the CD issue is now 6.0 (although the Automatic startup initially says 5.2).
  

• Pad dimensions and hole sizes may not exceed 65532 Thou (about 2 metres!). Sizes above 819'1 (20.47mm) should be avoided if TOOLBOX 'STATISTICS' is used.

Version:    DRAFT 38.06g (VUTRAX 12.1c)
Entry Date: 4 July 1999 - 2 Sep 1999
Problems Fixed:

• Any whole structure PICK setting also locates any deselected structures with picked points & picks the whole structure.
  Workaround 1: UNDO, & use a series of Point or Segment Picks.
  Workaround 2: Do any whole structure PICK settings first. Most point pick functions (e.g. PICK SHUFFLE) only need Point Pick.
  
• AUTO PAN sensitivity is patchable (<n> 'AutoPanM'), most unexpected 'Hint' windows when auto-panning removed, & fixed not reliably auto-panning after FIND, GOTO, and UP moving upwards.
  
• Some PICK commands (e.g. PICK SIZE, PICK LAYER) processed points in a picked structure even if the point was not picked.
  
• Hierarchical links from the menu system do not work in View-only mode (actually fixed in DRAFT.MNU 38.05b).
  Workaround: Use typed command DRAFT > instead.
  
• [Dimension Reset] from (Option > Dimension & Turn > Set Parameters ...) (DIM RESET) sets the dimension line metrics to a tenth of the intended values. (Also in 12.0)
  Workaround: Type command DIM RESET G50 H100 F300
  

• Erase Route (E#) might flip the side of a Surface Mount pad, particularly if the other end of the connection is a PTH or is on the opposite side.
  Workaround: Set the pad's layer back to the proper side.
  
• When defining Pad shapes, changes made to a pad name are discarded if you then select to change one of the layer settings. The loss is visible after the layers are set.
  Avoidance: Set the Name as the last field.
  
• Some SEG commands with 2 or more explicit layers specified (e.g. typed commands SEG SHIFT ..., SEG MOD ..., not offered by the menu system) could apply layer changes improperly.
  Workaround: UNDO, use SEG to fall to the first point of the segment, and do the operation again (press key F3 3 times).
  
• Some SEG commands with 2 or more explicit layers specified (e.g. typed commands SEG SHIFT ..., SEG MOD ..., not offered by the menu system) could apply layer changes improperly.
  Workaround: UNDO, use SEG to fall to the first point of the segment, and do the operation again (press key F3 3 times).
  
• When centring the cursor using GOTO (Home Key) it falls onto a grid of a maximum of 10 Thou (instead of 100 Thou).
  

• Move Component can use a components Gluespot as the selected reference point.
  
• New command BOX PICKALL ... picks the whole of any structure that has any of it's points inside the box. Used for applying 'whole structure only' operations (like PICK DELETE or PICK TRANSFER) to every structure that has any points in the selected area.

Version:    DRAFT 38.10b (*** On Beta Trial for VUTRAX 12.2)
Entry Date: 12 Sep 1999 - 26 Mar 2000
Problems:

• The settings of [Standard Paths] or [Other paths] in (File > Setup) ignores spaces embedded in folder names. Generally the paths find nothing if your Vutrax install folder includes spaces (which by default it does NOT). The project and current directory are searched reliably regardless.
  Workaround: If the file you want is not shown after selecting [All names] select [Browse] and navigate to.
  
• Use of the [Free] button in the Script setting dialogue never on its own marks the entry as 'not default'. On a drawing originally defaulted to [Diagram] style (orientation NUT) with no other Script changes, the change is not saved and on the next load reverts to 'NUT'. Individual settings, and the [Diagram] button, are saved as intended.
  Workaround: Force the settings out of default by clicking [Diagram] and then [Free]. This removes the [Dflt] indicator and all the script entries are saved.
  
• Use of OPTIMISE EDIT on Specctra Router output may produce excessive overlayed tracks. The result is valid, but makes applying some manual changes clumsy.
  Workaround: Don't 'optimise' Specctra output, or OPTIMISE PLOT.
  
• If you DRAFT a graphics file with extension .DGM which includes no artwork elements then the Script orientations are set to 'NUT' regardless of orientations defined in the file.
  Avoidance: If you want define a starting file use some other file extension and select mode appropriately. Alternatively include a useful outline or zero sized node in the graphics area so that drawing is interpreted as 'already started'.
  
• If you edit a milliohm value using the VALUE/old/new style, the replacement may fail if the edit refers to the display value (e.g. 4m7) rather than the device name (e.g. R0047). (These styles are adopted because case insensitive device names do not differentiate 'M' for Mega from 'm' for milli).
  Workaround: Apply the edit in the appropriate form, or more easily enter the whole new value in '4m7' style.
  
• In file FONTKIT.FNT (Vutrax Graphical Fonts) the font OUTAVALONBLD provides no '0' (zero) character.
  Reason: Two '0' data points exist, the first being empty.
  Fix: Terminate any tasks and then [Enable Changes] from (File > Setup > Configuration). Draft \VUTRAX\FONTKIT.FNT, go to coordinates 11741 18050 and press 'Esc'. Click the right mouse button, choose [Edit Data ...] and remove the '0' from the dialog. Click [OK], [Save] the file. Finally [Re-Initialise] from (File > Setup > Configuration).
  
• [List Pads Used] from (Options > Pads and Pad & Tables > List Pads) (PAD USED) omits any entries for Unspecified shapes.
  DESRULE and PLOT fault such pads later in the design cycle.
  
• [Export ...] from (Text > Export) (SCREED OUT) included an unintended indent, typically of 4 spaces.
  Workaround: [Open] from (Text > Recent Files) to remove the spaces explicitly or [Find/Replace] from (Search) (Ctrl+F).
  
• SHOW Z## (Hide Gluespot) and similar sequences made the gluespots white instead.
  Workaround: Change to recessive colour, e.g. SHOW B##
  
• [New] from (File), & then selecting Drawing Mode 'Schematic', selected the limited Script Text orientations, but left the entries marked as [Default], so that they were not saved in the file. Next time the file was loaded text could be mirrored and/or in inappropriate orientations.
  Workaround: Before saving, or after re-loaded the drawing, select [Text Table] from (Text), Click [Diagram] & [OK].
  
• If you run [Analyse ...] (WIREGEN) with background libraries loaded, the background library is scanned for names that appear to be signal name legends for invented names (which always containing a '#' symbol) and may produce a spurious report.
  Workaround 1: Ignore obviously spurious warnings.
  Workaround 2: Type command WIREGEN- to remove the background library and run the analysis again.
  

• PICK operations SHIFT, WIDTH, SIZE, LAYER, & ERASE followed the same rules regarding protected structures as structures partially in a box. The new style removes such limits when in MAKELIB mode, and its temporary override PRIV prefix.
  
• On-line design checking showed only the first 25 violations. On partially routed items this might stop before highlighting the most obvious violation. Raised to 100 for this issue.
  

• After using most Graphics Processing Utilities, the display of all layers is enabled in order to avoid the added layers such as routing or rats layers being invisible. However, layers and pads set to the Zilch colour still do not appear.
  Workaround: If confused use [Show All Layer] from (View), or type commands SHOW ALL or SHOW D to obtain defaults.
  Change: Vutrax 12.2 utilities will force Zilch back to the original colour.
  
• The following important documentation got removed from the on-line manual ...
  Track Widths, and Pad shape definition sizes, centre offsets, and hole sizes switch between THOU and METRIC coordinates by treating the coordinate increments (0.0001" and 0.0025mm) as equivalent. At the small sizes involved, the errors (1.6%) are usually negligible, while the scheme retains 'sensible' values that will appear in photoplot aperture selections and have available drills of the nominated size. The equivalents are shown in the Pad setting dialogue and pad shape listings, with current coordinate system first.
  PLOT is specially aware of THOU/METRIC conversion problems - see the section PHOTO-PLOT APERTURES IN METRIC ARTWORKS.

Version:    LIB12 11 1.00c (VUTRAX-12.1c with 16 bit version available for download)
Entry Date: 20 Aug 1999
Purpose:

• Convert Vutrax 12.0 .LIB files (and other Text files that include coordinate fields) to VUTRAX 11 format by:-
      Removing any pad titles.
      Removing any pad references to explicit powerplane pads.
      Rounding any fractional THOU coordinates to whole THOU.

Version:    TOOLBOX 11.05d (*** On Beta Trial for VUTRAX 12.2)
Entry Date: 9 Sep 1999 - 13 Apr 2000
Problem Fixed:

• STATISTICS analysis of hole & drill sizes above 819'1 thou (20.47mm) will be grouped into an entry listing for this size (which far exceeds normal PCB drilled hole sizes).
  
• DXF files were expected always to start with
  0
  SECTION
  If the first line started with anything else the diagnostic message 'No a DXF File' was produced. Workaround 1: Remove initial comment (999) or other material. Workaround 2: Add to the start of the file the 2 lines
  0
  X
  
• POWERPLANE rings with no specified drill size assumed a drill of 3 Thou rather than the documented 30 Thou. Avoidance: Specify drill sizes in the pad table.
  
• GLUESPOT generated 'GLUE 0' entries for un-selected side/pad type combinations were placed at coordinate 0, 0 rather than at the device pin 1 position. Photoplotting and actual Gluespot output is unaffected. If coordinate 0, 0 is outside your drawing, ZOOM FULL will not work properly.
  Workaround 1: Move the GLUE points at 0 0 to their proper positions (banding shows which device they come from).
  Workaround 2: Type command PRIV S A (Privileged SHIFT ALL) Select any Glue point at 0 0 and move it (with the rest) to some arbitrary position within the drawing.
  

• The search for powerplane rings given the required clearance assumes that the rings in the pad table are compatible with the clearance specified. If the best fit outer diameter has an inside diameter smaller than the drill size, it will be selected anyway. In most instances this is of no consequence.
  
• POWERPLANE pad specifications for Vutrax 12.1 were taken from the last referenced pad of a pad stack, regardless of layers.
  To simplify determination of the ring chosen, and to provide for control of rings on a per-plane basis (e.g. different rings on a high voltage plane) Vutrax 12.2a changes the pad chosen to determine the ring specifications to be the first shape that appears on the powerplane layer. If no pads appear on the powerplane layer, the primary shape is used.
  If you require explicit powerplane rings you must specify them to appear with the pad, either primary or alternate, that you are using for your powerplanes layers, otherwise they will be invented.
  The simplest way to use this scheme with multiple pad stacks is to define the rings in the primary pad shape, and include the powerplane layers in the pad's 'Appears on Layers' entry.
  For the most usual case where a single shape is defined for all layers, the design change has no effect.

Version:    PLOT 15.06b (*** On Beta Trial for VUTRAX 12.2)
Entry Date: 3 Sep 1999 - 24 Mar 2000
Problem:

• A zero value for 'Round Width' caused Pen & Photoplotting to report an incomplete PLOT listing 'Width 0 ... Type R'. The Plot is correct.
  Avoidance: To remove the reports convert each ineffective ROUND point to an angle, or assign it a useful width.
  

• Automatic 274X Aperture photoplots didn't include any aperture for a pad 999. Details & fix at GERB274X 1.02a.
  

• Plot control files HP *.BXY implement data compression. For old printers this does not work, and utility HPCOMPRE is provided to select less or no compression. The Trouble shooting section (CNFG0170.HTM) identifies this correctly, but the main description in PLOT (PLOT0480.HTM) names the command as HPCOMPRES - simply omit the S.

Version:    GERB274X 1.04a (*** On Beta Trial for VUTRAX 12.2)
Entry Date: 12 Sep 1999
Inefficiency:

• Automatic allocation (used by PLOT for Automatic 274X Apperture photoplots) didn't build an apperture for a pad 999. PLOT 'constructs' the shape each time it appears. Normally such high numbered pads are used for 'Trace' shapes which are not allocated apertures anyway.
  Fix: Implement SAN 197 to patch ...\WIN32\GERB274X.EXE using
  E7 3 0 0 7C ;
  ? ? ? ? 7E

Version:    GBTOVTX 10.02a (VUTRAX 12.1a)
Entry Date: 5 Apr 2000
Problem:

• When analysing a RS274-X file with the first item being a macro definition, GBTOVTX may get complain of a 'Spurious Character' or 'Block Terminator Expected'.
  Workaround: Add an initial (empty comment) line 'G04*'.

Version:    WIRE 67.06a (VUTRAX 12.1c)
Entry Date: 20 Aug 1999
Change:

• If a device is replaced by one apparently not just a change of 'value', existing Gluespots are ignored, and any new Gluespots derived from the new library definition.

Version:    WIRE 67.07a (*** On Beta Trial for Vutrax 12.2a)
Entry Date: 18 Dec 1999 - 16 Jan 2000
Problems:

• Use of options [Value legends] (+V) and/or [Device Legends] (+L) with automatic positioning then the Silk and Optional are only slightly offset - you may not even realise that both legends are present. The same options produced neither legend for device names ending in a '#'.
  Fix: Request Development issue WIRE 67.06a Dev C.

Version:    SEE 10.03a (VUTRAX 12.1c)
Entry Date: 7 Aug 1999
Enhancement:

• (32 bit Windows only) The @<command file> parameter accepts spaces after the '@' to provide more convenient handling of quoted filenames. (Previous command formats still work.)

Version:    SEE 11.00b (*** On Beta Trial for VUTRAX 12.2)
Entry Date: 18 Dec 1999 - 5 Apr 2000
Problem:

• Saving a command sequence to a new explicit file (other than TEMP.ASC) produced a spurious report that the file existed and would be overwritten. Reply [Yes] to proceed normally.
  
• If you select Windows option [Show Windows Content While Dragging] in Windows 98 or 2000, the SEE window may not update until you type the next character. The file content is not effected.
  
• [Copy Section], [Print] (Ctrl+W, P), and then [Cancel] may sometimes cause SEE to stall. Close SEE using the task manager - unsaved changes are lost.
  There are no known problems with the more usual [Print] from (File) or [Copy Section] [Dflt Print] (Ctrl+W, D).

Version:    MENUVTX 10.05b (VUTRAX 12.1c)
Entry Date: 4 July 1999 - 7 Aug 1999
Problems Fixed:

• Spaces in the installation directory cause [Standard Paths] and [Other Paths] from (File > Setup) to include unwanted quotes. Spaces are discarded when the list is used.
  Workaround: Use [Browse] if the file you want is not shown.
  
• The Decode Rules function always updates the primary menu settings in the install directory rather than any project or user specific directories.
  Avoidance: With project based menus you can usually avoid 'Decode Rules' because rules files match the dialogue.
  Workaround if you must import rules:
  RENAME %VTXCFG%\VUTRUL.MNU *.ORIG
  COPY <project/user path>\VUTRUL.MNU %VTXCFG%\VUTRUL.MNU
  Run the 'Decode Rules' (updating the copy)
  COPY %VTXCFG%\VUTRUL.MNU <project/user path>\VUTRUL.MNU
  RENAME %VTXCFG%\VUTRUL.ORIG *.MNU
  Fix: Ask the office for a pre-release update.
  
• Decode Rules would fail to update, or crash, if the target menu had been compressed and not subsequently used.
  Workaround: Select [Build Rules] and then [Cancel] first.
  
• Installation in a path including spaces prevented DRAFT starting a new menu thread for multiple viewing.
  Workaround: Choose [Add Window] instead.
  

• Handling of menus needing final 'install' discovered when using an explicit menu directory has been improved.
  

• Extra temporary files are removed at the first Vutrax startup of a Windows session.

Version:    MENUVTX 10.06a (*** On Beta Trial for Vutrax 12.2a)
Entry Date: 14 Oct 1999 - 16 Jan 2000
Problems:

• The settings of [Standard Paths] or [Other paths] in (File > Setup) ignores spaces embedded in folder names. Generally the paths find nothing if your Vutrax install folder includes spaces (which by default it does NOT). The project and current directory are searched reliably regardless.
  Workaround: If the file you want is not shown after selecting [All names] select [Browse] and navigate to.
  
• If you attempt to specify [Set Index Path] from (File > Setup) with a path including a space, index building and use will fail.
  Fix: Use SEE editor on \VUTRAX\VUTRAX.MNU as follows:-
  Ctrl+G 501 46 <Enter> (goto line 501, column 46)
  (the line should start with '00214Set Index Path')
  Press the Ins key (to select Overtype)
  Replace 'Q' with 'U' (must be UPPER case)
  (checking that the final ^ doesn't move.)
  If anything goes wrong Abort the edit with Alt+F4
  otherwise Ctrl+Q Y (save the result if OK)
  In the menu system, reselect the item, and it is fixed.

Version:    VTXHELP 1.02a (VUTRAX 12.1c)
Entry Date: 7 Aug 1999
Problem Fixed:

• The tutorial practice facilities did not work if you installed Vutrax into a directory path including spaces.

Version:    VUTRAX.MNU 10.03g (VUTRAX 12.1c)
Entry Date: 4 July 1999
Problem Fixed:

• Settings in [Other Paths] and [Standard Paths] from (File > Setup) that include embedded spaces are inappropriately enclosed in quotes.
  Workaround: Use [Browse] if the file you want is not shown.

Version:    VTXSETUP 12.1f (VUTRAX 12.1c)
Entry Date: 13 July 1999
Enhancement:

• Complaints about not removing already absent directories no longer appear.
  

• At least some configurations of Microsoft Internet Explorer 5 are reported to introduce an extra dot into the offered archive filenames. Installation will fail on the 2nd file.
  Workaround: Rename system archives to VTX12 1B.M01 to VTX12 1B.M07 and similarly for other names.
  The download pages have been reformatted to specify the exact name you should use.

Version:    VTXSHELL 4.04b (*** On Beta Trial for VUTRAX 12.2)
Entry Date: 20 Aug 1999 - 5 Apr 2000
Problems:

• REN (Rename) between directories was refused if disk drive letters were included with different letter cases.
  Workaround: Drive letters must both be lower or upper case.
  
• If VTXSHELL 'COPY' and 'XCOPY' commands run out of disk space an incomplete destination file remains. COPY (not XCOPY) only sets exit code 1 if ALL files of a wildcard set fail.
  
• XCOPY with /COMP & /C options stopped to report mismatches rather than reporting and continuing.
  
• TABLE option variant /c*... may be rejected, or may even crash VTXSHELL. There is no impact on normal Vutrax operation. Avoidance: Use explicit settings for each field/column.
  

• TABLE option '/t' discards leading spaces and tabs in each field. When used with option '/c*m' fields already expanded to columns are reduced to the original form.
  
• TABLE option /c is extended to
  /c<column> l|r|m [<width> [f]]
  where the new fields are
  'm' Minimum Width - do not expand the fields.
  'f' Full field - do not truncate fields over <width>.
  
• The DIR command with /J option will place quotes round names containing spaces. (No impact on standard Vutrax operation).
  
• Commands DEL, ERASE and ERASEDIR by default now place what they remove in the Windows Recycle Bin.
  To have deleted items permanently removed SET NOUNDEL=Y

Version:      VTXFIND 1.02a (*** On Beta Trial for VUTRAX 12.2)
Entry Date:   6 Nov 1999
Problem:

• If the Vutrax installation directory name contains spaces the display of items found using [Search] from (File) will malfunction - graphics are displayed with a complaint, text is not displayed. The workarounds are mutually exclusive:-
  Workaround 1: Prior to Vutrax startup (e.g. in AUTOEXEC.BAT and then reboot) include a command such as
  SET VTXTEMP=C:\VTXTEMP
  to build temporary files without embedded spaces.
  Workaround 2: To view the file but without localising the found item, implement SAN 197 to patch
  ...\WIN32\VTXFIND.EXE using
  20 40 25 73 0 ;
  0 0 0 0 0
  Workaround 3: Request a development fix from the Office (requires prior upgrade to Vutrax 12.1c).

Version:      CHECKLIB 1.02a (VUTRAX 12.1c)
Entry Date:   7 Aug 1999
Problem Fixed:

• Installation in a path including spaces prevented starting the text editor from within CHECKLIB.
  Workaround: Note the problem, and start SEE from the menu. (The fix needs SEE 10.03a)

Version:     VTX2000 1.01a
Date:        27 Mar 1998 - 18 Mar 2000

Operational Note:

• If VTX2000 gets fooled into providing dates in the future:-
  1 Set the clock (using windows or DOS).
  2 Delete file \VTX2000.LOG (or wherever you put VTX2000).
  3 Run VTX2000 from the DOS and Windows command prompt, and ignore the messages about it being the first use.
  4 Reboot to check that it is now working correctly.

Version:    VTXTOSPC 4.02, SPCTOVTX 4.03 (VUTRAX 12.1)
Entry Date: 21 Aug 1999 - 24 Aug 1999
Changes:

• Shared changes to allow nested (i.e. '.'s) in directory names

Version:    VTXTOSPC 4.02, SPCTOVTX 4.04 (VUTRAX 12.1)
Entry Date: 3 Dec 1999
Problem:

• Unrouted connections to SMD pads were placed onto routed layers (1 & 2) instead of Rats Nest Layers (0 & 5). Usually caused if doing 'FANOUT' pass only and returning to Vutrax for editing.

Version:    VTXTOSPC 4.02, SPCTOVTX 4.05 (*** On Trial for VUTRAX 12.2a)
Entry Date: 5 Apr 2000
Problem:

• If the router fails to complete non-netted signals with SM pads, it can leave the partial route without a connecting via. SPCTOVTX might have then incorrectly omitted the connected SM pads from the Vutrax artwork.

Version:    VTX2IDEA 5.03 (Vutrax 12.1)
Entry Date: 21 Aug 1999 - 24 Aug 1999
Changes:

• If given a filename with multiple file extensions (i.e. '.'s), the extension up to the next 'space' after the first '.' was assumed to conclude the filename.

Version:    CDI2VTX 3.10 (Vutrax 12.1)
Entry Date: 21 Aug 1999 - 24 Aug 1999
Changes:

• Was a 16-bit program. Converted to 32-bit. 'Long' file names are accepted.
  
• If given a filename with multiple file extensions (i.e. '.'s), the extension up to the next 'space' after the first '.' was assumed to conclude the filename.
  
• Handles the increased resolution available in Vutrax-12.

Version:    CDI2VTX 3.11 (Vutrax 12.1)
Entry Date: 24 Aug 1999
Problem Fixed:

• Reproduction of non-360 degree arcs did not provide the correct trace width.

Version:    MCRSGEN 2.03 (Vutrax 12.1)
Entry Date: 21 Aug 1999 - 24 Aug 1999
Changes:

• If given a filename with multiple file extensions (i.e. '.'s), the extension up to the next 'space' after the first '.' was assumed to conclude the filename.

Version:    VTX2AMAP 2.03 (Vutrax 12.1)
Entry Date: 21 Aug 1999 - 24 Aug 1999
Changes:

• If given a filename with multiple file extensions (i.e. '.'s), the extension up to the next 'space' after the first '.' was assumed to conclude the filename.

Version:    VTX2SPG 4.03 (Vutrax 12.1)
Entry Date: 21 Aug 1999 - 24 Aug 1999
Changes:

• If given a filename with multiple file extensions (i.e. '.'s), the extension up to the next 'space' after the first '.' was assumed to conclude the filename.