Sender: rich AT phekda DOT freeserve DOT co DOT uk Message-ID: <3EA2B7E2.E83694EA@phekda.freeserve.co.uk> Date: Sun, 20 Apr 2003 16:08:18 +0100 From: Richard Dawe X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586) X-Accept-Language: de,fr MIME-Version: 1.0 To: Eli Zaretskii CC: acottrel AT ihug DOT com DOT au, djgpp-workers AT delorie DOT com Subject: Re: fstat, fd_props and inventing inodes, revision 3 [PATCH] References: <003101c30704$8dbb1ea0$0100a8c0 AT acp42g> <000a01c30708$aacbc680$0100a8c0 AT acp42g> <3EA2685E DOT 725043BC AT phekda DOT freeserve DOT co DOT uk> <8296-Sun20Apr2003135633+0300-eliz AT elta DOT co DOT il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. Eli Zaretskii wrote: > > > Date: Sun, 20 Apr 2003 10:29:02 +0100 > > From: Richard Dawe > > > > It's interesting that 'getshare' doesn't know > > about unavailable disks. The code doesn't ignore unavailable disks, so it > > looks like your OS (Win2k/XP?) doesn't report unavailable disks via the > > LANMan APIs. > > Actually, I'm guessing that unavailable disks simply return an error > when you call Int 21h/AX=5F46h. That is, they don't show in the list > returned by that function. But that's just a guess. There's only one call to get the list of shares. So if it returns an error for unavailable disks, the whole call should have failed and Andrew should have seen no mappings listed by the test program. Presumably you mean that the error is an internal error in the code implementing Int 21h/AX=5F46h, so that it just ignores that drive and returns no information for it? That seems a bit odd, when there is a status field in the use_info_1 structure (which I called "share_info" in the code). Thanks, bye, Rich =] -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]