Hello, I've tested this several times on several machines including VMware. Before I begin please don't quickly run off and build a test AMS, or Setup Factory app
You can only re-produce this bug IF <--- you have NEVER <--- used HTTP.Download, or HTTP.TestConnection on that PC before.
This bug will only appear the first time ever running AMS/SF on a new PC, or Virtual PC.
Once AMS/SF has downloaded, or tested the connection at least once on the same PC the bug then vanishes, you can even make new AMS apps, or Setup Installers and the bug doesn't happen on any of the newer apps, or setup installers once it's been at least run once.
The 1 time bug This is for AMS and Setup Factory latest versions, and older versions.
HTTP.Download
HTTP.TestConnection
If you have any HTTP.Download from a normal HTTP address it will take 31s for the file to appear at 0btyes and start to download. After the first time and every other time it's instant.
If you have any HTTP.TestConnection it will completely ignore the "Timeout" and it will run for 20 seconds regardless if you put any other number. After the first time just like above it then abides by this "Timeout"
You can only test this on a PC/VMware that hasn't run AMS HTTP.Download & HTTP.TestConnection beforeI would like to know what happens to make this bug vanish once it's been run at least once? I'm hoping the developers would jump in here, or at least tell me what gets set into the systems registry once it's been run once, so I can copy that data out and include it in my AMS/SF registry entries on startup.
If anyone else has found this bug before, is there any plugins they could provide me that maybe bypasses the built in http.download action script that seems to be faulty.
You can only re-produce this bug IF <--- you have NEVER <--- used HTTP.Download, or HTTP.TestConnection on that PC before.
This bug will only appear the first time ever running AMS/SF on a new PC, or Virtual PC.
Once AMS/SF has downloaded, or tested the connection at least once on the same PC the bug then vanishes, you can even make new AMS apps, or Setup Installers and the bug doesn't happen on any of the newer apps, or setup installers once it's been at least run once.
The 1 time bug This is for AMS and Setup Factory latest versions, and older versions.
HTTP.Download
HTTP.TestConnection
If you have any HTTP.Download from a normal HTTP address it will take 31s for the file to appear at 0btyes and start to download. After the first time and every other time it's instant.
If you have any HTTP.TestConnection it will completely ignore the "Timeout" and it will run for 20 seconds regardless if you put any other number. After the first time just like above it then abides by this "Timeout"
You can only test this on a PC/VMware that hasn't run AMS HTTP.Download & HTTP.TestConnection beforeI would like to know what happens to make this bug vanish once it's been run at least once? I'm hoping the developers would jump in here, or at least tell me what gets set into the systems registry once it's been run once, so I can copy that data out and include it in my AMS/SF registry entries on startup.
If anyone else has found this bug before, is there any plugins they could provide me that maybe bypasses the built in http.download action script that seems to be faulty.
Comment