开云体育

Installing 24.1.9 Removed My 24.0.12


 

Hello All:
?
I just installed 24.1.9 and the 24.1.9 installer removed my installation of 24.0.12.
I was running a sim in 24.0.12 when the 24.1.9 installer said that it needed to close other programs because they were using files required by the 24.1.9 installer.
So I stopped my sim, closed 24.0.12 and continued the 24.1.9 installation.
On completion I saw that my 24.0.12 desktop shortcut is now blank and the 24.0.12 program folder is now empty, WTF!
?
17.1.15 sits in a folder right next to the now empty 24.0.12.
The 24.1.9 installer didn't deem to erase it, 17.1.15 still works.
?
Now I have to decide to restore 24.0.12 from a backup which would leave all of the registry's default file settings pointing to 24.1.9.
Or, reinstall 24.0.12 to restore the default file pointers to point to 24.0.12.
?
More to come...
?
All for now
?


 

Hello All:
?
I decided to reinstall 24.0.12.
YOU CAN'T.
The 24.0.12 installer says that there is A NEWER version already installed, then the 24.0.12 installer aborts.
So I decided to rename the 24.1.9 program folder so it could no longer be found by the 24.0.12 installer.
I always test, and to my amazement, dbl-clicking the 24.1.9 shortcut on my desktop started 24.1.9.
I have no idea how ADI's registry spaghetti could possibly cause their desktop icon to find the 24.1.9 program folder after it had been renamed to "Junk" but, IT DOES.
Even the "Open Location" button on the LTspice 24.1.9 shortcut's properties dialog opened the "Junk" folder.
So I erased the folder "Junk" and finally the 24.1.9 desktop shortcut failed to start 24.1.9.
?
Now reinstalling 24.0.12 still says that there is A NEWER version already installed and then aborts.
The only possibility remaining is a registry key.
?
Now I have several options available.
1. Put the copy I made of 24.1.9 back in place and then uninstall 24.1.9 to get rid of whatever is blocking the 24.0.12 installer.
2. Dust of my copy of Sysinternals Process Monitor to follow the 24.0.12 installer to find the registry key that is blocking the 24.0.12 installation, NO FUN.
?
More to come...
?
All for now

?
Sent:?Saturday, May 31, 2025 at 10:17 PM
From:?"eewiz via groups.io" <eewiz@...>
To:[email protected]
Subject:?[LTspice] Installing 24.1.9 Removed My 24.0.12
Hello All:
?
I just installed 24.1.9 and the 24.1.9 installer removed my installation of 24.0.12.
I was running a sim in 24.0.12 when the 24.1.9 installer said that it needed to close other programs because they were using files required by the 24.1.9 installer.
So I stopped my sim, closed 24.0.12 and continued the 24.1.9 installation.
On completion I saw that my 24.0.12 desktop shortcut is now blank and the 24.0.12 program folder is now empty, WTF!
?
17.1.15 sits in a folder right next to the now empty 24.0.12.
The 24.1.9 installer didn't deem to erase it, 17.1.15 still works.
?
Now I have to decide to restore 24.0.12 from a backup which would leave all of the registry's default file settings pointing to 24.1.9.
Or, reinstall 24.0.12 to restore the default file pointers to point to 24.0.12.
?
More to come...
?
All for now
?


 

On Sat, May 31, 2025 at 10:54 PM, eewiz wrote:
I always test, and to my amazement, dbl-clicking the 24.1.9 shortcut on my desktop started 24.1.9.
I have no idea how ADI's registry spaghetti could possibly cause their desktop icon to find the 24.1.9 program folder after it had been renamed to "Junk" but, IT DOES.
I think that is a Microsoft Windows function.? When a link (shortcut) to a program fails, Windows instantly starts looking to find where it might have gone, and if it finds it, it uses it.
?
I have seen this with recent versions, since at least Win 7.
?
This has nothing to do with Analog Devices, nor a Registry thing.? It must be a Windows task waiting to run in the background.? It has happened to me with several kinds of programs.
?
Now reinstalling 24.0.12 still says that there is A NEWER version already installed and then aborts.
I would expect that, because Windows thinks it is still installed, unless you specifically uninstalled it.? I assume it still has dozens of hooks to that version in the Windows Registry.? Renaming a file changes nothing, except for direct access to it.
?
Andy
?


 

