Upgrading breaks previous configuration?

[8086]

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: Select all

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: Select all

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 believe (not sure) I have been running programs after upgrading to (0.9.57).

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?
Is this normal when upgrading wine? I though the registry settings were "forward-compatible"?


---
edit:
Running "WINEPREFIX=~/.photoshop_wine/ winecfg" just gives me these error messages, and then it hangs. Does not respond to Ctrl-C, and has to be forced to terminate.

Code: Select all

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/carl-erik', starting in the Windows directory.
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 '/', starting in the Windows directory.
err:wineboot:main Cannot set the dir to L"c:\\windows" (2)

[8086]

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).

[Dan Kegel]

On Tue, Mar 18, 2008 at 6:11 AM, 8086 <[email protected]> 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

[8086]

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

So if you really mean the wine related 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 physical errors in the hard drive.

Thanks for the answer, though.

[Dan Kegel]

On Tue, Mar 18, 2008 at 4:06 PM, 8086 <[email protected]> wrote:

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.

Oh. I wouldn't use anything that tended to corrupt
my hard drive.

And I can't really support users who do, sorry.

My recommendation is to reformat your Linux partition,
and stop using ext2ifs if it corrupts your disk.
- Dan

[8086]

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.

[8086]

On Tue, Mar 18, 2008 at 4:06 PM, 8086 <wineforum-
Oh. I wouldn't use anything that tended to corrupt
my hard drive.

And I can't really support users who do, sorry.

Clear enough Totally understand.

[Dan Kegel]

On Tue, Mar 18, 2008 at 4:12 PM, 8086 <[email protected]> wrote:

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.

The point is, any time you have gazillions of fsck errors,
something's seriously wrong. Either you're using
software that corrupts the hard drive (in your case),
or your hard drive is breaking (it's happened to me several times),
or there's a bug in the filesystem (not especially likely).

No point in trying to limp along. Best to nuke things and start over.