• Welcome to Battlezone Universe.
 

News:

Welcome to the BZU Archive dated December 24, 2009. Topics and posts are in read-only mode. Those with accounts will be able to login and browse anything the account had access granted to at the time. No changes to permissions will be made to be given access to particular content. If you have any questions, please reach out to squirrelof09/Rapazzini.

Main Menu

patch error...

Started by Gibbz, August 12, 2006, 04:18:17 AM

Previous topic - Next topic

Gibbz

Ive done a fresh install of bz2, then patched with the new 1.3beta 3 and when i goto launch i get the following error....

[ E X C E P T I O N ]
Patch 1.3pb3 Aug 10 2006 07:49:33
Type:    ERROR
SubType: FATAL - fatal error
Message: Error reading 52369324 bytes from pack file ' '
Module:  .\filesrcpack.cpp
Line#:   393
Stamp:   Sat Mar 18 09:25:55 2006
CallStack:
7C81EB33 +7C81EB33 kernel32.dll [Unknown] [Unknown] [Unknown]
0060F24A +00BA bzone.exe system debug.obj void __cdecl Debug::Error::Err(char const *,...)
Registers:
EAX: 0229F7E8h   CS: 0000001Bh  DS: 00000023h
EBX: 031F1904h  EIP: 7C81EB33h  ES: 00000023h
ECX: 00000000h   SS: 00000023h  FS: 0000003Bh
EDX: 0229F850h  EBP: 0229F838h  GS: 00000000h
ESI: 0229F864h  ESP: 0229F7E4h           
EDI: 00000061h                       
CF: 00200206h PF:0 AF:1 ZF:0 SF:0 OF:0
Entering critical shutdown
Input not initialised

Avatar

This:

Message: Error reading 52369324 bytes from pack file ' '

Would seem to indicate a corrupted PAK file.  Did you try to run BZ2 after the clean install?  If it ran then I'd say your patch download was corrupted...

-Av-

OvermindDL1

#2
Here are some hashes of the files, pick whatever is your favorate of the three for each file and make sure yours are the same:

data.pak:
MD5: D97FF14E2B11C1018E0BFE430E3397C6
SHA1: 3C4FE332B461393C17084BDBA508E17153A4E096
CRC-32: 242D7F61

smtex.pak:
MD5: 390FDCEBA3A1CF3CAFC73092ACC1871E
SHA1: 1F1CBAA35A082C9DB19A5B82C4C4FD7C386015F3
CRC-32: 4E874788


Seems to me more like that the ' ' should be the filename, in which case, make sure your bzone.cfg file is not wrong.  Or that could just be because of memory stomping due to trying to read too much data or what-not...