Bizarre issue - typing 'wine [anything]' launches FileMaker

[pquesinb]

A while back I attempted to install FileMaker Server under Wine and ran into trouble since it was an old version of Wine - 1.01, included with CentOS 5.x. So I compiled and installed the latest stable version of Wine, 1.4.1 and FileMaker appears to run, although other tasks have kept me from fully testing it. Now when I type anything after wine on the command line, or even attempt to launch winecfg, it launches FileMaker! If I type 'wine test' at the prompt, it launches FileMaker and then attempts to launch test.exe. Here are a couple of examples of what I'm talking about, so you won't think I've completely lost it:

[root@Server1 bin]# pwd
/usr/local/bin
[root@Server1 bin]# ls wi*
widl wine wineboot winebuild winecfg wineconsole winecpp winedbg winedump winefile wineg++ winegcc winemaker winemine winepath wine-preloader wineserver
[root@Server1 bin]# wine --version
wine-1.4.1
[root@Server1 bin]# wine test
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
fixme:advapi:RegisterEventSourceA ((null),"FileMaker Server"): stub
fixme:advapi:RegisterEventSourceW (L"",L"FileMaker Server"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0xace744,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0x11bb08,(nil)): stub
fixme:netbios:Netbios NCBADDNAME: stub, returning success
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000006a,(nil),0x0001,0x00000000,0xace94c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x4000006a,(nil),0x0001,0x00000000,0x129460,(nil)): stub
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 5
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0xc0000020,(nil),0x0003,0x00000000,0xace6e8,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0xc0000020,(nil),0x0003,0x00000000,0x1ad720,(nil)): stub
err:eventlog:ReportEventW L"IPX/SPX"
err:eventlog:ReportEventW L"an unexpected error occurred."
err:eventlog:ReportEventW L"10022"
wine: cannot find L"C:\\windows\\system32\\test.exe"
[root@Server1 bin]# fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000003,(nil),0x0001,0x00000000,0xace938,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000003,(nil),0x0001,0x00000000,0x1ada38,(nil)): stub
...

[root@Server1 bin]# ./winecfg
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
err:systray:initialize_systray Could not create tray window
fixme:advapi:RegisterEventSourceA ((null),"FileMaker Server"): stub
fixme:advapi:RegisterEventSourceW (L"",L"FileMaker Server"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0xace744,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000001,(nil),0x0002,0x00000000,0x11bb00,(nil)): stub
fixme:netbios:Netbios NCBADDNAME: stub, returning success
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000006a,(nil),0x0001,0x00000000,0xace94c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x4000006a,(nil),0x0001,0x00000000,0x129458,(nil)): stub
fixme:winsock:convert_socktype_w2u unhandled Windows socket type 5
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0xc0000020,(nil),0x0003,0x00000000,0xace6e8,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0xc0000020,(nil),0x0003,0x00000000,0x1ad718,(nil)): stub
err:eventlog:ReportEventW L"IPX/SPX"
err:eventlog:ReportEventW L"an unexpected error occurred."
err:eventlog:ReportEventW L"10022"
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
[root@Server1 bin]# fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x40000003,(nil),0x0001,0x00000000,0xace938,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x40000003,(nil),0x0001,0x00000000,0x1ada30,(nil)): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x4000005c,(nil),0x0001,0x00000000,0xace92c,(nil)): stub
...

Has anyone seen anything like this before? I never reinstalled FileMaker after updating Wine, so should I uninstall it and try again? I wanted to ask here first, just in case it's something silly I did or didn't do.

Many Thanks,

- Phil

[dimesio]

Never run Wine as root. http://wiki.winehq.org/FAQ#run_as_root

Delete the wineprefix you created as root and reinstall Filemaker as a normal user.