Nomen

I thought that saying the drive was 700 gb, and had 22 gb free was sufficient information. Please accept my apology if I didn't say that it was a SATA drive being controlled and used in native SATA mode, and that it was formatted as a single primary FAT32 partition with 732,395,680 kilobytes total disk space, 23,095,744 kilobytes free, 32kb cluster size, 22,887,365 total clusters on disk, 721,742 available clusters. Is there any other information that is necessary in order to arrive at an answer to my original question? Or perhaps nobody here has encountered this phenomena before?

Ok, I'll completely re-edit this. System 1 has KeX 4.5.10.1 (2010-12-30) and Flash 11.2.202.197 System 2 has Kex 4.5.12 (2011-11-14) and Flash 11.1.102.62 I obtain NPSWF32.dll (version 11.3.300.262) and just copy that file over the existing files on both systems. This works for system 1(all flash content is viewable on firefox 2.0.0.20) but FF crashes on system 2 when attempting to view flash content. Comments? What do I need to do to get Flash 11.3.300.262 working on system 2?

The registry key "DisableLowDiskSpaceBroadcast" is probably used by the Disk Cleanup utility. Mine is currently set to 12 - indicating drives C and D are not to invoke the cleanup tool upon reaching the low-disk-space criteria. I currently have the cleanup utility deactivated on those 2 drives, but win-98 will still generates "disk full" errors when I try to copy files (even relatively small files) from the C to the D drive.

This is a SATA hard drive connected to a SiL 3512 controller, using the driver file SI3112r.mpd. I thought it was common knowledge that win-98 is fully compatible with most SATA-1 controller hardware and that no special drivers are needed because those controllers came with win-98 drivers, allowing them to be used in native SATA mode (not IDE emulation mode).

Win-98 seems to have a hard-coded threshold of 3% free disk space that I can't find any way to reduce or disable. This is not the same as changing the settings for the Disk Cleanup tool. Disabling the activation of that tool when free disk space reaches the 3% mark does not seem to prevent the OS from generating "disk full" messages when you want to copy files to the affected drive - or when applications are attempting to write to the affected drive. I came across some mention of this Explorer registry value: NoLowDiskSpaceChecks (set to value 1) But my win-98 system doesn't seem to pay any attention to it. I've got a 700 gb drive, and it's got about 22 gb free, but win-98 won't allow any more files to be written to it. Ordinarily, you would think that having 22 gb of free disk space wouldn't be a problem... Is this a known issue for win-98, and is there a solution? Or must I simply live with the fact that 22 gb of this drive is unusable?