The latest version of the SOSLIB is 142. I haven't created a consolidated zip since 122, but you can get the entire package via the Update Center. (Just LOG 901,2 and RUN SOSUPD.) The release notes are here and also in [901,2]soslib.html (after you update).

Many thanks to the people who have contributed samples and utilities.

When I try to update as described above, I get the following:

SOSLIB Update 2.1(110)
Checking for updates...
Error: %MIAME%\bin\sosupd.lst not created

I'm not sure why and would appreciate any help.

I can confirm Herman's results. I get the same thing under the same conditions. (This may be evidence that great minds not only think alike but make the same dumb mistakes...!!)

Ty, if there is a dumb mistake to make, I have either made it, will make it, or Frank has made it!

...and i was getting ready to stick up for you after Jack's last comment... :p

I just tried it and it worked as expected. I will admit that we've had periodic reports of the initial attempt to contact the Update Center timing out.

When you see the message "Checking for updates..." it is attempting to contact the Update Center website to request a list of what has been updated, into the file %MIAME%\bin\sosupd.lst. It waits for several seconds for the file to be created, and then will eventually give up. But in my experience, when that happens to me, it generally works fine on the second attempt. (Almost as if it the first effort is needed to blaze the trail.)

If that doesn't succeed, let's have a look at your %MIAME%\bin\UpdateCenter.debug.log file.

I'll confirm that a second try worked just fine.

Yes, it worked for me too. By the way, when I get the message box that says "Please wait for the update to complete - then click OK to display the notes.", nothing ever indicates when it is complete. How do I know when it is complete?

Hmmm...
Regarding the need for a second try, it remains a mystery. The Internet doesn't normally work that way. Maybe we all have routers that need to be warmed up?

As for knowing when it is complete, indeed that is a bit misleading. What happens under Windows is that an instance of A-Shell launches an independent instance of the Update Center to do the update. In the case of SOSUPD, there is no need for A-Shell to be shut down, it just sits there waiting ..., but it has no good way of knowing when the update is complete, since the update is being handled by a totally separate process. On the other hand, it really makes no difference in this case whether you wait or not, since updating RUN programs and source modules does not conflict with anything. The one exception would be if you were VUEing a file that the Update Center was trying to update.

I guess that the general principle is that once the Update Center window disappears, it's done. And if you're not sure if you were paying attention, you can always run it again (hopefully the next time it will say that there are no updates available.)

(Note that unlike ASHUPD, SOSUPD is purely a developer tool, so the fact that the user interface is a bit ragged is hopefully not a major shortcoming.)

No problem with sosupd. I can try twice and was just wondering about the time of completion. I guess the Update Center window disappeared so fast, I didn't think that that was an indication. It's all fine with me. Don't spend any time for me on this. I can easily try twice.