Jump to content


Photo

Near infinity reports corrupted files


  • Please log in to reply
7 replies to this topic

#1 OneEyedPhoenix

OneEyedPhoenix
  • Member
  • 308 posts

Posted 18 September 2009 - 02:01 PM

When searching for corrupted files with near infinity the tool reports 58 errors.
Most of these concerns "unused bytes" or "overlapping" bytes.
The question is, how serious are these errors and why do they occur?
Some files are more affected than others and all files come from diverse mods, so I guess it has something to do with the coding of these...?

#2 Sam.

Sam.
  • Administrator
  • 1294 posts

Posted 18 September 2009 - 02:41 PM

I just found 28 errors in a total of two files. Overlaps are probably more serous than unused bytes, though. Want to save your results and paste them so everyone can have a look? I recall there being a few files in the unmodded BGII (I'm playing Classic Adventures) that were "corrupted". TCGOBSHA.CRE is messed up in-game, I believe. Don't know about the .WED.

Here's what I had:
File corruption search
Number of errors: 28

File: TC1200N.WED   Offset: 5f9eh  Error message: 3680 unused bytes between Overlays drawn(5f9eh) and Tilemap index 0(6e02h)
File: TC1200N.WED   Offset: 8198h  Error message: 736 unused bytes between Tilemap index 2391(8198h) and Polygon index(847ah)
File: TCGOBSHA.CRE  Offset: 48ch   Error message: Spell(48ch) overlaps Spell(48ch) by 8 bytes
File: TCGOBSHA.CRE  Offset: 494h   Error message: Memorization(494h) overlaps Memorization(494h) by 2 bytes
File: TCGOBSHA.CRE  Offset: 496h   Error message: Unknown(496h) overlaps Unknown(496h) by 2 bytes
File: TCGOBSHA.CRE  Offset: 4b0h   Error message: Spell(4b0h) overlaps Spell(4b0h) by 8 bytes
File: TCGOBSHA.CRE  Offset: 4b8h   Error message: Memorization(4b8h) overlaps Memorization(4b8h) by 2 bytes
File: TCGOBSHA.CRE  Offset: 4bah   Error message: Unknown(4bah) overlaps Unknown(4bah) by 2 bytes
File: TCGOBSHA.CRE  Offset: 4bch   Error message: Spell(4bch) overlaps Spell(4bch) by 8 bytes
File: TCGOBSHA.CRE  Offset: 4c4h   Error message: Memorization(4c4h) overlaps Memorization(4c4h) by 2 bytes
File: TCGOBSHA.CRE  Offset: 4c6h   Error message: Unknown(4c6h) overlaps Unknown(4c6h) by 2 bytes
File: TCGOBSHA.CRE  Offset: 4c8h   Error message: Spell(4c8h) overlaps Spell(4c8h) by 8 bytes
File: TCGOBSHA.CRE  Offset: 4d0h   Error message: Memorization(4d0h) overlaps Memorization(4d0h) by 2 bytes
File: TCGOBSHA.CRE  Offset: 4d2h   Error message: Unknown(4d2h) overlaps Unknown(4d2h) by 2 bytes
File: TCGOBSHA.CRE  Offset: 4d2h   Error message: 48 unused bytes between Unknown(4d2h) and Item(504h)
File: TCGOBSHB.CRE  Offset: 48ch   Error message: Spell(48ch) overlaps Spell(48ch) by 8 bytes
File: TCGOBSHB.CRE  Offset: 494h   Error message: Memorization(494h) overlaps Memorization(494h) by 2 bytes
File: TCGOBSHB.CRE  Offset: 496h   Error message: Unknown(496h) overlaps Unknown(496h) by 2 bytes
File: TCGOBSHB.CRE  Offset: 4b0h   Error message: Spell(4b0h) overlaps Spell(4b0h) by 8 bytes
File: TCGOBSHB.CRE  Offset: 4b8h   Error message: Memorization(4b8h) overlaps Memorization(4b8h) by 2 bytes
File: TCGOBSHB.CRE  Offset: 4bah   Error message: Unknown(4bah) overlaps Unknown(4bah) by 2 bytes
File: TCGOBSHB.CRE  Offset: 4bch   Error message: Spell(4bch) overlaps Spell(4bch) by 8 bytes
File: TCGOBSHB.CRE  Offset: 4c4h   Error message: Memorization(4c4h) overlaps Memorization(4c4h) by 2 bytes
File: TCGOBSHB.CRE  Offset: 4c6h   Error message: Unknown(4c6h) overlaps Unknown(4c6h) by 2 bytes
File: TCGOBSHB.CRE  Offset: 4c8h   Error message: Spell(4c8h) overlaps Spell(4c8h) by 8 bytes
File: TCGOBSHB.CRE  Offset: 4d0h   Error message: Memorization(4d0h) overlaps Memorization(4d0h) by 2 bytes
File: TCGOBSHB.CRE  Offset: 4d2h   Error message: Unknown(4d2h) overlaps Unknown(4d2h) by 2 bytes
File: TCGOBSHB.CRE  Offset: 4d2h   Error message: 48 unused bytes between Unknown(4d2h) and Signature(504h)

"Ok, I've just about had my FILL of riddle asking, quest assigning, insult throwing, pun hurling, hostage taking, iron mongering, smart-arsed fools, freaks, and felons that continually test my will, mettle, strength, intelligence, and most of all, patience! If you've got a straight answer ANYWHERE in that bent little head of yours, I want to hear it pretty damn quick or I'm going to take a large blunt object roughly the size of Elminster AND his hat, and stuff it lengthwise into a crevice of your being so seldom seen that even the denizens of the nine hells themselves wouldn't touch it with a twenty-foot rusty halberd! Have I MADE myself perfectly CLEAR?!"

--<CHARNAME> to Portalbendarwinden

--------------------

post-10485-0-15080600-1348188745.jpg
___________Old pen and paper modules of the 70s and 80s.___________

CA Forums CA Homepage


#3 OneEyedPhoenix

OneEyedPhoenix
  • Member
  • 308 posts

Posted 18 September 2009 - 02:51 PM

Want to save your results and paste them so everyone can have a look?


Yup. Before the list is generated though I get quite a few errors about non-existing bif files, more specifically progtest.bif and progtes2.bif. Given the names of these I assume that they have no ingame importance...

My error list looks like this:
File corruption search
Number of errors: 58
File: #GSOR.WED  Offset: 4ch  Error message: 72 unused bytes between Tilemap lookup offset(4ch) and # wall polygons(98h)
File: ARDEM.ARE  Offset: 1ach  Error message: 2372 unused bytes between Unknown(1ach) and Name(b70h)
File: ARDEM.ARE  Offset: 10f4h  Error message: 20 unused bytes between Unknown(10f4h) and Name(1140h)
File: ARDEM.ARE  Offset: 2344h  Error message: Present at(2344h) overlaps Day song reference number(2344h) by 4 bytes
File: ARDEM.ARE  Offset: 2348h  Error message: Animation(2348h) overlaps Night song reference number(2348h) by 8 bytes
File: ARDEM.ARE  Offset: 2350h  Error message: Animation nr.(2350h) overlaps Battle song reference number(2350h) by 2 bytes
File: ARDEM.ARE  Offset: 2350h  Error message: Battle song reference number(2350h) overlaps Frame nr.(2352h) by 2 bytes
File: ARDEM.ARE  Offset: 2354h  Error message: Flags(2354h) overlaps Unknown(2354h) by 4 bytes
File: ARDEM.ARE  Offset: 2358h  Error message: Unknown(2358h) overlaps Unknown(2358h) by 4 bytes
File: ARDEM.ARE  Offset: 235ch  Error message: Unknown(235ch) overlaps Unknown(235ch) by 4 bytes
File: ARDEM.ARE  Offset: 2360h  Error message: Palette(2360h) overlaps Unknown(2360h) by 8 bytes
File: ARDEM.ARE  Offset: 2368h  Error message: Unknown(2368h) overlaps Unknown(2368h) by 4 bytes
File: ARDEM.ARE  Offset: 236ch  Error message: Filename?(236ch) overlaps Name(236ch) by 16 bytes
File: ARDEM.ARE  Offset: 236ch  Error message: Name(236ch) overlaps Unknown(237ch) by 16 bytes
File: ARDEM.ARE  Offset: 2380h  Error message: Filename?(2380h) overlaps Location: X(238ch) by 4 bytes
File: ARDEM.ARE  Offset: 2390h  Error message: Unknown(2390h) overlaps Present at(2390h) by 4 bytes
File: ARDEM.ARE  Offset: 2394h  Error message: Unknown(2394h) overlaps Animation(2394h) by 4 bytes
File: ARDEM.ARE  Offset: 2394h  Error message: Animation(2394h) overlaps Unknown(2398h) by 4 bytes
File: ARDEM.ARE  Offset: 2398h  Error message: Unknown(2398h) overlaps Animation nr.(239ch) by 56 bytes
File: ARDEM.ARE  Offset: 23b8h  Error message: Name(23b8h) overlaps Name(23d4h) by 4 bytes
File: ARDEM.ARE  Offset: 23d4h  Error message: Name(23d4h) overlaps Location: X(23d8h) by 28 bytes
File: ARDEM.ARE  Offset: 23f4h  Error message: Unknown(23f4h) overlaps Creature 1 string (23f4h) by 4 bytes
File: ARDEM.ARE  Offset: 23f8h  Error message: Palette(23f8h) overlaps Creature 2 string (23f8h) by 8 bytes
File: ARDEM.ARE  Offset: 2400h  Error message: Unknown(2400h) overlaps Creature 4 string (2400h) by 4 bytes
File: ARDEM.ARE  Offset: 2480h  Error message: 180 unused bytes between Unknown(2480h) and Item(256ch)
File: ARPSQ2.ARE  Offset: 3a04h  Error message: 148 unused bytes between Unknown(3a04h) and X(3aa0h)
File: ARPSQ2.ARE  Offset: 3abeh  Error message: 24 unused bytes between Y(3abeh) and X(3ad8h)
File: ARPSQ2.ARE  Offset: 3ae6h  Error message: 304 unused bytes between Y(3ae6h) and X(3c18h)
File: ARPSQ2.ARE  Offset: 3c8ah  Error message: 216 unused bytes between Y(3c8ah) and X(3d64h)
File: ARPSQ2.ARE  Offset: 3d72h  Error message: 620 unused bytes between Y(3d72h) and X(3fe0h)
File: ARPSQ2.ARE  Offset: 3feeh  Error message: 136 unused bytes between Y(3feeh) and X(4078h)
File: ARPSQ2.ARE  Offset: 53c4h  Error message: 12 unused bytes between Unknown(53c4h) and Name(540ch)
File: ARPSQ2.ARE  Offset: 54b8h  Error message: Unknown(54b8h) overlaps X-coord(54e4h) by 12 bytes
File: ARPSQ2.ARE  Offset: 55e8h  Error message: 48 unused bytes after Unknown(55c4h)
File: BH0111.ARE  Offset: 522h  Error message: 324 unused bytes between Y(522h) and X(668h)
File: BH0114.ARE  Offset: 3feh  Error message: 104 unused bytes between Y(3feh) and X(468h)
File: BH0118.ARE  Offset: 87eh  Error message: 16 unused bytes between Y(87eh) and X(890h)
File: BH0119.ARE  Offset: 412h  Error message: 112 unused bytes between Y(412h) and X(484h)
File: BH0201.ARE  Offset: 50eh  Error message: 104 unused bytes between Y(50eh) and X(578h)
File: BH0202.ARE  Offset: 4e6h  Error message: 48 unused bytes between Y(4e6h) and X(518h)
File: BH0501.ARE  Offset: 50eh  Error message: 104 unused bytes between Y(50eh) and X(578h)
File: BH0502.ARE  Offset: 4e6h  Error message: 48 unused bytes between Y(4e6h) and X(518h)
File: CB3661.WED  Offset: 1f60h  Error message: 4 unused bytes between Y(1f60h) and X(1f66h)
File: CB3661.WED  Offset: 1fd2h  Error message: X(1fd2h) overlaps X(1fd2h) by 2 bytes
File: CB3661.WED  Offset: 1fd4h  Error message: Y(1fd4h) overlaps Y(1fd4h) by 2 bytes
File: CB3664.WED  Offset: 20b6h  Error message: 4 unused bytes between Y(20b6h) and X(20bch)
File: CB3664.WED  Offset: 20ech  Error message: X(20ech) overlaps X(20ech) by 2 bytes
File: CB3664.WED  Offset: 20eeh  Error message: Y(20eeh) overlaps Y(20eeh) by 2 bytes
File: DD1401.WED  Offset: 34h  Error message: 96 unused bytes between Tilemap lookup offset(34h) and # wall polygons(98h)
File: DW#ABBL2.DLG  Offset: c4h  Error message: Text(c4h) overlaps Text(c4h) by 34 bytes
File: POTSELCA.STO  Offset: 78h  Error message: Unknown(78h) overlaps Item(98h) by 4 bytes
File: POTSELCA.STO  Offset: 2fch  Error message: 4 unused bytes between Infinite supply flag?(2fch) and Store purchases(304h)
File: PSFURN.DLG  Offset: 38a9h  Error message: Text(38a9h) overlaps Text(38a9h) by 21 bytes
File: PSFURN.DLG  Offset: 38a9h  Error message: 21 unused bytes between Text(38a9h) and Text(38beh)
File: PSFURN.DLG  Offset: 38beh  Error message: Text(38beh) overlaps Text(38beh) by 21 bytes
File: PSFURN.DLG  Offset: 38beh  Error message: 21 unused bytes between Text(38beh) and Text(38d3h)
File: TS0020.ARE  Offset: 458h  Error message: 16 unused bytes between Flags(458h) and X(46ch)
File: TT0100.WED  Offset: e1ech  Error message: 12 unused bytes between Tilemap index 5(e1ech) and Polygon index(e1fah)

The worst of these are obviously ardem.are with 24 errors (Domains of Dread mod), arpsq2.are with 9 errors (PlanarSphereMod), psfurn.dlg with 4 errors (PlanarSphereMod), 2 "Check the bodies" .wed's with three errors each (CB3661.WED and CB3664.WED), 2 errors with "potselca.sto" (Region Of Terror) and 8 Bonehill areas with 1 single error.

#4 Sam.

Sam.
  • Administrator
  • 1294 posts

Posted 18 September 2009 - 05:34 PM

I wonder if there is real file corruption for all of these or if a tool could be written to fix some of them. For instance, could you just remove all of the unused bytes and correct the offset values?

Interestingly, the second set of "Unused Bytes?" in TC1200N.WED translates to what looks kind of like a charset:
[codebox]
X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~  � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ­ ® ¯ ° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß à á â ã ä å æ ç è é ê ë ì í î ï ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ �

































!
"
#
$
%
&
'
(
)
*
+
,
-
.
/
0
1
2
3
4
5
6
7
8
9
:
;
<
=
>
?
@
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
[
\
]
^
_
`
a
b
c
d
e
f
g
h
i
j
k
l
m
n
o
p
q
r
s
t
u
v
w
x
y
z
{
|
}
~


































¡
¢
£
¤
¥
¦
§
¨
©
ª
«
¬
­
®
¯
°
±
²
³
´
µ

·
¸
¹
º
»
¼
½
¾
¿
À
Á
Â
Ã
Ä
Å
Æ
Ç
[/codebox]
And the first set of "Unused Bytes?" in TC1200N.WED has each of the above characters except each is preceded by �ÿÿ����. Any idea what that's about?

Edited by Sam., 18 September 2009 - 05:39 PM.

"Ok, I've just about had my FILL of riddle asking, quest assigning, insult throwing, pun hurling, hostage taking, iron mongering, smart-arsed fools, freaks, and felons that continually test my will, mettle, strength, intelligence, and most of all, patience! If you've got a straight answer ANYWHERE in that bent little head of yours, I want to hear it pretty damn quick or I'm going to take a large blunt object roughly the size of Elminster AND his hat, and stuff it lengthwise into a crevice of your being so seldom seen that even the denizens of the nine hells themselves wouldn't touch it with a twenty-foot rusty halberd! Have I MADE myself perfectly CLEAR?!"

--<CHARNAME> to Portalbendarwinden

--------------------

post-10485-0-15080600-1348188745.jpg
___________Old pen and paper modules of the 70s and 80s.___________

CA Forums CA Homepage


#5 OneEyedPhoenix

OneEyedPhoenix
  • Member
  • 308 posts

Posted 21 September 2009 - 07:26 AM

Anybody know anything more about these types of errors?

#6 Zyraen

Zyraen
  • Modder
  • 1402 posts

Posted 21 September 2009 - 09:23 AM

from some experience dealing with ITMs, SPLs etc, such errors are common when you are modifying a file, particularly increasing the number of effects.

For me, it has something to do with the field I'm selecting when I click Add a Effect. So I kinda just select a different row and the end result works well. even then for complicated ITMs and SPLs I save duplicates often so that I don't end up having to redo everything.

I'm not sure about others though, just what i know from dabbling.

kiyos.jpg____btlbn2.gif____kovaS.jpg
Love between a Law Enforcer and a Fugitive - can such a thing even happen?
SoA Release - Overview / Download Links

Zyraen's Miscellaneous Mods - Ust Natha Accelerator, item tweaks, XP caps, The Ub3r Reaver Kit, and much more...
Spellhold Gauntlet - more than just a Spellhold-Be-Gone
Hidden Kits - hidden dual-classed kits with a twist for progression


#7 Miloch

Miloch

    Barbarian

  • Modder
  • 6573 posts

Posted 21 September 2009 - 01:06 PM

Usually these errors suggest offsets are incorrect. Taking Sam.'s tcgobsha.cre for example, the Memorised Spells Offset points to 0x45c. In reality, they begin at 0x34c. This should never happen if you're patching or creating your CREs correctly. DLTCEP is probably better at this than NI, as are the ADD_SPELL macros in WeiDU. I think Nythrun's resource fixer macros (buried around here somewhere, or in the /lib folder of most of my mods) will fix most of these successfully (for CREs anyway) though some are fubared beyond recovery.

Infinity Engine Contributions
Aurora * BG1 NPC * BG1 Fixpack * Haiass * Infinity Animations * Level 1 NPCs * P5Tweaks
PnP Free Action * Thrown Hammers * Unique Containers * BG:EE * BGII:EE * IWD:EE
================================================================
Player & Modder Resources
BAM Batcher * Creature Lister * Creature Checker * Creature Fixer * Tutu/BGT Area Map & List * Tutu Mod List
================================================================
"Infinity turns out to be the opposite of what people say it is. It is not 'that which has nothing beyond itself' that is infinite, but 'that which always has something beyond itself'." -Aristotle


#8 -Guest-

-Guest-
  • Guest

Posted 24 September 2009 - 08:50 PM

Most of these sorts of errors can be safely ignored.

For some engines, NI doesn't actually know all the structures, so you'll get spurious errors (there are just floating sections of data that NI doesn't try to handle). For dialogues, there are certain instances where WeiDU can create dialogues that game likes just fine but that NI will complain about.

Most of this sort of "corruption" will either lead to a game crash or have little effect at all. So unless you're crashing, it's not worth worrying about.

If you're creating files, NI will happily sprinkle random corruption into them, then erase your hard drive and bust you for drug trafficking. Don't create your files in NI, please.