Unfortunately the files I uploaded will not run. In the ASC file, the
attribute for L1 reads

  SYMATTR InstName L1
  SYMATTR Value 10=B5

The correct value is

  SYMATTR Value 10u

In the PLT file, each entry for the X scale reads

  X: ('=B5',1,0,5e-007,5e-006)

The correct value should read

  X: ('u',1,0,5e-007,5e-006)

Your email client may use different characters for mu. None of them will
work in LTspice.

The problem comes when you try to enter the letter "u" to signify micro,
such as 10 microhenries. LTspice changes the letter "u" to mu, which is
ascii 230.

This character is outside the normal ascii range of 32 to 127, so it gets
translated to B5 which I believe is unicode.

However, LTspice cannot understand B5, so it gives an error and won't run.

You can change the default behavior in LTspice to stop changing the letter
"u" to mu. In Control Panel -> Netlist Options -> Style/Conventions, click
the box that states

  Convert mu to u

However, this only affects future files. For current files, you have to go
into each one and manually change mu to u. Then run the file and save the
new PLT file.

A solution to mangled files is to package the ASC and PLT files into a zip
archive and append it to the post. I don't know if this will work in febo,
so I am trying it here to find out.

Other things to watch out for are long lines that get wrapped in the email,
and using models that are not available in every users's installation. You
have to test the simulation in a virgin installation to make sure there are
no special components.

Mike
