Re: file names, symbolic links
From: Peter Wieland [MSFT] (peterwie_at_online.microsoft.com)
Date: 06/02/04
- Next message: Eliyas Yakub [MSFT]: "Re: Official support for MmFrameBufferCached?"
- Previous message: Michael S: "Official support for MmFrameBufferCached?"
- In reply to: finecats: "RE: file names, symbolic links"
- Next in thread: finecats: "Re: file names, symbolic links"
- Reply: finecats: "Re: file names, symbolic links"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 2 Jun 2004 10:10:48 -0700
why do you need the target of the symbolic link in the kernel? The symbolic
links are generally there for a reason (like they provide a well-known name
link to an object whose name can change each boot) so in most cases you're
better off reporting or saving the symbolic link name rather than the actual
object name.
-p
-- This posting is provided "AS IS" with no warranties, and confers no rights. "finecats" <finecats@noemail.noemail> wrote in message news:E8CF84FB-3AF3-4EA3-8687-81BFAA4FF81B@microsoft.com... > This API appears to be part of win32 and not part of kernel mode > programming? Could you please clarify that. I need an api to be called > from kernel mode. > Thanks > Finecats > > ----- Bart Bartel [MSFT] wrote: ----- > > The API QueryDosDevice(szDriveLetter, szNtDeviceName, MAX_PATH) takes > the > drive letter and returns the \Device\HarddiskVolumeX string in the > second > argument. The sample code for this is in the Base Win32 SDK in the > Samples\winbase\IO\DLEdit directory. > > This posting is provided "AS IS" with no warranties, and confers no > rights
- Next message: Eliyas Yakub [MSFT]: "Re: Official support for MmFrameBufferCached?"
- Previous message: Michael S: "Official support for MmFrameBufferCached?"
- In reply to: finecats: "RE: file names, symbolic links"
- Next in thread: finecats: "Re: file names, symbolic links"
- Reply: finecats: "Re: file names, symbolic links"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|