<snip> > [Version] > ; Windows version to imitate > (win95,win98,winme,nt351,nt40,win2k,winxp,win2k3,win20,win30,win31) > ;"Windows" = "win98" > ; DOS version to imitate > ;"DOS" = "6.22" you should remove ";" from the line starting "Windows" to set your win version correctly (but this should not cause the problems with your software) > > ; Be careful here, wrong DllOverrides settings have the potential > ; to pretty much kill your setup. > [DllOverrides] > ; some dlls you may want to change > "oleaut32" = "builtin, native" > "ole32" = "builtin, native" > "commdlg" = "builtin, native" > "comdlg32" = "builtin, native" > "shell" = "builtin, native" > "shell32" = "builtin, native" > "shfolder" = "builtin, native" > "shlwapi" = "builtin, native" > "shdocvw" = "builtin, native" > "advapi32" = "builtin, native" > "msvcrt" = "native, builtin" > "mciavi.drv" = "native, builtin" > "mcianim.drv" = "native, builtin" > "msi" = "native, builtin" > "LEAD40" = "native" this looks ok. but I found out that LEAD40.dll needs a file called lead.vbx in the same directory (program and/or windows/system dir). if this file is available too, which should be because you use your windows drive, you can: (because I think this is a path issue) try to load some other dll native i.e. advapi32.dll and look wether wine finds this dll. or (if nobody else has a better idea ;-): start over again with an empty fake_windows dir. then copy your program dir from your windows drive, import your registry and (if needed) copy dll files from the windows/system dir. _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
