|
|
Windows 98 Scandisk will not run
Scandisk will not run because it reports there is not enough "available
memory". I've tried shutting down the majority of programs that run in the background but Scandisk keeps reporting insufficient available memory. What else can be preventing scandisk from functioning properly? |
Scandisk reports insufficient memory if the drive is partitioned with too
many sectors. Has Scandisk ever worked properly with this drive? You can check the number of sectors using CHKDSK from DOS (it calls them 'allocation units"). -- Jeff Richards MS MVP (Windows - Shell/User) "lugnut554" wrote in message ... Scandisk will not run because it reports there is not enough "available memory". I've tried shutting down the majority of programs that run in the background but Scandisk keeps reporting insufficient available memory. What else can be preventing scandisk from functioning properly? |
I don't think I've run scandisk on this drive--at least not from Windows. The
drive is 160 Gb and is not partitioned. What is the largest partition scandisk can work with? "Jeff Richards" wrote: Scandisk reports insufficient memory if the drive is partitioned with too many sectors. Has Scandisk ever worked properly with this drive? You can check the number of sectors using CHKDSK from DOS (it calls them 'allocation units"). -- Jeff Richards MS MVP (Windows - Shell/User) "lugnut554" wrote in message ... Scandisk will not run because it reports there is not enough "available memory". I've tried shutting down the majority of programs that run in the background but Scandisk keeps reporting insufficient available memory. What else can be preventing scandisk from functioning properly? |
How many clusters (or allocation units) did CHKDSK report? It is not the
partition size, but number of clusters, that Scandisk is concerned about. Your drive must be partitioned or you can't install Windows, so I presume you mean it is partitioned as a single primary partition. You won't be able to use Scandisk with a partition of that size, and you can't even reliably run Windows like that without a lot of additional support. Unless you have specially prepared the system to cope with a drive of this size I would recommend that you use motherboard, disk controller or disk drive features to limit the disk drive size to 127Gb. As a matter of personal preference, I would recommend that you create several partitions for the drive. -- Jeff Richards MS MVP (Windows - Shell/User) "lugnut554" wrote in message ... I don't think I've run scandisk on this drive--at least not from Windows. The drive is 160 Gb and is not partitioned. What is the largest partition scandisk can work with? "Jeff Richards" wrote: Scandisk reports insufficient memory if the drive is partitioned with too many sectors. Has Scandisk ever worked properly with this drive? You can check the number of sectors using CHKDSK from DOS (it calls them 'allocation units"). -- Jeff Richards MS MVP (Windows - Shell/User) "lugnut554" wrote in message ... Scandisk will not run because it reports there is not enough "available memory". I've tried shutting down the majority of programs that run in the background but Scandisk keeps reporting insufficient available memory. What else can be preventing scandisk from functioning properly? |
"lugnut554" wrote in message ... I don't think I've run scandisk on this drive--at least not from Windows. The drive is 160 Gb and is not partitioned. What is the largest partition scandisk can work with? Using FAT32, the largest drive can be up to 2 terabytes [2047 GB], based on the 32 KB cluster size limitation. The largest possible file for a FAT32 drive is 4 GB minus 2 bytes. ScanDisk has a couple of restrictions: A Maximum Number of Files in a Directory Drive Cluster Size Max # of Directory Files -------------------------------------------------- 512 bytes (floppy) ~ 1280 give or take 16 2K ~ 5120 give or tak e 64 4K ~10240 give or take 256 8K ~20480 give or take 1024 16K ~40960 give or take 4096 32K ~81920 give or take 16384 B ScanDisk will balk with an out-of-memory error if you have a hard disk that is larger than 8 GB that has a cluster size that is smaller than 8 KB. The standard FAT32 cluster size of 4,096 bytes applies only to hard disks that are smaller than 8 GB. You will also receive this error with a very large hard disk that has a default Windows cluster size of 32 KB. C If you use the protected-mode (graphical) version of ScanDisk to perform a thorough scan (which includes a surface scan) on an IDE hard disk that is larger than 32 GB in size, ScanDisk may report errors on every cluster after approximately cluster number 967,393. http://support.microsoft.com/kb/243450/EN-US/ D Windows 98 provides two versions of ScanDisk: a graphical Windows-based version (Scandskw.exe) that you can run from the Start menu or from Windows Explorer, and an MS-DOS-based version (Scandisk.exe) that is contained in the \Windows\Command folder. Running Scandisk.exe while in Windows will invoke Scandskw.exe. ScanDisk cannot find or fix errors on CD-ROM drives, network drives, or drives created by using Assign, Subst, Join, or Interlnk. E ScanDisk cannot automatically fix errors if a file name (including the file's full path) exceeds 259 characters. This includes file names in the MS IE cache folder. If this occurs, empty the cache and try ScanDisk again. F The ScanDisk tool included with Microsoft Windows 95 and Microsoft Windows 98 is a 16-bit program. Such programs have a single memory block maximum allocation size of 16 MB less 64 KB. Therefore, The Windows 95 or Windows 98 ScanDisk tool cannot process volumes using the FAT32 file system that have a FAT larger than 16 MB less 64 KB in size. A FAT entry on a volume using the FAT32 file system uses 4 bytes, so ScanDisk cannot process the FAT on a volume using the FAT32 file system that defines more than 4,177,920 clusters (including the two reserved clusters). Including the FATs themselves, this works out, at the maximum of 32 KB per cluster, to a volume size of 127.53 gigabytes (GB). For a full treatise on ScanDisk, go to this List of Articles About the ScanDisk Tool http://support.microsoft.com/default...b;en-us;287914 See also Chapter 10 [Disks and File Systems] of the Windows 98 Resource Kit at http://www.microsoft.com/resources/d...t2/wrkc10.mspx |
The file system (FAT32 etc) does not impose a maximum drive size. The file
system is only concerned with a maximum partition size. It's the BIOS and the way that the OS uses the BIOS that imposes a drive size limitation. The table of cluster sizes and directory files (sic) is wrong - FAT32 allows 65k entries per directory regardless of cluster size and makes no distinction between entries that are files, folders, or long filenames. The rest is not related to maximum partition size, except for the bit about a maximum number of clusters before Scandisk throws the out-of-memory error. -- Jeff Richards MS MVP (Windows - Shell/User) "Hugh Candlin" wrote in message ... "lugnut554" wrote in message ... I don't think I've run scandisk on this drive--at least not from Windows. The drive is 160 Gb and is not partitioned. What is the largest partition scandisk can work with? Using FAT32, the largest drive can be up to 2 terabytes [2047 GB], based on the 32 KB cluster size limitation. The largest possible file for a FAT32 drive is 4 GB minus 2 bytes. ScanDisk has a couple of restrictions: A Maximum Number of Files in a Directory Drive Cluster Size Max # of Directory Files -------------------------------------------------- 512 bytes (floppy) ~ 1280 give or take 16 2K ~ 5120 give or tak e 64 4K ~10240 give or take 256 8K ~20480 give or take 1024 16K ~40960 give or take 4096 32K ~81920 give or take 16384 B ScanDisk will balk with an out-of-memory error if you have a hard disk that is larger than 8 GB that has a cluster size that is smaller than 8 KB. The standard FAT32 cluster size of 4,096 bytes applies only to hard disks that are smaller than 8 GB. You will also receive this error with a very large hard disk that has a default Windows cluster size of 32 KB. C If you use the protected-mode (graphical) version of ScanDisk to perform a thorough scan (which includes a surface scan) on an IDE hard disk that is larger than 32 GB in size, ScanDisk may report errors on every cluster after approximately cluster number 967,393. http://support.microsoft.com/kb/243450/EN-US/ D Windows 98 provides two versions of ScanDisk: a graphical Windows-based version (Scandskw.exe) that you can run from the Start menu or from Windows Explorer, and an MS-DOS-based version (Scandisk.exe) that is contained in the \Windows\Command folder. Running Scandisk.exe while in Windows will invoke Scandskw.exe. ScanDisk cannot find or fix errors on CD-ROM drives, network drives, or drives created by using Assign, Subst, Join, or Interlnk. E ScanDisk cannot automatically fix errors if a file name (including the file's full path) exceeds 259 characters. This includes file names in the MS IE cache folder. If this occurs, empty the cache and try ScanDisk again. F The ScanDisk tool included with Microsoft Windows 95 and Microsoft Windows 98 is a 16-bit program. Such programs have a single memory block maximum allocation size of 16 MB less 64 KB. Therefore, The Windows 95 or Windows 98 ScanDisk tool cannot process volumes using the FAT32 file system that have a FAT larger than 16 MB less 64 KB in size. A FAT entry on a volume using the FAT32 file system uses 4 bytes, so ScanDisk cannot process the FAT on a volume using the FAT32 file system that defines more than 4,177,920 clusters (including the two reserved clusters). Including the FATs themselves, this works out, at the maximum of 32 KB per cluster, to a volume size of 127.53 gigabytes (GB). For a full treatise on ScanDisk, go to this List of Articles About the ScanDisk Tool http://support.microsoft.com/default...b;en-us;287914 See also Chapter 10 [Disks and File Systems] of the Windows 98 Resource Kit at http://www.microsoft.com/resources/d...t2/wrkc10.mspx |
To add to the others. See:
http://support.microsoft.com/default...;EN-US;q229154 -- Mikhail Zhilin http://www.aha.ru/~mwz Sorry, no technical support by e-mail. Please reply to the newsgroups only. ====== On Wed, 12 Jan 2005 15:35:03 -0800, lugnut554 wrote: Scandisk will not run because it reports there is not enough "available memory". I've tried shutting down the majority of programs that run in the background but Scandisk keeps reporting insufficient available memory. What else can be preventing scandisk from functioning properly? |
lugnut554 wrote:
Scandisk will not run because it reports there is not enough "available memory". I've tried shutting down the majority of programs that run in the background but Scandisk keeps reporting insufficient available memory. What else can be preventing scandisk from functioning properly? [...] I don't think I've run scandisk on this drive--at least not from Windows. The drive is 160 Gb and is not partitioned. What is the largest partition scandisk can work with? lugnut, Yes it is absolutely true that you will get that exact memory error on your 160 GB drive with scandisk because W98SE scandisk will not work with partitions above 128GB - that is is a known limitation. The only way around that is to re-partition your drive to have smaller than 128 GB partitions if you want to use scandisk with W98x Rick .........ps: Microsoft MVP Ron Martell has also mentioned this issue before and I quote: The problem you are encountering arises because Scandisk and Defrag cannot cope with drives that have more than 4.1 million total clusters [2^22] and with a maximum cluster size of 32 kilobytes [2^15 bytes] this equates to a maximum partition size of 128 binary gigabytes [2^37 bytes]. |
"Jeff Richards" wrote in message ... The file system (FAT32 etc) does not impose a maximum drive size. It does. No question about it. A partition gets assigned a DRIVE letter. You are reading "drive" as equivalent to "hard drive", which is an incorrect perspective. The file system is only concerned with a maximum partition size. If you say so. Many other issues are important, such as cluster size as it relates to wasted space - 32K per cluster wastes hard disk space - but I'm not here to argue. It's the BIOS and the way that the OS uses the BIOS that imposes a drive size limitation. Actually, it is the numerical storage referential capability of the binary system that imposes the limit, regardless of the entity, BIOS or OS. The table of cluster sizes and directory files (sic) Files in a directory. What is the problem that you see here? FAT32 allows 65k entries per directory regardless of cluster size and makes no distinction between entries that are files, folders, or long filenames. You seem to have lost sight of the objective here. The discussion is about ScanDisk limitations. Nothing else. The rest is not related to maximum partition size, except for the bit about a maximum number of clusters before Scandisk throws the out-of-memory error. Maximum partition size per se is NOT the issue. If you have a problem with the accuracy of anything I posted, take it up with Microsoft. It is all KB data. -- Jeff Richards MS MVP (Windows - Shell/User) "Hugh Candlin" wrote in message ... "lugnut554" wrote in message ... I don't think I've run scandisk on this drive--at least not from Windows. The drive is 160 Gb and is not partitioned. What is the largest partition scandisk can work with? Using FAT32, the largest drive can be up to 2 terabytes [2047 GB], based on the 32 KB cluster size limitation. The largest possible file for a FAT32 drive is 4 GB minus 2 bytes. ScanDisk has a couple of restrictions: A Maximum Number of Files in a Directory Drive Cluster Size Max # of Directory Files -------------------------------------------------- 512 bytes (floppy) ~ 1280 give or take 16 2K ~ 5120 give or tak e 64 4K ~10240 give or take 256 8K ~20480 give or take 1024 16K ~40960 give or take 4096 32K ~81920 give or take 16384 B ScanDisk will balk with an out-of-memory error if you have a hard disk that is larger than 8 GB that has a cluster size that is smaller than 8 KB. The standard FAT32 cluster size of 4,096 bytes applies only to hard disks that are smaller than 8 GB. You will also receive this error with a very large hard disk that has a default Windows cluster size of 32 KB. C If you use the protected-mode (graphical) version of ScanDisk to perform a thorough scan (which includes a surface scan) on an IDE hard disk that is larger than 32 GB in size, ScanDisk may report errors on every cluster after approximately cluster number 967,393. http://support.microsoft.com/kb/243450/EN-US/ D Windows 98 provides two versions of ScanDisk: a graphical Windows-based version (Scandskw.exe) that you can run from the Start menu or from Windows Explorer, and an MS-DOS-based version (Scandisk.exe) that is contained in the \Windows\Command folder. Running Scandisk.exe while in Windows will invoke Scandskw.exe. ScanDisk cannot find or fix errors on CD-ROM drives, network drives, or drives created by using Assign, Subst, Join, or Interlnk. E ScanDisk cannot automatically fix errors if a file name (including the file's full path) exceeds 259 characters. This includes file names in the MS IE cache folder. If this occurs, empty the cache and try ScanDisk again. F The ScanDisk tool included with Microsoft Windows 95 and Microsoft Windows 98 is a 16-bit program. Such programs have a single memory block maximum allocation size of 16 MB less 64 KB. Therefore, The Windows 95 or Windows 98 ScanDisk tool cannot process volumes using the FAT32 file system that have a FAT larger than 16 MB less 64 KB in size. A FAT entry on a volume using the FAT32 file system uses 4 bytes, so ScanDisk cannot process the FAT on a volume using the FAT32 file system that defines more than 4,177,920 clusters (including the two reserved clusters). Including the FATs themselves, this works out, at the maximum of 32 KB per cluster, to a volume size of 127.53 gigabytes (GB). For a full treatise on ScanDisk, go to this List of Articles About the ScanDisk Tool http://support.microsoft.com/default...b;en-us;287914 See also Chapter 10 [Disks and File Systems] of the Windows 98 Resource Kit at http://www.microsoft.com/resources/d...t2/wrkc10.mspx |
The file system imposes a maximum partition size. The drive size is
irrelevant as far as the file system is concerned. I don't know what the numerical storage referential capability of the binary system is, but maximum usable drive sizes are dictated by the BIOS and the way that the operating system can access BIOS functions. Other OSes can bypass the BIOS and go straight to the hardware, but Windows 98 can't. Since you claim that the information is from Microsoft, then please provide a reference to the directory sizes table. Maximum partition size is exactly the issue. OP has a 160Gb disk created as a single partition, and that is the reason for the Scandisk error message he's getting. He is not getting the other error message you have mentioned. -- Jeff Richards MS MVP (Windows - Shell/User) "Hugh Candlin" wrote in message ... "Jeff Richards" wrote in message ... The file system (FAT32 etc) does not impose a maximum drive size. It does. No question about it. A partition gets assigned a DRIVE letter. You are reading "drive" as equivalent to "hard drive", which is an incorrect perspective. The file system is only concerned with a maximum partition size. If you say so. Many other issues are important, such as cluster size as it relates to wasted space - 32K per cluster wastes hard disk space - but I'm not here to argue. It's the BIOS and the way that the OS uses the BIOS that imposes a drive size limitation. Actually, it is the numerical storage referential capability of the binary system that imposes the limit, regardless of the entity, BIOS or OS. The table of cluster sizes and directory files (sic) Files in a directory. What is the problem that you see here? FAT32 allows 65k entries per directory regardless of cluster size and makes no distinction between entries that are files, folders, or long filenames. You seem to have lost sight of the objective here. The discussion is about ScanDisk limitations. Nothing else. The rest is not related to maximum partition size, except for the bit about a maximum number of clusters before Scandisk throws the out-of-memory error. Maximum partition size per se is NOT the issue. If you have a problem with the accuracy of anything I posted, take it up with Microsoft. It is all KB data. -- Jeff Richards MS MVP (Windows - Shell/User) "Hugh Candlin" wrote in message ... "lugnut554" wrote in message ... I don't think I've run scandisk on this drive--at least not from Windows. The drive is 160 Gb and is not partitioned. What is the largest partition scandisk can work with? Using FAT32, the largest drive can be up to 2 terabytes [2047 GB], based on the 32 KB cluster size limitation. The largest possible file for a FAT32 drive is 4 GB minus 2 bytes. ScanDisk has a couple of restrictions: A Maximum Number of Files in a Directory Drive Cluster Size Max # of Directory Files -------------------------------------------------- 512 bytes (floppy) ~ 1280 give or take 16 2K ~ 5120 give or tak e 64 4K ~10240 give or take 256 8K ~20480 give or take 1024 16K ~40960 give or take 4096 32K ~81920 give or take 16384 B ScanDisk will balk with an out-of-memory error if you have a hard disk that is larger than 8 GB that has a cluster size that is smaller than 8 KB. The standard FAT32 cluster size of 4,096 bytes applies only to hard disks that are smaller than 8 GB. You will also receive this error with a very large hard disk that has a default Windows cluster size of 32 KB. C If you use the protected-mode (graphical) version of ScanDisk to perform a thorough scan (which includes a surface scan) on an IDE hard disk that is larger than 32 GB in size, ScanDisk may report errors on every cluster after approximately cluster number 967,393. http://support.microsoft.com/kb/243450/EN-US/ D Windows 98 provides two versions of ScanDisk: a graphical Windows-based version (Scandskw.exe) that you can run from the Start menu or from Windows Explorer, and an MS-DOS-based version (Scandisk.exe) that is contained in the \Windows\Command folder. Running Scandisk.exe while in Windows will invoke Scandskw.exe. ScanDisk cannot find or fix errors on CD-ROM drives, network drives, or drives created by using Assign, Subst, Join, or Interlnk. E ScanDisk cannot automatically fix errors if a file name (including the file's full path) exceeds 259 characters. This includes file names in the MS IE cache folder. If this occurs, empty the cache and try ScanDisk again. F The ScanDisk tool included with Microsoft Windows 95 and Microsoft Windows 98 is a 16-bit program. Such programs have a single memory block maximum allocation size of 16 MB less 64 KB. Therefore, The Windows 95 or Windows 98 ScanDisk tool cannot process volumes using the FAT32 file system that have a FAT larger than 16 MB less 64 KB in size. A FAT entry on a volume using the FAT32 file system uses 4 bytes, so ScanDisk cannot process the FAT on a volume using the FAT32 file system that defines more than 4,177,920 clusters (including the two reserved clusters). Including the FATs themselves, this works out, at the maximum of 32 KB per cluster, to a volume size of 127.53 gigabytes (GB). For a full treatise on ScanDisk, go to this List of Articles About the ScanDisk Tool http://support.microsoft.com/default...b;en-us;287914 See also Chapter 10 [Disks and File Systems] of the Windows 98 Resource Kit at http://www.microsoft.com/resources/d...t2/wrkc10.mspx |
| All times are GMT +1. The time now is 08:43 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Win98Banter.com