FF autoit not going past the first URL.

[tommytx]

Has anything changed recently with how FF interacts with autoit.. I cannot get it to do anything past start the first url and just hangs at that piont.
here is the code i am using..
The only thing it does is open up the vahud.com and never moves on to the test.htm page.. and does this on all my FF autoit programs..
I am using XP but it has alwasy been fine in the past..

 

#Include <FF.au3>

_FFStart("http://vahud.com")

    Sleep(2000)
    _FFAction("presentationmode", True)
    Sleep(2000)
    _FFOpenURL("http://vahud.com/test.htm")
    Sleep(2000)
Exit

and here is the rusults i obtain.
 

__FFStartProcess: ""C:\Program Files\Mozilla Firefox\firefox.exe" -new-window "http://vahud.com"  "-repl 4242 "
_FFConnect: OS: WIN_XP WIN32_NT 2600 Service Pack 3
_FFConnect: AutoIt: 3.3.12.0
_FFConnect: FF.au3: 0.6.0.1b-10
_FFConnect: IP: 127.0.0.1
_FFConnect: Port:   4242
_FFConnect: Delay:  2ms
_FFConnect ==> Timeout: TCPConnect Error: 10061
_FFConnect ==> General Error: Timeout: Can not connect to FireFox/MozRepl on: 127.0.0.1:4242
__FFSend ==> Socket Error
_FFCmd ==> Error return value
_FFOpenURL: http://vahud.com/test.htm
__FFSend ==> Socket Error
_FFCmd ==> Error return value
_FFOpenURL ==> No match: http://vahud.com/test.htm
>Exit code: 0    Time: 72.04

 

[Danp2]

Looks like MozRepl is either not installed or not running...

[AutoBert]

Downoad the actual FF.Au3 and test again. The console output tells ff want to connect on Port 4242 but afair it must be 42, so test the linked version. @Stilgar has posted the link on autoit.de yesterday and told the V0.6.0.2b is out of the beta state and had reached stable state. After testing come back and report.

Edited February 12, 2016 by AutoBert

[tommytx]

1 hour ago, AutoBert said:

Downoad the actual FF.Au3 and test again. The console output tells ff want to connect on Port 4242 but afair it must be 42, so test the linked version. @Stilgar has posted the link on autoit.de yesterday and told the V0.6.0.2b is out of the beta state and had reached stable state. After testing come back and report.

Looks like it was the Moz not activating automatically.. as I forced it on manually and its seemed ok.. so thanks for the advice...