wine users - Mar 2008 - CDROM detect failed

Hi,
   I was trying to install an old Sierra game called Lighthouse. It
used to fail completely under old versions of Wine and I got a request
to try it again. I am doing this on a Gentoo 64-bit machine but Wine
is a 32-bit app on this machine:

mark at lightning ~ $ file /usr/bin/wine
/usr/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs),
stripped
mark at lightning ~ $

   Anyway, in a clean account with no .wine directory (I don't run
Wine much...) I mounted the CD and then executed wine
/mnt/cdrom/setup.exe. The setup starts, checks sound and then fails
saying the system has no CDROM.

Questions:

1) Is it even valid to install Wine this way where there isn't an
existing Wine directory before I start the application install or is
preferred that I do some specific set of steps first.

2) How do I correctly show wine where to get the CD so that I can try
to move forward? Is that in winecfg, and if so then does running
winecfg first create everything required to install an app? I'm
running it right now and I see a C: and Z: drive. How do I specify a
CDROM in this? Just link it to /mnt/cdrom?

Thanks,
Mark

On Tue, Mar 4, 2008 at 8:48 AM, Mark Knecht <markknecht at gmail.com>
wrote:
> Hi,
>    I was trying to install an old Sierra game called Lighthouse. It
>  used to fail completely under old versions of Wine and I got a request
>  to try it again. I am doing this on a Gentoo 64-bit machine but Wine
>  is a 32-bit app on this machine:
>
>  mark at lightning ~ $ file /usr/bin/wine
>  /usr/bin/wine: ELF 32-bit LSB executable, Intel 80386, version 1
>  (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs),
>  stripped
>  mark at lightning ~ $
>
>    Anyway, in a clean account with no .wine directory (I don't run
>  Wine much...) I mounted the CD and then executed wine
>  /mnt/cdrom/setup.exe. The setup starts, checks sound and then fails
>  saying the system has no CDROM.
>
>  Questions:
>
>  1) Is it even valid to install Wine this way where there isn't an
>  existing Wine directory before I start the application install or is
>  preferred that I do some specific set of steps first.
>
>  2) How do I correctly show wine where to get the CD so that I can try
>  to move forward? Is that in winecfg, and if so then does running
>  winecfg first create everything required to install an app? I'm
>  running it right now and I see a C: and Z: drive. How do I specify a
>  CDROM in this? Just link it to /mnt/cdrom?
>
>  Thanks,
>  Mark
>
Following on I specified drive D: as a CD and tried the install. One
option was to test the system. Sound worked. Then it tried testing the
CD and crashed immediately with this and more:

mark at lightning ~ $ wine /mnt/cdrom/setup.exe
fixme:wave:wodPlayer_Reset shouldn't have headers left
wine: Unhandled division by zero at address 0x127f:0x00009de9 (thread
0015), starting debugger...
Unhandled exception: divide by zero in 16-bit code (127f:9de9).
In 16 bit mode.
Register dump:
 CS:127f SS:12c7 DS:12c7 ES:12c7 FS:0063 GS:006b
 IP:9de9 SP:5214 BP:533a FLAGS:0a47(   - 00     ROIZP1C)
 AX:0a00 BX:000e CX:04a9 DX:048d SI:001a DI:001a
Stack dump:
0x12c7:0x5214:  129f 12c7 6c53 129f 5da2 0001 12c7 002b
0x12c7:0x5224:  0000 8308 7dae 0000 0000 0000 0000 529c
0x12c7:0x5234:  0000 12c7 1688 1287 2654 12c7 0dfc 12c7
0258: sel=12c7 base=0040e2d0 limit=000067bf 16-bit rw-
Backtrace:
=>1 0x127f:0x9de9 (0x12c7:0x533a)
  2 0x129f:0x5265 (0x12c7:0x534a)
  3 0x129f:0x538f (0x12c7:0x5360)
  4 0x129f:0x1c8b (0x12c7:0x5394)
  5 0x129f:0x0243 (0x12c7:0x53c4)
  6 0x1287:0x2d2a (0x12c7:0x540e)
  7 0x101f:0x0468 in kernel32 (+0x7e30c) (0x12c7:0x5448)
  8 0x7ee8d48e K32WOWCallback16Ex+0xce() in kernel32 (0x7dae9628)
  9 0x7ed0cdfe WINPROC_wrapper+0x50e() in user32 (0x7dae9968)
  10 0x7ed0cefb WINPROC_wrapper+0x60b() in user32 (0x7dae9998)
  11 0x7ed0f86c in user32 (+0xaf86c) (0x7dae9e98)

I have to Ctrl-C out of the setup to get control again.

   Is this type of info of any use to anyone?

Thanks,
Mark

Since gentoo does not have 32-bit HAL you have to run winecfg, add cd-rom
mapping on "Drives" page, make sure it's type is set to cd-rom.
Verify that you do have access to the device (not just the mount point). Then
run your program with:

Code:
cd /mnt/cdrom/
wine "D:\setup.exe"


Assuming that you mapped cd-rom to D: drive. And that this is a single-cd
install.

Looks like a 16-bit app. These are horribly broken in Wine ATM. Please file a
bug in bugzilla. There is no fix, except returning to some 1 - 2 years old Wine.

Mark Knecht wrote:
> I tried to actually. When I copied the backtrace data from the
> terminal into a vi file it became unreadable by inserting more and
> more tab characters on each line. Line 1 got 1 tab, line 2 got 2 tabs,
> etc. After a few lines it was all wrapped around and completely
> useless.
> 


Code:
wine progy.exe &> /tmp/wine_log.txt

 always works.

On Wed, Mar 5, 2008 at 7:33 AM, vitamin <wineforum-user at winehq.org>
wrote:
>
>  Mark Knecht wrote:
>  > I tried to actually. When I copied the backtrace data from the
>  > terminal into a vi file it became unreadable by inserting more and
>  > more tab characters on each line. Line 1 got 1 tab, line 2 got 2
tabs,
>  > etc. After a few lines it was all wrapped around and completely
>  > useless.
>  >
>
>
>
>  Code:
>  wine progy.exe &> /tmp/wine_log.txt
>
>   always works.
>
Thanks.