Invalid Stream Format in Delphi 3 App
nos...@cp.duluth.mn.us
Has anyone else out there experienced seemingly random "Invalid Stream
Format" errors from an application compiled with Delphi 3?
I'll give some background information. This particular application was
originally written and compiled with Delphi 2.0. The versions compiled
under that compiler had no such problems. But the program has since
been moved to Delphi 3, and now the errors seem to be disturbingly
common (about 1% of users seem to report it.)
Here's the odd thing about this error: not only does it only appear on
1% of installations, but on those that DO exhibit the error, it seems to
happen in a random/different part of the program. Some machines will
show the error whenever Form A is displayed but not Form B, and some
will show the error when Form B is displayed but not Form A. (These are
not actual forms--I am just illustrating.)
What's even worse is that the errors also seem to be intermittant. The
affected machines will work sometimes and not other times.
I have heard of Invalid Stream Format errors in the Delphi IDE itself,
due to corrupt program files. But this seems to be totally unrelated to
that (I've never had such an error in the IDE.) Since all of the window
"streams" come from resources in the application file, it's not like the
streams are being modified in any way between attempts or between
machines.
I hope I have explained this adequately. Basically, it's just an
EXTREMELY frustrating problem, and I'd like to know if anyone else has
experienced it (and more importantly, if anyone has found a fix!!)
Thanks for your time,
--Matt Jensen
(mattj [.at.] computerpro [.dot.] com)
jame...@task.co.nz
I'm experiencing a similar problem in BC++5.01.
Basically what happened is that some fstream corrupted occasionally for
unknow reason. Reading corrupted fstream will return all 0, while
iostream.bad() shows no problem.
I have isolated the problem to a smaller range: It will happen if my program
opened a network remote file on another computer. If I keep the fstream open,
and Win95 find a network connection down. At this point of time Win95 will
fill the fstream with 0. It will corrupt the fstream even if the network
down only last half second and come back again, which I think could happen in
the Win95 network, and normally nobody will notice it. You can test this by
unplug the network connector, let Win95 realise this, then replug it in.
The thing I still don't understand is that I have several fstream opened,
only one fstream got problem as I found now. So the corruption should not be
caused by the physical network down, but by some other reason which caused
Win95 corrupted the particular fstream. Still cannot figure out what's the
cause. File accessing conflict? But I have synchronized the file properly.
What's your situation?
Please email the reply to jame...@task.co.nz.
JM
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum