download link of last LTspice 17 version

Hi petle ,

LTspice 17.1.x is no longer supported, but I'll find out if I we can supply the last 17.1.x version.

mike

Hi petle ,

Is there a particular reason you would like to use LTspice 17? 

Thanks,

mike

Yes, the LTspice 24 UI "improvements" are terrible.

Hi petle ,

LTspice 24 allows you to somewhat evert to the legacy UI. See this FAQ.

mike

Of cause I've tried that. This is the result.

I don’t see the appeal or benefit of the increased status bar font size and especially not of the increased context menu entry height. Looks like a failed attempt at making the UI touch monitor friendly. Not that anyone needs that.

The new cursors look and feel out of place, too.

At least I’ve discovered one actual improvement: Monospaced font in the “Edit Text on the Schematic” window. Unfortunately that is the only one. All other edit windows use a normal font.

so ... can you?

Hi petle ,

You are correct, the increased sizes of cursors and status font were increased in size in response to numerous complaints that LTspice was difficult to use on modern high resolution monitors. Although DPI awareness is added to LTspice 24, and many UI items can be resized by the user, some UI items have proven difficult to control because of the legacy code base. We will look into an option to reduce the size of these items for low-resolution monitors.

We will also look into text in the other edit windows. The Edit Text on Schematic to monospace was a common request.

Thank you for your time,

mike

I'm in the same boat.  More important to me than icons is that it appears that some of the methods of importing a model are different in version 24.  I tried to add a diode to the diode components and couldn't get it to work.  If I can't go back to 17 then I need a tutorial for adding a new diode in version 24.

Hi JRB24 ,

The import method should be the same, but for one thing. You cannot edit the standard library, but you can use your own user.dio library. This avoids the problem from earlier versions where users would unknowingly overwrite their custom components on an update.

Please open a new Q&A thread with your problem and upload any files you are using.

mike

From the LTspice 24 FAQ.

•  Optional user-defined libraries for additional discrete components

- By default, LTspice looks in Documents\LTspice for user.*
 (user.dio, mos, res, cap, ind, bead, jft, bjt)

- Directory is configurable in Settings > Search Paths

•  Users should not edit ADI-provided files in %localappdata%\LTspice

- LTspice will attempt to dissuade users from saving files here