Stupid? pfft. If I can figure it out...
bob and dimesio and the rest are good instructors. You'll be fine, don't give up. Just because you haven't done it before doesn't mean you can't do it! Look, you're here trying to fix it not giving up and booting into windows. So it's clear you're technical and want to learn. So don't sweat it, I promise this one is fixable. I can run it just fine on a pentium laptop... pentium, good sir. From before windows vista, from before 64-bit processors, from before even Intel Core series. this is a DX7 game. It flies. You cannot tell you're not in native Windows.
OK.
Do you see that L"unix... bit?
This is what I'm talking about. Your wine is not there. Inside wine, it just doesn't know how to find it. You basically told the windows machine to go all the way back to c:\ but then keep going ..\ and that's impossible, so it cannot transition. It'll happen with wineconsole too, if you start it from outside a mapped reachable position, it'll start the path with "unix", and any command you try, even just 'dir' will toss a Syntax error.
Let's back up.
First, no need to export WINEPREFIX... most of us change them every single time we have to run a program, just put it on the command line before do the command as we've been showing in the thread. Set-and-forget is just a bad habit. If you do that, you may also try to run multiple things inside the same wine, while trying to get it to work - dangerous, what makes one thing good makes others broken. (well not everytime, but) and if you do that, you might leave wineserver running a singular instance and you'll have to start issuing wineserver -w ... because all running wine instances share the same wineserver as the same user, same shared memory space, same kernel, same registry, etc. This is why individual WINEPREFIXes are very, very useful.
I know it seems annoying at first, but granular control is never a bad thing.
Also I know it's frustrating seeing all the endless text fly by, but fixmes are just that, developers making notes. Watch for errors not fixmes. Rare is the fixme that is the cause of your stress. Once you get it working you can turn off alot of that stuff with WINEDEBUG options.
Look, the reason you're trying to start it from say D: is, because in winecfg on the drives tab, that's where the system put your mounted volume, right? Can you verify for me that when you run winecfg, the drives tab looks something like:
C: ../drive_c
D: /run/media/daten350/games-software
E: /some/other/mount/location
Oh wait, gotta ask, wine 101 type question just to be thorough; is your WINEPREFIX being built on a NTFS or FAT32 volume or other filesystem that does not support unix symbolic linking? That can complicate things, the dosdevices tree is all symlinks to system resources. Because, again, if you do say:
WINEPREFIX=/run/media/youracct/usbdrive/wine-games wine /run/media/youracct/usbdrive/wine-games/drive_c/Program\ Files/Bullfrog/Dungeon\ Keeper\ 2/DKII.EXE
It will fail every single time.
err:process:blah blah blah directory L"C:\\blah
wine: cannot find blahblah