Re: Windows timing subroutines, how do they work?

Well.. I just downloaded the newer emc.. I'll try again. I have had
some squirrels in XP and Mach2.. I saw the table bobble once for sure
when the lil balloon popped up telling me to "stay connected for
updates".
I have never liked windows. I used to do quite well on dos. I guess
I liked knowing what the machine was doing. With windows you never
really know.. I know it sends packets of information somewhere.
Itemizes the hard drive and returns that data, pirate software beware.

Problems with the last emc? A pci parallel card I could not get
configured, the ini file on the cdrom, meaning I had to install it or
learn how to load a file off the windows drive.
I rewired my bridgeport to emc specs.. hoping.. But like another
said to me, you can spend your time building things or spend your time
working on software.

I gave away several of the EMC R44 cdroms, They make excellent
"porn" surfers, when you shut down all the bad stuff just
evaporates... ha.. the people that got them don't even have cnc machines.

I spent about six hours fixing Mach2 when I tried to install a USB
wireless network in my shop. I can try emc one more time.

David

--- In CAD_CAM_EDM_DRO@yahoogroups.com, "Jack Hudler" <yahoo@h...> wrote:
> No I think over analyzed my post.
>
> -----Original Message-----
> From: CAD_CAM_EDM_DRO@yahoogroups.com
> [mailto:CAD_CAM_EDM_DRO@yahoogroups.com] On Behalf Of Jon Elson
> Sent: Sunday, July 24, 2005 10:01 PM
> To: CAD_CAM_EDM_DRO@yahoogroups.com
> Subject: Re: [CAD_CAM_EDM_DRO] Windows timing subroutines, how do
they work?
>
> Jack Hudler wrote:
>
> >Turn off multitasking: NO. You could try elevating your process to
realtime
> >status, but I can tell you it probably will not fix your issue.
Doing so
> >would probably make the user experience unpalatable.
> >
> >You're trying to do realtime work on an operating system that isn't
> designed
> >for realtime work (Linux or Windows). Even if you use a special
realtime
> >build you just run into CPU bandwidth issues with your requirements
and the
> >requirements of other devices (clock, comports, disk, mouse, display,
> sound,
> >dma, pci, usb, etc). There are other interrupts and processes that
require
> >service and the OS has no idea that doing so will crash your
machine tool.
> >
> >
> So, you are saying that EMC (using a real-time Linux) simply has never
> worked, and
> perfoms unpredictably? The way they fixed this is to make the real
time
> extension
> to Linux able to pre-empt the kernel, and all of its tasks. The
> interrupt latency
> is around 5 uS on a 100 MHz pentium classic, and vastly faster on newer
> hardware.
> The jitter in the regularly scheduled interrupts is under 1 uS! And,
> that is an absolute,
> not some statistical average. It NEVER stutters by more than 1 uS,
> EVER, no matter
> how long you sample for.
>
> >
> >
> I've been running a servo Bridgeport mill since 1998 using EMC under
> real-time Linux,
> and I can tell you with great authority that the timing is not
corrupted
> by "clock, comports,
> disk, mouse, display, sound,dma, pci, usb, etc."
>
> Jon