Mail Archives: djgpp-workers/2001/08/14/13:43:16
> Does the LFN open work with devices? That is, if we use LFN open on
> devices, can we then reliably determine that they are devices?
LFN open works with devices (better than SFN does for like directory
detection). LFN handles have dev info as zero, just like LFN files. But
7160c1 fails for devices, so you don't know if the file doesn't exist
or is a device.
> For devices, we need to be able to determine other attributes (those
> which _get_dev_info returns and some others). I think we need to test
> all the IOCTL functions called by the library and see which open (SFN
> or LFN) is better.
SFN opens are better if you want dev info. But they don't work for
directory/nul opens, and they aren't good if you want to create LFNs.
> > For new files short of reopening I don't have a fix.
>
> We should solve this as well, somehow.
>
> > Another thought it to use the 71a6 information which provides a volume
> > serial number - I'm not sure how we use this yet, but this might be
> > better.
>
> is there a way to find out the drive given the serial number?
Look up table?
> > Note that on a valid handle 71a6 appears to fail for device handles,
> > which may be another hint on how to deal with devices on W2K.
>
> That's good to know, but I'm afraid I don't see how does it help with
> any of the problems we are considering. Are you suggesting to use the
> failure as a sign of a device? If so, we will need to find a way to
> distinguish between a failure-because-device and a failure-because-
> invalid-handle.
Correct, but it may be useful.
- Raw text -