Hello All:
?
I chose option 1. below.
I put a copy I made of the 24.1.9 program folder back in place and then uninstalled 24.1.9.
Then I was able to reinstall 24.0.12.
Then I copied the 24.1.9 program folder back in place.
I can now start 24.1.9 but, all the file extensions point to 24.0.12 as desired.
Dbl-clicking a .sub or .asy or especially a .asc, starts 24.0.12.
But I can still start 24.1.9 and drop a .asc file onto it if I want to take the chance of simulating with 24.1.9.
?
I wish ADI would stop thinking that they know what versions of LTspice I should have on my computer.
Also, please pull out and make usable the part of the installer that writes the registry so users can switch versions easily.
A utility that will re-write the registry so all of the file extensions will open IV or XVII or 17.1 or 24.0 or 24.1 at whim of the user.
?
I ask this because it will be a royal PITA to keep up with the 24.1.x changes in the future.
For example, to install 24.1.10 here in the neer future wil require:
1. Install 24.1.10 which will erase 24.0.12.
2. Copy the 24.1.10 program folder to a safe place.
3. Uninstall 24.1.10 so 24.0.12 can be re-installed.
4. Re-install 24.0.12 to return the registry to point to 24.0.12.
5. Move the copy of the 24.1.10 program folder from the safe place back to it's original place so 24.1.10 will run.
Whew! that's alot of work that should not have to be done.
?
Also, after installing 24.1.9, simulating with 24.0.12 or 24.1.9 both produced 4 duplicate BJT warnings.
I found all 4 duplicated BJT's in the user.bjt file that came from 24.1.9's .zip expanded libraries installation.
I did not do a component update from 24.1.9.
User.bjt contained all four duplicated BJT's, (2scr375p, bc857b, bc847b and bc847c).
After doing a component update from 24.0.12, the duplicate BJT's were gone.
?
My project is a moderately complex circuit as far as LTspice is concerned.
?? --- Expanded Deck Component Count ---
A's 42
B's 21
C's 105
D's 93
E's 23
F's 9
G's 16
H's 3
I's 23
L's 35
M's 7
Q's 153
R's 269
S's 21
V's 41
tot: 861
?
LTspice 24.0.12 - SYSTEM IDLE = 50% avg across 16 cores
LTspice 24.0.12 for Windows
Start Time: Sun Jun? 1 00:04:56 2025
.tran 0 180m 80m
.options chgtol=1e-8
.options vntol=1e-3
.options abstol=1e-7
.options trtol=7
.options plotwinsize=0
.options gminsteps=0
.options nomarch
.options noopiter
.option temp=25
solver = Normal
Maximum thread count: 16
tnom = 27
temp = 25
method = modified trap
abstol = 1e-07
chgtol = 1e-08
trtol = 7
volttol = 0.001
noOpIter = 1
Direct Newton iteration for .op point skipped.
Gmin stepping method for .op point skipped.
Starting source stepping with srcstepmethod=0
Source Step = 3.0303%
Source Step = 33.3333%
Source Step = 63.6364%
Source Step = 93.9394%
Source stepping succeeded in finding the operating point.
2137 DefCon's
Total elapsed time: 1556.499 seconds.
?
LTspice 24.0.12 for Windows
Start Time: Sun Jun? 1 00:51:38 2025
.tran 0 180m 80m
.options chgtol=1e-8
.options vntol=1e-3
.options abstol=1e-7
.options trtol=7
.options plotwinsize=0
.options gminsteps=0
.options nomarch
.options noopiter
.option temp=25
solver = Alternate
Maximum thread count: 16
tnom = 27
temp = 25
method = modified trap
abstol = 1e-07
chgtol = 1e-08
trtol = 7
volttol = 0.001
noOpIter = 1
Direct Newton iteration for .op point skipped.
Gmin stepping method for .op point skipped.
Starting source stepping with srcstepmethod=0
Source Step = 3.0303%
Source Step = 33.3333%
Source Step = 63.6364%
Source Step = 93.9394%
Source stepping succeeded in finding the operating point.
No DefCon's
Total elapsed time: 3046.351 seconds.
?
LTspice 24.1.9 - SYSTEM IDLE = 20% avg across 16 cores. (ADI caused 24.1.9 to use more processor cores)
24.1.9 No longer outputs an "Expanded Deck Component Count"
LTspice 24.1.9 for Windows
Start Time: Sun Jun? 1 01:54:33 2025
Options: noopiter? NoMarch? gminsteps=0? PlotWinSize=0? trtol=7? abstol=1e-7? vntol=1e-3? chgtol=1e-8
solver = Normal
Maximum thread count: 16
tnom = 27
temp = 25
method = modified trap
abstol = 1e-07
chgtol = 1e-08
trtol = 7
volttol = 0.001
noOpIter = true
Direct Newton iteration for .op point skipped.
Gmin stepping method for .op point skipped.
Starting source stepping with srcstepmethod=0
Source Step = 3.0303%
Source Step = 33.3333%
Source Step = 63.6364%
Source Step = 93.9394%
Source Step = 96.5436%
vernier = 0.00390625
Source Step = 96.6146%
Source Step = 96.6412%
Source Step = 96.6708%
Source Step = 96.7004%
Source Step = 96.73%
Source Step = 96.7596%
Source Step = 96.7892%
Source Step = 96.8188%
Source Step = 96.8484%
Source Step = 96.878%
Source Step = 96.9076%
Source Step = 96.9371%
Source Step = 96.9667%
Source Step = 96.9963%
Source Step = 97.0259%
Source Step = 97.0555%
Source Step = 97.0851%
Source Step = 97.1147%
Source Step = 97.1443%
Source Step = 97.1739%
Source Step = 97.2035%
Source Step = 97.2331%
Source Step = 97.2627%
Source Step = 97.2923%
Source Step = 97.3219%
Source Step = 97.3514%
Source Step = 97.381%
Source Step = 97.4106%
Source Step = 97.4402%
Source Step = 97.4698%
Source Step = 97.4994%
Source Step = 97.529%
Source Step = 97.5586%
Source Step = 97.5882%
Source Step = 97.6178%
Source Step = 97.6474%
Source Step = 97.677%
Source Step = 97.7066%
Source Step = 97.7362%
Source Step = 97.7657%
Source Step = 97.7953%
Source Step = 97.8249%
Source Step = 97.8545%
Source Step = 97.8841%
Source Step = 97.9137%
Source Step = 97.9433%
Source Step = 97.9729%
Source Step = 98.0025%
Source Step = 98.0321%
Source Step = 98.0617%
Source Step = 98.0913%
Source Step = 98.1209%
Source Step = 98.1504%
Source Step = 98.18%
Source Step = 98.2096%
Source Step = 98.2392%
Source Step = 98.2688%
Source Step = 98.2984%
Source Step = 98.328%
Source Step = 98.3576%
Source Step = 98.3872%
Source Step = 98.4168%
Source Step = 98.4464%
Source Step = 98.476%
Source Step = 98.5056%
Source Step = 98.5352%
Source Step = 98.5647%
Source Step = 98.5943%
Source Step = 98.6239%
Source Step = 98.6535%
Source Step = 98.6831%
Source Step = 98.7127%
Source Step = 98.7423%
Source Step = 98.7719%
Source Step = 98.8015%
Source Step = 98.8311%
Source Step = 98.8607%
Source Step = 98.8903%
Source Step = 98.9199%
Source Step = 98.9495%
Source Step = 98.979%
Source Step = 99.0086%
Source Step = 99.0382%
Source Step = 99.0678%
Source Step = 99.0974%
Source Step = 99.127%
Source Step = 99.1566%
Source Step = 99.1862%
Source Step = 99.2158%
Source Step = 99.2454%
Source Step = 99.275%
Source Step = 99.3046%
Source Step = 99.3342%
Source Step = 99.3638%
Source Step = 99.3933%
Source Step = 99.4229%
Source Step = 99.4525%
Source Step = 99.4821%
Source Step = 99.5117%
Source Step = 99.5413%
Source Step = 99.5709%
Source Step = 99.6005%
Source Step = 99.6301%
Source Step = 99.6597%
Source Step = 99.6893%
Source Step = 99.7189%
Source Step = 99.7485%
Source Step = 99.7781%
Source Step = 99.8076%
Source Step = 99.8372%
Source Step = 99.8668%
Source Step = 99.8964%
Source Step = 99.926%
Source Step = 99.9556%
Source Step = 99.9852%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source Step = 100%
Source stepping succeeded in finding the operating point.
Warning: Simulation tolerance relaxed to achieve convergence from 5.2763753634517503e-03
Convergence Failure:? Time step too small; time = 0.00527638, timestep = 1.25079e-18: trouble with instance "xucc:u3:A2"
Simulation Failed: Iteration limit reached
Total elapsed time: 52.671 seconds.
?
LTspice 24.1.9 - SYSTEM IDLE = 20% avg across 16 cores
LTspice 24.1.9 for Windows
Start Time: Sun Jun? 1 01:54:33 2025
Options: noopiter? NoMarch? gminsteps=0? PlotWinSize=0? trtol=7? abstol=1e-7? vntol=1e-3? chgtol=1e-8
solver = Alternate
Maximum thread count: 16
tnom = 27
temp = 25
method = modified trap
abstol = 1e-07
chgtol = 1e-08
trtol = 7
volttol = 0.001
noOpIter = true
Direct Newton iteration for .op point skipped.
Gmin stepping method for .op point skipped.
Starting source stepping with srcstepmethod=0
Source Step = 3.0303%
Source Step = 33.3333%
Source Step = 63.6364%
Source Step = 93.9394%
Source stepping succeeded in finding the operating point.
Simulation STUCK
115,007 Warning: Simulation tolerance relaxed to achieve convergence.
55 minutes later.
Simulation stopped by user.
Total elapsed time: 6025.053 seconds.
?
The results are:
24.0.12 Normal Solver - 2137 DefCon's to finish in Total elapsed time: 1556.499 seconds.
24.0.12 Alternate Solver - No DefCon's to finish in Total elapsed time: 3046.351 seconds.
24.1.9 Normal Solver - Many Source Step's to FAIL with "Time step too small" in Total elapsed time: 52.671 seconds.
24.1.9 Alternate Solver - 115,007 Simulation tolerance relaxed Warnings to FAIL stalled with Total elapsed time: 6025.053 seconds.
?
ADI has a very long row to hoe when it comes to perfecting LTspice 24.1.x.
I see no choice but to use 24.0.12 into the foreseeable future.
?
All for now
?

