Cannot run Win16 installer for Judaic Classics

onecoolcouple · Post by **onecoolcouple** » Sun Nov 30, 2008 9:53 am

Hi,

I am trying to install Davka Judaic Classics IIc, a bookshelf kind of software with Hebrew books. It is a win32 program that was designed for running also on win3.11, hence the installer is, I believe, win16. I have used this software on Win95 and Win98. The program happily runs off emulated cdroms.

I have now tried to install this program under wine, but can't even get the installer to run. Below you will find the output when running "wine installa.exe" (the installer for installs from floppy drive a:". For the record, I am using Fedora 10 for x86_64, with wine i386 (wine x86_64 doesn't even exist AFAIK), and the version of wine is 1.1.7. The kernel is 2.6.27.5-117.fc10.x86_64.

The output:

Code: Select all

[user@localhost ]$ wine ./installa.exe 
ALSA lib pcm.c:2162:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so                                              
ALSA lib pcm.c:2162:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so                                              
wine: Unhandled stack overflow at address 0x6036589d (thread 0017), starting debugger...                                                                        
Unhandled exception: stack overflow in 32-bit code (0x6036589d).                
fixme:dbghelp:addr_to_linear Failed to linearize address 7edb:00006648 (mode 0) 
Register dump:                                                                  
 CS:0023 SS:1207 DS:002b ES:11c7 FS:0063 GS:006b                                
 EIP:6036589d ESP:5447fff2 EBP:0000ad32 EFLAGS:00010202(   - 00      - -RI1)    
 EAX:120f0100 EBX:00001207 ECX:7edb6324 EDX:00000171                            
 ESI:000003c8 EDI:000004e8                                                      
Stack dump:                                                                     
0x1207:0xfff2:  0000 0000 0000 0000 0000 0000 0000 0000                         
0x1207:0x10002:  0000 0000 0000 0000 0000 0000 0000 0000                        
0x1207:0x10012:  0000 0000 0000 0000 0000 0000 0000 0000                        
Backtrace:                                                                      
=>1 0x6036589d in ntdll (+0x6589d) (0x003a19e2)                                 
  2 0xca0111f7 (0x06e1ad6e)                                                     
  3 0x00000000 (0x00000000)                                                     
0x6036589d: pushl       0xc0(%ecx)                                              
Modules:                                                                        
Module  Address                 Debug info      Name (57 modules)               
ELF     60000000-60023000       Deferred        ld-linux.so.2                   
ELF     60023000-6015a000       Deferred        libwine.so.1                    
ELF     6015a000-60174000       Deferred        libpthread.so.0                 
ELF     60174000-602e8000       Deferred        libc.so.6                       
ELF     602e8000-602ed000       Deferred        libdl.so.2                      
ELF     602ed000-6039c000       Export          ntdll<elf>                      
  \-PE  60300000-6039c000       \               ntdll                           
ELF     6039c000-603c5000       Deferred        libm.so.6                       
ELF     603c5000-603d2000       Deferred        libnss_files.so.2               
ELF     603d2000-603e7000       Deferred        winevdm<elf>                    
  \-PE  603e0000-603e7000       \               winevdm                         
ELF     603e7000-6048f000       Deferred        gdi32<elf>                      
  \-PE  60400000-6048f000       \               gdi32                           
ELF     6048f000-604e8000       Deferred        advapi32<elf>                   
  \-PE  604a0000-604e8000       \               advapi32                        
ELF     604e8000-6057b000       Deferred        libfreetype.so.6                
ELF     6057b000-605aa000       Deferred        libfontconfig.so.1              
ELF     605aa000-605d1000       Deferred        libexpat.so.1                   
ELF     605d1000-60671000       Deferred        winex11<elf>                    
  \-PE  605e0000-60671000       \               winex11                         
