Mail Archives: djgpp-workers/2003/04/22/03:45:29
> Date: Mon, 21 Apr 2003 19:50:25 +0100
> From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
> >
> > --------N-215F46-----------------------------
> > INT 21 u - LAN Manager Enhanced DOS - LOCAL NetUseEnum
>
> It works fine under Windows '95, '98, 2000/XP (whichever Andrew is using). I
> expect it works under Windows NT 4 - after all, that was a "replacement" for
> LAN Manager. I expect it to work under Windows ME too.
I was worried about MS-DOS. Can someone please boot into plain DOS,
even the one from Windows 9x, and see if the function works?
> > Btw, do we have any info on how long does it take for 5F46h to do its
> > job on a typical system?
>
> Not very long! I add a one million iteration for loop executing
> get_shares_internal (which calls Int 21h/5F46h) to the test program for
> profiling. On my Athlon 850MHz running Windows '98 SE it sometimes took:
>
> 6.06 seconds for 1,000,001 calls to get_shares_internal with 1 share mapped
> 12.56 seconds for 1,000,001 calls to get_shares_internal with 2 shares mapped
> 16.50 seconds for 1,000,001 calls to get_shares_internal with 4 shares mapped
Thanks for testing.
> Other times it the times were spread over 1.5s - 2.5s, 6s-7.5s. Anyway, even
> worst-case it's not very long - < 20 microseconds.
I'm not sure the time is linear with the number of iterations: Windows
could do some kind of caching to hold the results of this lookup; if
it does, the first call will account for most of the elapsed time.
Can you see if the times are indeed linear with the number of
iterations?
- Raw text -