This morning I ran ashupd version 1.2(119) and received a new UpdateCenter.exe. A-Shell could not restart. I found that ashw32.exe had been renamed to ashw32.exe.tmp, but apparently was not renamed back to ashw32.exe. I don't have this in the standard vm directory and this may have something to do with it. Changing the name backed to ashw32.exe seems to have solved the problem.

Let's have a look at your updatecenter.log file (in the same directory as the updatecenter.exe). Them tmp file is a normal intemediate stage in the operation (the UpdateCenter wants to make sure it can download all the critical files before starting to replace any) but I'm not sure why it failed to get renamed or why you got a new UpdateCenter.exe in the first place. What version of UpdateCenter.exe do you have now?

The version now is 1.0.2734.17534. There is an UpdateCenter.log and an UpdateCenterDebug.log so I have emailed them to you.

I must admit I'm a little confused about the current version of the Update Center itself.

As for the log files, I do see a couple of anomalies:

[6/27/2007 8:59:52 AM] ERROR launching temporary update center on retry 1 (Access to the path "C:\company shared folders\proscript\bin\UPDATECENTER.TEMP.EXE" is denied.)
[6/27/2007 8:59:55 AM] Executing UpdateCenter Temporary ("C:\company shared folders\proscript\bin\UPDATECENTER.TEMP.EXE") with the following arguments: ashw32 -D"c:\company shared folders\proscript\" -BU"http://updatecenter.microsabio.net/" -I"C:\company shared folders\proscript\bin\UpdateCenter.ini"

followed by

[6/27/2007 8:59:58 AM] ERROR deleting temporary file (Access to the path "C:\company shared folders\proscript\bin\UPDATECENTER.TEMP.EXE" is denied.)

and then

[6/27/2007 9:00:06 AM] Downloading files...
[6/27/2007 9:00:06 AM] ERROR while updating! (Specified argument was out of the range of valid values.
Parameter name: '0' is not a valid value for 'displayIndex'.)
[6/27/2007 9:00:06 AM] Deleting temporary files...
[6/27/2007 9:00:06 AM] ERR Error while updating! (Cancelled by user!)

