Page 1 of 1

What's keeping me busy

PostPosted: Thu Jul 20, 2006 4:23 pm
by n7Epsilon
Here's what I'm working on currently:

1. Allow Reg2Inf to process a list file containing paths to REG files to merge into one final INF file.
- Progress: DONE

2. Process all subkeys and locate common roots and substitute with variables.
- Progress: DONE

3. %16427% was removed because it wasn't being correctly substituted.
- Progress: DONE

4. BUG: Incorrect handling of strings that have \r\n in them.
- Resolution: Appears to be a bug in REGEDIT itself ! I cannot fix something that doesn't work correctly by exporting from REGEDIT to begin with... :(

If anyone has any feature requests, please post in this thread... :)

PostPosted: Sat Jul 22, 2006 9:35 am
by n7Epsilon
Released 0.30 Beta, see announcement.

PostPosted: Wed Sep 13, 2006 10:03 pm
by n7Epsilon
Work in progress for version 0.40:

1. COMPLETE: Add support for:
- hex(1) : REG_SZ (hex notation) - see note below
- hex(3) : REG_BINARY (hex notation)
- hex(4) : REG_DWORD (hex notation)
- hex(6) : REG_LINK
- hex(b) : REG_QWORD
(Thanks to MrWoo for his research which helped a lot)

2. COMPLETE: RegEx compilation flag set for quicker matching in larger REG files.
3. COMPLETE: When Reg2Inf fails to convert a certain line, a Failed comment for that line is now logged in the output REG file (= Much easier debugging in larger files).
4. In Progress: Simplify some routines and combine redundant calls to decrease memory usage on larger files.
5. In Progress: Better handling when output already exists, merge handler code into main executable.
6. PLANNED: Reg2Inf will write to the screen the no. of produced warnings/failures after execution is complete.

- As noted in the 1st post, there are some programs that use multiline strings (ie: REG_SZ containing \x0D\x0A (\r\n)) which are not even exported by REGEDIT correctly and cannot be input using normal INF format type 0 REG line. While this can be overcome (somewhat), by expressing the REG_SZ in the REG file as hex(1), there is still no way to input this via INF. In such case Reg2Inf will convert hex(1) back to string and if \r\n is found, it will be replaced with a _ and a warning line will be written below the affected value(s).

(btw, I am conducting suicidal testing, trying to convert my SOFTWARE hive into INF format, a bit ambitious I know ;) :) ).