Page 4 of 5
Re: Failed to check for update
Posted: Thu Nov 02, 2023 1:15 am
by Couin
Hmmm, which internet connection have you?
How about time this page answers?
https://jinglepalettereloaded.com/check ... hp?lastver
Re: Failed to check for update
Posted: Thu Nov 02, 2023 1:28 am
by SKHockeyDJ
That loads fast. Probably just my Internet. All that matters really is it works. My computer has always been a bit slow loading pages on Edge.
Re: Failed to check for update
Posted: Thu Nov 02, 2023 1:35 am
by Couin
Did you test the page with Edge ? Or another browser ?
If another browser, can you test with Edge ?
VB6 http request should use the Windows integrated internet browser (Internet Explorer for XP for example).
Re: Failed to check for update
Posted: Thu Nov 02, 2023 1:40 am
by SKHockeyDJ
No it was fast on Edge - that's what I tested it on.
Re: Failed to check for update
Posted: Thu Nov 02, 2023 1:59 am
by Couin
Thanks for feedbacks
Re: Failed to check for update
Posted: Sun Nov 05, 2023 6:49 am
by Couin
Hi,
I uploaded a new exe.
https://jinglepalettereloaded.com/files/JPUSC.exe
Can you download it and test ?
You should see a fast coutner increasing on the right side of form.
When you click on Command1 button, the counter should not freeze while getting http request result.
You should get the result (5.3.2) under the Command1 button.
Also, can you report me the "Timer cycle to get result" value ?
Can you confirm me, Boot Camp is only a boot menu , not a Virtual Machine (where you run Win 10) running on Mac ?
Thanks
Re: Failed to check for update
Posted: Sun Nov 05, 2023 9:12 pm
by SKHockeyDJ
I tried it out - I get the 5.3.2 and a time between 55-71 when I retry it.
I'm running a seperate Windows Partitiion, so it boots right into it, which was created by Bootcamp. All the drivers and stuff came from Apple to make it work, that's what Bootcamp does for Macs to make it boot/install Windows and install the necessary drivers, otherwise Windows wouldn't be able to be installed without major issues.
Re: Failed to check for update
Posted: Mon Nov 06, 2023 12:02 am
by Couin
Okay so it's not a virtual machine
Between 55 to 71 cycles, ok I understand, it means around 0,55 to 0,71 second, so that explains the"Failed to check" you have, becasue it's over the timeouts.
Can you confirm that the counter was continue to increase between hitting Command1 button, and the result appears ? I think yes, as well it is the same timer that increase the counter than measuring the timer cycles (55 t o 71 you have).
Re: Failed to check for update
Posted: Mon Nov 06, 2023 12:04 am
by SKHockeyDJ
Couin wrote: ↑Mon Nov 06, 2023 12:02 am
Can you confirm that the counter was continue to increase between hitting Command1 button, and the result appears ? I think yes, as well it is the same timer that increase the counter than measuring the timer cycles (55 t o 71 you have).
The Timer was slowest when I did the first check - around 71, but got faster each other time I clicked it.
Re: Failed to check for update
Posted: Mon Nov 06, 2023 1:15 am
by Couin
Ok but good if did not freeze