convert NTFS in to fat32
i want to ask that when hdd is having fat32 partition it is possible to convert in to NTFS , but when u convert it in to NTFS , then afterwards it is not possible to again change it in to fat32 so i am asking u why ?
i want to ask that when hdd is having fat32 partition it is possible to convert in to NTFS , but when u convert it in to NTFS , then afterwards it is not possible to again change it in to fat32 so i am asking u why ?
0 pts.
NTFS.sys error
I have been given a laptop to fix. The error message that comes up when you boot it up is missing/corrupt file: system32/drivers/ntfs.sys. How do I fix the computer? Suggestions appreciated. Thanks.
I have been given a laptop to fix. The error message that comes up when you boot it up is missing/corrupt file: system32/drivers/ntfs.sys. How do I fix the computer? Suggestions appreciated. Thanks.
Increasing server performance
Help reviving servers. Configuration current: 8 300GB disks in Raid 5 10000RPM Each. Total 2TB (70%Full) with an average of 68kb files tottal of 24 million files. The curent read rate is at 8MB/Sec on NTFS windows 2003 Partition. Any suggestions on increasing performance on current configuration. ...
Help reviving servers. Configuration current: 8 300GB disks in Raid 5 10000RPM Each. Total 2TB (70%Full) with an average of 68kb files tottal of 24 million files. The curent read rate is at 8MB/Sec on NTFS windows 2003 Partition. Any suggestions on increasing performance on current configuration. ...
indexes status error Chkdsk won't run on (SCSI) Disk 0 with FAT and NTFS Need advice.
System indicates indexes status error: "index entry bac3pm.ini in index $130 of file 50" and "index error bac3pm.tmp in index $130 of file 50" and system running very slowly. Attempts to repair problem are prevented, I believe, because (SCSI disk 0) C: drive was set up with a small 39MB EISA...
System indicates indexes status error: "index entry bac3pm.ini in index $130 of file 50" and "index error bac3pm.tmp in index $130 of file 50" and system running very slowly. Attempts to repair problem are prevented, I believe, because (SCSI disk 0) C: drive was set up with a small 39MB EISA...