ELF     60671000-60679000       Deferred        libsm.so.6                      
ELF     60679000-60693000       Deferred        libice.so.6                     
ELF     60693000-606a3000       Deferred        libxext.so.6                    
ELF     606a3000-607a4000       Deferred        libx11.so.6                     
ELF     607a4000-607a8000       Deferred        libuuid.so.1                    
ELF     607a8000-607ab000       Deferred        libxau.so.6                     
ELF     607ab000-607ad000       Deferred        libxcb-xlib.so.0                
ELF     607ad000-607c9000       Deferred        libxcb.so.1                     
ELF     607c9000-607cf000       Deferred        libxdmcp.so.6                   
ELF     607cf000-607f0000       Deferred        imm32<elf>                      
  \-PE  607e0000-607f0000       \               imm32                           
ELF     607f0000-607f3000       Deferred        libxinerama.so.1                
ELF     607f3000-607fa000       Deferred        libxrandr.so.2                  
ELF     607fa000-607fd000       Deferred        libxcomposite.so.1              
ELF     607fd000-60802000       Deferred        libxfixes.so.3                  
ELF     60802000-6080c000       Deferred        libxcursor.so.1                 
ELF     6080c000-60871000       Deferred        winedos<elf>                    
  \-PE  60810000-60871000       \               winedos                         
ELF     60871000-60908000       Deferred        winmm<elf>                      
  \-PE  60880000-60908000       \               winmm                           
ELF     60908000-6093f000       Deferred        winealsa<elf>                   
  \-PE  60910000-6093f000       \               winealsa                        
ELF     6093f000-60a21000       Deferred        libasound.so.2                  
ELF     60a21000-60a2b000       Deferred        librt.so.1                      
ELF     60a2b000-60a43000       Deferred        msacm32<elf>                    
  \-PE  60a30000-60a43000       \               msacm32                         
ELF     60a43000-60a58000       Deferred        midimap<elf>                    
  \-PE  60a50000-60a58000       \               midimap                         
ELF     617a0000-617c9000       Deferred        msacm32<elf>                    
  \-PE  617b0000-617c9000       \               msacm32                         
ELF     66511000-66516000       Deferred        libxxf86vm.so.1                 
ELF     67ebf000-6800a000       Deferred        kernel32<elf>                   
  \-PE  67ee0000-6800a000       \               kernel32                        
ELF     6fbc6000-6fd22000       Deferred        user32<elf>
  \-PE  6fbe0000-6fd22000       \               user32
ELF     71fb2000-71fbb000       Deferred        libxrender.so.1
ELF     7bf00000-7bf03000       Deferred        <wine-loader>
Threads:
process  tid      prio (all id:s are in hex)
0000000c
        00000013    0
        00000012    0
        0000000e    0
        0000000d    0
0000000f
        00000014    0
        00000011    0
        00000010    0
00000015 (D) C:\windows\system32\winevdm.exe
        00000017    0 <==
        00000016    0
Backtrace:
=>1 0x6036589d in ntdll (+0x6589d) (0x003a19e2)
  2 0xca0111f7 (0x06e1ad6e)
  3 0x00000000 (0x00000000)
err:ntdll:RtlpWaitForCriticalSection section 0x68007be0 "syslevel.c: Win16Mutex" wait timed out in thread 0016, blocked by 0017, retrying (60 sec)
[user@localhost ]$

Can someone make sense out of the error message? How do I get around this?

--OCC

austin987 · Post by **austin987** » Sun Nov 30, 2008 12:51 pm

On Sun, Nov 30, 2008 at 8:53 AM, onecoolcouple
<[email protected]> wrote:

Hi,

I am trying to install Davka Judaic Classics IIc, a bookshelf kind of software with Hebrew books. It is a win32 program that was designed for running also on win3.11, hence the installer is, I believe, win16. I have used this software on Win95 and Win98. The program happily runs off emulated cdroms.

