19 replies to this topic

[pscEx]

File Name: reg2WBS
File Submitter: pscEx
File Submitted: 31 Aug 2011
File Updated: 22 Dec 2012
File Category: Tools

Generates WinBuilder script code from *.reg files

reg2WBSprg.zip contains 2 files:

• cmdline app reg2WBSprg.exe as the real 'worker'
• GUI app reg2WBS.exe as wrapper for easier use

The generated script code can be optionally

• native WinBuilder script format
• API script format
• ...
• just the translated code lines
• full usable WinBuilder script code
• ...

Click here to download this file

Attached Thumbnails

• 

[carloscape]

I recently started to have problems using this tool. I am getting the following error when I open its GUI.

'0x' is not a valid integer value

I click ok, and the program starts. When I press build, I get an error dialog from windows asking to close the program and send a report. The script nevers builds.

Update: It seems the problem is in a specific registry file that the tool can't understand. I will attempt to modify the file in order to make it work.

[pscEx]

The easier answer first.

I am sure that I did not put any trojan into Reg2WBS code.
I cannot influence, how AV programs interprete some binary sequences.

If you do not trust me, just delete Reg2WBS.exe and forget it.

Now to

'0x' is not a valid integer value

That is right. But it never should appear on the first start of Reg2WBS.

IMO It only can appear in a second, third, ... start, when in the previous run this error occurred.

Reg2WBS stores the actual conversion when it exits.
In the next start it loads this actual conversion.

Please open Reg2WBS.ini, look at 'LastInFile' and post the file mentioned there.

I'm sorry, tomorrow morning I'm going into vacation for two weeks. So no more reactions for that time.

As temporary solution: Delete the "LastInFile" line and try a differen *.reg.

Peter

EDIT: I'm confused. The first post I saw mentioned a trojan. Did you edit your post in the mean time?

If yes, a hint for the future: Do not simply delete some lines, strike trough these lines, when they are not more relevant.

[pscEx]

Update: It seems the problem is in a specific registry file that the tool can't understand. I will attempt to modify the file in order to make it work.

Can you give me a chance to catch the issue?

For that I need consistence posts, maybe with (strikethough) edits and addons.

I cannot work with posts which completelly change all ten minutes ...

Peter

[carloscape]

Can you give me a chance to catch the issue?

For that I need consistence posts, maybe with (strikethough) edits and addons.

I cannot work with posts which completelly change all ten minutes ...

Peter

Sorry about that. I posted the file and noticed the infected file was in another unrelated directory, the notice just happened to occur when I pressed build so it was more of a coincidence than a problem. The error occurs when it tries to read the registry file, since it saves the last file it tried to use, when you open the GUI it starts with the error. If you change the registry file to a more friendly one, the error doesn't occur.

[carloscape]

This is the file that gives the error http://www.megaupload.com/?d=UPVMBVLX

[pscEx]

New version 4.4.1 is uploaded.

• Fixed bug when key name contained a comma

Peter

[Filip Hasa]

Hi Peter,

your program does not support ";" (comma with point). It is used as comment in reg file. Please can you add this to your program?

Thank you

[pscEx]

Done!

Version 4.4.2

Peter

[paraglider]

Ascii strings are not converted correctly in ascii regedit4 files:

REGEDIT4



[HKEY_LOCAL_MACHINESOFTWAREClassesInstallerWin32AssembliesGlobal]

"Microsoft.VC80.CRT,version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",processorArchitecture="x86""=hex(7):38,78,45,74,79,74,2e,47,63,41,6b,60,2b,44,44,63,31,77,74,41,43,6c,69,65,6e,74,3e,5f,6a,30,2c,59,5d,73,21,53,6f,65,38,4d,6b,62,49,64,46,77,55,00,00,

becomes ( only alternate characters are converted ):

reg_add,0x7,%reg%ClassesInstallerWin32AssembliesGlobal,"Microsoft.VC80.CRT#$cversion=#$q8.0.50727.762#$q#$cpublicKeyToken=#$q1fc8b3b9a1e18e3b#$q#$ctype=#$qwin32#$q#$cprocessorArchitecture=#$qx86","8Ey.ck+D1tCin>j#$c]!o8kIFU"

Value should start "8xEty....

[pscEx]

Thanks, Paraglider!

It has been a small discrepancy between regedit5 wide strings to regedit4 ansi strings.

Fixed in version 4.5.0

Peter

[paraglider]

reg2WBS program seems to hang converting this reg file ( using default options ) when Build is pressed:

http://paraglidernc....Files/4pscex.7z

[pscEx]

reg2WBS program seems to hang converting this reg file ( using default options ) when Build is pressed:

A leftover from last debug session. Some code executed, where an invisible window waits for input ...

Fixed in 4.5.1

Peter

[vlados]

Application error, when I try convert my reg file. Please help me. regfile: http://depositfiles....files/cy1q43v1i

[pscEx]

Sorry, the URL tries to sell me an download account.

I did not find a way to free download.

Peter

[vlados]

Sorry, the URL tries to sell me an download account.

I did not find a way to free download.

Peter

New place http://rapidshare.co...YD_RUS_5308.reg
I think this error is due to multiline strings are used

Edited by vlados, 02 December 2012 - 12:30 PM.

[pscEx]

That has been my opinion, too.
Such XML multilines are not (yet?) supported.

Peter

[pscEx]

I was able to reproduce with a simpler two-lines-string, and will try to fix the issue.

Peter

[vlados]

I was able to reproduce with a simpler two-lines-string, and will try to fix the issue.

Peter

If is possible. Thank you.

[pscEx]

New version 4.6.1 ready for download at http://reboot.pro/fi...ile/48-reg2wbs/

Peter