Beta 123 Scripts Don't Run And No Errors

[ptrex 57]

After upgrading to the Beta 123 some of the scripts don' t run through the SciTE ALT + F5.

This is the ouput :

>"C:\Program Files\AutoIt3\SciTe\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /beta /ErrorStdOut /in "C:\_\Apps\AutoIT3\_Development\Firewall\Firewall Log Analyzer.au3" /autoit3dir "C:\Program Files\AutoIt3\beta" /UserParams

>Running AU3Check (1.54.1.1) params: from:C:\Program Files\AutoIt3\beta

+>AU3Check ended.rc:0

>Running:(3.1.1.123):C:\Program Files\AutoIt3\beta\autoit3.exe "C:\_\Apps\AutoIT3\_Development\Firewall\Firewall Log Analyzer.au3"

There are no errors only the CPU hangs at 100 %

Without error messages I don' t have a clue to start looking at what's wrong.

I tried running my scripts as well as from others -> same problem.

Here is 1 example :

http://www.autoitscript.com/forum/index.ph...topic=15220&hl=

In version Beta 119 Everyting was working fine.

Can anyone give me a tîp where to start looking.

Did anything fundamental change in COM coding.

Thanks in advance !!

ptrex

[ptrex 57]

If I add trace lines to debug.

I get -1 status at RegEnumVal() Function.

Is that a hint ?

[ptrex 57]

I have seen that there are some REGENUM issues as of version 122, in the Bug Forum Section.

So maybe this post should be moved to the BUG section.

Thanks

[jpm 37]

I have seen that there are some REGENUM issues as of version 122, in the Bug Forum Section.

So maybe this post should be moved to the BUG section.

Thanks

if you have a small repro script do it.

As I remember the enumeration was not so good for key. But val certainly have been impact too.

[ptrex 57]

@jpm

If you go to my first post, click the link -> download the ODBCquery.au3 and run it as it is.

You will notice that the problem that the GUI does not display and it consumes 100 % CPU.

If you eliminate the REGENUM () function it is solved.

Thanks

[ptrex 57]

@Larry

It's not only this script that showed a difference in behaviour, there are more.

By the way, apart from the bad coding, those scripts ran good till Beta 119 ?

An other example is my Firewall Log Analyzer for XP see link in my signature.

In the first post is the au3 script.

Problems occured after Beta 119.

[jpm 37]

@Larry

It's not only this script that showed a difference in behaviour, there are more.

By the way, apart from the bad coding, those scripts ran good till Beta 119 ?

An other example is my Firewall Log Analyzer for XP see link in my signature.

In the first post is the au3 script.

Problems occured after Beta 119.

You right, for debugging some regenum issue I change the return on error.

it does not return "" anymore but @error should be check to work on abnormal condition.

Func ODBCsources($h_controlID, $s_RegEntry, $s_Type)
    Local $s_List, $i_dsncount, $s_VarNm, $s_Value, $i
    $i = 1
    While $@error = 0
        $s_VarNm = RegEnumVal($s_RegEntry,  $i)
        If @error = 0 Then
            $s_Value = RegRead($s_RegEntry, $s_Varnm)
            GUICtrlCreateListViewItem($s_VarNm & "|" & $s_Type & "|" & $s_Value, $h_controlID)
            $i += 1
            $i_DSNcount += 1
        EndIf
    Wend
EndFunc

Can I change the doc or do I really need to go back to what is documented?

the posted code was wrong in checking in the loop but more buggy as stated by Larry

Edited May 9, 2006 by jpm

[ptrex 57]

@Jpm

Thanks for the feedback.

I leave it up to you guys, wether you return back to previous behavious or stay as it is.

Best is to let everyone know, if you decide to stay as it is, that the behaviour has changed since version 119.

Regards,

ptrex

[jpm 37]

@Jpm

Thanks for the feedback.

I leave it up to you guys, wether you return back to previous behavious or stay as it is.

Best is to let everyone know, if you decide to stay as it is, that the behaviour has changed since version 119.

Regards,

ptrex

Thanks

I think I will document the new behavior as it help to understand what is going wrong. the error should be checked with @error first.

[jpm 37]

Thanks

I think I will document the new behavior as it help to understand what is going wrong. the error should be checked with @error first.

That's what I did

[ptrex 57]

@jpm

You are the MAX !!