Archive: NSIS support for Win95
NSIS support for Win95
I am working on an installer for our
product and have run into some issues
installing the product on Win95. The
installer was built on WinNT then
tested in Win95. When we run the
installer on Win95, sometimes a bitmap
is misplaced and on one screen the
textfields do not display at all.
Are there issues supporting Win95?
I don't know of any issues with Windows 95.
What version of NSIS? What bitmap? What text? Does it happen with the examples too? Can you attach an example script if it doesn't?
I am using the latest version, 2.0 beta 3.
The example scripts seem to work ok,
as well as the majority of our installer.
There are 2 screens that don't work,
one displays the bitmap in the wrong
place and the other doesn't display
the text types at all. I looked at the
.ini file with the bitmap issue and I
noticed that NumFields=9 when in fact there were only 7 actual fields. The text fields not displaying may be an issue with the .nsi script as there is some dynamic string writing going on.
Thanks for the reply.
I understand you found out the problem. Is that correct or are you still having problems on Windows 95?
I did find out the issue with the bitmap problem. I'm investigating the other
problem right now. I probably jumped to
conclusions assuming the problems were
all Win95, but I was surprised to learn
our product manager was testing on Win95 when as a rule we don't support our
product on Win95.
Thanks for the quick replies.
Ok, I think I resolved the textfield problem seen on Win95, but not WinNT. In the .ini file defining the database properties, there are text fields that are to be set later. For some reason, the initital state is empty, with an additional state=1 declaration.
[Field 3]
Type=Text
state=
left=0
right=300
top=20
bottom=32
state=1
If I remove the state=1 declaration, then the problem disappears. For some reason this is not an issue on WinNT.
Thanks for listening to my ramblings.
You can't have more than one value with the same name in one section. If you do that you get an invalid INI file. Windows NT tends to deal with errors better, I guess that's why you have problems with this on Windows 95.