His quote appears to be information from a terminal about the links in his dosdevices directory. I think what he is trying to tell you is to use the dummy installation in your ~/.wine/drive_c directory instead of an actual windows installation. Are you mounting the DVD drive before you run DVD shrink in wine? What version of Wine are you using? The last person before you said that new versions of wine don't even have a config file. Here's the link I provided him with:

http://ftp4.de.freesbie.org/pub/misc...040716.tar.bz2

and he got it functioning properly. Try it out if you have a different version and don't mind starting from scratch.

-Knappster

I have wine 0.0.20050725-1 from debian unstable repository. I have just set it up to use fakewindows instead of the actual hda1 (C) drive.
Incidentally, in your tutorial you suggest using dpkg -r to remove/reinstall wine. A better way is to just 'apt-get -t unstable install wine' which will upgrade the wine installation to the latest version available as a debian package.
Yes I am mounting the dvd before attempting to use dvdshrink; the problem is that dvdshrink doesn't even attempt to find the drive ie the 'open drive' dialog box is empty.
Others seem to have solved this with the symlink to the dvd drive; I have tried this but no success. I guess the next step is to reinstall dvdshrink in fake windows instead of attempting to use the existing actual windows install.
It looks like perhaps I am the only one attempting to use an actual windows install.

I have just installed dvdshrink to fake windows (version 3.2.0.15) but it still acts just as it did with the winme install; empty 'open drive' dialog box. The dvd is currently mounted on /cdrom, attempting to 'open files' results in a 'failed to open z:\cdrom\VIDEO_TS\VTS_01_0.VOB' error.
It must be something wrong with the drive setup; even the 'My Computer' dialog box does not show any disk drive, only the c: & z: drives.

The dpkg -r command was to completely remove wine. I had all sorts of problems with it when I tried to install a pre-packaged version. That is why I suggested downloading the source and compiling/installing manually. It takes a long time, but it worked out a lot better for me. You have a much newer version of wine than the version I used/suggested. It probably handles symlinks and config differently. One option you can try is to manually enter the drive name when starting dvd shrink. i.e.

wine "DVD\ Shrink\ 3.2.exe D:"

(if D: is your DVD drive)
I don't think the My Computer box is related to your problem, because mine would never expand My Computer either. If that command doesn't work, I would suggest starting from scratch and following my tutorial on how to actually compile and install wine. I have no experience with any versions of wine outside that one, and to be honest I have very little experience with it. That's the best I can do for you at this point man, good luck.

Also, if you have any other apps, you can check if they detect any of your drives just to find out if it's more likely a general wine or dvd shrink installation issue.

-Knappster

Tried that; again it was a no-go. I think I'll just stick with the vobcopy method, it seems to work reliably.
Your experience with compiling wine vs installing the .deb package is just the opposite of mine; I have always had better success with the packages. That is why I have a debian system, it's so easy to add applications & keep it up to date.

That is why, I use Gentoo instead of other package based distributions. The one problem with Gentoo, it compiles everything. I rather wait for programs to be compiled and installed instead of going through the mess of RPM, deb, tar.gz (Slackware) files. Compiling and then installing is the way to go when using Linux.

My ~/.wine/config that winetools created.
The listing of ~/.wine/dosdevices.
All I do to make DVD Shrink read the DVD disc, is mount the DVD disc. Then tell DVD Shrink to look it up DVD disc. I do not have to install special drivers in WINE. I am using kernel version 2.6.13. If you are using kernel version that is equal or less than 2.6.10, you will have problems with programs accessing the drive to extract low-level information. Also you will have problems writing CD and DVD discs.