Hi,
try the following two commands:
sysuse auto
twoway line l w, lc(red)
this benchmark should work on all Stata versions, flavours, and platforms.
If it does not work, then some of the ADO files responsible for
handling graphics might become corrupted (perhaps during an update).
Make sure that you have not created your own command -twoway- which
has priority in -adopath- over the standard -twoway-.
Best regards,
Sergiy
On 8/15/07, Davide Cantoni <[email protected]> wrote:
> Thanks for your comments, Mike, but I'm afraid the problem is still
> there. Getting to your questions:
>
> - Both versions are abolutely up-to-date, using update all and update
> swap afterwards.
>
> - I entered exactly the same commands on both computers. Up to the
> last comma, parenthesis, line continuation sign.
>
> - I did not copy the command code in my previous email, defiying, the
> FAQ's, because I did not consider it essential to the problem that
> lcolor does not work in any case. But here is one example:
>
> . twoway (line difftosynth_10000 year, lcolor(black)) (line
> difftosynth_65 year, lcolor(gs12))
> option lcolor() not allowed
> r(198);
>
> It does not work in a simpler case, either:
>
> . twoway line difftosynth_10000 year, lcolor(black)
> option lcolor() not allowed
> r(198);
>
> - Again, all of these very same commands work on that other computer
> running WinXP.
>
> - Now that I am trying, here's another thing that does never work: lpattern():
>
> . twoway line difftosynth_10000 year, lpattern(dash)
> option lpattern() not allowed
> r(198);
>
> I have no clue at this point. Thanks for any suggestions, once again.
>
> Davide Cantoni
>
>
>
>
> On Aug 15, 2007, at 10:28 AM, Michael Hanson wrote:
>
> In my experience, the purported Mac vs. PC aspect of your problem is a
> red herring. More likely, one of the two following situations exist:
>
> 1. You have not entered *exactly* the same commands on both computers.
> The error you report can be caused by a misplaced comma or
> parentheses, or possibly by forgetting a line continuation (such as
> "///") -- all of which are difficult to spot with the unaided eye.
>
> Relatedly, you have not followed the advice of the Statalist FAQ: "Say
> exactly what you typed and exactly what Stata typed (or did) in
> response. N.B. exactly!" To reiterate: *exactly*!
>
> 2. Your version of Stata is not completely up-to-date on your Mac,
> relative to the PC you tried. Type -update all- and follow the advice
> given. Don't forget to "swap" the executable if instructed to do so.
> (That is, launch the new Stata program that is placed in your
> /Applications/Stata folder -- don't keep running the outdated one.) A
> less-than-complete update could create an environment in which
> standard commands produce non-standard results or errors.
>
> Hope this helps.
>
> -- Mike
> *
> * For searches and help try:
> * http://www.stata.com/support/faqs/res/findit.html
> * http://www.stata.com/support/statalist/faq
> * http://www.ats.ucla.edu/stat/stata/
>
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