Sent:?Saturday, May 31, 2025 at 10:54 PM
From:?"eewiz via groups.io" <eewiz@...>
To:[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12
Hello All:
?
I decided to reinstall 24.0.12.
YOU CAN'T.
The 24.0.12 installer says that there is A NEWER version already installed, then the 24.0.12 installer aborts.
So I decided to rename the 24.1.9 program folder so it could no longer be found by the 24.0.12 installer.
I always test, and to my amazement, dbl-clicking the 24.1.9 shortcut on my desktop started 24.1.9.
I have no idea how ADI's registry spaghetti could possibly cause their desktop icon to find the 24.1.9 program folder after it had been renamed to "Junk" but, IT DOES.
Even the "Open Location" button on the LTspice 24.1.9 shortcut's properties dialog opened the "Junk" folder.
So I erased the folder "Junk" and finally the 24.1.9 desktop shortcut failed to start 24.1.9.
?
Now reinstalling 24.0.12 still says that there is A NEWER version already installed and then aborts.
The only possibility remaining is a registry key.
?
Now I have several options available.
1. Put the copy I made of 24.1.9 back in place and then uninstall 24.1.9 to get rid of whatever is blocking the 24.0.12 installer.
2. Dust of my copy of Sysinternals Process Monitor to follow the 24.0.12 installer to find the registry key that is blocking the 24.0.12 installation, NO FUN.
?
More to come...
?
All for now
?
Sent:?Saturday, May 31, 2025 at 10:17 PM
From:?"eewiz via groups.io" <eewiz@...>
To:[email protected]
Subject:?[LTspice] Installing 24.1.9 Removed My 24.0.12
Hello All:
?
I just installed 24.1.9 and the 24.1.9 installer removed my installation of 24.0.12.
I was running a sim in 24.0.12 when the 24.1.9 installer said that it needed to close other programs because they were using files required by the 24.1.9 installer.
So I stopped my sim, closed 24.0.12 and continued the 24.1.9 installation.
On completion I saw that my 24.0.12 desktop shortcut is now blank and the 24.0.12 program folder is now empty, WTF!
?
17.1.15 sits in a folder right next to the now empty 24.0.12.
The 24.1.9 installer didn't deem to erase it, 17.1.15 still works.
?
Now I have to decide to restore 24.0.12 from a backup which would leave all of the registry's default file settings pointing to 24.1.9.
Or, reinstall 24.0.12 to restore the default file pointers to point to 24.0.12.
?
More to come...
?
All for now
?


 
Edited

On Sun, Jun 1, 2025 at 04:15 AM, eewiz wrote:
Also, after installing 24.1.9, simulating with 24.0.12 or 24.1.9 both produced 4 duplicate BJT warnings.
I found all 4 duplicated BJT's in the user.bjt file that came from 24.1.9's .zip expanded libraries installation.
I am pretty sure they fixed that.? Those duplicates date back to LTspice XVII version 17.0.something.? For a long time, Analog Devices stopped updating the standard.bjt files and carried that bug into newer versions, but I thought LTspice 24 version 24.1.x finally got rid of that problem.? So if you still have it there, it is probably because your library files already have it, and the new installation preserved your models.
?
I need to check, but I did not think that LTspice 24 comes with a user.bjt file.
?
I did not do a component update from 24.1.9.
Doing that ought to clear up duplicates (if there are any) in the standard.??? files.? But not if you have something wrong in your own user.??? files.

My project is a moderately complex circuit as far as LTspice is concerned.
?? --- Expanded Deck Component Count ---
...
(VERY VERY LONG error listing attached)
?
Please do not paste such ridiculously long things into group messages here.? You lost me there.? If you had anything else to say after that garbage, I did not bother looking at it.
?
Andy
?


 

Hello Andy:
?
Below Andy wrote: I would expect that, because Windows thinks it is still installed.
?
It's not windows. It is due to the programmer who wrote the LTspice 24.1.x installer.
Windows cares not if one re-installs a program over top of itself, or for that matter, 47 times beside itself, if the programmer who wrote the installer permits it.
?
Take Firefox for example.
The Firefox installer will permit one to clobber an existing version with any other version, newer or older.
The Firefox installer will also permit one to install any number of copies or different versions of Firefox each in a different folder.
Admittedly, multiple installations of Firefox may get confused when it comes to each program's data but, it lets you do it.
?
ADI could let the user install every existing version of LTspice on one machine if they chose to do so.
After all, it is a program used by electrical engineers.
?
All for now

?
Sent:?Saturday, May 31, 2025 at 11:05 PM
From:?"Andy I via groups.io" <AI.egrps+io@...>
To:[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12
On Sat, May 31, 2025 at 10:54 PM, eewiz wrote:
I always test, and to my amazement, dbl-clicking the 24.1.9 shortcut on my desktop started 24.1.9.
I have no idea how ADI's registry spaghetti could possibly cause their desktop icon to find the 24.1.9 program folder after it had been renamed to "Junk" but, IT DOES.
I think that is a Microsoft Windows function.? When a link (shortcut) to a program fails, Windows instantly starts looking to find where it might have gone, and if it finds it, it uses it.
?
I have seen this with recent versions, since at least Win 7.
?
This has nothing to do with Analog Devices, nor a Registry thing.? It must be a Windows task waiting to run in the background.? It has happened to me with several kinds of programs.
?
Now reinstalling 24.0.12 still says that there is A NEWER version already installed and then aborts.
I would expect that, because Windows thinks it is still installed, unless you specifically uninstalled it.? I assume it still has dozens of hooks to that version in the Windows Registry.? Renaming a file changes nothing, except for direct access to it.
?
Andy
?


 

On Sun, Jun 1, 2025 at 04:42 AM, eewiz wrote:
Hello Andy:
?
Below Andy wrote: I would expect that, because Windows thinks it is still installed.
?
It's not windows. It is due to the programmer who wrote the LTspice 24.1.x installer.
Not true.? You misread what I wrote.
?
Once 24.1.x is no longer there, the code that was in 24.1.x can no longer be responsible for noticing that it (a newer version) was previously installed.? It is the Windows Registry settings that the previous version added to your registry.
?
Then when attempting to install a different version (24.0.12), that version checks those Registry entries to see what had been installed -- even if you went and deleted that version from your drive.? It is the Windows entries (its Registry) that tells it what was there, just like I wrote.? The program being installed does not check what actual version you still have left on your drive.? It looks in the Registry.? In other words, it checks with Windows.
?
I'm not denying that the installation code checks to see what might have been there.? What I am saying is that it checks what Windows thinks was there.? I think you misread that.? Windows thinks 24.1.x is still installed, even though you deleted or moved it.? Deleting or moving it does not (yet) change Windows's Registry.
?
Andy
?
?


 

开云体育

On 01/06/2025 04:17, eewiz via groups.io wrote:
I just installed 24.1.9 and the 24.1.9 installer removed my installation of 24.0.12.
I was running a sim in 24.0.12 when the 24.1.9 installer said that it needed to close other programs because they were using files required by the 24.1.9 installer.
So I stopped my sim, closed 24.0.12 and continued the 24.1.9 installation.
On completion I saw that my 24.0.12 desktop shortcut is now blank and the 24.0.12 program folder is now empty, WTF!
?
17.1.15 sits in a folder right next to the now empty 24.0.12.
The 24.1.9 installer didn't deem to erase it, 17.1.15 still works.
?
Now I have to decide to restore 24.0.12 from a backup which would leave all of the registry's default file settings pointing to 24.1.9.
Or, reinstall 24.0.12 to restore the default file pointers to point to 24.0.12.
If you wanted to retain 24.0.12, did you change the installation folder to be a non-default location during the actual installation process? I have 17.1.15, 24.0.12 and 24.1.9 all installed alongside each other. All were installed to different folders, e.g.:

C:\Program Files\ADI\<CustomFolderName>\

I have never had any conflict. I also have all three versions sharing libraries and the plots.def. 24.0.12 and 24.1.x also share the LTspice.ini file. I kept the 17.1.15 inifile separate, as quite a few settings are different. I have three separate desktop shortcuts that call three separate batch files that keep track any changes to the inifiles so that if things go wrong between any of the versions, I have three separate backup inifiles. I use LTspice running in Wine on Linux, but exactly the same can be done running directly in Windows. I don't rely on registry settings for opening files from Explorer by double-clicking, so that aspect doesn't affect me. I tend to drag'n'drop files into LTspice as the means of opening them, or from the Recent Files list.

I have generally found that despite my whinging about changes (mainly about the stricter syntax checking that can break backward compatibility), that 24.1.x is somewhat faster for many things and converges better for some circuits, but YMMV. Bear in mind that you might need different SPICE settings. Indeed the defaults are different.

--
Regards,
Tony


 

On Sun, Jun 1, 2025 at 04:42 AM, eewiz wrote:
ADI could let the user install every existing version of LTspice on one machine if they chose to do so.
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.)
?
After all, it is a program used by electrical engineers.
Yup - which means that we are ideal candidates for really?screwing things up!? ;-)
?
Andy
?


 

