reg2au3

[Sigi2]

ever wanted to write many registry keys at once using regwrite within a script ??

tired about fileinstall a .reg file and run regedit -s ??

this script helps you converting your .reg files (exported with regedit from registry)

to .au3 code ready to paste into your script.

yes, it can read UNICODE files (exported with windows 2000/xp).

Unicode-Reading is limited to ANSI-Code only!

an other handicap is that autoit could not write every kind of registry

value types like REG_NONE or REG_LINK and others.

look at my way to read a simple unicode text file ...

the script is not well commented yet - give it a try.

comments / ideas are welcome.

Reg2au3.au3

Edited January 20, 2005 by Sigi2

[DirtyBanditos]

ever wanted to write many registry keys at once using regwrite within a script ??

tired about fileinstall a .reg file and run regedit -s ??

first use regedit to export a registry tree (yes windows 2000 / xp unicode file is

supported) and afterwards convert it to autoit code.

the only handicap is that autoit could not write every kind of registry

value types like REG_NONE or REG_LINK and others.

look at my way to read a simple unicode text file ...

the script is not well commented - give it a try.

comments / ideas are welcome.

<{POST_SNAPBACK}>

+

Hello Sigi Great Tool i like it ! Thx you)

[sugi]

I don't want to let you down but this was already written two times:

http://www.autoitscript.com/forum/index.php?showtopic=1952

IIRC these versions don't work with Unicode .regs... but it's not needed as you can simply tell regedit to write them as normal text (just change the filetype to NT4).

Edited January 19, 2005 by sugi

[SlimShady]

*I was planning on updating it soon anyway*

I know a way to convert Unicode to ASCII format.

I only need to know how to detect/recognize an Unicode file.

Then I'll be able to the following:

- Recognize if file Unicode: Convert and save to the TempDir

- Perform actions as usual

Edited January 20, 2005 by SlimShady

[sugi]

Why go through the hassle of detecting it?

RunWait('cmd /c type possibleunicode.txt > plaintext.txt', '', @SW_HIDE)

and you're done.

[Sigi2]

you're right - i have not seen the post before.

now, this is my way ...

this version can read unicode files, has full regdelete support and is tested with many complicated registry exports.

try this key with any other tool:

[HKEY_CURRENT_USER\SYSTEM\CurrentControlSet\Control\Session Manager\AppCompatibility]

have you already tryed it out ?

[SlimShady]

@sugi:

That works. I'll update this tomorrow (I hope).

Edited January 20, 2005 by SlimShady

[DirtyBanditos]

@sugi:

That works. I'll update this tomorrow (I hope).

<{POST_SNAPBACK}>

Thx SlimShady

[Sigi2]

@SlimShady

sorry - i really have not seen your post before .

i am curious about your version.

ok - i will rename my next version to avoid confusions

@sugi

why using external 'tools' when the job could be done inside autoit ?

[MHz]

first use regedit to export a registry tree (yes windows 2000 / xp unicode file is

supported) and afterwards convert it to autoit code.

@Sigi2

I think you mentioned external tools ? Sugi just reflected on what you said.

[Sigi2]

@MHz

have you read the purpose of the script ???

have i used any external tools / commands whitin the script ???

do i look as a bloody beginner to you ??

i have written this script on my own, without anybodies help or

stealing code from others.

@all

has anybody tested the script - any comments ?

helpful suggestions are welcome

Thx,

Sigi

PS: like testing around with reg2au3 ??

see the attechment (rename it to .reg first) and test it.

you can test it against oter reg2au3 skripts and see what happens ...

reg_test.txt

Edited January 20, 2005 by Sigi2

[Lazycat]

ANSI reg files converts fine. But script have troubles with non-english characters in the unicode reg-files.

[Sigi2]

ANSI reg files converts fine. But script have troubles with non-english characters in the unicode reg-files.

<{POST_SNAPBACK}>

Yes, I only tested with ANSI files - without any problem.

As i know there is no way dealing with Unicode Chars in AutoIt .

