+
+Project Home
+------------
+
+http://www.jankratochvil.net/
+
+
+Overview
+--------
+
+Any errors from 'captive-lufs' are written to '/var/log/messages'.
+
+Needed drivers (at least ntoskrnl.exe+ntfs.sys) must be in '/var/lib/captive'.
+
+'captive' package creates 'captive' user and 'captive' group on your system.
+
+
+Drivers Availability
+--------------------
+
+All the source packages involved in this project are GNU General Public License
+2.0 (GPL-2.0) compatible (see the file "AUTHORS" for details). The purpose of
+this project is to run the original Microsoft Windows drivers to get the best
+filesystem compatibility and safety ever reachable. This is the method known
+most by the Wine http://www.winehq.com/ project. Required driver files:
+
+ ntoskrnl.exe - Windows NT kernel; required for ANY use of this project.
+ ntfs.sys - NTFS filesystem driver; required to access NTFS disk drives.
+
+Run captive-install-acquire(1) installer for proper guided steps.
+
+
+Packaged Installations
+----------------------
+
+Required W32 drivers were automatically found if Microsoft Windows XP is
+installed on any NTFS or FAT partitions. FAT partitions must be already
+mounted. You may want to run captive-install-acquire(1) to check the drivers
+state and possibly update them. Installer uses X Windows or console
+automatically.
+
+Any NTFS disk partitions were automatically added to /etc/fstab.
+These partitions are now available for mount by
+ mount /mnt/captive-DISK_LABEL
+
+NTFS disk drives can be also mounted by
+ mkdir /mnt/drive-c
+ mount -t captive-ntfs /dev/hda1 /mnt/drive-c
+
+
+If you do not use the captive-install-acquire(1) installer you may also
+copy the drivers yourself - at least "ntoskrnl.exe" and "ntfs.sys".
+They should be stored in '/var/lib/captive' directory (lowercased filenames).
+These driver must be from Microsoft Windows XP while
+Service Pack 1 Check Build U.S. is their preferred version:
+ http://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/checkedbuild.asp
+
+
+Command-line client access only:
+
+NTFS disk drives can be also accessed without Linux kernel support by:
+ captive-cmdline \
+ --load-module=/var/lib/captive/ntoskrnl.exe \
+ --filesystem=/var/lib/captive/ntfs.sys \
+ --sandbox-server=/usr/sbin/captive-sandbox-server \
+ --bug-pathname=/tmp/captive-bug-%FT%T.captivebug.xml.gz \
+ --disk --rw /dev/hda1
+ (Backslash end-of-line characters '\' to be omitted for line continuation.)
+
+In the case of 'sandbox' invocation error it can be also run directly but
+read/write (--rw) mode is definitely discouraged in such case:
+ captive-cmdline \
+ --load-module=/var/lib/captive/ntoskrnl.exe \
+ --filesystem=/var/lib/captive/ntfs.sys \
+ --disk --rw /dev/hda1
+ (Backslash end-of-line characters '\' to be omitted for line continuation.)
+
+
+Gnome-VFS aware applications can access NTFS disk drives by:
+ gnomevfs-info file:///dev/hda1#captive-ntfs:/config.sys
+ gnomevfs-copy file:///dev/hda1#captive-ntfs:/config.sys /tmp/
+You can replace 'captive-ntfs' by other supported methods, see:
+ /etc/gnome-vfs-2.0/modules/captive.conf
+
+(Gnome-VFS client is not contained in 'captive-static' package.)
+
+
+
+Source Installations
+--------------------
+
+Case #1 - All packages installed:
+ ./configure --enable-lufs --enable-install-pkg
+Case #2 - Packages without installer:
+ ./configure --enable-lufs
+Case #3 - Command-line client (or Gnome-VFS) access only:
+ ./configure
+'configure' will compile 'Case #1' or 'Case #2' automatically if possible
+when run with no arguments. For generic instructions see the file 'INSTALL'
+otherwise run:
+ ./configure --help
+
+Compile by:
+ make
+
+Now you have './src/client/cmdline/captive-cmdline' available for testing.
+
+Manual addition of user and group 'captive' is required for '--sandbox-server'.
+User 'captive' should have its group 'captive'. Login should be forbidden.
+Commands may vary on your system, please consult groupadd(8) and useradd(8):
+ groupadd captive
+ useradd -g captive -r -s /sbin/nologin captive
+
+Later you may invoke standard:
+ make install
+
+Both these steps will be suggested during 'make install' if appropriate:
+You may need to add '/usr/local/lib' line (without quotes) to your
+'/etc/ld.so.conf' file. You may also need to run as 'root' user:
+ ldconfig
+
+
+Bug Reporting