开云体育

Sigh...

?

Yet another undocumented feature. There is no mention of this option in the help for ".options" or "Transient analysis options".

?

How are users supposed to know what this does or when it might be useful?

10/8/24 LTspice 24.1.0
?????? * Improved performance and convergence
?????? * Add support for directory hierarchy for symbol search paths and schematic directory
?????? * Add support for environment variables in Settings > Search Paths
?????? * Add "All" symbol directories view in Place Component dialog
?????? * Add .savestate and .loadstate simulator directives to save and restore the complete transient simulation condition
?????? * Add ".option debugtran" to add report in log file to indicate convergence challenges
?????? * Enhanced netlist syntax checking
?????? * Introduced string parameters that allow easy stepping of models and subcircuits
?????? * Allow device flags to be set to zero for ease of parameterization
?????? * Changed default integration method to Trapezoidal
?????? * Remember waveform compression settings (under Settings > Compression) between LTspice invocations
?????? * Always accept "3k4" notation as 3.4k (no longer optional)
?????? * Update FRA example fra_eg1
?????? * Update Help documentation
?????? * Bug fixes

开云体育

Please always include at least a bit of the post you are replying to.?

In this case, a Search for 'debugtran' cause the Offline Manual to sulk. This is with 24.1.9.

Sigh...

?

Yet another undocumented feature. There is no mention of this option in the help for ".options" or "Transient analysis options".

?

How are users supposed to know what this does or when it might be useful?

开云体育

The two diodes I used were BAV199 at 10uA to 15mA & 1PS66SB82 at 100uA to 150uA, both running at 25'C.

开云体育

'tera', not 'terra'. I don't see that a voltage change could be superluminal, because it's based on a field, but a current in a wire is electrons, and they can't exceed the speed of light in a vacuum, although they could exceed the sped of light in the material of the wire, while emitting Cerenkov radiation.

The singular matrix must be caused by the processing not being accurate enough, presumably making at least one matrix element evaluate to zero instead of a finite number.

Hello All:

?

I managed to catch a TRAP glitch in the wild.

?

The photo Glitch10 shows a TRAP glitch that caused a singular matrix failure somewhat later at 96.518252ms.

?

The photo Glitch11 shows a TRAP glitch that has been zoomed-in to femtosecond resolution.

?

After following Andy's suggestion of changing the X axis to show time-96.517852ms, I was able to eventually zoom in on one of those TRAP glitches down to a fraction of a femtosecond.

As can be seen in Glitch11 in the V(v+15) pane, current changes first.

The current changes 2.88A in 157fs and probably faster because there are only two interpolated time points on the current plot.

Using the data shown, the current changes at the rate 18.3 terraamperes per second.

?

The voltage changes 116 millivolts in 2.35 femtoseconds for a slew rate 50 terravolts per second.

I wonder if those changes might be superluminal and therefor impossible in this universe.

?

All for now

开云体育

I agree that Win32 is not a native Windows folder, but the preference for running third-party apps is still to put them in C:\Users\User\AppData\Local\Programs\ Why risk trouble by not doing that?

Hello John:

?

Yep, except my seperated versions reside in C:\Win32\LTC.

?

C:\Win32 is not a native folder in Windows 10 nor windows 11.

You may be thinking of C:\Windows\System32, which is a Windows native folder, which I am not using.

C:Win32 in no more native to windows than C:\John or C:\William is.

?

Windows nor LTspice has any preference where LTspice is installed.

There are places that the LTspice installer puts things because the programmer of the installer decided to put them there.

Those places are not "Preferred."

LTspice will run from wherever the Windows directory points the .asc file extension to.

Or, wherever LTspice is installed if run directly.

?

You can even run multiple simultaneous copies of different versions or simultaneous copies of the same version.

The only restriction is that each copy must be cranking a differently named schematic or there will be temporary-file clash, since the .log and .raw files take on the same name as the schematic.

?

All for now