Hello Tony:
?
Yes I have each version in a different folder.
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
?
Yesterday, "C:\WIN32\LTC\LTspice24.1.9" did not exist and "C:\WIN32\LTC\LTspice24.0.12" was doing simulations.
Today, after installing "C:\WIN32\LTC\LTspice24.1.9" the "C:\WIN32\LTC\LTspice24.0.12" folder was empty as described below.

I will repeat the entire 24.1.9 installation maneuver tomorrow to see if the the 24.0.12 folder gets erased again.
?
More to come...
?
I found that the 4 duplicate BJT's reentered the situation when I reinstalled 24.0.12 after it was erased by installing 24.1.9.
The standard.bjt file with the duplicated BJT's can be found in the lib.zip file that comes with 24.0.12.
?
All for now

?
?
Sent:?Sunday, June 01, 2025 at 4:56 AM
From:?"Tony Casey via groups.io" <antoniustrevorum@...>
To:[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12
On 01/06/2025 04:17, eewiz via groups.io wrote:
I just installed 24.1.9 and the 24.1.9 installer removed my installation of 24.0.12.
I was running a sim in 24.0.12 when the 24.1.9 installer said that it needed to close other programs because they were using files required by the 24.1.9 installer.
So I stopped my sim, closed 24.0.12 and continued the 24.1.9 installation.
On completion I saw that my 24.0.12 desktop shortcut is now blank and the 24.0.12 program folder is now empty, WTF!
?
17.1.15 sits in a folder right next to the now empty 24.0.12.
The 24.1.9 installer didn't deem to erase it, 17.1.15 still works.
?
Now I have to decide to restore 24.0.12 from a backup which would leave all of the registry's default file settings pointing to 24.1.9.
Or, reinstall 24.0.12 to restore the default file pointers to point to 24.0.12.
If you wanted to retain 24.0.12, did you change the installation folder to be a non-default location during the actual installation process? I have 17.1.15, 24.0.12 and 24.1.9 all installed alongside each other. All were installed to different folders, e.g.:

C:\Program Files\ADI\<CustomFolderName>\

I have never had any conflict. I also have all three versions sharing libraries and the plots.def. 24.0.12 and 24.1.x also share the LTspice.ini file. I kept the 17.1.15 inifile separate, as quite a few settings are different. I have three separate desktop shortcuts that call three separate batch files that keep track any changes to the inifiles so that if things go wrong between any of the versions, I have three separate backup inifiles. I use LTspice running in Wine on Linux, but exactly the same can be done running directly in Windows. I don't rely on registry settings for opening files from Explorer by double-clicking, so that aspect doesn't affect me. I tend to drag'n'drop files into LTspice as the means of opening them, or from the Recent Files list.

I have generally found that despite my whinging about changes (mainly about the stricter syntax checking that can break backward compatibility), that 24.1.x is somewhat faster for many things and converges better for some circuits, but YMMV. Bear in mind that you might need different SPICE settings. Indeed the defaults are different.
?
--
Regards,
Tony
?


 

开云体育

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


 

Hello All,
?
It's now tomorrow and I performed a 24.1.9 installation again.
?
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.
?
2. Dbl-click a schematic which starts 24.0.12 and start it simulating.
?
3. Run the 24.1.9 installer up to the destination dialog.
The installer presents 24.0.12's existing installation location of C:\WIN32\LTC\LTspice24.0.12.
Overtype the 0.12, changing it to 1.9, creating the new installation location of C:\WIN32\LTC\LTspice24.1.9 and cllck OK.
?
4. The 24.1.9 installer now runs until a "File in use" dialog appears.
The dialog states that a "SPICE Simulator w/ Schematic Capture" has files in use that the installer needs to continue.
?
5. Bring up the running 24.0.12, stop the simulation and close 24.0.12.
?
6. Click OK and the 24.1.9 installer to continues.
?
7. The 24.1.9 installation is complete.
?
8. The C:\WIN32\LTC\LTspice24.0.12 folder is now empty and the 24.0.12 shortcut on the desktop is blank.
The 24.1.9 installer erased all file contents from the C:\WIN32\LTC\LTspice24.0.12 folder.
It left behind one folder that I put there.
In each LTspice program folder I put an additional folder to identify which LTspice version it is.
For example, in my C:\WIN32\LTC\LTspice24.0.12 folder I add an empty folder named "_v24.0.12".
The underscore puts that folder at the top of the file list, making it easy to determine which one of the LTspice program folders I may be in at that moment.
?
9. Copy the C:\WIN32\LTC\LTspice24.1.9 folder to a backup area.
?
10. Remove version 24.1.9, clearing the registry, to allow 24.0.12 to be re-installed.
?
11. Re-install version 24.0.12 to C:\WIN32\LTC\LTspice24.0.12.
?
12. Copy the C:\WIN32\LTC\LTspice24.1.9 folder from the backup area, back to the C:\WIN32\LTC folder.
Now the registry points all file extensions to 24.0.12 and 24.1.9 will also run if started directly.
?
13. Run 24.0.12 and do a Component Update to get rid of the duplicate BJT's in the standard.bjt file that comes with 24.0.12.
?
Thirteen steps later I can use 24.0.12 every day and also experiment with 24.1.9.
?
For the less intrepid, here are the condensed results of running my simulation on 24.0.12 vs. 24.1.9 brought to the top.
?
My project contains:
A's 42
B's 21
C's 105
D's 93
E's 23
F's 9
G's 16
H's 3
I's 23
L's 35
M's 7
Q's 153
R's 269
S's 21
V's 41
tot: 861
?
The results are:
24.0.12 Normal Solver - 2137 DefCon's to finish in Total elapsed time: 1556.499 seconds.
24.0.12 Alternate Solver - No DefCon's to finish in Total elapsed time: 3046.351 seconds.
24.1.9 Normal Solver - Many Source Step's to FAIL with "Time step too small" in Total elapsed time: 52.671 seconds.
24.1.9 Alternate Solver - 115,007 Simulation tolerance relaxed Warnings to FAIL stalled with Total elapsed time: 6025.053 seconds.
?
All for now

?
Sent:?Sunday, June 01, 2025 at 5:39 AM
From:?"eewiz via groups.io" <eewiz@...>
To:[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12
Hello Tony:
?
Yes I have each version in a different folder.
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
?
Yesterday, "C:\WIN32\LTC\LTspice24.1.9" did not exist and "C:\WIN32\LTC\LTspice24.0.12" was doing simulations.
Today, after installing "C:\WIN32\LTC\LTspice24.1.9" the "C:\WIN32\LTC\LTspice24.0.12" folder was empty as described below.

I will repeat the entire 24.1.9 installation maneuver tomorrow to see if the the 24.0.12 folder gets erased again.
?
More to come...
?
I found that the 4 duplicate BJT's reentered the situation when I reinstalled 24.0.12 after it was erased by installing 24.1.9.
The standard.bjt file with the duplicated BJT's can be found in the lib.zip file that comes with 24.0.12.
?
All for now
?
?
Sent:?Sunday, June 01, 2025 at 4:56 AM
From:?"Tony Casey via groups.io" <antoniustrevorum@...>
To:[email protected]
Subject:?Re: [LTspice] Installing 24.1.9 Removed My 24.0.12
On 01/06/2025 04:17, eewiz via groups.io wrote:
I just installed 24.1.9 and the 24.1.9 installer removed my installation of 24.0.12.
I was running a sim in 24.0.12 when the 24.1.9 installer said that it needed to close other programs because they were using files required by the 24.1.9 installer.
So I stopped my sim, closed 24.0.12 and continued the 24.1.9 installation.
On completion I saw that my 24.0.12 desktop shortcut is now blank and the 24.0.12 program folder is now empty, WTF!
?
17.1.15 sits in a folder right next to the now empty 24.0.12.
The 24.1.9 installer didn't deem to erase it, 17.1.15 still works.
?
Now I have to decide to restore 24.0.12 from a backup which would leave all of the registry's default file settings pointing to 24.1.9.
Or, reinstall 24.0.12 to restore the default file pointers to point to 24.0.12.
If you wanted to retain 24.0.12, did you change the installation folder to be a non-default location during the actual installation process? I have 17.1.15, 24.0.12 and 24.1.9 all installed alongside each other. All were installed to different folders, e.g.:

C:\Program Files\ADI\<CustomFolderName>\

I have never had any conflict. I also have all three versions sharing libraries and the plots.def. 24.0.12 and 24.1.x also share the LTspice.ini file. I kept the 17.1.15 inifile separate, as quite a few settings are different. I have three separate desktop shortcuts that call three separate batch files that keep track any changes to the inifiles so that if things go wrong between any of the versions, I have three separate backup inifiles. I use LTspice running in Wine on Linux, but exactly the same can be done running directly in Windows. I don't rely on registry settings for opening files from Explorer by double-clicking, so that aspect doesn't affect me. I tend to drag'n'drop files into LTspice as the means of opening them, or from the Recent Files list.

I have generally found that despite my whinging about changes (mainly about the stricter syntax checking that can break backward compatibility), that 24.1.x is somewhat faster for many things and converges better for some circuits, but YMMV. Bear in mind that you might need different SPICE settings. Indeed the defaults are different.
?
--
Regards,
Tony
?


 

开云体育

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


 

开云体育

All in the same bottle: ~/.LTCAD. I also have LTspice helper programs installed there, e.g. s2spice. although at one time, I did compile a native Linux version of that.

--
Regards,
Tony

On 01/06/2025 22:24, Donald H Locker via groups.io wrote:

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

Donald.



 

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


 

开云体育

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.


 

开云体育

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


 

开云体育

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 2025-06-01 22:05, Tony Casey via groups.io wrote:
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

--
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'm afraid I can't really comment specifically on Win11 because I've never used it. My desktop PC can run it, but my other machines can't because either their motherboard BIOS or CPU don't support Safe Boot. So, I've not considered using it. Linux is much more accommodating. But at least one of my PCs must run Widows (deliberate misspelling) because it
has ATE programs on it that aren't supported on Linux to any reasonable degree.

--
Regards,
Tony

On 01/06/2025 23:18, John Woodgate via groups.io wrote:

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 2025-06-01 22:05, Tony Casey via groups.io wrote:
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


 

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.