Initial original import from: fuse-2.4.2-2.fc4

[captive.git] / src / libcaptive / storage / disk.c

diff --git a/src/libcaptive/storage/disk.c b/src/libcaptive/storage/disk.c
index 384dda0..2bc4d37 100644 (file)
--- a/src/libcaptive/storage/disk.c
+++ b/src/libcaptive/storage/disk.c
@@ -31,13 +31,13 @@
  * captive_disk_init:
  *
  * Creates system device "\Device\CaptiveHarddisk%d" providing readwrite access
- * to the given #image_iochannel as emulation of harddisk driver.
+ * to the given #captive_image_iochannel as emulation of harddisk driver.
  * reactos initializes "\Device\Harddisk%d\Partition0" as the whole disk
  * and each partition it founds by IoReadPartitionTable() it will create
  * as "\Device\Harddisk%d\Partition1", "\Device\Harddisk%d\Partition2" etc.
  *
  * libcaptive does not (yet?) support any partitions and it will always create
- * just the disk device for the whole given #image_iochannel.
+ * just the disk device for the whole given #captive_image_iochannel.
  * As this behaviour is a bit specific we rather create some non-standard name
  * of the device; anyway I have seen some "\Device\Harddisk%dVolume%d" on W32
  * system.
@@ -52,7 +52,7 @@ gboolean captive_disk_init(void)
 static struct captive_DriverObject disk_captive_DriverObject;
 NTSTATUS err;
 
-       g_return_val_if_fail(captive_options->image_iochannel!=NULL,FALSE);
+       g_return_val_if_fail(captive_image_iochannel!=NULL,FALSE);
 
        disk_captive_DriverObject.DiskGeometry.BytesPerSector=512;
        disk_captive_DriverObject.DiskGeometry.MediaType=FixedMedia;