[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]
Re: st: OS X new update problem
On 2/5/03 10:25, David Airey wrote
>I have problems going from compile number 355 to 356 by typing update
>all. The new executable gets extracted as StataSE.1 rather than what
>the update swap routine expects, which is StataSE.bin.
This happened to me for both the version born in mid January and the
version born on January 30th.
>The only way around this seems to be to install the original copy of StataSE
>then type update executable. Any other OS X (10.2.3) users out there
>(or Unix users) experiencing this update problem. I'm just wondering if
>it's me and only me.
Renaming StataSE.1 to StataSE.bin causes -update swap- to successfully
swap the new and old files, but I'm still having problems where Stata
refuses to launch.
As this is something for tech support, I'll send the details there.
* For searches and help try: