(devtool)installer err - cannot locate program input point DiscardVirtualMemory on dynamic link library KERNEL32.dll

[jzy-chitong56]

Unable to locate program input point DiscardVirtualMemory on dynamic link library KERNEL32.dll

I'm not sure what the official English prompt is, so I'll post it in Chinese for you to proofread the machine translation above 无法定位程序输入点 DiscardVirtualMemory 于动态链接库 KERNEL32.dll 上

This issue seems to be common in WIN7, affecting all electronic packaging

@paulo101977 Excuse me, but I don't know how to handle it. Sorry

[SMUnlimited]

Based on translation installer still compiling for win10 and above somehow. Should be fixed as per https://github.com/SMUnlimited/AMAI/issues/317

Unless trying to use 32bit instead of a 64 bit system?

[paulo101977]

Unable to locate program input point DiscardVirtualMemory on dynamic link library KERNEL32.dll

I'm not sure what the official English prompt is, so I'll post it in Chinese for you to proofread the machine translation above 无法定位程序输入点 DiscardVirtualMemory 于动态链接库 KERNEL32.dll 上

This issue seems to be common in WIN7, affecting all electronic packaging

@paulo101977 Excuse me, but I don't know how to handle it. Sorry

Apologies for the delay. I didn't understand the context, but is it not due to the system version?

[paulo101977]

Based on translation installer still compiling for win10 and above somehow. Should be fixed as per #317

Unless trying to use 32bit instead of a 64 bit system?

I thought the same. Maybe because the system is 32 bits. I think we would have to generate a 32-bit artifact and test it.

[jzy-chitong56]

According to my personality •᷄ࡇ•᷅
Then don't test it, just package it as 64 bit . Write in the description that only 64 bit is supported o(￣ヘ￣o＃)

This kind of dependency package is too troublesome to check

[paulo101977]

According to my personality •᷄ࡇ•᷅ Then don't test it, just package it as 64 bit . Write in the description that only 64 bit is supported o(￣ヘ￣o＃)

This kind of dependency package is too troublesome to check

There is a way to compile using 32 bits, but this has to be done in deploy: npm run electron:build -- --ia32 So, we would have to run the build both to generate the 64-bit artifact and another for 32 bits.

[jzy-chitong56]

There is a way to compile using 32 bits, but this has to be done in deploy: npm run electron:build -- --ia32

So, we would have to run the build both to generate the 64-bit artifact and another for 32 bits.

If you're saying you don't need to worry about the configuration file and just modify the packaging command, I've already packed the package, but I don't know where to find a 32-bit system for testing. Sorry to ask for help

I like to package attachments on the workflow because I don't know how to install environments on a computer https://github.com/jzy-chitong56/Electron/actions/runs/11191617667

[jzy-chitong56]

it was found that the program is still 64 bit, so compilation cannot generate a 32-bit program

[paulo101977]

There is a way to compile using 32 bits, but this has to be done in deploy: npm run electron:build -- --ia32 So, we would have to run the build both to generate the 64-bit artifact and another for 32 bits.

If you're saying you don't need to worry about the configuration file and just modify the packaging command, I've already packed the package, but I don't know where to find a 32-bit system for testing. Sorry to ask for help

I like to package attachments on the workflow because I don't know how to install environments on a computer https://github.com/jzy-chitong56/Electron/actions/runs/11191617667

We could create two build processes. One for 32bits and one for 64bits. However, I had never tested this process for 32 bits, I don't know if it depends on some artifact, lib, etc.

[jzy-chitong56]

We could create two build processes. One for 32bits and one for 64bits. However, I had never tested this process for 32 bits, I don't know if it depends on some artifact, lib, etc.

no need My R&D team used the same tools to package our company's own software, but it still cannot run on WIN7 X64 So it should still be a compatibility issue with WIN7

[paulo101977]

We could create two build processes. One for 32bits and one for 64bits. However, I had never tested this process for 32 bits, I don't know if it depends on some artifact, lib, etc.

no need My R&D team used the same tools to package our company's own software, but it still cannot run on WIN7 X64 So it should still be a compatibility issue with WIN7

Yes, that could be it too. And perhaps even Electron's lack of support for Windows 7.

[jzy-chitong56]

https://blog.csdn.net/u012864465/article/details/135888718

here said , @SMUnlimited electron use 21.4.4 electron-builder use 21.2.0

[SMUnlimited]

Someone needs to try various tests before we downgrade.

Try electron downgrade only and see if that works on Win7 Downgrade electron-builder only and see if that works on Win7 as there is no hints this is incompatible with Win7. Try both and see if that works.

Official documentation states that electron 22 is the last version to work with Win7. The result of tests will be the right fix.

[jzy-chitong56]

you can try my branches Some branches can be automatically packaged as attachments, just modify the code and I will download it locally for testing later, because modifying this is not my expertise, but I suspect I cannot find 32-bit