I have now tried to install this program under wine, but can't even get the installer to run. Below you will find the output when running "wine installa.exe" (the installer for installs from floppy drive a:". For the record, I am using Fedora 10 for x86_64, with wine i386 (wine x86_64 doesn't even exist AFAIK), and the version of wine is 1.1.7. The kernel is 2.6.27.5-117.fc10.x86_64.

The output:

Code:
[user@localhost ]$ wine ./installa.exe
ALSA lib pcm.c(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so
ALSA lib pcm.c(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so
wine: Unhandled stack overflow at address 0x6036589d (thread 0017), starting debugger...
Unhandled exception: stack overflow in 32-bit code (0x6036589d).
fixme:dbghelp:addr_to_linear Failed to linearize address 7edb:00006648 (mode 0)
Register dump:
CS:0023 SS:1207 DS:002b ES:11c7 FS:0063 GS:006b
EIP:6036589d ESP:5447fff2 EBP:0000ad32 EFLAGS:00010202( - 00 - -RI1)
EAX:120f0100 EBX:00001207 ECX:7edb6324 EDX:00000171
ESI:000003c8 EDI:000004e8
Stack dump:
0x1207:0xfff2: 0000 0000 0000 0000 0000 0000 0000 0000
0x1207:0x10002: 0000 0000 0000 0000 0000 0000 0000 0000
0x1207:0x10012: 0000 0000 0000 0000 0000 0000 0000 0000
Backtrace:
=>1 0x6036589d in ntdll (+0x6589d) (0x003a19e2)
2 0xca0111f7 (0x06e1ad6e)
3 0x00000000 (0x00000000)
0x6036589d: pushl 0xc0(%ecx)
Modules:
Module Address Debug info Name (57 modules)
ELF 60000000-60023000 Deferred ld-linux.so.2
ELF 60023000-6015a000 Deferred libwine.so.1
ELF 6015a000-60174000 Deferred libpthread.so.0
ELF 60174000-602e8000 Deferred libc.so.6
ELF 602e8000-602ed000 Deferred libdl.so.2
ELF 602ed000-6039c000 Export ntdll<elf>
\-PE 60300000-6039c000 \ ntdll
ELF 6039c000-603c5000 Deferred libm.so.6
ELF 603c5000-603d2000 Deferred libnss_files.so.2
ELF 603d2000-603e7000 Deferred winevdm<elf>
\-PE 603e0000-603e7000 \ winevdm
ELF 603e7000-6048f000 Deferred gdi32<elf>
\-PE 60400000-6048f000 \ gdi32
ELF 6048f000-604e8000 Deferred advapi32<elf>
\-PE 604a0000-604e8000 \ advapi32
ELF 604e8000-6057b000 Deferred libfreetype.so.6
ELF 6057b000-605aa000 Deferred libfontconfig.so.1
ELF 605aa000-605d1000 Deferred libexpat.so.1
ELF 605d1000-60671000 Deferred winex11<elf>
\-PE 605e0000-60671000 \ winex11
ELF 60671000-60679000 Deferred libsm.so.6
ELF 60679000-60693000 Deferred libice.so.6
ELF 60693000-606a3000 Deferred libxext.so.6
ELF 606a3000-607a4000 Deferred libx11.so.6
ELF 607a4000-607a8000 Deferred libuuid.so.1
ELF 607a8000-607ab000 Deferred libxau.so.6
ELF 607ab000-607ad000 Deferred libxcb-xlib.so.0
ELF 607ad000-607c9000 Deferred libxcb.so.1
ELF 607c9000-607cf000 Deferred libxdmcp.so.6
ELF 607cf000-607f0000 Deferred imm32<elf>
\-PE 607e0000-607f0000 \ imm32
ELF 607f0000-607f3000 Deferred libxinerama.so.1
ELF 607f3000-607fa000 Deferred libxrandr.so.2
ELF 607fa000-607fd000 Deferred libxcomposite.so.1
ELF 607fd000-60802000 Deferred libxfixes.so.3
ELF 60802000-6080c000 Deferred libxcursor.so.1
ELF 6080c000-60871000 Deferred winedos<elf>
\-PE 60810000-60871000 \ winedos
ELF 60871000-60908000 Deferred winmm<elf>
\-PE 60880000-60908000 \ winmm
ELF 60908000-6093f000 Deferred winealsa<elf>
\-PE 60910000-6093f000 \ winealsa
ELF 6093f000-60a21000 Deferred libasound.so.2
ELF 60a21000-60a2b000 Deferred librt.so.1
ELF 60a2b000-60a43000 Deferred msacm32<elf>
\-PE 60a30000-60a43000 \ msacm32
ELF 60a43000-60a58000 Deferred midimap<elf>
\-PE 60a50000-60a58000 \ midimap
ELF 617a0000-617c9000 Deferred msacm32<elf>
\-PE 617b0000-617c9000 \ msacm32
ELF 66511000-66516000 Deferred libxxf86vm.so.1
ELF 67ebf000-6800a000 Deferred kernel32<elf>
\-PE 67ee0000-6800a000 \ kernel32
ELF 6fbc6000-6fd22000 Deferred user32<elf>
\-PE 6fbe0000-6fd22000 \ user32
ELF 71fb2000-71fbb000 Deferred libxrender.so.1
ELF 7bf00000-7bf03000 Deferred <wine-loader>
Threads:
process tid prio (all id:s are in hex)
0000000c
00000013 0
00000012 0
0000000e 0
0000000d 0
0000000f
00000014 0
00000011 0
00000010 0
00000015 (D) C:\windows\system32\winevdm.exe
00000017 0 <==
00000016 0
Backtrace:
=>1 0x6036589d in ntdll (+0x6589d) (0x003a19e2)
2 0xca0111f7 (0x06e1ad6e)
3 0x00000000 (0x00000000)
err:ntdll:RtlpWaitForCriticalSection section 0x68007be0 "syslevel.c: Win16Mutex" wait timed out in thread 0016, blocked by 0017, retrying (60 sec)
[user@localhost ]$

Can someone make sense out of the error message? How do I get around this?

--OCC

File a bug at http://bugs.winehq.org

--
-Austin

onecoolcouple · Post by **onecoolcouple** » Mon Jan 19, 2009 3:13 pm

I found a partial workaround: since this is an old program, which, as far as I can tell, does not use the registry, I simply copied the directory that contains the program files of that program in wine's program files directory, and also added the fonts it needs in wine's font directory, and voila, ...

... it works...

... almost.

The problem is that it expects a CDROM in the drive. I had ripped the cdrom into an iso, which was good enough when accessing that "cdrom" from under qemu+Win98 guest, so there is no copy protection on that disc, but yet, despite having loop mounted the iso on /mnt, which, according to my wine configuration, is a cdrom, the program complains of a lack of cdrom ("please insert your Davka Judaic Classics CD in your CD drive").

So, what can I do to fix this?

vitamin · Post by **vitamin** » Mon Jan 19, 2009 3:35 pm

onecoolcouple wrote:the program complains of a lack of cdrom ("please insert your Davka Judaic Classics CD in your CD drive").

Did you mapped it to a disk drive in winecfg?
Also note that some games record where they were installed from. And use that path to find "the CD-ROM" they want.

onecoolcouple · Post by **onecoolcouple** » Mon Jan 19, 2009 5:16 pm

I configured wine using the graphical winecfg, but I cannot find where it stores the info, so I cannot provide a listing. However, after closing and restarting that program, I see that the "drive" is indeed correctly configured, meaning, I mounted the iso on /mnt and configured /mnt as D:, which is reported as a cd drive.

Regarding the possibility that it saved the cd drive letter from during install, well, I changed /mnt to E:, and still got the same results.

I grepped my Windows98 virtual machine and didn't find anything significant, though the name of the program did show up in the registry, but a registry search did not bring up anything useful.

I also tried to let winecfg report the label of the mounted simulated cd as it is on the original cd, to no avail.

Is there a way to force wine on the command line, when executing the program, to mount a particular iso file as a cd, or, alternatively, to use a particular directory to simulate a cd?

vitamin · Post by **vitamin** » Mon Jan 19, 2009 5:20 pm

onecoolcouple wrote:I also tried to let winecfg report the label of the mounted simulated cd as it is on the original cd, to no avail.

This is not supported.

onecoolcouple wrote:Is there a way to force wine on the command line, when executing the program, to mount a particular iso file as a cd, or, alternatively, to use a particular directory to simulate a cd?

No, Wine can't mount ISO images.

onecoolcouple · Post by **onecoolcouple** » Mon Jan 19, 2009 5:23 pm

But,

Is there a way to force wine on the command line, when executing the program, to ... use a particular directory to simulate a cd?

austin987 · Post by **austin987** » Mon Jan 19, 2009 5:37 pm

On Mon, Jan 19, 2009 at 4:23 PM, onecoolcouple
<[email protected]> wrote:

But,

Is there a way to force wine on the command line, when executing the program, to ... use a particular directory to simulate a cd?

No.

--
-Austin

onecoolcouple · Post by **onecoolcouple** » Mon Jan 19, 2009 6:14 pm

It gets more fun. I popped in the original data disk, mounted it, and correspondingly changed the path to the cdrom device (E: ) in winecfg. I tried starting the program, and it complained that it could not find a valid cdrom. I edited fstab (because current distributions mount removable devices differently, which results in unpredictable path names for mounted removable file systems, and makes it difficult to provide the path to an as of yet unmounted filesystem) and added a trusted entry for the cdrom device, and tried starting the program both with mounted and with unmounted cdrom, but again had no success.

Where should I look for the problem? Remember that it is a win 3.1/win95 program (but win32).

I even tried through winecfg forcing it to emulate win95 and win3.1, but to no avail.

vitamin · Post by **vitamin** » Mon Jan 19, 2009 7:18 pm

onecoolcouple wrote:added a trusted entry for the cdrom device, and tried starting the program both with mounted and with unmounted cdrom, but again had no success.

As I said before, it might be writing the path you installed it from somewhere to ini/cfg/registry.

onecoolcouple · Post by **onecoolcouple** » Mon Jan 19, 2009 8:57 pm

I searched through all occurrences of the program name in the registry, and they only refer to the menus. I grepped for two forms of the program name in the entire Windows partition, and didn't come up with anything useful. Where else should I look?

onecoolcouple · Post by **onecoolcouple** » Tue Feb 03, 2009 3:24 am

I installed the software on a brand new WinXP machine, an Asus eee (I had to simulate the floppy with a driver that is floating around on the net, vfd21-080206.zip, which, AFAIK, is a totally legitimate thing), and took care to watch the registry before and after the install, using whatchanged.exe (which, again, seems totally legitimate. Just remember to always use a virus scanner and assorted anti-malware techniques).

Anyway, looking over the recorded changes, I could spot nothing deserving attention.

Is there an easy way to find out what files the program accesses or tries to access when it runs under Wine, so that I will be able to guess where to look for the missing settings?
--OCC

L. Rahyen · Post by **L. Rahyen** » Tue Feb 03, 2009 5:17 am

On 2009-02-03 (Tuesday) 08:24:55 onecoolcouple wrote:

Is there an easy way to find out what files the program accesses or tries
to access when it runs under Wine

Yes. There is many ways to do this. One of them is to run your program like
this:

WINEDEBUG=+file wine notepad

Obviously, instead of "notepad" you should use name of your program. You can
use grep to filter for particular pattern (for example, if you interested
only in files with .txt extension you can run this command:

WINEDEBUG=+file wine notepad | grep -i .txt

Alternatively you can use strace. For example (this command will work in
zsh):

strace wine notepad |& grep -i .txt

If you are using bash you can use this command instead:

strace wine notepad 2>&1| grep -i .txt

You should use grep to filter strace output to see only things you interested
in: for example extension, path (full or partial) or file related operations
(for example "grep -i stat64\(" or "grep -i open\("). I suggest you to play
with notepad to understand how it works then try it with your program.

onecoolcouple · Post by **onecoolcouple** » Tue Feb 03, 2009 8:36 am

Thank you. Unfortunately, I bit more than I can swallow. I redirected the output of strace to a file, but it has more than 22k lines. How do I sensibly winnow that down? I have never used strace before and the output is overwhelming.

Alternatively/additionally, is there something similar for windows, which I can use to check what happens under windows, with a functioning copy of the program I am researching?

--OCC

L. Rahyen · Post by **L. Rahyen** » Tue Feb 03, 2009 11:36 am

On 2009-02-03 (Tuesday) 13:36:07 onecoolcouple wrote:

Thank you. Unfortunately, I bit more than I can swallow. I redirected the
output of strace to a file, but it has more than 22k lines. How do I
sensibly winnow that down?

I'm not sure because you didn't give command you have used, you didn't mention what parameters for grep you have used (if you didn't
used grep to filter strace output or used it improperly you will get much less useful output), you didn't mentioned what shell you are
using and what OS.

I provide few more examples, perhaps they help you to understand what to do.

To record into log.txt what files *with* an extension (except ones with .dll, .exe, .sys, .drv, .tmp, .ttf, .lnk and .fon extensions)
the application tries to use on virtual C:\ disk (located in Wine prefix) run this:

For bash (in zsh you can replace "2>&1|" with "|&" but this isn't really necessary):

strace wine notepad 2>&1| \
egrep -i 'stat(64)\(".*?(/c:/|/drive_c/).*?\..*?"' | \
egrep -vi '(\.dll|win.ini|wininit.ini|\.exe|\.sys|\.drv|\.fon|\.tmp|\.ttf|\.lnk|\.windows-|desktop.ini|system.ini)' > log.txt

Or:

WINEDEBUG=+file wine notepad 2>&1| \
egrep -i 'L"C:\\.*?\..*?"' | \
egrep -vi '(\.dll|win.ini|wininit.ini|\.exe|\.sys|\.drv|\.fon|\.tmp|\.ttf|\.lnk|\.windows-|desktop.ini|system.ini|\*\.\*)' > log.txt

Note: Both commands are multi-line commands. To use them simply copy-paste all 3 lines to your console and press Enter; egrep filters
in above commands will also filter out useless stuff like use of "desktop.ini" or "win.ini" files. Instead of "notepad" use name of
your application. Don't use [Ctrl]+[C] in the console (or you may lose your log); exit from the application properly instead (or kill
it with xkill). If you want to see files without extension too (including directories) then remove ".*?\." from second line. If you
want to see files from all drives then replace "C:\\" in second line with "?:\\" or (for strace example) "(/c:/|/drive_c/)"
with "(/?:/|/cdrom/|/mnt/|/media/)".

If you still need help, please answer to questions above and explain what you are looking for (do you expect the file you want
to find to have an extension, do you expect to find it in drive_c, and other possibly useful information) and I may give you egrep
filters you need if above filters aren't suitable for you and you don't know how to change them.

Alternatively/additionally, is there something similar for windows,
which I can use to check what happens under windows, with a
functioning copy of the program I am researching?

Sorry, but I'm not a Windows expert. I never tried to debug anything in Windows so I don't know.

If above tricks with strace or WINEDEBUG=+file don't help you I recommend you to reinstall your application in clean Wine prefix with
latest Wine (1.1.14). For example:

rm -rf ~/.wine

Or:

mv ~/.wine{,.old}

And then run winecfg, configure your CD/DVD-ROM as CD-ROM in winecfg and then install your application. If still doesn't work, is
there any change in behavior or errors the application gives you after (possibly unsuccessful) installation in clean Wine?

onecoolcouple · Post by **onecoolcouple** » Tue Feb 03, 2009 12:03 pm

I ran strace without grep, and redirected stderr to a file, so that I can analyze it peacefully and change my mind as many times as I want without needing to run the command again (though that shouldn't be too troublesome, either).

command line:
strace wine .wine/drive_c/Program\ Files/davkajcl/judclib2.exe &> .wine/judaic_classics.stderr

Regarding your suggestion to capture the error messages when running wine directly, the problem is that there are no error messages anymore, at the command line level. As far as wine is concerned, the program runs fine, it starts, and it interacts with the user. However, its only interaction is a dialog box complaining about the lack of a valid CDROM in the drive.

The reason I didn't grep for anything in particular is that I have no idea what I am looking for. I am looking for what is missing, essentially, though if it is a registry key that is missing, then it won't show up as missing with strace, for the registry does exist, it may simply lack the information my program is looking for.

The way I imagine my research going, is by eliminating everything that is obviously not important, and then looking at what is left.

Oh, and, by the way, I know regex and am fine with writing my own grep commands. It's the what I should be excluding or looking for that I don't know.

onecoolcouple · Post by **onecoolcouple** » Tue Feb 03, 2009 12:15 pm

I forgot to specify my system:

Fedora 10 x86_64 with latest wine updates in the regular Fedora repository, wine-1.1.12-1.fc10.i386.

I have several programs running happily under wine, so the installation is generally OK.

onecoolcouple · Post by **onecoolcouple** » Tue Feb 03, 2009 12:24 pm

I ran the program with WINDEBUG=+file and got some useful output. It mentions a bunch of files that were not found. I will have to look at it in detail.

By the way, reviewing my own posts on this thread, I saw that all the way at the top I had already described my system.

Thanks for your continuing help, I look forward solving this enigma.

--OCC

Gert van den Berg · Post by **Gert van den Berg** » Tue Feb 03, 2009 2:03 pm

On Tue, Feb 3, 2009 at 3:36 PM, onecoolcouple <[email protected]> wrote:

Alternatively/additionally, is there something similar for windows, which I can use to check what happens under windows, with a functioning copy of the program I am researching?

Filemon and regmon from here: (They may / may not work under Wine and
may / may not be legal to use under Wine without a Windows license)
http://technet.microsoft.com/en-us/sysi ... 9e2f5.aspx

vitamin · Post by **vitamin** » Tue Feb 03, 2009 6:31 pm

Gert van den Berg wrote:They may / may not work under Wine

They will not work on Wine. Don't suggest something you do not know.

Gert van den Berg · Post by **Gert van den Berg** » Tue Feb 03, 2009 11:40 pm

On Wed, Feb 4, 2009 at 1:31 AM, vitamin <[email protected]> wrote:

Gert van den Berg wrote:
They may / may not work under Wine
They will not work on Wine. Don't suggest something you do not know.

What I meant was that I have not tested it (since he was asking about
the Windows side of thing I did not think it really mattered whether
or not it actually worked under Wine) and that he should not expect it
to work, although I though that it might, considering that I did not
try it / read the AppDb entries / know enough about how the tools are
implemented and what the state of the relevant Wine code is.. I
attempted to use the "may / may not" to indicate that it is purely
speculation and requires further research...

onecoolcouple · Post by **onecoolcouple** » Wed Feb 04, 2009 3:53 am

Gert van den Berg wrote:

They may / may not work under Wine

Vitamin wrote:

They will not work on Wine. Don't suggest something you do not know.

No problem; I had asked about them so I can analyze what the program uses *under* *Windows* (which I also run a a Qemu guest).