Sent:?Sunday, June 01, 2025 at 4:58 PM
From:?"John Woodgate via groups.io" <jmw@...>
To:?[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12

I'm not sure that it's good to put non-Windows files in C:/WIN32. I'm pretty sure that Windows 11 would like it here:? C:\Users\User\AppData\Local\Programs\ADI\LTspice\ltspice.exe Of course, to keep more than one version, you would need something like: C:\Users\User\AppData\Local\Programs\ADI\LTspice2x\ltspice.exe for each version.

On 2025-06-01 21:48, eewiz via groups.io wrote:

Hello Donald:

?

If bottles on WINE, are the same as, folders on Windows, then the answer is yes.

?

My file structure:

C:\WIN32\LTC\LTspice24.0.12
C:\WIN32\LTC\LTspice24.1.1
C:\WIN32\LTC\LTspice24.1.9
C:\WIN32\LTC\LTspiceIV
C:\WIN32\LTC\LTspiceXVII

?

Each version is installed in it's own folder.

Installing 24.1.9 creates a new folder C:\WIN32\LTC\LTspice24.1.9, and during the installation process, erases all files in the C:\WIN32\LTC\LTspice24.0.12 folder which is the current Windows registry holder.

If 24.1.9 interrogates the registry to determine what the current installed version is, it finds "C:\WIN32\LTC\LTspice24.0.12.

The 24.1.9 installer does not erase C:\WIN32\LTC\LTspice24.1.1 nor C:\WIN32\LTC\LTspiceXVII, etc...

It only erases the current registry holder which is version 24.0.12.

?

All for now

?

Sent:?Sunday, June 01, 2025 at 4:24 PM
From:?"Donald H Locker via groups.io" <dhlocker@...>
To:?[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12

Speaking of LTspice on WINE - do you use separate "bottles" for each installation, or are they all in the same bottle?

Donald.

On 6/1/25 08:35, Tony Casey via groups.io wrote:

On 01/06/2025 11:05, Andy I via groups.io wrote:

There might be problems if it does that.? I don't know, but I'm suggesting that there may have been a good reason for adding that check.

?

Previously, it was not an issue and you could install multiple versions of LTspice on the same PC, even installing them in random order.? But users, and LTspice itself, need to be careful about things like preserving the libraries, and I suspect that was the reason for Analog Devices to add code to check that it is not updating a newer version with an older one.? Maybe they want to reduce the chances of really screwing up your libraries.? (I don't know - I'm only guessing here.)

I've had no problems installing 3 different version of LTspice on my computer. (I used to keep LTspiceIV as well, but gave up on that, because it was too different, and very few folk can still have that installed, except for our friend in Syria, who cannot access any more recent versions.) As you know, I'm primarily a Linux user, but Wine supports a registry of sorts, too, that is broadly compatible with the Windows one insofar as necessary for Windows programs to function correctly. When I "upgrade" the 24.1.x version, I always download and install the new one, so I always have the installer program for the future, as the problem with always upgrading in situ is that you cannot easily go back to any particular setting you had in the past. I know that, technically, Windows provides this feature with the "System Restore Points", but that never seems to quite do what you want it to.

The uninstall/removal issue only happens if you try install the new version into the same folder the old version is located, in my experience. In which case, the installation program tells you the folder already exists, and asks if you want to install there anyway.
?

--
Regards,
Tony

--
Best wishes John Woodgate RAYLEIGH Essex OOO-Own Opinions Only If something is true: * as far as we know - it's science *for certain - it's mathematics *unquestionably - it's religion

?

Virus-free.

开云体育

开云体育

开云体育

I agree with your reasoning, but there are many hidden rules in Win 11, and it's unwise, I think, not to follow them, especially if there is no reason not to follow them. I suspect some of the 'rules' are 'not specifically intended' consequences of the Windows programmers assuming that all the rules they know about are followed by the app writers and the users.

On 01/06/2025 22:16, eewiz via groups.io wrote:

1. Erase the C:\WIN32\LTC\LTspice24.1.9 folder.

Makes no difference to windows because 24.1.9 had already been removed to allow re-installation of 24.0.12 yesterday.

Remember, today's existing 24.1.9 folder was copied there yesterday after 24.0.12 was re-installed.

This also shows that an LTspice installation folder can be copied anywhere just like you would a portable program that has no installer.

In my case, 24.1.9 ran normally from that copied folder, even though the windows registry contents now support 24.0.12.

It appears that LTspice actually is a portable program with an installer to setup only file extensions in the registry.

It appears to require no registry support at runtime.

If you're running from the executable, it make no difference.

If you're running from a shortcut, i.e. the Start Menu, and move the target file, the shortcut will follow it, which is different from a symbolic link, which does not follow the target.

If the folder name is unchanged but contains a different LTspice version, it will also continue to work.

That's because the name of the executable is the same (LTspice.exe) between all the different versions (17.* - 24.*). Windows doesn't know which one it's running.

--
Regards,
Tony

开云体育

1. Erase the C:\WIN32\LTC\LTspice24.1.9 folder.

Makes no difference to windows because 24.1.9 had already been removed to allow re-installation of 24.0.12 yesterday.

Remember, today's existing 24.1.9 folder was copied there yesterday after 24.0.12 was re-installed.

This also shows that an LTspice installation folder can be copied anywhere just like you would a portable program that has no installer.

In my case, 24.1.9 ran normally from that copied folder, even though the windows registry contents now support 24.0.12.

It appears that LTspice actually is a portable program with an installer to setup only file extensions in the registry.

It appears to require no registry support at runtime.

开云体育

I'm not sure that it's good to put non-Windows files in C:/WIN32. I'm pretty sure that Windows 11 would like it here:? C:\Users\User\AppData\Local\Programs\ADI\LTspice\ltspice.exe Of course, to keep more than one version, you would need something like: C:\Users\User\AppData\Local\Programs\ADI\LTspice2x\ltspice.exe for each version.

Hello Donald:

?

If bottles on WINE, are the same as, folders on Windows, then the answer is yes.

?

My file structure:

C:\WIN32\LTC\LTspice24.0.12
C:\WIN32\LTC\LTspice24.1.1
C:\WIN32\LTC\LTspice24.1.9
C:\WIN32\LTC\LTspiceIV
C:\WIN32\LTC\LTspiceXVII

?

Each version is installed in it's own folder.

Installing 24.1.9 creates a new folder C:\WIN32\LTC\LTspice24.1.9, and during the installation process, erases all files in the C:\WIN32\LTC\LTspice24.0.12 folder which is the current Windows registry holder.

If 24.1.9 interrogates the registry to determine what the current installed version is, it finds "C:\WIN32\LTC\LTspice24.0.12.

The 24.1.9 installer does not erase C:\WIN32\LTC\LTspice24.1.1 nor C:\WIN32\LTC\LTspiceXVII, etc...

It only erases the current registry holder which is version 24.0.12.

?

All for now

?

Sent:?Sunday, June 01, 2025 at 4:24 PM
From:?"Donald H Locker via groups.io" <dhlocker@...>
To:?[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12

Speaking of LTspice on WINE - do you use separate "bottles" for each installation, or are they all in the same bottle?

Donald.

On 6/1/25 08:35, Tony Casey via groups.io wrote:

On 01/06/2025 11:05, Andy I via groups.io wrote:

There might be problems if it does that.? I don't know, but I'm suggesting that there may have been a good reason for adding that check.

?

Previously, it was not an issue and you could install multiple versions of LTspice on the same PC, even installing them in random order.? But users, and LTspice itself, need to be careful about things like preserving the libraries, and I suspect that was the reason for Analog Devices to add code to check that it is not updating a newer version with an older one.? Maybe they want to reduce the chances of really screwing up your libraries.? (I don't know - I'm only guessing here.)

I've had no problems installing 3 different version of LTspice on my computer. (I used to keep LTspiceIV as well, but gave up on that, because it was too different, and very few folk can still have that installed, except for our friend in Syria, who cannot access any more recent versions.) As you know, I'm primarily a Linux user, but Wine supports a registry of sorts, too, that is broadly compatible with the Windows one insofar as necessary for Windows programs to function correctly. When I "upgrade" the 24.1.x version, I always download and install the new one, so I always have the installer program for the future, as the problem with always upgrading in situ is that you cannot easily go back to any particular setting you had in the past. I know that, technically, Windows provides this feature with the "System Restore Points", but that never seems to quite do what you want it to.

The uninstall/removal issue only happens if you try install the new version into the same folder the old version is located, in my experience. In which case, the installation program tells you the folder already exists, and asks if you want to install there anyway.
?

--
Regards,
Tony