tror att man kan öppna filen med en hex editor... för när steam kom i helgen så var det massa tjöt om att någon .gcf-fil sökte igenom hårddisken.. och om man öppnade den med en hex-editor kunde man se att filen innehöll information om vad man hade på hårddisken (mp3, kazaa osv)...
Citat:
Quote:
Originally Posted by LanceVorgin
1) Browse to steam dir
2) Search for gcache.gcf
3) Open the 400+ meg file in a hex editor
4) Search for 'kazaa' and 'mp3'
----
5) Ponder
6) Curse and uninstall steam
Wtf? Why the hell is steam looking at kazaa user names, mp3 contents, HTM records, and a whole lot of other #### I particularly don't want Valve having detailed records on passed through an undocumented protocol?
lite orelevant information, men det förklarar hur du öppnar filen... och OM någon som spelar cs läser detta nu och blir rädd för att valve ska få veta vad du har på disken så kommer ytterligare ett citet (OT):
Citat:
--------------------------------
Not true. We have no interest in what's on your hard drive.
When we first heard about this, we were perplexed. Then we realized that
the people who were seeing this were running FAT32 instead of NTFS. In
Windows, if you have the NTFS file system, it zeros out sectors before it
reallocates them. With FAT32, it doesn't. So if you allocate a large file
(it doesn't matter if it's a Steam cache or some other application's files),
in FAT32 if you open that file, you will see whatever data was left over
from the previous writes to those sectors until your application writes over
that data with new data. So on FAT32, Steam allocates 400 MB of space,
fills up 200 MB with game stuff, and the remaining 200 MB contains whatever
was already there.
Does this make sense? You can try it with other large unfilled files on
your system and see the same thing.
Gabe
