WineHQ
Wine Forums

Board index » WineHQ » Wine Help




 Page 1 of 1 [ 24 posts ] 



 
Author Message
 Post Posted: Wed Dec 16, 2009 11:08 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Running Wine 1.0.1 in Ubuntu 9.10, trying to install FileMaker Pro 9 from CD. (Install from this CD works fine on Windows machine.)

'Setup cannot find necessary files' message appears when launching setup.exe with Wine.

WINEDEBUG=+loaddll on setup.exe gives the output below; looks like all needed .dlls are there.

Same problem reported on Ubuntu forums earlier in 2009 by another user: http://ubuntuforums.org/archive/index.p ... 83015.html

Suggestions for a work-around would be very welcome!

trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b820000: builtin
trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b820000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\wineboot.exe" at 0x6db60000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x602e0000: builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "krnl386.exe" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "system.drv" : builtin
trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b820000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\services.exe" at 0x601c0000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x60260000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\iphlpapi.dll" at 0x60240000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x601e0000: builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "krnl386.exe" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "system.drv" : builtin
trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b820000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\winedevice.exe" at 0x601e0000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x60200000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\ntoskrnl.exe" at 0x60250000: builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "krnl386.exe" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "system.drv" : builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\iphlpapi.dll" at 0x602e0000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x60290000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x60320000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\mountmgr.sys" at 0x69970000: builtin
trace:loaddll:load_native_dll Loaded L"Z:\\home\\bob\\Desktop\\setup.exe" at 0x400000: native
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x60320000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x65240000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x601e0000: builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "krnl386.exe" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "system.drv" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "gdi.exe" : builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x71c00000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x603b0000: builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "gdi.exe" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "user.exe" : builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x60660000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x60460000: builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "user.exe" : builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x607c0000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x605b0000: builtin
trace:loaddll:load_builtin_dll Loaded L"KERNEL32.dll" at 0x7b820000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\explorer.exe" at 0x60310000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x603c0000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\iphlpapi.dll" at 0x60390000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x60330000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x60560000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x60420000: builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "krnl386.exe" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "system.drv" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "gdi.exe" : builtin
trace:loaddll:MODULE_LoadModule16 Loaded module "user.exe" : builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x62de0000: builtin
trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x606c0000: builtin


Top 
 Post Posted: Wed Dec 16, 2009 11:44 pm 
Offline
Moderator
Moderator
User avatar

Joined: Tue Mar 25, 2008 10:30 pm
Posts: 8319
fmp_user wrote:
Running Wine 1.0.1 in Ubuntu 9.10,


Upgrade to the latest development release. 1.0.1 is over a year old.


Top 
 Post Posted: Thu Dec 17, 2009 12:13 am 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Hi, dimesio.

No difference with Wine 1.1.34


Top 
 Post Posted: Thu Dec 17, 2009 12:22 am 
Offline
Moderator
Moderator

Joined: Sat Feb 23, 2008 2:29 pm
Posts: 6605
fmp_user wrote:
No difference with Wine 1.1.34

Remove ~/.wine directory and try again. If still doesn't work - what exactly the error message say? What files can't it find?


Top 
 Post Posted: Thu Dec 17, 2009 2:23 am 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Hi Vitamin.

No difference after deleting .wine and reinstalling.

The Windows error msg is a small window with 'Setup Error' in the title bar. There's a big red X in the pane and this exact message: 'Setup cannot find the necessary files.'

Below that is an 'OK' button which closes the window. No option to learn which files are needed.

