Coppermill
3rd July 2004 13:18 UTC

NSISdl::Download Failing
I have been using NSISdl::Download for sometime and after extensive testing it is being rolled out, and we are starting to get reports of problems in the section that deals with NSISdl::Download.

We are getting the following error

The instrudtion at "0x77fcdf2a" referenced memory at "0x00180c08". The memory could not be "read"

I have attached a screen shot if this helps?

This has happened on two machine, one being a new installation of XP

Coppermill
3rd July 2004 13:27 UTC

File did not attach so posted another message

kichik
3rd July 2004 13:34 UTC

NSIS version? Script?

b_avery@yahoo.c
3rd July 2004 15:11 UTC

I'm using NSIS 2

Script is using

Using NSISdl to download from a random (or not random) mirror.nsi

From the archive

Here is the script:

# Downloads NSIS 2.0 Beta 3a from a max of 10 mirrors

Push "http://lib360.com/upgrade/Setup_Coview_Catalogue.exe"
Push 1
Push "$TEMP\Setup_Coview_Catalogue.exe"
Call DownloadFromRandomMirror
Pop $0

The machine this is failing on is running Windows 2000, with a Router VIGOR 2600, IE6

kichik
3rd July 2004 15:20 UTC

Why do you have two usernames? That's confusing.

I need the entire script. Specifically, I would like to see where that code is placed. NSISdl doesn't work outside of sections.

kichik
3rd July 2004 15:39 UTC

Looking at the screen shot I see it is in a section, as the progress bar of the installation page shows. I would still like to have the script so I can reproduce this.

Can you also use Dr. Watson and attach its crash report?

Coppermill
4th July 2004 17:33 UTC

Here is the dump.

I'll produce just the script that is failing so as you can repeat if possible on your machine

<?xml version=\"1.0\" encoding=\"UTF-16\"?>
<DATABASE>
<EXE NAME=\"Setup.exe\"
FILTER=\"GRABMI_FILTER_PRIVACY\">
<MATCHING_FILE NAME=\"Setup.exe\"
SIZE=\"326294\" CHECKSUM=\"0x3227A656\"
MODULE_TYPE=\"WIN32\" PE_CHECKSUM=\"0x0\"
LINKER_VERSION=\"0x0\" LINK_DATE=\"02/07/2004
17:26:11\" UPTO_LINK_DATE=\"02/07/2004 17:26:11\" />
</EXE>
<EXE NAME=\"ntdll.dll\"
FILTER=\"GRABMI_FILTER_THISFILEONLY\">
<MATCHING_FILE NAME=\"ntdll.dll\"
SIZE=\"654336\" CHECKSUM=\"0xC568C00F\"
BIN_FILE_VERSION=\"5.1.2600.1217\"
BIN_PRODUCT_VERSION=\"5.1.2600.1217\"
PRODUCT_VERSION=\"5.1.2600.1217\" FILE_DESCRIPTION=\"NT
Layer DLL\" COMPANY_NAME=\"Microsoft Corporation\"
PRODUCT_NAME=\"Microsoft® Windows® Operating System\"
FILE_VERSION=\"5.1.2600.1217 (xpsp2.030429-2131)\"
ORIGINAL_FILENAME=\"ntdll.dll\"
INTERNAL_NAME=\"ntdll.dll\" LEGAL_COPYRIGHT=\"©
Microsoft Corporation. All rights reserved.\"
VERFILEDATEHI=\"0x0\" VERFILEDATELO=\"0x0\"
VERFILEOS=\"0x40004\" VERFILETYPE=\"0x2\"
MODULE_TYPE=\"WIN32\" PE_CHECKSUM=\"0xA5841\"
LINKER_VERSION=\"0x50001\"
UPTO_BIN_FILE_VERSION=\"5.1.2600.1217\"
UPTO_BIN_PRODUCT_VERSION=\"5.1.2600.1217\"
LINK_DATE=\"05/01/2003 23:56:10\"
UPTO_LINK_DATE=\"05/01/2003 23:56:10\"
VER_LANGUAGE=\"English (United States) [0x409]\" />
</EXE>
<EXE NAME=\"kernel32.dll\"
FILTER=\"GRABMI_FILTER_THISFILEONLY\">
<MATCHING_FILE NAME=\"kernel32.dll\"
SIZE=\"930304\" CHECKSUM=\"0xCBCCF8A9\"
BIN_FILE_VERSION=\"5.1.2600.1106\"
BIN_PRODUCT_VERSION=\"5.1.2600.1106\"
PRODUCT_VERSION=\"5.1.2600.1106\"
FILE_DESCRIPTION=\"Windows NT BASE API Client DLL\"
COMPANY_NAME=\"Microsoft Corporation\"
PRODUCT_NAME=\"Microsoft® Windows® Operating System\"
FILE_VERSION=\"5.1.2600.1106 (xpsp1.020828-1920)\"
ORIGINAL_FILENAME=\"kernel32\"
INTERNAL_NAME=\"kernel32\" LEGAL_COPYRIGHT=\"© Microsoft
Corporation. All rights reserved.\"
VERFILEDATEHI=\"0x0\" VERFILEDATELO=\"0x0\"
VERFILEOS=\"0x40004\" VERFILETYPE=\"0x2\"
MODULE_TYPE=\"WIN32\" PE_CHECKSUM=\"0xE7ED3\"
LINKER_VERSION=\"0x50001\"
UPTO_BIN_FILE_VERSION=\"5.1.2600.1106\"
UPTO_BIN_PRODUCT_VERSION=\"5.1.2600.1106\"
LINK_DATE=\"08/29/2002 10:40:40\"
UPTO_LINK_DATE=\"08/29/2002 10:40:40\"
VER_LANGUAGE=\"English (United States) [0x409]\" />
</EXE>
</DATABASE>

kichik
7th July 2004 17:59 UTC

Can you make it produce a log with some more information? I was thinking of something along the lines of:

http://forums.winamp.com/showthread....ight=dr+watson

In my Dr. Watson there's an option for full dump. This should do the trick. Since you're on XP too, you should have it too.

If you don't want to attach it here, you can e-mail it to me.

Coppermill
7th July 2004 18:25 UTC

The machine it is falling over on is not a development environment, so not sure how I can improve the log for you?

kichik
7th July 2004 18:29 UTC

When you activate Dr. Watson it asks you what type of log you want. Choose full dump.