Re: june 2005 release and 'registry' ?

[Dan Sawyer <dansawyer@xxxxxxxxxxxxx>]

I am trying to run m$office. Below is an override pattern including the preference for 'native' for all non essential dll's. How can these be implemented? How can the default be set to native?

When I tried to type then in winecfg errored with: wine: Unhandled exception (thread 0009), starting debugger...

How do the two screens interact? What does 'default' mean? What are the alternatives?

The browse arrow on the libraries screen does not seem to work. What is it supposed to do.

I am sorry to be slow.

- Dan

[DllOverrides]
"commdlg"      = "builtin, native"
"comdlg32"     = "builtin, native"
"ver"          = "builtin, native"
"version"      = "builtin, native"
"shell"        = "builtin, native"
"shell32"      = "builtin, native"
"shfolder"     = "builtin, native"
"shlwapi"      = "builtin, native"
"shdocvw"      = "builtin, native"
"lzexpand"     = "builtin, native"
"lz32"         = "builtin, native"
"comctl32"     = "builtin, native"
"commctrl"     = "builtin, native"
"advapi32"     = "builtin, native"
"crtdll"       = "builtin, native"
"mpr"          = "builtin, native"
"winspool.drv" = "builtin, native"
"ddraw"        = "builtin, native"
"dinput"       = "builtin, native"
"dsound"       = "builtin, native"
"opengl32"     = "builtin, native"
"msvcrt"       = "native, builtin"
"rpcrt4"       = "native, builtin"
"msvideo"      = "builtin, native"
"msvfw32"      = "builtin, native"
"mcicda.drv"   = "builtin, native"
"mciseq.drv"   = "builtin, native"
"mciwave.drv"  = "builtin, native"
"mciavi.drv"   = "native, builtin"
"mcianim.drv"  = "native, builtin"
"msacm.drv"    = "builtin, native"
"msacm"        = "builtin, native"
"msacm32"      = "builtin, native"
"midimap.drv"  = "builtin, native"
"ole2disp"      = "native, builtin"
; default for all other dlls
"*" = "native, builtin"


Mike Hearn wrote:

On Sat, 2005-07-09 at 11:07 -0700, Dan Sawyer wrote:
  

Mike,

Given that we take your point, how can winecfg be made 'optional'.
There are many of us that are trying to use wine and find winecfg
creates roadblocks. If winecfg will be unnecessary then why not remain
with the config option. At least that is easily managable.
    

What roadblocks exactly does it create? It could use some polish for
sure, but it seems to basically work (at least, it does for me).

A few things it could do better are:

- Imported pre-canned application setups (basically .reg files)
- Drive detection sometimes creates a lot of drives
- Could be prettier: using app icons would be a good start but as always
  with win32 the code to do that is non-trivial

The thing about winecfg shrinking is a long term thing. It won't happen
tomorrow. For a few things, it may never happen, it'll just become less
and less necessary to run it as time goes on. It's an ideal to which we
aim rather than a fixed target.

thanks -mike

_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users