"Program too big to fit in memory"

[NewsArchive]

I run Wupdate to check for an update. An update is found and downloaded.
When the update is attempted, I am getting what seems to be a DOS window
which flashes the error "Program too big to fit in memory".

The setup program physical size is 10445KB.

If I download the same setup program without using Wupdate, the program
runs correctly with no error.

The current workstation is using Windows7 Home Premium 32.

The Wupdate setup is copied to the program folder.

The download setup is copied to a folder under the Documents folder.

Any clue what's happening here?

Thanks,

Bob

[NewsArchive]

Bob,

>
> Any clue what's happening here?
>

Yes, I assume the downloaded file is corrupted (transmission error,
protection software modified, etc.).

Friedrich

[NewsArchive]

BTW, you can check this by verifying the code-signature of the downloaded
file.

Friedrich

[NewsArchive]

This is an interesting 'Why does a corrupted binary sometimes result in
"Program too big to fit in memory"?' reading:

http://blogs.msdn.com/b/oldnewthing/archive/2006/01/30/519388.aspx

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows 7 installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Friedrich,

You are correct, the code signature on the program downloaded using
Wupdate, is missing. When I download the same exact program directly
from the website the signature is there.

Is there no solution? I tried this on two separate computers with the
same result.

What would cause the code signature to be striped from the program?

Bob

[NewsArchive]

Hi Bob,

> You are correct, the code signature on the program downloaded using
> Wupdate, is missing. When I download the same exact program directly from
> the website the signature is there.
>
> Is there no solution? I tried this on two separate computers with the same
> result.
>
> What would cause the code signature to be striped from the program?

This has nothing to do with SetupBuilder, so I can only guess what
happens. "Something" (perhaps a protection software product) corrupts the
downloaded file. If wupdate.exe (or wucheck.exe) does not report any error
then the file downloaded okay and the server did not report any error.

Hope this helps.

Friedrich

[NewsArchive]

Friedrich,

Well, this is interesting. I just went to the site and changed
permissions on the program from 664 to 755, retried the download using
Wupdate, and it worked.

I'm not sure what that means, because the permission has been set to 664
for at least 2 years.

Whatever works, I will take.

Thanks,

Bob

[NewsArchive]

Bob,

> Well, this is interesting. I just went to the site and changed permissions
> on the program from 664 to 755, retried the download using Wupdate, and it
> worked.
>
> I'm not sure what that means, because the permission has been set to 664
> for at least 2 years.
>
> Whatever works, I will take.

IMO, it should make no difference but it tells us that it is not a
transmission problem but a server side issue.

664 means that owner is read/write, group is read/write, other is read-only
755 means that owner is read/write/execute, group is read, execute, other is
read/execute

Friedrich

[NewsArchive]

I agree. Should I ever discover what is really happening, I will let you
know.

Thanks,

Bob