zimsms
25th March 2004 14:01 UTC

MUI_DIRECTORY crash on NT 4SP6a?
Hello Everyone!,

I'm having an issue that only occurs on Windows NT4. When I run the Basic example that is included with NSIS it reproduces the problem. The problem is when I click the next button on the components screen to go to the directory screen I get an access violation error and the installer aborts.

What is causing this behaviour? If I remark the call to insert the directory page, the issue doesn't occur, but I'd like my end-user to be able to define the install dir.

NSIS 2.0 (from CVS 2004/03/24 4pm EST)
NT 4 SP 6a


Any help would be appreciated.

Cheers,

ZIMSMS

Joost Verburg
25th March 2004 15:25 UTC

Please try the stable 2.0 release.

zimsms
25th March 2004 15:29 UTC

Joost,

I can't use the stable one, because of the browse install bug you fixed for me. This was fine in the stable release, it's in the 'special one'.

Joost Verburg
25th March 2004 15:42 UTC

So it's a problem with the development version? Can you help us finding out when the problem was introduced?

zimsms
25th March 2004 15:48 UTC

I have one compiled on March 2 which works before the browse fix, and one on the 11th that doesn't. So it looks like it was introduced on the 2nd because that's when I built with the changes you gave me for the browse installation bug. I also have one built on the second a few hours after the other that doesn't work but has the browse fix, so that has to be it. I hope that helps.

kichik
26th March 2004 16:40 UTC

What's the exact error mesasge shown?

zimsms
26th March 2004 16:55 UTC

Here's an image of the error.

kichik
26th March 2004 17:02 UTC

What's the error without Dr. Watson? Can you get a stack trace (WinDbg.exe, VC, etc.)?

zimsms
26th March 2004 18:21 UTC

I apologize, but there is no development environment on our nt4 box. However, here is the dr watson log. I made sure it was empty before creating the crash. I used basic.exe (basic.nsi) to do this.


[attached below]

zimsms
26th March 2004 18:24 UTC

Looks like GetDiskFreeSpaceExW, isn't supported on NT4 using unicows.dll?

kichik
26th March 2004 18:32 UTC

No, GetDiskFreeSpaceExW is supported on NT4. The problem is probably wrong documentation in MSDN. It looks like GetDiskFreeSpaceExW doesn't check if one of its parameters is NULL like MSDN says it should.

Please attach large files/logs next time.

zimsms
26th March 2004 18:40 UTC

Kichik,

Sorry, I tried to attach it as a file, but it was too big. I guess I could have compressed it, my apologies. When should this be fixed?

kichik
24th April 2004 20:12 UTC

Fixed in latest CVS version.

mrtech
29th April 2004 20:34 UTC

Tried the latest dev build, but I'm still seeing this crash on NT systems, any help?

zimsms
29th April 2004 20:43 UTC

Even though you have the latest CVS, it is not in the included binaries. You will need to rebuild.

mrtech
29th April 2004 21:20 UTC

??, the latest Dev Snaphost is 4/29 the patch was checked in 4/24. I've downloaded the dev snapshot, installed it, rebuilt my installer and tested with no success.

What am I doing wrong here?

pengyou
29th April 2004 23:08 UTC

"Even though you have the latest CVS, it is not in the included binaries. You will need to rebuild."

This refers to rebuilding the NSIS compiler (makensis.exe), not rebuilding your script.

If you cannot rebuild the NSIS compiler, you'll need to wait until a new binary version of it is available.

You can check the Changelog (http://nsis.sourceforge.net/development/changelog/) to see if a new NSIS compiler (makensis.exe) is available.