V3.0.102 Unstable Updated

[Valik]

I can't even create such an entry in regedit,

It take it such entries still manage to exist?

I don't use regedit, but the editor I do use will allow me to create such keys. I assume this issue was found because some application is incorrectly doing it with some key, also.

[Holger]

That is i.e. (I think) if you install many patche and/or then use "qchain" to install only the files with the highest version.

I think the tool then will change the lines to this...

[bcording]

The MoveFileEX API will create a NULL value in the PendingFileRename registry key to copy a file to NULL thus deleting it at bootup.

[ezzetabi]

I don't use regedit, but the editor I do use will allow me to create such keys.  I assume this issue was found because some application is incorrectly doing it with some key, also.

The problem has been born because someone (and also I) wanted to make a _DeleteOnReboot function that needs double null to works.

Edit: As Bcoding said.

Edited July 26, 2004 by ezzetabi

[Jon]

Updated:

http://www.autoitscript.com/autoit3/files/unstable/autoit/

3.0.102 (27th July, 2004) (Beta)

- Changed: REG_MULTI_SZ values allow double NULL values.

- Changed: BirOr(), BitAnd() and BitXOR() take up to 255 parameters

- Changed: FileSelectFolder() flag changes

- Added: DriveMapAdd(), DriveMapDel() and DriveMapGet()

[Holger]

@Jon: thanks

At first only a very small helpfile-bug in the BitAnd/Or/Xor-functions:

value2 The second number.
alue n 
[optional] The nth number - up to 255 values can be specified.

Do you see it? it's the letter "v" -> "alue n".

[Jon]

Updated:

http://www.autoitscript.com/autoit3/files/unstable/autoit/

- Fixed the issues with FileGetSize

- Documented the remote registry stuff

- DriveMapAdd returns the drive letter used when * is specified

[Jon]

Updated:

- Minor script reading bug (in compiled scripts)

- Removed left over debug code from FileGetSize