RE: Getting EMC to install. Was: Is EMC and RTL2.2.13 viable?

["Tim Goldstein" <tgoldste-at-mlh-services.com>]

That is the error message I was seeing if I had the period set to low in
emcfreqmot.c

I am on a AMD K6 500 and The lowest I can use is 10 as my period.

Tim
[Denver, CO]

> -----Original Message-----
> From: emc-at-nist.gov [emc-at-nist.gov]On Behalf Of Joel Jacobs
> Sent: Saturday, March 11, 2000 12:31 PM
> To: Multiple recipients of list
> Subject: Re: Getting EMC to install. Was: Is EMC and RTL2.2.13 viable?
>
>
>
> Well, changed 'PERIOD' in emcfreqmot.c to 40 and freqmot.o no longer locks
> up my pentium 100.  ./run.emc still doesn't work though and produces the
> following output:  Could sure use a clue here....
>
>
> starting emc...
> /sbin/insmod -f /lib/modules/2.2.13-rtl2.0/misc/rtl_time.o
> /sbin/insmod -f /lib/modules/2.2.13-rtl2.0/misc/rtl_sched.o
> /sbin/insmod -f /lib/modules/2.2.13-rtl2.0/misc/rtl_posixio.o
> /sbin/insmod -f /lib/modules/2.2.13-rtl2.0/misc/rtl_fifo.o
> /sbin/insmod -f /lib/modules/2.2.13-rtl2.0/misc/mbuff.o
> starting freqmod.o...done
> starting minimillio...done
> starting minimilltask...done
> running xemc...
> minimilltaskintf.cc 908: Error on axis 0.
> minimilltaskintf.cc 908: Error on axis 1.
> minimilltaskintf.cc 908: Error on axis 2.
> xemc.cc 5414: can't establish communication with emc
>
>
> Thanks.
>
>