Windows 98SE : Scandisk - Not enough available memory

[GeneSG]

Hi guys/girls I have read the the other threads in this forum regarding the infamous more then 512MB memory problem with Windows 98SE. However my scenario seems to be a little unique please take time to read and provide advice. Thank you

I am using Windows 98SE with 512MB RAM and 2 HDD. 1 80GB and 1 160GB. The 160GB HDD was just installed because my older 80GB HDD was burned out. The 80GB HDD is partition with 1 5GB (OS) and 75GB (Programs). 160GB drive is data storage just 1 big partition.

The problem happened when I was playing World of Warcraft with Bitorrent on. My system crashed then rebooted. I started scandisk to check for errors. C: and E: drives on the 80GB scanned fine. However when i moved to D: drive 160GB I get the not enough memory error. This did not happen when I used to have 2 80GB HDD.

Solutions tried after coming to this forum. I went to (Vcache) and set the min64 and max to 128. Then I went to msconfig and limited memory to 128MB. I rebooted still having the problem.

2nd time I went to safe mode with the (Vcache) still at min 64MB and max 128MB, msconfig memory setting still at 128MB. Result was still the same.

3rd time i tried (Vcache) at 64MB and max 128MB but removed the memory setting at msconfig. I also did it vice versa in normal windows mode and safe mode. Still getting the same error.

Lastly i just resetted everything to normal and rebooted to MS-Dos mode. Scandisk worked fine for all drives and partition. After which i entered windows and tried scanning again. I still get the same error. My D: drive is working fine i still access my data files there with no problem and i can still run World of Warcraft with bitorrent on.

My conclusion 160GB HDD drives not supported in scandisk in windows 98SE ? Can anyone confirm that ? Its just a guess my knowledge of such problems is very limited. Please do reply with advice or references. And thank you for taking time to reading this lengthy post.

[PC_Fanatic]

Yes, you found out the truth the hard way. Win98's Scandisk has a problem with large drives.

Here is a link that explains the problem. Although the heading is titled Windows 2000, there are references to Win98's Scandisk problem.

http://web.ukonline.co.uk/cook/fat32.htm

Looks like you'll have to partition the drive.

[GeneSG]

Hi Bro thx for the prompt reply. The link you gave answered my questions pretty well. I guess if i partition my 160GB HDD to 1 120GB 1 40GB it should work fine for scandisk. Thank again.

Just 1 last question before i officially end this thread. Why does scandisk work in DOS Mode for my 160GB HDD and not in Windows mode ? Seems a bit weird that if scandisk couldn't process drives larger then 127.53GB, shouldn't it apply to both DOS and Windows mode ? Maybe there's a way to bypass it ? Like changing registry values or msconfig ? Welcoming all advice and references again. Thank you

[PC_Fanatic]

Good question,

I'd guess that Dos uses entirely different code to implement Scandisk.

One thing you might try is to increase the cluster (allocation) size when you format the drive. This would reduce the memory required to cache the FAT tables.

This would also tend to waste drive space; A 64k cluster is overkill for small files.

I'm afraid that Win98 and FAT32 will soon be obsolete. I still use Win98 on a separate drive, but I'm using it less and less. The hardware and software support just isn't there.

[zepper]

Use the scandisk.exe and defrag.exe (and any associated help files) from WinMe with 98. They are statically linked (i.e. don't use any .DLLs) so they will work fine with W98/SE. They work considerably better that the OE files. There are plenty of places to download them from (if you can't nab them from a friend) around the web and more complete instructions. But the main thing is to rename the current files and copy the new files into the same folder(s) as the old ones. Couldn't be easier.
.bh.

[GeneSG]

K guys/girls , as adhering to the rules of this forums i am posting a conclusion and solution to end this thread officially. Firstly I would like to thank PC_Fanatic for his useful advice and references. ( Thank a lot bro (>_<)b. ) And zepper for his suggested solution but didn't work .

Last solution tested before ending this thread was what zepper adviced. Using Windows ME scandisk and defrag.exe with exactly the 4 methods I used for Windows 98SE testing both did not work i still get the same error so i will not bother posting the links to this files.

-Conclusion-
Windows 98SE and Windows ME scandisk and defrag .exes do NOT support drives larger then 127.53GB. If using FAT32.

-Solution-
Tested/Workable Solution :
Do a scandisk in dos ( you have to reboot to DOS-Mode, using DOS-prompt in Windows will not work. You will hit the same error )for HDD drives larger then 127.53GB you can't defrag in DOS but if you are using the HDD for data storage like me i don't think it reallys matters if you can defrag or not.

Suggested Solution :
1.Parition your drive to allow a maxium of 127.53Gb per partition best if its only 120GB allow some space for errors. You do not want to be like me after shifting 65GB of data for 5hrs and find that you cannot defrag because of the 127.53GB limitation again ~_~; .

2.Change OS as what PC_Fanatic has said FAT32 system is really outdated. Change to the XP series.

Although I have ended this thread. Please if you have any more advice or suggestions and solutions to this problem feel free to post under this thread again. Technology is always changing o.O. Me ending this thread is just that I will not be replying that often due to time constraints when new solutions advice are given.

[Richard Broberg]

I got that not enough space problem when I tried to defrag my Win98SE using the MSFT defragger.

I installed my old Norton Systemworks 2002 from the CD and no more space problems.

Norton SW 2002 has neither an install code nor activation, which is good because my 98SE PC has no connection to the outside world except thru CDs using Nero 6.

Google Norton 2002 SW and you can buy it cheap.