I moved to Topspin 4.3.0 for an important reason i.e. the accompanying
upgraded and patched version of IconNMR for our system that runs fully
automated with SampleCase. I haven't dug deep into the pros and cons
between the two i.e. 4.1.4 and 4.3.0. Yes, I was using 4.2.0 in between.
I haven't found a material difference imho between 4.2.0 and 4.3.0 when it
comes to reliability of day to day operations. That said, the frequency
with which the entire desktop of my CentOS 7.2 used to go into a comatose
state has certainly reduced. Well, this may or maynot be Topspin centric.
The thread started with Windows but I don't have any Windows based system
to compare it to. I hope the additional info above is helpful to someone
in the community.
Best Regards
Rajan
On Wed, Oct 18, 2023 at 6:57 AM Bob Berno <bberno_at_mcmaster.ca> wrote:
> Hello everyone,
>
> The perils of software upgrades!
> How many of you have encountered weird error messages and are told to
> download and install the latest version of TopSpin? Was this error message
> due to a known bug that was fixed in the current release? Maybe, or maybe
> not. But applying a software update to a workstation in a multiuser
> facility is never as easy and straightforward as they think.
>
> I never bothered with TopSpin 4.2 on any of our spectrometer
> workstations. I was waiting for TopSpin 4.2.1, but I guess v4.2 was so bad
> that they decided to go straight to v4.3.0 instead. I used v4.2.0 as a
> datastation and I hated it. And when I read the release notes for 4.3.0 I
> was really glad I never bothered with v.4.2.0 on any of our spectrometer
> hosts. One of my colleagues described v4.2.0 as "...the devil, and should
> never be installed on a spectrometer workstation."
>
> So far, I have upgraded one spectrometer host to v4.3.0 of TopSpin. It is
> our most heavily used spectrometer (in terms of sample throughput), and it
> has been working quite well since early August. We did encounter some
> "communication" issues at first like have been described, but that was
> resolved after a few workstation and console reboots/power cycles. Maybe
> these repeated reboots were needed for all of the firmware updates? This
> spectrometer workstation runs CentOS 7, as do most of the rest of our
> workstations.
>
> We have a Fourier 80 benchtop spectrometer running Windows 10 which is
> also running TopSpin 4.3.0. It's been online for a few months, and so far
> it has been working fine. It was updated to 4.3.0 during the installation,
> so I can't comment on how this spectrometer performs compared to earlier
> versions of TopSpin.
>
> I guess my suggestion is, "if it ain't broke, don't fix it." I've so far
> had some good success with v4.3.0 on a spectrometer host, and I plan to
> start upgrading the others soon. But if you don't have a pressing need to
> upgrade, then don't bother.
>
> Good luck everyone,
> Bob.
> -----Original Message-----
> From: main_at_ammrl.groups.io <main_at_ammrl.groups.io> On Behalf Of Ulrich via groups.io
> Sent: October 18, 2023 6:32 AM
> To: main_at_ammrl.groups.io
> Subject: Re: [AMMRL] updating TopSpin 4.1.4 to TopSpin 4.3.0
>
>
> Hello All!
>
> I tried TS 4.2 and then 4.3 both are a bit ... a mess. Please stay on
> 4.1.4 - this one is a bit more stable.
> TS 4.3 was so bad - so I had to switch back to 4.2 - but this is not so
> good.
> OK - I use the Linux versions - not the Microsoft Windows 10 or 11 stuff!
>
> Yours sincerly,
>
> Ulrich Haunz
>
> Am Mittwoch, Oktober 18, 2023 01:45 CEST, schrieb "Tom Pratum" tkp9551_at_gmail.com>:
>
> > Hello All-
> > We have recently had a NEO 400 installed with TopSpin 4.1.4 running
> under Windows 10. We are now trying to install 4.3.0, and following the
> instructions one of our faculty members received at a recent training
> course. We find that the new installation is not communicating with the
> spectrometer, despite having all of the correct configuration files from
> the previous configuration in the new configuration directory. We also
> noted a number of “Windows Defender” exceptions when running cf and/or
> expinstall, so we turned off Windows Defender, but still, the new
> installation is unable to communicate with the spectrometer. The old
> installation still works fine.
> >
> > Does anyone have any tips on completing this update?
> >
> > Thanks very much in advance!
> >
> >
> >
> > Tom Pratum, Southern Oregon Univ.
> >
> >
> >
> >
> --
> =========================
>
> Ulrich Haunz, Dipl.-Ing. (FH)
> NMR-Spektroskopie
>
> Raum L 710, L 807
> NMR-Center M520, M521, M527
> Postfach M 715
> Fachbereich Chemie
> Universitaet Konstanz
>
> 78457 Konstanz
>
> Tel.: +49 (0)7531 88-4261 -> M521 Bruker Avance NEO 800
> Tel.: +49 (0)7531 88-4422 -> L807 JEOL Lambda 400
> Tel.: +49 (0)7531 88-4955 -> L710 Bruker AVIII HD 400
> Tel.: +49 (0)7531 88-4956 -> M520a Bruker AVIII 600
> Tel.: +49 (0)7531 88-4957 -> M527 Bruker AVIII 400 Automation
> Tel.: +49 (0)7531 88-4958 -> M520 Bruker AVIII 400 WB
> Tel.: +49 (0)170 9153213
> FAX : +49 (0)7531 88-3898
> =========================
>
>
>
--
____________________________________
Rajan K Paranji, Ph.D.NMR Services Manager
*Department of Chemistry**Room 65, Bagley Hall*
University of WashingtonSeattle, WA 98195
phone : 206 685 2581 fax: 206 685 8665email: rajanp_at_uw.edu
____________________________________________________________________
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#705): https://urldefense.com/v3/__https://ammrl.groups.=
io/g/main/message/705__;!!PvDODwlR4mBZyAb0!ToHYe5bmX6l_V4qor7SAiROwsovG8BiO=
5IwkcFHcTU2hjiGa7sgUrACTJ93aYxKM-lCRNGfO-DAPQA$
Mute This Topic: https://urldefense.com/v3/__https://groups.io/mt/102029967=
/7559972__;!!PvDODwlR4mBZyAb0!ToHYe5bmX6l_V4qor7SAiROwsovG8BiO5IwkcFHcTU2hj=
iGa7sgUrACTJ93aYxKM-lCRNGcfqaXaUg$
Group Owner: main+owner_at_ammrl.groups.io
-=-=-=-=-=-=-=-=-=-=-=-
Received on Wed Oct 18 2023 - 10:00:22 MST