Clock.ini bug?

[Ontosy]

I not know if it is a bug.

i have Clock.au3 and Clock.ini in a folder.

Clock.ini have:

[Clock]

Voice=222

I run:

$v=IniRead(@ScriptDir & "\Clock.ini","Clock","Voice","111")

and

$v is set to 111 intead of 22

if rename Clock.ini to aaaa.ini it work fine

again

I run:

$v=IniWrite(@ScriptDir & "\Clock.ini","Clock","Voice","333")

ini file not change 111 but if i restart au3 iniread get 333 from Clock.ini

[Melba23]

Ontosy,

I not know if it is a bug

I doubt it very much if you mean a bug in AutoIt.

This snippet works fine for me - I get the correct returns and the ini file is updated:

; Click.ini set to Voice=222

$v=IniRead(@ScriptDir & "Clock.ini","Clock","Voice","111")
ConsoleWrite($v & @CRLF) ; I get 222
$v=IniWrite(@ScriptDir & "Clock.ini","Clock","Voice","333")
$v=IniRead(@ScriptDir & "Clock.ini","Clock","Voice","111")
ConsoleWrite($v & @CRLF) ; I get 333 and the ini file holds that value

ini file not change 111

Why would it? You have just set it to 333!

M23

[Ontosy]

to me it not work.

do you have Autoit 3, 3, 8, 0?

do you have read Clock.ini with a editor?

The script work also for me but the "Clock.ini" file is not changed.

[guinness]

Is the file read-only? Is the file in use by another application?

[Ontosy]

Is the file read-only? Is the file in use by another application?

Not, Not.

[Melba23]

Ontosy,

Are you sure you are looking at the right Clock.ini file? Do you have another one somewhere other than in your @ScriptDir?

M23

[Ontosy]

I searched all disk but i have only 1 Clock.ini. The path is.

[PsaltyDS]

You said the Clock.au3 script and Clock.ini file were "in a folder". Are you compiling the script into an .exe and running it from somewhere else? If so, then @ScriptDir is pointing to a different location. Add a MsgBox() or something to report the full path from within the script, like:

MsgBox(64, "Debug", "Path = " & @ScriptDir & "Clock.ini")

See if that matches what you expect.

[Ontosy]

I not compiled it.

It that matches what i expect.

Edited January 2, 2012 by Ontosy

[PsaltyDS]

The INI functions you are using work fine in 3.3.8.0 and earlier versions. We can't help you until you post a short demo script we can run to reproduce the symptoms.

[Ontosy]

If i run this code in the file called "Clock.au3" or in any other way:

Dim $ini=@ScriptDir & "Clock.ini"
IniWrite($ini,"Clock","Left",111)

the Clock.ini is not created but the value in key section IniRead($ini,"Clock","Left","22") is readed. I scan all disks but Clock.ini is not found.

If i run this code:

Dim $ini=@ScriptDir & "Clockbbb.ini"
IniWrite($ini,"Clock","Left",111)

the Clockbbb.ini is created

i have tried in 2 computer.

Edited January 2, 2012 by Ontosy

[Ontosy]

I solved it's amazing !

On XP, we cannot use Clock.ini, Win.ini, System.ini, etc., as ini filename. These ini filenames are handled as "IniFileMapping". Administering the Windows NT Registry Quote: How Does Mapping Work? NT implements mapping by trapping the private profile API routines I mentioned in Chapter 1. Windows applications and components ordinarily use these calls to get and set data stored in INI files, but when there's a mapping entry, the NT kernel first checks for the presence of a mapping key. If one exists, and if it points to a key that contains data, that data is returned to the caller. If there's no mapping key, or if it points to an empty or non-existent Registry key, NT will go ahead and try to read the data from the INI file. The caller need never be aware that the data didn't come from the requested file. Mapping only occurs when there's a mapping key in place. These keys are stored beneath the HKLMSOFTWAREMicrosoftWindows NTCurrentVersionIniFileMapping subkey. If you look there, you'll notice a number of subkeys with names like Clock.INI, Win.INI, and SYSTEM.INI. These keys tie sections of the old Win 3.1-style INI files to keys in the Registry so that old Windows 3.1 components like the Clock and the original media controller interface (MCI) will continue to find their settings.

But it is strange to you that works! ; )

Edited January 2, 2012 by Ontosy

[Melba23]

Ontosy,

Well found!

M23

[guinness]

But it is strange to you that works! ; )

I believe most in this thread use Windows Vista or above. I found an article on MSDN that describes a little more about what you quoted from Rainmeter.

[PsaltyDS]

@Ontosy: Nice catch. I haven't had to mess with NT in almost a decade, and wouldn't have hit on that.

[Ontosy]

I haven't had to mess with NT in almost a decade, and wouldn't have hit on that.

This problem is also for Windows XP.