Hi everyone. I'm trying to install a program, each time I receive the error that _INS5176._MP has encountered a problem. Is there a work around or fix ?
pod25music wrote:> I'm trying to install a program, each time I receive the error that _INS5176._MP has encountered a problem.What Wine version? If it's older then wine-1.3.12 - upgrade. If still doesn't work, post complete terminal output.
dimesio wrote:> > pod25music wrote: > > > > I opened up terminal and tried installing from there so I could copy the errors, but now I get > > > > wine: /home/john/.wine is not owned by you > > > > > > You have to run Wine as the user who owns the wineprefix. Most likely you were running Wine as root, or ran Wine as root sometime in the past and messed up the permissions. > http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 > > What app are you trying to install? Have you checked the AppDB?Its a program that calculates the sizes of a Bass box based on the specs of the speaker you are fitting. Its called BassBox 6 AppDB ?? Where is that ?
Finally got the installer to run in terminal. This was the short output it gave: ~/BassBox$ wine SETUP.EXE wine: Unhandled page fault on read access to 0x01090000 at address 0x4469d1 (thread 0020), starting debugger...
James McKenzie wrote:> On 2/5/11 6:53 AM, pod25music wrote: > > > dimesio wrote: > > > > > pod25music wrote: > > > > > > > I opened up terminal and tried installing from there so I could copy the errors, but now I get > > > > > > > > wine: /home/john/.wine is not owned by you > > > > > > > > > > > > > > > You have to run Wine as the user who owns the wineprefix. Most likely you were running Wine as root, or ran Wine as root sometime in the past and messed up the permissions. > > > http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 > > > > > > What app are you trying to install? Have you checked the AppDB? > > > > > > > Its a program that calculates the sizes of a Bass box based on the specs of the speaker you are fitting. > > Its called BassBox 6 > > > > AppDB ?? > > > It is the place where Wine's users have put information on the various > Windows programs they have tried to run under various versions of Wine. > > > Where is that ? > > > > > It is accessible from the Main Wine page at http://www.winehq.org or > directly at http://appdb.winehq.org/ > > There is no entry for BassBox in the database. > > Can you create one for us? > > Also, can you try and produce a logging file from the installer from the > instructions at: http://wiki.winehq.org/FAQ#get_log and then post it to > a site like pastebin.com? > > Post the URL where the file is located here so someone can go out and > look at it and provide a possible solution. > > Also, is this program available from a vendor site as a demo? > > Thank you. > > James McKenzie > > > > > > >Yes, I will make a report. I'm not sure if BassBox has a demo, but will check. Here is the link to the log file. http://dl.dropbox.com/u/9849597/log.txt
To save me searching. What is the code needed to create a log file before the installer starts ?
On 2/5/11 10:31 AM, pod25music wrote:> To save me searching. What is the code needed to create a log file before the installer starts ?I use the following code: wine <installer.exe> > <name of logging file.txt> 2>&1 Where <installer.exe> is the program name for installing the program and <name of logging file.txt> is the name, including path, for the file to output log information to. Since I am on a Mac, an example would not be appropriate. James McKenzie
James McKenzie wrote:> On 2/5/11 10:31 AM, pod25music wrote: > > > To save me searching. What is the code needed to create a log file before the installer starts ? > > > I use the following code: > > wine <installer.exe> > <name of logging file.txt> 2>&1 > > Where <installer.exe> is the program name for installing the program > and <name of logging file.txt> is the name, including path, for the file > to output log information to. > > Since I am on a Mac, an example would not be appropriate. > > James McKenzieI used: 3630:~/BassBox$ wine SETUP.EXE &> log.txt And the output is the file you have seen.
On 2/5/11 11:57 AM, pod25music wrote:> James McKenzie wrote: >> On 2/5/11 10:31 AM, pod25music wrote: >> >>> To save me searching. What is the code needed to create a log file before the installer starts ? >>> >> I use the following code: >> >> wine<installer.exe> > <name of logging file.txt> 2>&1 >> >> Where<installer.exe> is the program name for installing the program >> and<name of logging file.txt> is the name, including path, for the file >> to output log information to. >> >> Since I am on a Mac, an example would not be appropriate. >> >> James McKenzie > > I used: > > 3630:~/BassBox$ wine SETUP.EXE&> log.txtIs this where the setup program resides? Did you copy it from media or download the program. This will NOT capture any errors generated by wine. Please see my previous post on how to use the command to create a logging file.> And the output is the file you have seen. > >And it is missing all of the error/warning/fixme messages generated by Wine which are sent to the error pipe. You are only capturing what appears normally as text on the screen. Both outputs are needed for troubleshooting. James McKenzie
Thanks James. Here is the file you need. http://dl.dropbox.com/u/9849597/output.txt
pod25music wrote:> Thanks James. > > Here is the file you need. > > http://dl.dropbox.com/u/9849597/output.txtBe warned . . . . It is 80mb !!!!
Topic closed for illegal link posting.
James McKenzie wrote:> On 2/6/11 10:29 AM, pod25music wrote: > I got the link and vitamin restored it. > > I'll look at the logging file. 80MB is huge but not the largest I've seen. > > James McKenzieThanks James.
On 2/6/11 4:18 AM, pod25music wrote:> pod25music wrote: >> Thanks James. >> >> Here is the file you need. >> >> http://dl.dropbox.com/u/9849597/output.txt > > Be warned . . . . It is 80mb !!!! > >What options did you use when you started the program? Can you try just running the program without any WINEDEBUG options and then create the file? Please include, in the file, how you started the program. Thank you. James McKenzie
I used this: WINEDEBUG=+relay,+seh,+tid wine SETUP.EXE &> output.txt What should it be for what you need ?
On 2/6/11 11:51 AM, pod25music wrote:> I used this: > > WINEDEBUG=+relay,+seh,+tid wine SETUP.EXE&> output.txt > > What should it be for what you need ? >Just wine SETUP.EXE &> output.txt 2>&1 should suffice for now. James McKenzie
You have an native overrides that braking Wine (ole32, and shlwapi). Remove them and try again!
vitamin wrote:> You have an native overrides that braking Wine (ole32, and shlwapi). Remove them and try again!I have no idea how to do that.
James McKenzie wrote:> On 2/6/11 11:51 AM, pod25music wrote: > > > I used this: > > > > WINEDEBUG=+relay,+seh,+tid wine SETUP.EXE&> output.txt > > > > What should it be for what you need ? > > > > > Just wine SETUP.EXE &> output.txt 2>&1 > > should suffice for now. > > James McKenzieThat gives the same output as the first file I showed you. If it helps at all, the error appears at the very last install window, when it is about to do the actual install. So it lets me put in the serial number and choose where the install should go (I left at default).