Anyone tried WinUAE with Linux & WINE?

[mark_k]

Hi,

I'm trying to get WinUAE 1.4.1 to work under Linux using WINE (latest version).

It installs and runs, but the Amiga display remains black. I'm guessing that's due to WINE's DirectX support not being perfect, but I'd like to know if anyone else has had more luck. Maybe some adjustment to the WINE configuration could get WinUAE working???

[Toni Wilen]

Try ticking "Don't use RGB overlays" in misc panel.

[mark_k]

Hi,

Thanks for the tip, unfortunately that didn't seem to help.

I guess it may be down to WINE's DirectX emulation not being good enough yet. But I would like to hear whether anyone else has got WinUAE running under Linux/WINE to rule out some issue with my system. (If any non-Linux user wants to try, it's very simple to download a live Linux CD like Knoppix and install WinUAE & the latest WINE version.)

E-UAE does work on my system, by the way.

[Of course this isn't a problem in WinUAE, but this is probably the most appropriate forum to ask a question like that.]

[billy]

I've used WinUAE to vering degrees of success in WINE. I don't have specifics now, because I've been playing with it for years and each time Toni releases a beta executable, I give it another shot on whicever version of WINE I happen to have installed at the time.

I've always had difficulties with video and on some versions of WINE, audio as well. The present state of my systen iis that Fullscreen 16-bit works the best. The problem being, WINE fails to context switch properly between the GUI Properties window [F12] and the main WinUAE screen. So, it will start fine, but if you press F12, you get the Properties screen Fullscreen in the same size screen as the WinUAE display. For instance if you run 640x480 Fullscreen, the Properties dialog comes up in 640x480 Fullscreen and obviously isn't shown in it's entirety. Then there is no way for me to switch back to WinUAE, almost as if we have lost focus on the dialog. Pretty useless.

I have thought about playing with my keyboard mappings but often loose my train of thought when my pint runs dry

There was a period where it worked flawlessly, however being a tinkerer I wasn't content, I tried to get WINE to function with JACK audio. That never worked properly. I quit playing about the time that WINE decided there was a problem with it's JACK interface.

Bottom line is, you can probably make it work... it's just been since WinUAE 1.0/1.2 that I have done so. I know 0.8.8 something or other used to do quite well, but that was before WINE underwent it's major DirextX overhaul.

[mark_k]

Hi,

A quick update since I just tried WinUAE 1.4.2a with the now-latest version of WINE, 0.9.37. (Previously I used WINE 0.9.36.)

WinUAE now works, mostly. The graphics work and I can see the emulated program fine. However there is still a minor issue, at least on my system. After pressing F12 to bring up the settings window, often clicking the OK, Reset or Quit buttons causes the settings windows to close then reopen. (Using Ctrl-F4 does exit WinUAE.)

Still, this is *much* better than before, so hopefully as WINE improves it will become a reasonable alternative to using E-UAE in Linux.

-- M

[etnablog]

I had just download winuae 1.4.2a and I'm using wine 0.9.37 but winuae doesn't want to work on my linux (Ubuntu Feisty).

Can you give me any suggestion to configure wine or winuae?

[Fackamato]

Using E-UAE would probably result in better performance in all ways... I wish the GUI of E-UAE would improve (copy WinUAE's GUI perhaps )

[mark_k]

Originally Posted by etnablog

I had just download winuae 1.4.2a and I'm using wine 0.9.37 but winuae doesn't want to work on my linux (Ubuntu Feisty).

Can you give me any suggestion to configure wine or winuae?

Can you give a more detailed explanation of what the problem is? Does WinUAE start at all?

I'm booting from a Linux live CD, Backtrack 2.0 (available from http://www.remote-exploit.org/). That's based on the Slackware distribution. The CD includes an older version of WINE. I just downloaded the latest WINE binary .tgz file for Slackware from winehq.com, and un-tar'ed it to the root directory.

Then I ran the WinUAE 1.4.2a executable installer using WINE: wine InstallWinUAE1420a.exe

The installer appears to work fine, and after it completes I can use wine to run winuae.exe.

Originally Posted by Fackamato

Using E-UAE would probably result in better performance in all ways... I wish the GUI of E-UAE would improve (copy WinUAE's GUI perhaps )

Sure. It's just that WinUAE seems significantly more up-to-date feature-wise than E-UAE.


-- M

[etnablog]

- linux distribution: Ubuntu Feisty Fawn
- wine 0.9.37
- winuae 1.4.2a

on winecfg: windows 2000, XP, or 98.

Winuae installs perfectly and Winuae GUI works perfectly as well.

I set a normal a500, with kickstart 1.3, a game on df0: drive, ecc..ecc....

When I try to start emulation it crashes giving me: "crash detected: Minidump saved as: c:\Programmi\WinUae\winuae_1420_20070517_233057.dmp"

If I try fullscreen mode it does not give me that error, simply directly exits Winuae..

Can you play something with winuae on wine?

[haps]

Originally Posted by mark_k

Sure. It's just that WinUAE seems significantly more up-to-date feature-wise than E-UAE.

euae may not be on par with winuae feature wise, but you will find that it is more than capable of doing just about anything you ask of it. I use it every day and have had no trouble.

[Shoonay]

Cool, someday i'll try to run Ubuntu on VMware on Vista, with WinUAE on WINE.

[mark_k]

Originally Posted by etnablog

- linux distribution: Ubuntu Feisty Fawn
- wine 0.9.37
- winuae 1.4.2a

on winecfg: windows 2000, XP, or 98.

Winuae installs perfectly and Winuae GUI works perfectly as well.

I set a normal a500, with kickstart 1.3, a game on df0: drive, ecc..ecc....

When I try to start emulation it crashes giving me: "crash detected: Minidump saved as: c:\Programmi\WinUae\winuae_1420_20070517_233057.dmp"

If I try fullscreen mode it does not give me that error, simply directly exits Winuae..

Can you play something with winuae on wine?

Yes, I've tried loading a couple of demos and docs disks and they seem to work okay. Full-screen mode doesn't work for me either. It doesn't directly exit, but kind of "hangs up". Perhaps the problem is related to your graphics card driver or the X.org support for it? Which make of graphics card do you have? On my (old and slow) system I'm just using the Intel i810 integrated graphics.

Also try selecting the "Don't use RGB overlays" option in the Misc panel as Toni suggested before. (WinUAE works for me regardless of that setting.)

For testing purposes, try downloading the BackTrack 2.0 CD image from http://www.remote-exploit.org/backtrack.html and boot from that, since that's what I'm booting from for testing WinUAE.

-- M

[etnablog]

Originally Posted by mark_k

Perhaps the problem is related to your graphics card driver or the X.org support for it? Which make of graphics card do you have?

It's an ATI 9500 pro (it seems to be correctly installed..) :/

I've tried to modify "RGB overlays", disable/enable sound on winuae, and some other options.. Nothing to do...It always gives to me the same error...

But I don't exclude a graphic card trouble.

When I have installed winuae here with wine, first it asks to such as a "graphic test of winuae", i have selected "ok" and it kicked me directly to GDM (the screen when I tipe login & password of my linux box), terminating my session...

I tried to install again & again.. same problem..

The only possibility for me it was to skip that test... And now I'm here.

[Toni Wilen]

Check also logs (winuaebootlog.txt and winuaelog.txt, winuaelog.txt enable checkbox is in misc-panel). Or run with -log command line parameter to enable log console.

[etnablog]

Originally Posted by Toni Wilen

Check also logs (winuaebootlog.txt and winuaelog.txt, winuaelog.txt enable checkbox is in misc-panel). Or run with -log command line parameter to enable log console.

My winuaebootlog.txt:

WinUAE 1.4.2a (2007.05.13) (NT 5.0 Service Pack 4 [1]) 32-bit 6.304 1 
(c) 1995-2001 Bernd Schmidt   - Core UAE concept and implementation. 
(c) 1998-2007 Toni Wilen      - Win32 port, core code updates. 
(c) 1996-2001 Brian King      - Win32 port, Picasso96 RTG, and GUI. 
(c) 1996-1999 Mathias Ortmann - Win32 port and bsdsocket support. 
(c) 2000-2001 Bernd Meyer     - JIT engine. 
(c) 2000-2005 Bernd Roesch    - MIDI input, many fixes. 
Press F12 to show the Settings Dialog (GUI), Alt-F4 to quit. 
End+F1 changes floppy 0, End+F2 changes floppy 1, etc. 
AF_NEW: 'c:\windows\profiles\All Users\Documenti\Amiga Files\WinUAE\' 
EXE: 'C:\Programmi\WinUAE\', DATA: 'C:\Programmi\WinUAE\' 
CLOCKFREQ: QPF 1.19MHz (1.19MHz, DIV=1) 
CLOCKFREQ: RDTSC 2565.64MHz (busy) / 2421.04MHz (idle) 
CLOCKFREQ: CPU throttling detected, using QPF instead of RDTSC 
Testing MM-timer resolution: 
115.51ms 112.06ms 103.74ms 0.17ms 107.68ms  
Testing Sleep() resolution: 
103.68ms 112.22ms 111.44ms 111.99ms 107.95ms  
falling back to busy-loop waiting (timer resolution > 2.5ms) 
Enumerating display devices..  
'DirectDraw HAL' 'display' NULL 
Sorting devices and modes.. 
Desktop: W=1024 H=768 B=24 
0: 400x300, 8-bit (85,75,72,60) 
1: 400x300, 16-bit (85,75,72,60) 
2: 400x300, 32-bit (85,75,72,60) 
3: 416x312, 8-bit (75) 
4: 416x312, 16-bit (75) 
5: 416x312, 32-bit (75) 
6: 512x384, 8-bit (87) 
7: 512x384, 16-bit (87) 
8: 512x384, 32-bit (87) 
9: 640x350, 8-bit (85) 
10: 640x350, 16-bit (85) 
11: 640x350, 32-bit (85) 
12: 640x400, 8-bit (85) 
13: 640x400, 16-bit (85) 
14: 640x400, 32-bit (85) 
15: 640x480, 8-bit (85,75,73,60) 
16: 640x480, 16-bit (85,75,73,60) 
17: 640x480, 32-bit (85,75,73,60) 
18: 720x400, 8-bit (85) 
19: 720x400, 16-bit (85) 
20: 720x400, 32-bit (85) 
21: 800x600, 8-bit (85,75,72,60,56) 
22: 800x600, 16-bit (85,75,72,60,56) 
23: 800x600, 32-bit (85,75,72,60,56) 
24: 832x624, 8-bit (75) 
25: 832x624, 16-bit (75) 
26: 832x624, 32-bit (75) 
27: 1024x768, 8-bit (85,75,70,60,87) 
28: 1024x768, 16-bit (85,75,70,60,87) 
29: 1024x768, 32-bit (85,75,70,60,87) 
30: 1152x768, 8-bit (55) 
31: 1152x768, 16-bit (55) 
32: 1152x768, 32-bit (55) 
33: 1152x864, 8-bit (85,75) 
34: 1152x864, 16-bit (85,75) 
35: 1152x864, 32-bit (85,75) 
36: 1280x768, 8-bit (60) 
37: 1280x768, 16-bit (60) 
38: 1280x768, 32-bit (60) 
39: 1280x800, 8-bit (60) 
40: 1280x800, 16-bit (60) 
41: 1280x800, 32-bit (60) 
42: 1280x960, 8-bit (85,60) 
43: 1280x960, 16-bit (85,60) 
44: 1280x960, 32-bit (85,60) 
45: 1280x1024, 8-bit (85,75,60) 
46: 1280x1024, 16-bit (85,75,60) 
47: 1280x1024, 32-bit (85,75,60) 
48: 1400x1050, 8-bit (85,75,70,60) 
49: 1400x1050, 16-bit (85,75,70,60) 
50: 1400x1050, 32-bit (85,75,70,60) 
51: 1440x900, 8-bit (60) 
52: 1440x900, 16-bit (60) 
53: 1440x900, 32-bit (60) 
54: 1600x1200, 8-bit (75,70,65,60) 
55: 1600x1200, 16-bit (75,70,65,60) 
56: 1600x1200, 32-bit (75,70,65,60) 
'DirectDraw HAL', 57 display modes (enabled) 
done 
CW: No Catweasel detected 
PARAPORT: no ParaPort.dll, direct parallel port emulation disabled 
IPC: Named Pipe '\\.\pipe\WinUAE' open 
IPC: waiting for connections 
Serial port enumeration.. 
SERPORT: 0:'COM1' = '\.\\COM1' (\dev\ttyS0) 
SERPORT: 1:'COM2' = '\.\\COM2' (\dev\ttyS1) 
SERPORT: 2:'COM3' = '\.\\COM3' (\dev\ttyS2) 
SERPORT: 3:'COM4' = '\.\\COM4' (\dev\ttyS3) 
Serial port enumeration end 
DirectInput enumeration.. Keyboards.. 
GUID=6F1D2B61-0000D5A0-000011CF-BFC7444553540000: 
'Wine Keyboard' 'Keyboard' 00000013 [Keyboard] 
DirectInput enumeration.. Pointing devices.. 
GUID=6F1D2B60-0000D5A0-000011CF-BFC7444553540000: 
'Wine Mouse' 'Mouse' 00000212 [Mouse] 
DirectInput enumeration.. Game controllers.. 
RawInput enumeration.. 
RAWINPUT not available or failed to initialize 
Windowsmouse initialization.. 
Catweasel joymouse initialization.. 
end 
Mouse * (GUID=6F1D2B60-0000D5A0-000011CF-BFC7444553540000): 
00 000 'X-Axis' (-99,0) 
04 004 'Y-Axis' (-98,0) 
08 008 'Wheel' (-97,0) 
Mouse * (GUID=6F1D2B60-0000D5A0-000011CF-BFC7444553540000): 
0C 012 'Button 0' (12,-1) 
0D 013 'Button 1' (13,-1) 
0E 014 'Button 2' (14,-1) 
0F 015 'Button 3' (15,-1) 
10 016 'Button 4' (16,-1) 
11 017 'Button 5' (17,-1) 
12 018 'Button 6' (18,-1) 
13 019 'Button 7' (19,-1) 
Keyboard * (GUID=6F1D2B61-0000D5A0-000011CF-BFC7444553540000): 
01 001 'Escape' (0,-1) 
02 002 '1' (0,-1) 
03 003 '2' (0,-1) 
04 004 '3' (0,-1) 
05 005 '4' (0,-1) 
06 006 '5' (0,-1) 
07 007 '6' (0,-1) 
08 008 '7' (0,-1) 
09 009 '8' (0,-1) 
0A 010 '9' (0,-1) 
0B 011 '0' (0,-1) 
0C 012 ''' (0,-1) 
0D 013 'igrave' (0,-1) 
0E 014 'BackSpace' (0,-1) 
0F 015 'Tab' (0,-1) 
10 016 'Q' (0,-1) 
11 017 'W' (0,-1) 
12 018 'E' (0,-1) 
13 019 'R' (0,-1) 
14 020 'T' (0,-1) 
15 021 'Y' (0,-1) 
16 022 'U' (0,-1) 
17 023 'I' (0,-1) 
18 024 'O' (0,-1) 
19 025 'P' (0,-1) 
1A 026 'egrave' (0,-1) 
1B 027 '+' (0,-1) 
1C 028 'Return' (0,-1) 
1D 029 'Control_L' (0,-1) 
1E 030 'A' (0,-1) 
1F 031 'S' (0,-1) 
20 032 'D' (0,-1) 
21 033 'F' (0,-1) 
22 034 'G' (0,-1) 
23 035 'H' (0,-1) 
24 036 'J' (0,-1) 
25 037 'K' (0,-1) 
26 038 'L' (0,-1) 
27 039 'ograve' (0,-1) 
28 040 'agrave' (0,-1) 
29 041 '\' (0,-1) 
2A 042 'Shift_L' (0,-1) 
2B 043 'ugrave' (0,-1) 
2C 044 'Z' (0,-1) 
2D 045 'X' (0,-1) 
2E 046 'C' (0,-1) 
2F 047 'V' (0,-1) 
30 048 'B' (0,-1) 
31 049 'N' (0,-1) 
32 050 'M' (0,-1) 
33 051 ',' (0,-1) 
34 052 '.' (0,-1) 
35 053 '-' (0,-1) 
36 054 'Shift_R' (0,-1) 
37 055 'KP_Multiply' (0,-1) 
38 056 'Alt_L' (0,-1) 
39 057 'space' (0,-1) 
3A 058 'Caps_Lock' (0,-1) 
3B 059 'F1' (0,-1) 
3C 060 'F2' (0,-1) 
3D 061 'F3' (0,-1) 
3E 062 'F4' (0,-1) 
3F 063 'F5' (0,-1) 
40 064 'F6' (0,-1) 
41 065 'F7' (0,-1) 
42 066 'F8' (0,-1) 
43 067 'F9' (0,-1) 
44 068 'F10' (0,-1) 
45 069 'Pause' (0,-1) 
46 070 'Scroll_Lock' (0,-1) 
47 071 'KP_Home' (0,-1) 
48 072 'KP_Up' (0,-1) 
49 073 'KP_Prior' (0,-1) 
4A 074 'KP_Subtract' (0,-1) 
4B 075 'KP_Left' (0,-1) 
4C 076 'KP_Begin' (0,-1) 
4D 077 'KP_Right' (0,-1) 
4E 078 'KP_Add' (0,-1) 
4F 079 'KP_End' (0,-1) 
50 080 'KP_Down' (0,-1) 
51 081 'KP_Next' (0,-1) 
52 082 'KP_Insert' (0,-1) 
53 083 'KP_Delete' (0,-1) 
56 086 '<' (0,-1) 
57 087 'F11' (0,-1) 
58 088 'F12' (0,-1) 
60 096 'ISO_Level3_Shift' (0,-1) 
61 097 'Super_L' (0,-1) 
62 098 'Super_R' (0,-1) 
63 099 'Menu' (0,-1) 
64 100 'ISO_Level3_Shift' (0,-1) 
65 101 '=' (0,-1) 
80 128 'XF86Music' (0,-1) 
82 130 '1' (0,-1) 
83 131 '2' (0,-1) 
84 132 '3' (0,-1) 
85 133 '4' (0,-1) 
86 134 '5' (0,-1) 
87 135 '6' (0,-1) 
88 136 '7' (0,-1) 
89 137 '8' (0,-1) 
8A 138 '9' (0,-1) 
8B 139 '0' (0,-1) 
8C 140 ''' (0,-1) 
90 144 'Q' (0,-1) 
91 145 'W' (0,-1) 
92 146 'E' (0,-1) 
93 147 'R' (0,-1) 
94 148 'T' (0,-1) 
95 149 'Y' (0,-1) 
96 150 'U' (0,-1) 
97 151 'I' (0,-1) 
98 152 'O' (0,-1) 
99 153 'P' (0,-1) 
9B 155 '+' (0,-1) 
9C 156 'KP_Enter' (0,-1) 
9D 157 'Control_R' (0,-1) 
9E 158 'A' (0,-1) 
9F 159 'S' (0,-1) 
A0 160 'D' (0,-1) 
A1 161 'F' (0,-1) 
A2 162 'G' (0,-1) 
A3 163 'H' (0,-1) 
A4 164 'J' (0,-1) 
A5 165 'K' (0,-1) 
A6 166 'L' (0,-1) 
A9 169 '\' (0,-1) 
AC 172 'Z' (0,-1) 
AD 173 'X' (0,-1) 
AE 174 'C' (0,-1) 
AF 175 'V' (0,-1) 
B0 176 'B' (0,-1) 
B1 177 'N' (0,-1) 
B2 178 'M' (0,-1) 
B3 179 ',' (0,-1) 
B4 180 '.' (0,-1) 
B5 181 'KP_Divide' (0,-1) 
B7 183 'Print' (0,-1) 
B8 184 'Mode_switch' (0,-1) 
BB 187 'F1' (0,-1) 
BC 188 'F2' (0,-1) 
BD 189 'F3' (0,-1) 
BE 190 'F4' (0,-1) 
BF 191 'F5' (0,-1) 
C0 192 'F6' (0,-1) 
C1 193 'F7' (0,-1) 
C2 194 'F8' (0,-1) 
C3 195 'F9' (0,-1) 
C4 196 'F10' (0,-1) 
C5 197 'Num_Lock' (0,-1) 
C7 199 'Home' (0,-1) 
C8 200 'Up' (0,-1) 
C9 201 'Prior' (0,-1) 
CA 202 '-' (0,-1) 
CB 203 'Left' (0,-1) 
CD 205 'Right' (0,-1) 
CE 206 '+' (0,-1) 
CF 207 'End' (0,-1) 
D0 208 'Down' (0,-1) 
D1 209 'Next' (0,-1) 
D2 210 'Insert' (0,-1) 
D3 211 'Delete' (0,-1) 
D6 214 '<' (0,-1) 
D7 215 'F11' (0,-1) 
D8 216 'F12' (0,-1) 
E5 229 '=' (0,-1) 
NATMEM: Our special area: 0x03740000-0x34740000 (784M) 
Max Z3FastRAM 512M. Total physical RAM 503M 
shmget of size 65536 (64k) for rtarea 
VirtualAlloc 00F00000 - 00F10020 10020 (64k) ok 
load config '.\Configurations\default.uae':0 
load failed 
failed to load config '.\Configurations\default.uae' 
LCD: Logitech LCD system not detected 
Entering GUI idle loop 
load config '.\Configurations\Amiga 500 di Marco.uae':0 
Log (enabled): 'C:\Programmi\WinUAE\winuaelog.txt'

[etnablog]

(sorry, too long post, I need to re-post)

...and my winuaelog.txt:

2007-05-19 00:13:49 
49-926: WinUAE 1.4.2a (2007.05.13) (NT 5.0 Service Pack 4 [1]) 32-bit 6.304 1 
(c) 1995-2001 Bernd Schmidt   - Core UAE concept and implementation. 
(c) 1998-2007 Toni Wilen      - Win32 port, core code updates. 
(c) 1996-2001 Brian King      - Win32 port, Picasso96 RTG, and GUI. 
(c) 1996-1999 Mathias Ortmann - Win32 port and bsdsocket support. 
(c) 2000-2001 Bernd Meyer     - JIT engine. 
(c) 2000-2005 Bernd Roesch    - MIDI input, many fixes. 
Press F12 to show the Settings Dialog (GUI), Alt-F4 to quit. 
End+F1 changes floppy 0, End+F2 changes floppy 1, etc. 
49-926: AF_NEW: 'c:\windows\profiles\All Users\Documenti\Amiga Files\WinUAE\' 
49-926: EXE: 'C:\Programmi\WinUAE\', DATA: 'C:\Programmi\WinUAE\' 
49-930: Entered action_replay_load() 
49-934: hrtmon installed at 00A10000 
2007-05-19 00:13:50 
50-017: Building CPU table for configuration: 68000 prefetch 24-bit 
50-074: 1890 CPU functions 
50-075: Building CPU function table, 44736 opcodes (0 1 1). CPU=68000, FPU=0. 
50-075: CPUID level=5, Family=15, Model=3, Mask=4, Vendor=GenuineIntel [0] 
50-076: JIT: Setting signal handler 
50-076: JIT: Building Compiler function table 
50-079: JIT: Supposedly 42108 compileable opcodes! 
50-103: DirectDraw GUID=NULL 
50-105: W=1024 H=768 B=24 CT=3 
50-105: using desktop depth (16 -> 24) because not using overlay or opengl mode 
50-105: ignored overlay because desktop depth == requested depth (24) 
50-609: DDRAW: Primary surface created in video-memory 
50-614: DDRAW: Secondary surface created in video-memory 
50-618: try_surface_locks() returning secondary 
50-618: set_ddraw() called, and is 720x568@24-bytes 
50-618: Window mode (bits: 24, pixbytes: 3) 
50-682: Reset at 00000000 
50-682: 00000000    2048K/4 =     512K Chip memory 
50-682: 00200000    8192K/0 =    8192K <none> 
50-682: 00A00000    2048K/0 =    2048K CIA 
50-682: 00C00000     512K/1 =     512K Slow memory 
50-682: 00C80000    1024K/0 =    1024K Custom chipset 
50-682: 00D80000     256K/0 =     256K <none> 
50-682: 00DC0000      64K/0 =      64K Battery backed up clock 
50-682: 00DD0000      64K/0 =      64K <none> 
50-682: 00DE0000     128K/0 =     128K Custom chipset 
50-684: 00E00000     512K/1 =     512K Kickstart ROM (F6290043) 
50-684: 00E80000      64K/0 =      64K Autoconfig 
50-684: 00E90000     960K/0 =     960K <none> 
50-686: 00F80000     512K/1 =     512K Kickstart ROM (F6290043) 
50-707: PAL mode, 50Hz (h=227 v=312) 
50-726: hardreset, memory cleared

winecfg: I set windows 2000
My system: Ubuntu Feisty, 512 Mb ram, ATI 9500 pro

Is it possible to see something interesting from these logs?.. :/

[mark_k]

Originally Posted by etnablog

winecfg: I set windows 2000
My system: Ubuntu Feisty, 512 Mb ram, ATI 9500 pro

Is it possible to see something interesting from these to logs?.. :/

Toni would be the one to answer that.

I do suspect the problem is graphics driver-related. You could try these things:
- Make sure you're using the latest ATI proprietary binary driver, or
- Make sure you're using the latest open-source driver for ATI cards (if that supports your card), or
- Try using a VESA driver, or
- Try using a plain unaccelerated SVGA driver.

If you can get it to work in unaccelerated SVGA (albeit really slowly), that suggests the problem is with your graphics card driver. So if I were you, I'd try that first then if you have any success work your way up.


-- M

[Toni Wilen]

Testing MM-timer resolution:
115.51ms 112.06ms 103.74ms 0.17ms 107.68ms
Testing Sleep() resolution:
103.68ms 112.22ms 111.44ms 111.99ms 107.95ms
falling back to busy-loop waiting (timer resolution > 2.5ms)

This looks very wrong. It means single wait smaller than 100ms means (for example 10ms) means 100ms delay.. Usually this is max 10-15ms, not 100ms.

Note that this may not be the cause of this problem but at least it causes 100% CPU usage, even in A500-mode.

[mark_k]

Hi,

I just tried booting from an Ubuntu 7.04 CD-ROM and installed Wine 0.9.37 (using the Ubuntu package from www.winehq.com) & WinUAE 1.4.2a.

I also got the timer-related message. (I'll double-check whether that also appears when booting from the other Linux CD; it probably will.)

This time WinUAE crashed for me as well. It crashes after opening the emulation window, before rendering any graphics (at least, the window remains all black). WinUAE writes a dump file, and in the terminal window, this text is printed by wine:

fixme:process:IsWow64Process (0xffffffff 0x340fd44) stub!
fixme:ddraw:IDirectDrawImpl_SetCooperativeLevel (0x36a4260)->(0x20032,00000008)

wine: Unhandled page fault on write access to 0x24f1ff30 at address 0x602c17 (thread 0009), starting debugger...
Unhandled exception: page fault on write access to 0x24f1ff30 in 32-bit code (0x00602c17).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
 EIP:00602c17 ESP:0340fc7c EBP:00000004 EFLAGS:00210202(   - 00      - -RI1)
 EAX:00000000 EBX:00000068 ECX:00000000 EDX:24f1ff30
 ESI:00000016 EDI:00000000
Stack dump:
0x0340fc7c:  00000238 00000000 0340fcfc 03458ab0
0x0340fc8c:  031101c8 00000001 00000000 02295000
0x0340fc9c:  00000001 0340fcfc 00000000 00000002
0x0340fcac:  02295000 00000000 0042fc40 00000fa0
0x0340fcbc:  00604256 00000000 00000001 02295000
0x0340fccc:  00000000 0340fcfc 00000000 00020032
Backtrace:
=>1 0x00602c17 in winuae (+0x202c17) (0x00000004)

Next I'll see whether just downloading and unpacking the plain wine .tgz file makes any difference. At the moment, it looks like the problem may be specific to Ubuntu (& possibly other Linux distributions too). So if you're having trouble, try the BackTrack 2.0 live CD I mentioned earlier.

-- M

[mahen]

Hi !

Personnally, I managed to get WinUAE working quite properly with Wine + Ubuntu Hardy beta.

Full screen, direct 3D, open gl, sound etc. All seem OK.

However... As soon as I hit a key, the emulation is stopped In other words, I cannot play any game (as I emulate the joystick with the keyboard).

But overall, it seems very good (fast, smooth).

Any idea ?