Re: EMM386

Hi Jerry,

Further experimentation. I had left a "recovery" disk in the drive when
I booted the system, an the system booted to DOS (98 DOS?). Drives ran
poorly, or not at all. I would have thought that would have been
"clean". I will see what they build, EMM? I think I will also
investigate what interrupts are enabled, and if the timer interrupt is
chained BEFORE I get it.

I rebooted, told LILO "DOS", came up in Windoz98, and "restarted in
DOS". Drives back to normal.

Alan KM6VV
(trying to drill and tap 4-40 holes in a mushy heat sink)

Carol & Jerry Jankura wrote:

>
> Alan:
>
> My guess is that it was hooking into the timer interrupt. If I'm not
> mistaken, that's the only one that DOS actually uses. But, I didn't actually
> check it out so I can't say that as gospel.
>
> -- Jerry
>
> |-----Original Message-----
> |From: Alan Marconett KM6VV [mailto:KM6VV@...]
> |Sent: Monday, December 17, 2001 7:11 PM
> |To: CAD_CAM_EDM_DRO@yahoogroups.com
> |Subject: [CAD_CAM_EDM_DRO] Re: EMM386
> |
> |
> |Hi Jerry,
> |
> |Did you determine which interrupt EMM386 was using? I notice there IS a
> |difference between "exit to DOS" and just "coming up" in DOS with
> |Windoz98. I'm wondering if it's the same thing?
> |
> |Alan
> |
> |KM6VV
> |
> |Carol & Jerry Jankura wrote:
> |>
> |> Initially, I had problems with delivering a smooth
> |> pulse train, but this problem was caused by the EMM386.EXE driver hogging
> |> the processor when it was given control during an interrupt.
> |Once I removed
> |> the driver, I was able to pump out at least 4000 pulses per
> |second before my
> |> X motor didn't have enough torque to reliable turn the screw.
> |> -- Carol & Jerry Jankura
> |> Strongsville, Ohio
> |> So many toys, so little time....