(This is why I migrated to Linux years ago. Windows is built to be unhelpful. Now if only sqlite3 had FMP's friendliness...)


Top 
 Post Posted: Thu Dec 17, 2009 10:10 am 
Offline
Moderator
Moderator

Joined: Sat Feb 23, 2008 2:29 pm
Posts: 6605
fmp_user wrote:
No option to learn which files are needed.

Try WINEDEBUG=warn+all (don't paste here it would be big).


Top 
 Post Posted: Thu Dec 17, 2009 5:35 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Hi, vitamin.

Have I got the usage right? In the 'fake' CD directory,

WINEDEBUG=warn+all setup.exe

returns 'setup.exe command not found' and without a file argument, nothing is returned.


Top 
 Post Posted: Thu Dec 17, 2009 5:46 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Whoops, wrong command. This worked

wine setup.exe WINEDEBUG=warn+all

and I'm now checking the output.


Top 
 Post Posted: Thu Dec 17, 2009 6:00 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Getting somewhere? Apart from a lot of font and keyboard warnings, there's a repeated complaint that 'user.exe16' can't be found anywhere (debug looked on the CD and in the various WINE directories on my hard drive.

The closest name-matches I can find are in /usr/lib/wine:

gdi.exe16
krnl386.exe16


Top 
 Post Posted: Thu Dec 17, 2009 6:49 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Sorry: the command that worked was

WINEDEBUG=warn+all wine setup.exe

Are there specific messages I should look for in the output that might explain 'Setup cannot find the necessary files'?


Top 
 Post Posted: Sat Dec 19, 2009 1:42 pm 
Offline
Moderator
Moderator

Joined: Sat Feb 23, 2008 2:29 pm
Posts: 6605
fmp_user wrote:
Are there specific messages I should look for in the output that might explain 'Setup cannot find the necessary files'?

File not found messages. Don't pay attention to Wine looking for each dll in every directory - those are fine and eventually found.


Top 
 Post Posted: Sat Dec 19, 2009 5:22 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Hi, vitamin.

Many thanks for the pointer. There are dozens of warn:ntdll not found msgs but I'm not sure how to interpret them. For example,

warn:module:load_builtin_dll cannot open .so lib for builtin L"krnl386.exe16": /usr/bin/../lib/wine/krnl386.exe16.so: cannot open shared object file: No such file or directory
warn:module:load_dll Failed to load module L"krnl386.exe16"; status=c0000135

There is definitely a krnl386.exe16 in /usr/lib/wine, but not a shared object library krnl386.exe16.so. Does that matter?

There are also lots of warn:font and warn:keyboard msgs I assume I can ignore. The only other msgs seem to be version warnings

warn:ver:VERSION_GetFileVersionInfo_PE Could not find VS_VERSION_INFO in L"C:\\windows\\hh.exe"
warn:ver:VERSION_GetFileVersionInfo_PE Could not find VS_VERSION_INFO in L"C:\\windows\\system32\\winhlp32.exe"
warn:ver:VERSION_GetFileVersionInfo_PE Could not find VS_VERSION_INFO in L"C:\\windows\\system32\\winebrowser.exe"
warn:ver:VERSION_GetFileVersionInfo_PE Could not find VS_VERSION_INFO in L"C:\\windows\\system32\\notepad.exe"
warn:ver:VERSION_GetFileVersionInfo_PE Could not find VS_VERSION_INFO in L"C:\\windows\\system32\\wordpad.exe"

and these:

warn:file:CreateFileW Unable to create file L"C:\\windows\\wininit.ini" (status c0000034)
warn:profile:PROFILE_Open profile file L"C:\\windows\\wininit.ini" not found
...
warn:class:CLASS_RegisterClass Win extra bytes 44 is > 40
warn:ntdll:FILE_CreateFile L"\\??\\C:\\windows\\(None)" not found (c0000034)
warn:file:CreateFileW Unable to create file L"(None)" (status c0000034)
warn:ntdll:FILE_CreateFile L"\\??\\C:\\windows\\(None)" not found (c0000034)
warn:file:CreateFileW Unable to create file L"C:\\windows\\(None)" (status c0000034)
warn:file:CreateFileW Unable to create file L"D:\\files\\setup.exe" (status c0000022)
warn:file:CreateFileW Unable to create file L"D:\\files\\setup.exe" (status c0000022)
warn:gdi:GDI_GetObjPtr Invalid handle (nil)
warn:gdi:GDI_GetObjPtr Invalid handle (nil)

Any clues there?


Top 
 Post Posted: Sat Dec 19, 2009 9:35 pm 
Offline
Moderator
Moderator

Joined: Sat Feb 23, 2008 2:29 pm
Posts: 6605
fmp_user wrote:
There is definitely a krnl386.exe16 in /usr/lib/wine, but not a shared object library krnl386.exe16.so. Does that matter?

No, Wine will look for a dll in many places failing to find it until it looks in it's library directory (last place to look). So all those are harmless if it's Wine's own dll.

fmp_user wrote:
warn:ntdll:FILE_CreateFile L"\\??\\C:\\windows\\(None)" not found (c0000034)

This is default desktop wallpaper.

fmp_user wrote:
warn:file:CreateFileW Unable to create file L"D:\\files\\setup.exe" (status c0000022)

Now this is a problem. c0000022 is STATUS_ACCESS_DENIED which might mean whatever your d: drive mapped to doesn't have enough access rights. Unless of course it's a cd/dvd and something checking if it can open files r/w.


Top 
 Post Posted: Sat Dec 19, 2009 9:57 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
The installation CD appears in .wine/dosdevices/d:, which is a link to a block device and has brw-rw---- permissions.

There are actually 2 setup.exe files on the installation CD. One is a 40kb DOS/Windows executable which returns the 'Setup cannot find the necessary files' msg when opened with WINE. It's -rw-r--r--.

The main setup and data files are in a directory on the CD called 'files'. There seem to be 3 installation files here: setup.exe (103kb), iassist.exe (248kb) and instmsiw.exe (1.7mb). All are shown as -r-x------.

The warning msg you point to refers to the 'files' setup.exe. Nothing at all happens when I try to open any of these with WINE, i.e. no read of the CD (no whirring noise from the CD drive).


Top 
 Post Posted: Sat Dec 19, 2009 10:04 pm 
 
fmp_user wrote:
Quote:
The installation CD appears in .wine/dosdevices/d:, which is a link to a block device and has brw-rw---- permissions.

There are actually 2 setup.exe files on the installation CD. One is a 40kb DOS/Windows executable which returns the 'Setup cannot find the necessary files' msg when opened with WINE. It's -rw-r--r--.

It does not matter if the files can be written to, the device should be
mounted ro (read-ony) thus the error should occur.

James McKenzie


Top 
 Post Posted: Sat Dec 19, 2009 11:28 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Hi, James.

Not sure what you're saying. The real mount in Ubuntu 9.10 is /dev/disk and here too the permissions are brw-rw----.


Top 
 Post Posted: Sat Dec 19, 2009 11:35 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
To make things easier (???) I burned an .iso of the CD and extracted it to my hard drive. All files still have the same permissions, of course, and I get the same behaviour as when they're on the CD: the un-directoried setup.exe returns the 'cannot find' msg with WINE, and nothing happens at all when I try to open the files/setup.exe with WINE. chmod does nothing, just says these are read-only.


Top 
 Post Posted: Sun Dec 20, 2009 12:12 am 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Another try: prowling through the CD I found an .msi called filemaker pro 9.msi (note spaces). Another fail:

foo@foo:~/.wine/dosdevices/d:/files$ msiexec /i "filemaker pro 9.msi"
err:menubuilder:WinMain unknown option -a
err:menubuilder:WinMain unknown option -r
err:msi:copy_package_to_temp failed to copy package L"filemaker pro 9.msi"
fixme:msi:MSI_OpenDatabaseW open failed r = 80030005 for L"filemaker pro 9.msi"


Top 
 Post Posted: Sun Dec 20, 2009 4:30 am 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
More possibly diagnostic info for anyone still interested in this problem:

1. On the chance that 'filemaker pro 9.msi' wanted Windows Installer but couldn't find it, I made sure that WI 2 was in both Windows/Installer and /system32. When I then double-clicked on 'filemaker pro 9.msi', something happened! I got a Windows Installer msg saying "Incorrect command line parameters".

2. On my Linux box I can't read the setup.ini file on the CD for some reason. On a Windows machine I opened it in Notepad and got the product code and package code listed in setup.ini. I notice that msiexec has an option

msiexec {package|productcode} [property]

but I don't understand how to read this. Does it mean literally put the package and product codes between curly brackets with a pipe between? And what is '[property]'?


Top 
 Post Posted: Sun Dec 20, 2009 2:10 pm 
Offline
Moderator
Moderator

Joined: Sat Feb 23, 2008 2:29 pm
Posts: 6605
fmp_user wrote:
On my Linux box I can't read the setup.ini file on the CD for some reason.

Sounds like incorrectly mastered CD. Disable rock-ridge extension when mounting this CD and try again.


Top 
 Post Posted: Sun Dec 20, 2009 6:21 pm 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Hi, vitamin.

Good thinking! isoinfo returned a 'BAD RRVERSION' msg, so I mounted the CD with the norock option and all went well - until...

FileMaker Pro tried to set up the install wizard and failed with WINE configured as XP. I'm guessing this is because the installer in WINE is MSI 2.0, and for XP FMP requires the MSI 3.0 installer.

I tried downgrading WINE to 2000 and ME, and got a msg that FMP 9 doesn't work on these earlier versions of Windows!

Looking in the setup.ini on the CD I find

[SupportOS] ;Supported platforms for MSI 2.0

Win95=1

Win98=1

WinME=1

WinNT4SP6=1

Win2K=1



[SupportOSMsi30] ;Supported platforms for MSI 3.0

Win2KSP3=1

WinXP=1

Win2003Server=1

Too bad I can't edit that file...


Top 
 Post Posted: Sun Dec 20, 2009 11:50 pm 
Offline
Moderator
Moderator

Joined: Sat Feb 23, 2008 2:29 pm
Posts: 6605
fmp_user wrote:
I tried downgrading WINE to 2000 and ME, and got a msg that FMP 9 doesn't work on these earlier versions of Windows!

Use winetricks to install that stuff, don't install it directly - in most cases it won't work.


Top 
 Post Posted: Mon Dec 21, 2009 12:04 am 
Offline
Level 2
Level 2

Joined: Wed Dec 16, 2009 9:55 pm
Posts: 15
Codeweavers has given up on FileMaker Pro 9

http://www.codeweavers.com/compatibilit ... pp_id=3635

and so have I. I've rebuilt the database I built last week in FMP9 on a Windows machine as a Kexi database (KOffice app running under Gnome). For what I want, Kexi's just fine.

Many thanks for the help in jumping the hurdles, tho.


Top 
 Post subject:
 Post Posted: Tue Dec 22, 2009 11:36 am 
Offline
Newbie
Newbie

Joined: Tue Dec 22, 2009 10:25 am
Posts: 1
No difference with Wine 1.1.34


Top 
Display posts from previous:  Sort by  
 
 Page 1 of 1 [ 24 posts ] 




Board index » WineHQ » Wine Help


Who is online

Users browsing this forum: Google [Bot] and 0 guests

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: