Andrew wrote:
> Yes, please email it to me, too!
Sorry, you should have mailed me since I've been too busy to keep up
with the group. Do you still want it?
> If you are a guru about writing dos-Drivers:
> Can I log several interrupts (initialising driver, driver-functions),
> (as detailed as Do
The below text is 100% correct.
In our office, with Hog set to 1 (the slowest setting) printing took 60
seconds or so.
I set everyone in the office to 5 and I set the people who write the
checks to 8. ;-)
That got printing down to about 15-20 seconds for the people set to 5
and 3-4 seconds for
"Steve K. Sears" wrote:
> Got it down to 35 seconds before it starts to print by following your
> suggestion. Still don't know why it takes that long to process a 2K
> ASCII file.
> I thought maybe dosemu was hogging all the resources (from reading
> previous threads),
When dosemu hogs CPU, it ac
Got it down to 35 seconds before it starts to print by following your
suggestion. Still don't know why it takes that long to process a 2K
ASCII file.
I thought maybe dosemu was hogging all the resources (from reading
previous threads), but it only takes about 1% when this program runs (or
even p
