[Bug 963] New: - Default values for wineconsole are not saved

[wine-bugs at winehq.com]

http://bugs.winehq.com/show_bug.cgi?id=963

           Summary: Default values for wineconsole are not saved
           Product: Wine
           Version: CVS
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: wine-debug
        AssignedTo: wine-bugs at winehq.com
        ReportedBy: tony_lambregts at telusplanet.net


While trying to make sense of bug 745 I ran across this bug. The problem is that
if I change the default values in winedebug those values are not saved to the
registry. 

When I ran a trace using --debugmsg +wineconsole,+reg I get some indication as
to why. It looks like it is not finding the registry entries in order to update
them.

trace:wineconsole:WINECON_RegSave saving registry settings.
trace:reg:NtCreateKey(0x80000001,L"Console\0000Cursor"...,(null),0,f003f,0x405c5ee4)
trace:reg:NtCreateKey <- 0x0050
trace:reg:NtSetValueKey(0x50,L"CursorSize\0000CursorVis"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"CursorVisible\0000ExitOnDie\0000Fa"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"ExitOnDie\0000FaceName",4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"FaceName\0000FontSiz"...,1,0x40396108,12)
trace:reg:NtSetValueKey(0x50,L"FontSize\0000FontWei"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"FontWeight\0000HistoryBu"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"HistoryBufferSize\0000MenuMask\0000QuickEd"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"MenuMask\0000QuickEd"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"QuickEdit\0000ScreenBu"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"ScreenBufferSize\0000ScreenColors\0000Wi"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"ScreenColors\0000WindowSize\0000"...,4,0x405c5ee0,4)
trace:reg:NtSetValueKey(0x50,L"WindowSize\0000\7250\706f\7265\7974\6853\6565\5774\4900\696e"...,4,0x405c5ee0,4)

If I change the values using regedit they are read by winedbg and wcmd but they
seem to be ignored by both programs when creating the window. The only registry
settings that seem to be used are those for the font settings.

It concerns me that both winedbg and wcmd would share the same registry settings
in the first place since they are totally different programs, and in my mind
should have setting that are independent to each other.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://bugs.winehq.com/show_bug.cgi?id=963>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.