Why won't my C# app work on Windows 98 SE?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an application that works fine on 2000/XP but crashes on Windows 98.
I haven't started to do any extensive debugging because if I install Sp1 of
the framework it is fixed.

I believe it has to do with the fact that I persist data using
BinaryReader/Writer but I don't see how.

Any thoughts?

Thanks
 
CN78 said:
I have an application that works fine on 2000/XP but crashes on Windows 98.
I haven't started to do any extensive debugging because if I install Sp1 of
the framework it is fixed.

I believe it has to do with the fact that I persist data using
BinaryReader/Writer but I don't see how.

Any thoughts?

Well, it sounds like it's a bug which has been fixed in SP1 - fixing
bugs is the whole point of service packs. Any reason you can't just
tell your users that they have to have SP1 installed?
 
No reason but I just wanted to know what object(s) might be causing the
issue so that I can be mindful of this in the future. I don't really have
the time at present to do an extensive debugging invetigation to find out
either :)
 
CN,

I don't have a list which won't work, one I know for sure is the Smtp (web)
mail.
That is only delivered with NT from version 5 (it does not work on NT4
either).

You have to find yourself if there are some "special" things in your
application. (Let say resources) and than find out if there is something why
that is not working on W98/Me/Nt4

I hope this helps,

Cor
 
I have an application that works fine on 2000/XP but crashes on Windows 98.
I haven't started to do any extensive debugging because if I install Sp1 of
the framework it is fixed.

I believe it has to do with the fact that I persist data using
BinaryReader/Writer but I don't see how.

Any thoughts?

I've noticed on several occasions that if you tried to access a Control
from another thread than the UI thread (which is very bad), it usually
seems to work fine under XP but always crashes under 98. There are little
chances that this is the problem though since the service pack solved your
problem.
 
Back
Top