search for: lalev

A) DON'T EVER RUN WINE AS ROOT! B) What version of wine? C) Remove ~/.wine (and probably /root/.wine) and try again. If you still have problems, post back. -Austin On 8/6/07, lalev@uni-svishtov.bg < lalev@uni-svishtov.bg> wrote: Hi everyone, This happens every time I start winedbg, no matter what program I want to debug. It's ubuntu feisty fawn and I have built wine from sources. user@machine:~$ winedbg "C:\Program Files\Diablo II\Diablo II.exe" WineDbg...

Greetings, I have Xen installation with all domains (dom0+domU) being Debian Lenny. I''d like to pass my usb printer to one of those domU domains. I couldn''t make usb passthrough to work, so I decided that I will pass the whole usb controller to the domU. It didn''t worked either. I have read tons of internet howtos only to find the solutions proposed don''t

server:~# dmesg|grep pciback [ 0.000000] Kernel command line: root=/dev/hda1 ro console=tty0 pciback.permissive pciback.hide=(00:1d.00)(00:1d.01)(00:1d.07) [ 0.000000] Unknown boot option `pciback.permissive'': ignoring [ 1.210945] pciback 0000:00:1d.0: seizing device [ 1.211082] pciback 0000:00:1d.1: seizing device [ 1.211215] pciback 0000:00:1d.7: seizing device [

Hi everyone, This happens every time I start winedbg, no matter what program I want to debug. It's ubuntu feisty fawn and I have built wine from sources. user@machine:~$ winedbg "C:\Program Files\Diablo II\Diablo II.exe" WineDbg starting on pid 000a wine: Unhandled page fault on read access to 0x00000000 at address 0xb7d5cc23 (thread 0009), starting debugger... Unhandled exception: