0 0 means that the filesystem partitions will not be checked at each startup.
for showing partitions use fdisk:
fdisk /dev/hda
The number of cylinders for this disk is set to 2432.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p <--- print partitions
Disk /dev/hda: 20.0 GB, 20003880960 bytes
255 heads, 63 sectors/track, 2432 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 1217 9775521 83 NTFS
/dev/hda2 1218 1226 72292+ 83 Linux
/dev/hda3 1227 2432 9687195 83 Linux
Command (m for help): q <--- quit
now if you know the partition of your Windows system you also need to have the ntfs-filesystem option as module or fix compiled in you kernel.
Check if you got an ntfs filesystem modul with:
xxx01# modprobe -l | grep ntfs
/lib/modules/2.4.22/kernel/fs/ntfs/ntfs.o
If you got it. Load it using: "modprobe ntfs"
Verifying: lsmod
Unloading: rmmod ntfs
If you haven't got an ntfs modul, or if it is'nt fix in the kernel, you need to compile your own kernel with this settings.
After this when the module is loaded you can mount the partition with the "mount" command.
mount -t ntfs /dev/hda1 /mnt/windows
hope this helps