Lt. Commander
Join Date: Dec 2007
Posts: 120
# 51
01-30-2010, 12:27 PM
Quote:
Originally Posted by Tjienta.Vara
Either they have update all of the files again, or all my files are corrupt.
Quote:
Originally Posted by -Prophet- View Post
Same here. Every one of mine is different.

Downloaded from Steam.
Yup, corrupted download or something wrong during the file compression/decompression process.

There was an update today (both EST and PST), but it only changed two files.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 52
01-30-2010, 12:28 PM
I updated all of the checksums for the hogg files as of the 1/30/2010 EST/PST patch.

This patched the bins.hogg and exes.hogg files. This is the 2nd day into headstart.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 53 Where to Download?
01-30-2010, 09:10 PM
I previoisly had the Star Trek loader on another computer, but now I need it on this one, where can I download the game so I can play my pre-oder bonus time. I pre-odered the game at Gamestop fyi.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 54
01-31-2010, 10:59 AM
I deleted all of my .hogg files and had them download ovenight.. not one match the hashcheck.


Quote:
Originally Posted by cipher_nemo View Post
How to generate a client DUMP for Cryptic
If Cryptic devs ask you to provide a DUMP for an STO client freeze or crash, here's how to generate that report.
  1. Browse to the location where you installed STO. The default location is in your Program Files folder, or Program Files (x86) for 64-bit versions of Windows. You'll need to go here and even further into the Live folder.

    %PROGRAMFILES%\Cryptic Studios\Star Trek Online\Live
    .
  2. Find the executable named crypticError.exe and launch it with the frozen STO client still running.
    .
  3. Find the process named GameClient.exe and select it.
    .
  4. Click on the "Send" button. Make sure the STO client and the CrypticError application are running during this entire process. This helps Cryptic trace and identify the cause of your client freeze/crash.

How to get a copy of your client settings
If a community member ever asks you for a copy of your client settings (ie: graphics settings) to help troubleshoot performance, here's one way.
  1. Browse to the location where you installed STO. The default location is in your Program Files folder, or Program Files (x86) for 64-bit versions of Windows. You'll need to go here and even further into the Live and then Localdata folders.

    %PROGRAMFILES%\Cryptic Studios\Star Trek Online\Live\Localdata
    .
  2. Open the only file here, Gameprefs.Pref with a text editor such as Notepad.
    .
  3. Select the desired text and copy it (right click and choose Copy or Ctrl-C). For just graphics settings, copy only the lines prefixed with PrefEntry GfxSettings.
    .
  4. Paste it into your post (ie: Ctrl-V).


