PDA

View Full Version : Error GEN1094



David Webber
10-05-2014, 08:52 AM
I am suddenly getting an error message compiling a script which I don't think I've changed for months.

Towards the end, after

Linking Loader...
Compile Version Resource...
Code size: 14848 bytes

I get

Fatal Compiler Error GEN1094: Cannot inject stub loader entry point: Para 1: <installer-file-name.exe> Para 2: 14848 Para3: 6664

I can't find any information on errors. What do I have to do?

[ I'm using SetupBuilder Developer Edition Version 7.4.3313 ]

Dave

David Webber
Mozart Music Software

linder
10-05-2014, 09:09 AM
David,

You have received a buggy definition update from your protection (anti-virus / anti-spyware, etc.) vendor ;) That is the reason why it "suddenly" started.

Search for GEN1094 here in the forum and you'll find tons of threads.

Hope this helps a bit.

Friedrich

David Webber
10-05-2014, 10:40 AM
David,
You have received a buggy definition update from your protection (anti-virus / anti-spyware, etc.) vendor ;) That is the reason why it "suddenly" started.
Search for GEN1094 here in the forum and you'll find tons of threads.
Hope this helps a bit.
Friedrich

Thanks for an incredibly quick reply - on a Sunday too! Impressive.

Thought I'd searched the other threads but obviously made a pig's ear of it - sorry.

I use McAfee - not AVG or ESET - on Windows 8.0 but I guess the cause is the same.

Interestingly (perhaps) I have different 'compilations' (full version, beta version, evaluation version) with the same script which behaves slightly differently according to the value of a compiler variable, and the problem doesn't occur for all of them. So I guess the problem is some combination of bytes in the file it's creating.

But now I have to figure out a way round it.

Dave

David Webber
Mozart Music Software

David Webber
10-05-2014, 10:50 AM
You have received a buggy definition update from your protection (anti-virus / anti-spyware, etc.) vendor ;) That is the reason why it "suddenly" started.
Friedrich

Well that wasn't too bad - I just went into McAfee and switched 'real-time scanning' off while I compiled, and Bob's my uncle - success!

[And scanning the installation executable afterwards tells me it doesn't have a virus, so there is definitely something funny going on.]

Dave
David Webber
Mozart Music Software

linder
10-06-2014, 02:33 AM
Hi Dave,

Does not make any difference. AVG, ESET, whatever. McAfee introduced the false-positive bug in one of your latest definition updates. What you can try to do is to add your Output folder to the "exclusion" list. This should work around their bug. You can contact your virus-protection vendor and report the false-positive. With some luck, they'll fix it :)

Friedrich

linder
10-06-2014, 02:36 AM
Dave,

No need to turn real-time scanning off. It should be enough to add the Output folder to the exclusion list. It's caused by a false-positive bug in one of your latest McAfee definition updates.

Friedrich