LiveCode Forums.

Simon wrote:Try the attached

Test_connect.zip

With that simple stack it fails?

Simon

Thanks Simon... I will try it first thing in the morning and report back!

Jay

Simon,

Here is a result screenshot of the standalone on the Vista target machine.
I am using LC 7.0.1.
I remain thoroughly confused.

Thanks in advance,
Jay

I'm thoroughly confused too, if that helps.

Does it fail with any test URL or only google? Does it help if you include the SSL libraries in your standalone (standalone settings, select SSL in the library list.)

jacque wrote:I'm thoroughly confused too, if that helps.

Does it fail with any test URL or only google? Does it help if you include the SSL libraries in your standalone (standalone settings, select SSL in the library list.)

Thanks for your suggestions Jacque...
I have tried multiple valid URL's with no success
...and will now try with the SSL dll and report back.

Thanks in advance,
Jay

Jacque,

No success with the SSL dll...
I think I will just completely remove LC and do a clean install (and hope that remedies the issue)... Fun!

Thanks,
Jay

It's a long shot and and didn't really think it would matter. I was thinking maybe Google was enforcing https, and LiveCode couldn't find the SSL certificate on those computers. But if multiple URLs fail, that's probably not the reason. It does seem computer specific but I've never heard of a problem like this before. It's the rebooting part that's so weird.

Some anti-virus utilities have a setting to block "unsafe" urls but I doubt Google is one of those. So, it's a mystery. I suppose you could look to see if any anti-virus apps on those machines are set up to scan URLs and if so, turn that off, but I'm guessing wildly. Another off the cuff idea is to try a different version of LC. There were some changes made to libURL in 6.x and 7.x.

Jacque,

Those are all great ideas... and I had also thought of and tried the https://google thing using the SSL dll.
I've tried LC 7.0.0 and 7.0.1... (maybe I crosslink engine library files having both versions installed during the windows build?)
Driving me nuts!
PS. the Android standalone version works fine

Thanks,
Jay

Try LC 6.7 for a lark.

Another idea: reset the hosts file. http://www.pchell.com/support/reset_win ... file.shtml MS has tool to do that, the link is at the bottom of the page. The flaw in this theory is that URLs work okay in a browser, which would be using the same hosts file.

jacque wrote:Try LC 6.7 for a lark.

Good News!... downloaded and installed LC 6.7.2
opened my rev file in 7.0.1 to save to legacy 6... there is no option for that in my dropdown?
saved to 5.5 (closest option) with a new file name.
Opened new rev file in LC 6.7.2 and created windows standalone
Installed on target Vista machine and works like expected... (obviously I'll need to change some UI things)
I noticed that the EXE was considerably smaller (almost 70%)
the standalone loaded incredibly faster than the 7.0.1 version...
Guess I'm using 6.7.2 moving forward

Thanks everyone for your help,
Jay

Cool. You should report this so no one else has to go through the suffering and heartache:http://quality.runrev.com

Only the versions where there was a file format change are listed in the dropdown, and 5.5 was the last format before 7.0. So you did the right thing.

Edit: the huge file size is due to all the unicode libraries that 7.0 requires.

jacque wrote:Cool. You should report this so no one else has to go through the suffering and heartache:

Only the versions where there was a file format change are listed in the dropdown, and 5.5 was the last format before 7.0. So you did the right thing.

Edit: the huge file size is due to all the unicode libraries that 7.0 requires.

Okay, then one would think that I could open the 7.0 file in LC 6.2 without the need to "save to legacy" option (file format change as you mention above), however I was given a dialog box stating that I couldn't open since the file was in a newer format? strange?

Thanks,
Jay

All versions are backward compatible (7.0 can open 5.5 stacks and other earlier formats) but none are forward-compatible. When the file format changes it looks like garbage to the older engines. The error used to say "stack is corrupted" and threw everyone for a loop, it's good they now give you the real reason.