When I go to the window to set virtual memory and check "Let me specify my own virtual memory", the disk space is set to c:\-15721 MB free. The minimum is set at 0 and if I try to adjust it, it also goes negative. Running ME, 1 gig processor, 256MB mem, 80 gig HD, 50 gig free. System seems to run fine, but this setting is obviously wrong. Any idea how it got that way?

Could be that some apps in ME can only recognise up to..erm...an 10 digit HEX number I think (80 Bits) sort of like some old win 95 apps/installers only recognising 2Gb of freespace max which is 64 Bit Since the freespace is greater than the maximum number that can be recognised it can go negative in some circumstances (if the first bit of a number is a 1 not a 0, shouldn't be a consideration for freespace as can't have less than zero..but might be something else to..) if it runs fine I would just leave it as it is...but you could try puting 20-40 Gb of just stuff on there to reduce your freespace. Then setting your swapfile size, then delete the temp stuff.. sorry if the first part makes no sense but its late and I'm tired :)

Do you by some chance have Norton SystemWorks? If so, It seems as though I remember an issue with Norton and Microsoft which hasn't been resolved yet. Bruce

This is a known problem with WinME and a HD >32 MB. For a free fix you must contact Microsoft and request such. For further info please read article Q272620 from th Microsoft Support Knowledge base http://support.microsoft.com/support/kb/articles/Q272/6/20.ASP