Don:
Many thanks, that seems to have solved it. It also explains why it appeared to be intermittent. I must have drifted between modes for other reasons and not been paying attention.
It is also interesting to note, for anyone else with interest in this sub area of the calculator, that with mode set to, "EXACT" in the CAS screen, any subsequent attempt to use the ADDTMOD command when in, "DEGREES" mode will create a warning prompt/buzz/request to change to, "RADIAN" mode for the degree unit. Then it will calculate and provide the correct answer for the value set in the MODULO variable.
Again, thanks, I did find a work around to the problem at hand, but the on again off again nature of this was driving my buggy. So to speak.
--- In 50g@yahoogroups.com, Don Hart <ddhart1@...> wrote:
>
> I think you have to be in EXACT mode for ADDTMOD to work. Toggle between EXACT & APPROX with: Rightshift held down & press enter.
>
> ~~~
> ASCII shall receive, Hollerith and get it quicker
>
>
> --- On Wed, 4/25/12, Richard <rgking78@...> wrote:
>
> > From: Richard <rgking78@...>
> > Subject: [50g] ADDTMOD Error Condition, Help?
> > To: 50g@yahoogroups.com
> > Date: Wednesday, April 25, 2012, 8:54 AM
> > I am probably missing something
> > simple, but I am having intermittent problems with Modulo
> > Arithmetic via both the soft keys and when using the ADDTMOD
> > command within a program.
> >
> > And it is the intermittent part that is driving me
> > crazy. I'll put two integers on the stack, and then
> > when I try to execute the command, I get a generic, "Bad
> > Argument Type" error condition.
> >
> > Any suggestions? Many thanks in advance.
> >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> > 50g-fullfeatured@yahoogroups.com
> >
> >
>
