wine users - Mar 2008 - Upgrading breaks previous configuration?

So far, I have been installing each windows program to a separate wine
directory, thus avoiding that one program creates problems for another. For
instance Photoshop CS 2 is in .photoshop_wine, C?sar 3 is .caesar3_wine, etc.

So far I have had a number of programs running great, no problems. But today I
got an error that I tried googling to no avail:

Code:
12:46_acer6292:~$ photoshop 
Warning: the specified Windows directory L"c:\\windows" is not
accessible.
Warning: the specified System directory L"c:\\windows\\system32" is
not accessible.
Warning: could not find DOS drive for current working directory
'/local/data/myuser', starting in the Windows directory.
wine: cannot find 'c:\Programfiler\Adobe\Adobe Photoshop
CS2\Photoshop.exe'




If someone wonders what this script "photoshop" does, it is just:

Code:
export WINEPREFIX="/local/data/myuser/.photoshop_wine/"

wine "c:\\Programfiler\Adobe\Adobe Photoshop CS2\Photoshop.exe"  $@


The .photoshop_wine directory exists, and the files seem ok. Permissions also.

This actually happens to all the installed programs, and since they are in
totally different wine-dirs, no "inter-program pollution" is possible.
I have been running these programs for months, so it was really strange that
they stopped working now. I thought it might be because I upgraded wine, but the
funny thing is that I am quite sure I have been running the latest wine for more
than a week (0.9.57) without problems.

After reinstalling a program to a fresh wine directory, the program works, but
since I have rather many installed programs, each "customized", I
would really hate doing that with all the programs I need.

So does anyone know why I get this error, and/or how to fix it?[/code]

I also have Crossover Office installed, and have used that to install IE6. That
install is also ruined and that hasn't anything to do with my wine install!
So it seems the problems lays somewhere outside of wine ...

Could anyone think of a reason why this could have something to do with the file
system? I ran fsck.ext2 yesterday on the partition and the number of errors were
immense. Since I don't speak "fsck", I just ran "fsck
-y" (yes to all questions). The number of questions/errors (I piped the
output to a file, and counted with wc -l) was in the 100k range.

All the questions had either to do with 
- some count being wrong
- removing extended attributes (that were wrong)
- or fixing bitmap errors.

Everything seems to work just fine, otherwise. This is really the only thing I
can think of that might have something to do with it (outside of wine).

On Tue, Mar 18, 2008 at 6:11 AM, 8086 <wineforum-user at winehq.org>
wrote:
> I ran fsck.ext2 yesterday on the partition and the number of errors
> were immense.
The most likely explanation is that your hard drive is
about to fail completely.  Go buy a new hard drive and
reinstall Linux on it, then copy your home directory over.
And then take out the old hard drive and put it on the
shelf.
- Dan

I don't think the hard drive is failing. The cause of the errors is using
the EXT2IFS driver in Windows to access my ext2 drive. I usually get a bunch of
errors when running fsck after doing massive changes in Windows.

So if you really mean the errors I have been experiencing does not have to do
with wine or some other program, then the cause is likely to be a logical error
in the file system - not the physical errors in the hard drive.

I believe I have seen these errors before (in other configurations on other
machines) ... And I am quite confident their hard drives weren't failing.