But hey, there are many more Limitations to live with:

some Types of Registry Values: ( * = supported in AutoIt )

* hex: REG_BINARY

hex(0): REG_NONE - Null value

* hex(1): REG_SZ - Null terminated Unicode fixed string value

* hex(2): EXPAND_SZ - Null terminated unexpanded Unicode/ANSI environment string value

* hex(3): REG_BINARY - Binary value of any form/length

* hex(4): REG_DWORD - 32-bit numerical value

hex(4): REG_DWORD_LITTLE_ENDIAN - little-endian 32-bit numerical value (same as REG_DWORD)

hex(5): REG_DWORD_BIG_ENDIAN - 32-bit reversed numerical value

hex(6): REG_LINK - Symbolic Unicode link string value

* hex(7): REG_MULTI_SZ - Array of multiple Unicode strings separated/ended by null characters

hex(8): REG_RESOURCE_LIST - Device driver list of hardware resources in Resource Map tree

hex(9): REG_FULL_RESOURCE_DESCRIPTOR - List of hardware resources in Description tree

hex(a): REG_RESOURCE_REQUIREMENTS_LIST - Device driver list of hardware resource requirements in Resource Map tree

hex(?): REG_QWORD - 64-bit numerical value

hex(?): REG_QWORD_LITTLE_ENDIAN - little-endian 64-bit numerical value (same as REG_QWORD)

an other limitation is the maximum line and string-lenght ...

this key

[HKEY_CURRENT_USER\SYSTEM\CurrentControlSet\Control\Session Manager\AppCompatibility]

is to big to handle.

@sugi

RunWait('cmd /c type possibleunicode.txt > plaintext.txt', '', @SW_HIDE)

works only with ANSI-Chars too ..

Thx,

Sigi

Edited January 20, 2005 by Sigi2

[MHz]

first use regedit to export a registry tree (yes windows 2000 / xp unicode file is

supported) and afterwards convert it to autoit code.

Hmm, ok? How should I read this? After 5 posts, you are set on Ignore.

[Sigi2]

@MHz

ok, thanx for your exeption

i updated my 1st post now and hope there is no more misunderstanding.

[MHz]

@MHz

ok, thanx for your exeption

i updated my 1st post now and hope there is no more misunderstanding.

<{POST_SNAPBACK}>

MisUnderstanding perhaps yes. I do appreciate your redifining of your first post. Members only respond to what is feed to them. I am glad that you can see this simple misunderstanding.

Cheers.

[sugi]

RunWait('cmd /c type possibleunicode.txt > plaintext.txt', '', @SW_HIDE)

works only with ANSI-Chars too ..

Yes, of course this can only work with characters in the correct code page. But that's the problem with the missing unicode support in AutoIt. As long continues to support out of date systems like Win9x it wont be possible to support unicode without problems.

[AcidicChip]

Why go through the hassle of detecting it?

RunWait('cmd /c type possibleunicode.txt > plaintext.txt', '', @SW_HIDE)

and you're done.

That only supports so big of a file though. Know of a way to support larger files?

[Simucal]

Way to reply to someone over one year after they have written their post

[GEOSoft]

As long continues to support out of date systems like Win9x it wont be possible to support unicode without problems.

I for one don't want to see AI drop support for 9x systems. That is the one area where you will best be able use AutoIt scripting to the benifit of all Windows users. MS will no longer be providing support for 9x (and not because it's*out of date*) so it will be up to individuals to provide the support and tools to do it. By the looks of the way things are shaping up with Vista you also won't get a lot of coding opportunities there. Using your theory of dropping support for *out of date systems* you are limiting yourself to Windows 2K (if you are a home user then support ended a year ago. As a commercial user you have 4 years left),

Server 2003 (Mainstream support ends next year, Extended support ends in 2012),

XP (Support ends in 2008, 2 years from now). In 2 years your XP will be *out of date* so should AutoIt no longer support it after that time?

BTW I run a MultiBoot system with 3OS's. One of those will always be 98SE even though I seldom work in it anymore.