hi there i seem to have a problemo with the flash mx installer, looking
for a dll which is sitting in the system dir already. what could it be ?
Line 78: Unrecognized input '.'
Drive C: unknown filesystem type L"win98", defaulting to
'win95'.
Drive D: unknown filesystem type L"win98", defaulting to
'win95'.
Drive X: unknown filesystem type L"win98", defaulting to
'win95'.
Could not stat /home/electroteque/.wine/${HOME} (No such file or
directory), ignoring drive Y:
Drive Z: unknown filesystem type L"win98", defaulting to
'win95'.
Drive C: unknown filesystem type L"win98", defaulting to
'win95'.
Drive D: unknown filesystem type L"win98", defaulting to
'win95'.
Drive X: unknown filesystem type L"win98", defaulting to
'win95'.
Could not stat /home/electroteque/.wine/${HOME} (No such file or
directory), ignoring drive Y:
Drive Z: unknown filesystem type L"win98", defaulting to
'win95'.
err:module:import_dll Loading module (file) OLEAUT32.dll (which is
needed by X:\pft68cf.tmp\Disk1\Setup.exe) failed (error c00000e5).
--- electroteque <daniel@electroteque.org> a ?crit?:> hi there i seem to have a problemo with the flash mx installer, > looking > for a dll which is sitting in the system dir already. what could it > be ?first check your configuration by running winecheck. if wine is correctly installed it should be in $PATH. then follow instructions at http://www.winehq.org/site/docs/wine-user/bugs to give us a proper bug report. Note : the problem described by the following error message is real, just replace the filesystem type by 'win95'.> Drive C: unknown filesystem type L"win98", defaulting to 'win95'.====Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran?ais ! Yahoo! Mail : http://fr.mail.yahoo.com
>first check your configuration by running winecheck. if wine is >correctly installed it should be in $PATH. >then follow instructions at >http://www.winehq.org/site/docs/wine-user/bugs to give us a proper bug >report.This seems more like a configuration error, I don't think it's a bug These errors err:module:import_dll No implementation for ntdll.dll.NtImpersonateAnonymousToken imported from C:\Windows\System\rpcrt4.dll, setting to 0xdeadbeef err:module:import_dll No implementation for ntdll.dll.RtlDllShutdownInProgress imported from C:\Windows\System\rpcrt4.dll, setting to 0xdeadbeef err:module:import_dll No implementation for ntdll.dll.DbgPrintEx imported from C:\Windows\System\rpcrt4.dll, setting to 0xdeadbeef err:module:import_dll No implementation for ADVAPI32.dll.SystemFunction040 imported from C:\Windows\System\rpcrt4.dll, setting to 0xdeadbeef err:module:import_dll No implementation for ADVAPI32.dll.SystemFunction041 imported from C:\Windows\System\rpcrt4.dll, setting to 0xdeadbeef err:module:import_dll No implementation for ADVAPI32.dll.SystemFunction036 imported from C:\Windows\System\rpcrt4.dll, setting to 0xdeadbeef err:module:import_dll No implementation for ADVAPI32.dll.TraceMessage imported from C:\Windows\System\rpcrt4.dll, setting to 0xdeadbeef fixme:ntdll:NtQuerySystemInformation (0x00000000,0x40861a50,0x0000002c,(nil)) stub fixme:ntdll:RtlGetNtProductType (0x40861a7c): stub fixme:ntdll:RtlGetNtProductType (0x40861a58): stub fixme:global:GlobalMemoryStatusEx we shou just sat that the program needs some functions that are missing in wine, so the problem is cause by the fact that wine is incomplete; as some of these missing functions are in ntdll.dll there is no chance of solving the problem with a original microsoft dll. mind you from a base rpm install the most the dll's in the system dir have a filesize of 0 i've had to copy them over from my xp machine. That's normal, the wine dlls aren't in your fake windows installation, you can usually find them in /usr/lib, but this depend on the RPM you're using. It isn't a good idea to copy dlls from windows xp, for a start wine won't work well with xp dlls, and anyway it's a bad idea to have native dlls in the fake windows installation if you're using the builtin dlls. As the program needs some functions from ntdll.dll that aren't implemented in wine, for now you simply can't run the program. In the meantime, removing all those native dlls from your fake windows installation would be a good idea, as they can only create problems. The real wine dlls have names like advapi32.dll.so and are somewhere in /usr.
> Thats not in the docs should they not be in the system dir ? like there > is a heap of dll files there but all have a 0 filesize i had to copy > over files to start making things workWindows programs look in c:\windows\system to check that the dlls they need are there, so wine creates those fake dlls just to fool windows programs, the wine dlls are usually in /usr/lib/. The dlls you copied will not work until you don't tell wine to use them, to do this you must use the winecfg tool, but it isn't complete so you can only do that by manually changing your config file, look at the wine-user docs to do that.
As this setup can't work in wine, the only thing you can do is install the program on windows, and copy the files over to your fake windows installation. This won't be a proper install, but you might be able to run the program that way.