How to verify your client data files
We've seen all sorts of file corruption when downloading the STO client from other sources. If you have problems installing or running STO, you might have a corrupted installer file or client data files (*.hogg files found in the "piggs" folder... Cryptic used this naming convention with CO as well). Although this method is not 100% accurate, it will let you know if a file is truncated or moderately to severely corrupted and whether or not you need to download these files again.
  1. Download and install a free checksum utility such as HackCheck Shell Extension for Windows XP, Windows Vista, and Windows 7.
    .
  2. Browse to the location where you installed STO. The default location is in your Program Files folder, or Program Files (x86) for 64-bit versions of Windows. You'll need to go here and even further into the Live and then piggs folders.

    %PROGRAMFILES%\Cryptic Studios\Star Trek Online\Live\piggs
    .
  3. You'll see several files with the hogg extension in this folder. Repeat the following steps for each file.
    .
  4. Right click on a hogg file and choose "Properties".
    .
  5. Click on the "Checksums" tab and wait for the progress bar to indicate processing is complete. You'll only see this tab with the HackCheck Shell Extension installed. For other checksum software, follow their instructions for finding a file's checksums.
    .
  6. Compare your results with the current checksums for the latest patch. Some hogg files might remain the same through patches, and some might change. It really depends on what Cryptic fixes in each patch. You don't need to compare every type of checksum. Just pick one line to compare. If they don't match, delete them and run the launcher to let it patch (it will download the required hogg files again). If they match, then you might have issues related to something else.

    Latest version as of 1/30/2010 EST (headstart):

    All dates from EST timezone (GMT -5)

    File: bins.hogg (last patched 1/30)
    CRC-32: c89c35f9
    MD4: 39f8251adec6754280cd812a6a31264a
    MD5: 71564a59e61a80ccaf78d99ad359a8d9
    SHA-1: d348cebcd939770db49637ca0da29b474fe51df5

    File: bins2.hogg (last patched 1/21)
    CRC-32: a6ddb95b
    MD4: 103b34588ad4e21cc0a8b515b6390be0
    MD5: ba7aef0d459cbdc08ab29f55354bb73a
    SHA-1: a0929fba899335da8e8d7dd22baeec59e56fc7b9

    File: bins3.hogg (last patched 1/21)
    CRC-32: e8532c08
    MD4: 6a9d726e0eb37c5bbcc4f24df531aa72
    MD5: efb02d06709016b329c98a827175cfc5
    SHA-1: 2ef5b43a77a74088a1737a29523684eca37ab8ed

    File: character.hogg (last patched 1/11)
    CRC-32: 53eebc9f
    MD4: cd505d56fc2ee740bd65cab58004964b
    MD5: 842509911547f183769c6cb8a0861bc6
    SHA-1: e5cac054e3e925f09ddbf69c9b7438199840c1b6

    File: data.hogg (last patched 1/21)
    CRC-32: 7b204acb
    MD4: 2503cfdff57d5d60f2c9b4b6b9895044
    MD5: 307c8a6fcbcedd1c8b89d352bd451286
    SHA-1: 7c4649042a6d702f33be596cb1858ddb4b14e5a9

    File: exes.hogg (last patched 1/30)
    CRC-32: 4036d5f4
    MD4: 43c39ffa8a670a844a1cee3babd071a7
    MD5: 860dbd5cd9d597ab7d3b6f9bbd93f48a
    SHA-1: 856728e229012f15dbb0138fa1cf5037a5fffe2c

    File: object.hogg (last patched 1/11)
    CRC-32: a752c2ee
    MD4: 08b4008655b43aad1a44a4c1dfb749b1
    MD5: a3e5e9fcb41c5a12d31ac5ab448c7d05
    SHA-1: 02e81d1e2a836d8970cb07c3e76398dcaf1cdfbc

    File: sound.hogg (last patched 1/24)
    CRC-32: e9b1b6f2
    MD4: 8bed9168e8d5354f8d45a2d42003ff5c
    MD5: 473dbc0114f7c617670d81b54c47ad97
    SHA-1: b6e7978dbc8dbc7d73b755bb188fa791e2c942c3

    File: texture.hogg (last patched 1/28 - 1/29)
    CRC-32: b6301c96
    MD4: b786c358c637f26ea946ec22cc215422
    MD5: 257290abd9860ea4a93c56ee86e33df5
    SHA-1: 9fbee02f78de0b72670ba485bd562fe3392ec0e2

    File: texture2.hogg (last patched 1/21)
    CRC-32: 168270d0
    MD4: 947d9e6bb30c82a6bf09ac41ce722ebd
    MD5: 59a1b7e1731448b9f7b707226e071960
    SHA-1: cf0a4e71bbdb8f8e8cf39a7027e72f9054b541cc

    File: texture3.hogg (last patched 1/24)
    CRC-32: b1eebd75
    MD4: cc327af93f6b9cc4ba46aff79d56c9e5
    MD5: e9c3eb48225611d737866d83323eaf60
    SHA-1: 924f4464cdddf8efe08ace7801aedab7470141c1
    .

Tips
  • Downloader/Launcher: To view the individual files being downloaded at any given time, simply press your 'X' key when the Cryptic launcher window is active.
    .
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 55
01-31-2010, 01:51 PM
Quote:
Originally Posted by ardien.kinslayer View Post
I deleted all of my .hogg files and had them download ovenight.. not one match the hashcheck.
Please don't quote the entire help posts. As for your hogg files, did you do an update? They're going to be different until you do an update and get synced with everyone else. If they're different after an update, then you have issues.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 56
01-31-2010, 05:04 PM
I updated all of the checksums for the hogg files as of the 1/31/2010 EST/PST patch.

This patched the bins.hogg and exes.hogg files. This is the 3rd day into headstart.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 57
01-31-2010, 07:29 PM
The checksums are not useful. Few people will ever have matching ones. Hoggs do not work that way, and you cannot verify them in this manner.

Here's the correct way to do this: in the launcher, click on 'options', and select 'force verify'. The launcher will do a proper check of the file hashes. You don't need to do anything else.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 58
02-01-2010, 02:13 PM
Quote:
Originally Posted by Miiru
The checksums are not useful. Few people will ever have matching ones. Hoggs do not work that way, and you cannot verify them in this manner.
Sorry, that is incorrect. The hogg files are all the same for everyone. No one has unique hogg files unless they don't have the latest patch. Checksums are there to compare files. Compression does not vary if the source files are identical.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 59
02-01-2010, 02:55 PM
I updated all of the checksums for the hogg files as of the 2/01/2010 EST/PST patch.

This patched the bins.hogg and exes.hogg files. This is the 4th (last) day of headstart.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 60
02-01-2010, 10:28 PM
Quote:
Originally Posted by cipher_nemo View Post
The hogg files are all the same for everyone.
No, you're just wrong. Hogg files don't work that way. There is no particular expectation that they will be the same for everyone. (I hesitate to explain how they really work, as I'm not sure how much of that information is public)

Surely all the people with different hogg files in this thread would have clued you in by now.
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 04:33 AM.