> Just me, or is hldsupdatetool completely b0rked on windows?
If yours is crashing, it's not just you. Right now, if ClientRegistry.blob
is missing, hldsupdatetool seems to be creating a new one that is corrupted,
as further runs of hldsupdatetool either silently crash or say
"CMultiFieldBlob: Unable to grow blob". The problem is easily reproduced:
C:\test>mkdir hlds
C:\test>dir
Volume in drive C has no label.
Volume Serial Number is D086-4981
Directory of C:\test
10/14/2009 03:15 PM <DIR> .
10/14/2009 03:15 PM <DIR> ..
10/14/2009 03:15 PM <DIR> hlds
10/14/2009 03:15 PM 1,082,616 HldsUpdateTool.exe
1 File(s) 1,082,616 bytes
3 Dir(s) 791,420,563,456 bytes free
C:\test>HldsUpdateTool.exe -command update -game cstrike -dir hlds
Checking bootstrapper version ...
Getting version 35 of Steam HLDS Update Tool
Downloading. . . . . . . . . .
C:\test>Checking bootstrapper version ...
Updating Installation
CMultiFieldBlob: Unable to grow blob
HldsUpdateTool.exe -command update -game cstrike -dir hlds
Checking bootstrapper version ...
Updating Installation
C:\test>
I didn't notice this before today.
Existing installs continue to work, so the workaround for this is to replace
its bad ClientRegistry.blob with a known-good version from another
installation.
-John
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
