[Wine] Help installing application

Thu Jul 5 23:59:40 CDT 2007

	I assume file "Wine Debug" is full terminal output (second file contains only 
harmless warnings which are unrelated to your problem). From these lines:

melanie at atlasinstall:~$ wine /media/cdrom0/msetup4.exe
Warning: the specified Windows directory L"c:\\windows" is not accessible.
Warning: the specified System directory L"c:\\windows\\system32" is not 
accessible.
Warning: the specified Windows directory L"c:\\windows" is not accessible.
Warning: the specified System directory L"c:\\windows\\system32" is not 
accessible.
fixme:win:RegisterDeviceNotificationA (hwnd=0x10024, 
filter=0x33f614,flags=0x00000000),
        returns a fake device notification handle!
fixme:reg:GetNativeSystemInfo (0x33ec14) using GetSystemInfo()
err:shell:SHGetFolderPathW Failed to create directory L"c:
\\windows\\profiles\\melanie\\Local Settings\\Temporary Internet Files".
err:shell:SHGetFolderPathW Failed to create directory L"c:
\\windows\\profiles\\melanie\\Local Settings\\History".
err:shell:SHGetFolderPathW Failed to create directory L"c:
\\windows\\profiles\\melanie\\Cookies".

	...I think that you have problems with permissions. Try to execute the 
following:

mv ~/.wine ~/.wine.old

	This command will rename your ".wine" directory to ".wine.old". There 
shouldn't be any terminal output at all. If this command give you errors then 
you have problems with permissions. If renaming was successful then your 
permissions are OK, so we need to test farther; if so execute this:

wineprefixcreate

	This command shouldn't give you errors. It will create clean ".wine" 
directory for you. If it was OK with no errors, run your program as you did 
before:

wine /media/cdrom0/msetup4.exe

	And report results.

On Friday July 6 2007 03:05, M Thompson wrote:
> Ok That's quite a bit of homework:)  As for the reading, I've done that
> already.  As for the rest, I'll give it a try as soon as I have a few
> minutes.  In the meantime, can you see the attached text files?  If you
> can, I'll skip the  bz stuff, if not I'll send later.  Thanks again.
>
> On 7/5/07, L. Rahyen < research at science.su> wrote:
> >         .bz2 file is OK, but debug.log within it isn't. it just contain
> > this error:
> >
> > bash: cd: home/melanie/.wine/drive_c/ProgramFiles/msetup4.exe: No such
> > file or
> > directory
> >
> >         Okay, here is more detailed instructions:
> >
> >         1) Execute this:
> >
> > cd ~/.wine/drive_c/Program\ Files/your_application
> >
> >         Replace "your_application" with your application' program folder
> > if it has
> > one. Please note that you must use "\" before all spaces! This is
> > important.
> > You cannot ommit spaces or leave 'em without "\". "\" is just escape
> > character - it tells to the shell that next symbol shouldn't have any
> > special
> > meaning and it is a part of the file or directory name in this case.
> >         (Please note that this step have more importance than you may
> > think. Many
> > Windows application require you to cd to the directory with the
> > executable;
> > file managers like Nautilus and Konqueror will NOT do this - they always
> > set
> > your home directory as current one. If you try to execute such
> > applications
> > with full path they will fail to work. Some Win-apps work even if your
> > current directory is any directory on your system but you cannot assume
> > this
> > if you not sure. You may want to read brief and short intruduction to
> > typical
> > problems when using WINE here:
> > http://madewokherd.livejournal.com/5082.html ;
> > if you need more info you can read http://www.winehq.org/ )
> >
> >
> >         2) Execute:
> >
> > ls
> >
> >         You must see executable of your program in the output. If not,
> > make sure that
> > you in right directory (by executing command "pwd" to see your current
> > directory).
> >
> >
> >         3) Execute:
> >
> > wine program_name.exe
> >
> >         Substitute "program_name" with the name of your program
> > executable. Make sure
> > that your program can run and give you the error. You will have some
> > output
> > in your terminal. If this works as expected, execute:
> >
> > wine program_name.exe &> debug.log
> >
> >         And do everything neccessary to get the error from your program.
> > Then close
> > it correctly if possible (but even if not this isn't very important).
> >
> >         4) Execute:
> >
> > less debug.log
> >
> >         You can scroll up/down with up/down arrow keys. You must find
> > there terminal
> > output from WINE. If you find something else (for example, error about
> > non-existing file) make sure you followed instructions correctly; in
> > worst
> >
> > case you can ask additional questions.
> >
> >
> >         5) If everything is okay, execute:
> >
> > bzip2 -9 debug.log
> >
> >         Parameter "-9" means maximum possible compression level. You will
> > have
> > debug.log.bz2 file with compressed terminal output from WINE. If you want
> > you
> > may try to open this file in your favorite file manager (something like
> > Konqueror or Nautilus) but this is unnessery check if content of original
> > debug.log was OK.
> >
> > On Friday July 6 2007 01:54, M Thompson wrote:
> > > Ok I hope I have the debug file attached.  The exact errors are as
> >
> > follows:
> > > When I get to the install to C:program files screen, it says: "C: free
> > > space available is 1MB 65 MB needed."
> > >
> > > When I hit install anyway, it says "the specified folder is invalid.
> > > Specify a write enabled folder on the local hard disk drive".
> > >
> > > The folder is write enabled as far as I can tell.
> > >
> > > If it helps, I will send a screenshot of the above two error
> >
> > messages.  I
> >
> > > was going to but I was afraid it would bog down everyone's
> >
> > email.  Please
> >
> > > let me know if more info is needed or if I failed to do the bz2 file
> > > correctly.
> > >
> > > Thanks in advance for your advice and for your patience.
> > >
> > > On 7/5/07, L. Rahyen < research at science.su> wrote:
> > > >         Open a terminal, and execute this:
> > > >
> > > >         cd ~/.wine/drive_c/Program\ Files/your_application
> > > >         wine program_name.exe &> debug.log
> > > >         bzip2 -9 debug.log
> > > >
> > > >         You will have relatively small debug.log.bz2 file with full
> > > > terminal output.
> > > > Of course if debug.log will be of small size (say, few KiB or so)
> > > > then
> > > >
> > > > you don't need to compress it with bzip2. Just attach it to your next
> > > > message. It
> > > > may be helpful if you provide exact text message with the error you
> >
> > get
> >
> > > > from
> > > > the application or even provide a screenshot if you want (exact text
> >
> > or
> >
> > > > screenshot will be useful only if the error is written with English).
> > > >
> > > > On Thursday July 5 2007 18:12, M Thompson wrote:
> > > > > OK Thanks.
> > > > >
> > > > > I would be using this software in conjunction with my Canon MP 600
> > > >
> > > > printer
> > > >
> > > > > which works under Linux albeit with a nonspecific driver (MP 500
> > > >
> > > > driver).
> > > >
> > > > > The photo quality is OK just not good enough for keepsake photos (
> >
> > i.e.,
> >
> > > > my
> > > >
> > > > > child) even with turboprint.  Even under WIN XP, I had to use the
> >
> > Canon
> >
> > > > > software to make photos print correctly color-wise and borderless
> >
> > 4x6
> >
> > > > > (funny none of the glowing reviews mentioned this).  As for the
> > > > > full terminal output, I have already taken some screenshots at the
> >
> > relevant
> >
> > > > > times and I'd rather provide those if possible.  If not, I can try
> >
> > to
> >
> > > > send
> > > >
> > > > > the whole output - what do you consider very long bc I'm not sure I
> > > > > know how to create a bz2 file?  So, what do you think?