file corruption with Netscape messenger?
Joe Turco
I just began hosting a 4 player game, and the host program continuously
complains that the .x# file from the player using Netscape messenger is
corrupt. I've had him resend me the file a number of times, but am having
no luck. All other player files are fine. Other than the email client, I
don't know what else could be causing the corruption.
Thanks in advance for any information.
- Joe
Charles Tosh
"Joe Turco" <joet...@hotmail.com> wrote in message
news:ruzj8.19464$ia.42...@typhoon.ne.ipsvc.net...
> Has anyone heard of any problems with Netscape messenger corrupting files?
I seem to remember problems of this sort from a very long time ago - perhaps
try a google search? I think it was something to do with erroneous encoding
of the file because of the email program mis-recognising its type.
I also seem to remember there was a way of configuring things to end this
problem... but as you may have guessed, I have no idea what it was :)
However, I do definately remember one thing: the corruption issues
disappeared when the stars-generated file was archived into a zip file and
attached/sent in .zip (or presumably any other compression format) form.
HTH... now back to lurking.
Sincerely,
Charles
-------------------------------------------------------------------------
With your help I can advance against a troop;
with my God, I can scale a wall.
- Psalm 18:29
-------------------------------------------------------------------------
Contact me by e-mail : cim DOT cvtosh AT ntlworld DOT com
Or view random stuff : http://homepage.ntlworld.com/charles.tosh/CiM/
-------------------------------------------------------------------------
Jean-Claude Stranart
small (<1k) files, ie at the beginning of the game. For some reason it decides
to ignore the encoding settings. The work around is to send yourself a (long)
junk message or two to pad up the .x file size to > 1024 bytes. Also, always
copy yourself on the turn you send the host. You can then see if the attachment
was properly included.
John
Ulrich Schweitzer
>Has anyone heard of any problems with Netscape messenger corrupting files?
That's and old problem. If you send a file that has an extension which
is not registered with windows and the file is small then Netscape
sends it as text/plain. This, of course, mutilates the file and stars
cannot open it any more.
There are workarounds such as sending yourself a long ingame message
every turn to pad the file or zipping it before sending.
However, I would recommend registering all the possible extensions of
x-files (.x1 .x2 .x3 ...) with windows and giving them the MIME type
application/octet-stream. Tell your player to do this and neither he
nor you need to worry about this any more.
Ulrich
James McGuigan
From http://www.starsfaq.com/bugs.htm
Netscape email attachment corruption :
Wen sending emails using Netscape, it will treat small attachments of an
unknown file type as text (7bit byte) instead of binary (8bit byte) and so
truncates the leading byte, this can lead to corruption of turn files sent
this way. The solution is to tell it that the various stars file types
should be sent MIME encoded.
--
Rules are written for those who lack the ability to truly reason,
But for those who can, rules become nothing more than guidelines,
And live their lives governed not by rules but by reason.
- James McGuigan
The Stars! FAQ (www.starsfaq.com)
Christian Ræbild
Instead of registering all .x# filetypes, you can configure Netscape
to treat all unknown filetypes as application/octet-stream. That is
faster and easier, and also prevents the problem from appearing
again later with other unregistered filetypes.
--
Med venlig hilsen / Best regards / Mit freundlichen grüßen
Christian Ræbild / Christian Raebild
Ulrich Schweitzer
>Instead of registering all .x# filetypes, you can configure Netscape
>to treat all unknown filetypes as application/octet-stream. That is
>faster and easier, and also prevents the problem from appearing
>again later with other unregistered filetypes.
I didn't know you could do that. Where will I find that option?
Ulrich
Christian Ræbild
I do not remember where that is in Netscape 4.7x, and I am using
Netscape 6.2 at home now, which is either hardcoded to treat unknown
filetypes as application/octet-stream, or autodetects filetype.
I am still using Netscape 4.74 at work, so if I remember to check, I
should be able to tell you tomorrow. It is an option specific to
Netscape 4.7x (and possibly earlier versions), you will not find
that option in Outlook or Outlook Express. I should know, at the
office we have to send out "keyfiles", which are encrypted license
registration data, containing a registration number, the name of the
end user, and data on which options are licensed, how many COM ports
can be used, and which control protocols can be used. Those files
are 2048 bytes in size, and they are 8 bit files. If you are
confused about the described content of those "keyfiles", check out
www.cimco-software.com ;-)
Linking to a company homepage when it can deliver useful
clarification isn't spamming, I believe :-)
Ulrich Schweitzer
>I am still using Netscape 4.74 at work, so if I remember to check, I
>should be able to tell you tomorrow. It is an option specific to
>Netscape 4.7x (and possibly earlier versions), you will not find
>that option in Outlook or Outlook Express.
Don't imply I'm using Outlook or I might think you are trying to
insult me ;-).
Actually I also only use Netscape 4.7x at work but I still have it
installed at home and just tried to find the option but couldn't
locate it. Are you sure it really exists?
>Those files
>are 2048 bytes in size, and they are 8 bit files.
I just did a small test and found out that 2KB is big enough to be
always sent as application/octet-stream. The limit seems to be
somewhere between 500 and 800 bytes (I'm to lazy to narrow it down
further).
>If you are
>confused about the described content of those "keyfiles", check out
>www.cimco-software.com ;-)
>
>Linking to a company homepage when it can deliver useful
>clarification isn't spamming, I believe :-)
We'll let it slip through, this time... :-)
Ulrich