I need to confer with Jorge about this (although he has been so busy with LEO that I'm almost afraid to disturb him.)

I don't think this is of great concern to me. Let's let Jorge work on Leo. I am enjoying the newly found world of GUI (thanks Jorge ) and I'm not sure I want Leo taking all the fun away!

Hi,

But I'm here, please don't say that, or you will make me feel guilty on each of my next requests for help

Now, the problem on UpdateCenter...
Herman - did you stollen from here the source of it and changed it?
I don't know how you can have an higher version than me
The current version is 1.0.2664.31263.
But in fact, if I execute ASHUPD now, I receive that version.
Jack - Maybe you published a corrupted EXE file?

This is a quick response w/o any study, I'll be back later.

(crossed posts)

You're very kind Herman, and I'm very happy to know if I contributed in some way to put you in the GUI world, but I'm afraid to say that, in my opinion, Leo will not take the fun away, but add more fun :rolleyes:

It seems that, this morning (in Portugal), during half an hour, by mistake, there was on-line an updatecenter.exe with a TRACE in it.
Apparently, the only noticeable strange behavior should be a message popping up with an Ok button.

Right now, I made an ASHUPD and received the new updatecenter.exe, and everything is working fine.

Herman - I suggest you check in your "c:\company shared folders\proscript" folder for the existence of any *.TEMP.* file and delete any, after execute again the ASHUPD. I guess everything will be back to normal.

Jack & anyone who had problems with this - Sorry about that

Regards

I'm not aware of having posted an updated UpdateCenter.exe, but then again, I'm not sure now exactly how that module gets updated. I have an updatecenter.microsabio.net/updatecenter.zip file, and also an updatecenter.microsabio.net/UpdateCenter/UpdateCenter.exe.zip

Did I create those or did you? Also, are we standardizing now on the updated version you posted a few weeks ago. I'm confused now as to which version that is.

Note ASHUPD uses the -NOSELFUPDATE switch was a temporary measure to avoid the confusion of possibly updating/downdating itself, but when Herman ran the older version of ASHUPD, it wouldn't have had that switch in the command line.

I think we need to resync our versions of the UpdateCenter itself.

When I went to run ashupd (version 1.2(119), I got a slew (that's a lot in LA) of lits that were going to be updated. Before I actually run it, is that correct?

Some of the lits were do.lit, host.lit, ismdmp.lit, ismutl.lit, etc.

That doesn't sound right to me. Those LITs have not changed in awhile.

Jorge - sorry to say this in public - but it would sure be nice if the Update Center understood RUN and LIT file versions!

I'm guessing that in the process of all the futzing around you somehow got the file modification dates changed on your local installation, and since the UpdateCenter doesn't understand LIT file versions, it has only the file modification dates to go on. So it's probably OK, but definitely anomalous.

You are right, all the lits were the same version as what I had. I did think I saw A-Shell version 5.0.990.9 but it still shows 5.0.990.8. Just a FWIW.

Jack -
I don't know if you still keep that -NOSELFUPDATE switch, otherwise I shouldn't receive also an update for the updatecenter.exe (and I'm running the last ASHUPD.LIT 1.2(119))
And I think you really shouldn't use it, and let it check for updates, otherwise, it will be one more thing to worry about sending you any update, what is not a problem, and if you prefer we can go that way.

...

In the meantime, checking here with Filipe all the steps to find out a reason for what happened, it seems plausible that, Herman got the version with the TRACE message that caused an unexpected situation.
As I mentioned, please, try again and check if this time everything runs w/o problem.

PS: Probably another updatecenter.exe update will take place soon; we found that if the user makes some quick clicks, could cause problems.

Regards

Does the Update Center know where to look for it's own updates? I thought that originally, it was assume to be in a subfolder of the location where it was getting the target product update. If it always goes to updatecenter.firmaware.com, then should I remove the references to Updatecenter.zip and Updatecenter/UpdateCenter.exe.zip from updatecenter.microsabio.net?

I'm listening well OK reading with interest

Yes, the updatecenter only checks for updates in "updatecenter.firmaware.com", so you can just delete your folder "Updatecenter" in "updatecenter.microsabio.net".

Please, remove the -NOSELFUPDATE switch from your command, on the next update, everybody using ASHUPD will receive the new ASHUPD.LIT, but it will still run with -NOSELFUPDATE, so it will be necessary to run ASHUPD a second time to execute it w/o that switch and, this time, a new updatecenter.exe will be downloaded.

As for the RUN, LIT (you forgot SBX's, Herman didn't like that ) versions, it's on the list, now I moved it to the top

Talking about updates, there is an update for UpdateCreator (click in Check for updates)...now you can call it by command:
updatecreator.exe [INI filename] [BACKUP]
(use BACKUP if you want a backup before update)

PS: I forgot about this message unfinished here, hope it's still useful

Muito bem, obrigado. I'll post an update later tonight, which will probably be 5.0.991.

Por nada, eu é que agradeço

Jorge, you didn't teach me all of that!

Well, but I'm sure you will remember this...

Quinta do Esporão - Alentejo :rolleyes:

Yes, Jorge, and I'm ready for my next lesson! I have not stopped talking about my trip.

And Jack, Sandy said in light of the fact you didn't go, you should be saying "Muito bem, obrigada". Actually, maybe she wasn't the one that said that.

Ouch! (That's Portuguese for "ouch!", and mercifully gender-neutral.)

Who would have thought that beneath all that Southern Belle demure charm and allure, lurked all the compassion of jacarés? (That's Portuguese for alligators.)

Até à vista,
O Senhor Macho

Pesaroso. (That's Portuguese for sorry)

Não faz mal. Tudo é bem.
(That's Portguese for your mother wears army boots.)

Ty... how long are you going to tolerate this banter??!!

I'm biting my tongue (fingers?), Frank. Of course, I think it all started with your sexist joke, so you're first on my list of people to whom I should be issuing stern reminders about the serious and professional nature of our bulletin board. Then there's the problem of reprimanding the guy who runs the show, and of course that's always awkward.

So I'm stymied, at least for the moment, though feeling very anxious and distraught about all these bad jokesters running amok...

Doh...