I realize that. The way NAV works is that the scanner process itself does
the scanning on behalf of the invoking process and thus gets the CPU, or
that's my limited understanding. But like I said, the problem disappeared
after another update from Symnatec, so they must have corrected whatever
o point an
accusatory finger at. I might take some time and put a dev build of ant
on and see if I can narrow down where the pause occurs. It must be very
early in the ant startup, however.
--Joe
________
Joseph Millar <[EMAIL PROTECTED]>
Principal S
hile it
did find a Core update, after installation and rebooting, the problem
still exists.
I figure I can't be the only one in the world using ant and NAV 2004, so
I'm hoping someine can either tell me what my issue is, or confirm the
problem.
Anyone?
--Joe
___
