Introduction - Updating Windows 2000 ifs drivers to Windows xp

|
Updating Windows 2000 ifs drivers to Windows xp
|
bet | 2/9 | Sana | 22.07.2021 | Hajmi | 124 Kb. | | #15612 |
This document is a checklist for developers of file systems and file system filter drivers who are developing or porting Windows 2000 drivers to run under Windows XP, including information about new features. Readers should be familiar with Windows 2000 file systems. The document does not attempt to describe each of these issues fully, but is intended to help developers keep track of the various issues that they should consider.
New Features
Item
|
Description
|
WebDAV Redirector
|
Windows XP builds 2269 and later include a new component: the WebDAV redirector.
The WebDAV redirector allows applications on Windows XP to connect to and natively read and write data on Internet sites. The WebDAV redirector uses the WebDAV protocol, an extension to HTTP that allows data to be written to HTTP targets. The WebDAV redirector provides file system-level access to these servers in the same way that the existing redirector provides access to SMB and CIFS servers.
You can access an existing WebDAV share using the "net use" command, as in the following example:
NET USE * http://webserver/davscratch
To connect to an MSN Web Community, use http://www.msnusers.com/yourcommunityname/files as the target. The credentials you need in this case are your Passport credentials. (For more information about Passport, see http://www.passport.com.) You can enter you Passport credentials in the "connect using different user name" dialog if you are using map network drive, or use the /u: switch with the NET USE command, as shown in the following example:
NET USE http://www.msnusers.com/yourcommunityname/files /u:yourpassportaccount@hotmail.com
Note: You will need to install build 2290 or later to get access to the MSN Web Communities.
You can also create your own WebDAV server using Internet Information Server (IIS) or MSN Communities.
With the IIS 5.0 implementation of WebDAV, you can allow remote authors to move, search, edit, or delete files and directories–as well as their properties–on your server. WebDAV is configured using the Web server permission settings. For more information, see http://www.microsoft.com/windows2000/techinfo/howitworks/iis/iis5techoverview.asp
File Cabinets in MSN Communities are WebDAV shares. For more information, see http://communities.msn.com/filecabinets.
Further information about WebDAV is available from http://www.webdav.org.
|
System Restore
|
System Restore is a combination of file system filter driver and user-mode services that provide a way for users to unwind configuration operations and restore a system to an earlier configuration.
System Restore is a feature of Windows XP Personal and Professional SKUs only. It is not in Server-based SKUs.
System Restore includes a file system filter driver, SR.SYS, which helps to implement a copy-on-write process by which older copies of files are backed up. Specifically, SR.SYS logs the necessary information about changes to application files so that these changes can be undone at a later time.
|
64-bit Intel Itanium support
|
For information about 64-bit Intel Itanium support, see
http://www.microsoft.com/whdc/system/platform/64bit/default.mspx
|
Volume Snapshot Service
|
A snapshot of a volume is a point-in-time copy of that volume. The snapshot is typically used by a backup application so that it may backup files in a consistent manner, even though they may really be changing during the backup. Windows XP includes a framework for orchestrating the timing for a snapshot, as well as a storage filter driver (not a file system filter driver) that uses a copy-on-write technique in order to create a snapshot.
File system filter drivers, such as antivirus programs, that need to fail an operation that would otherwise write to a read-only snapshot should return STATUS_MEDIA_WRITE_PROTECTED.
One important new snapshot-related IOCTL that affects file systems is IOCTL_VOLSNAP_FLUSH_AND_HOLD_WRITES. This is actually intended for interpretation by file systems, even though it is an IOCTL. This is because all file systems should pass the IOCTL down to a lower-level driver that is waiting to process the IOCTL after the file system. The choice of an IOCTL instead of an FSCTL ensures that even legacy file system drivers will pass the IOCTL down.
This IOCTL is sent by the Volume Snapshot Service. When a file system, such as NTFS, receives the IOCTL, it should flush the volume, and hold all file resources to make sure that nothing more gets dirty. When the IRP completes or is cancelled, the file system then releases the resources and returns.
IOCTL_VOLSNAP_FLUSH_AND_HOLD_WRITES is documented in the Volume Snapshot SDK.
|
|
| |