search for: jacklaunch

wine: Unhandled page fault on read access to 0x409ffd80 at address 0x4000ba7c (thread 0009), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 32") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger This happens on everything I try run. Note: Still a problem with latest upgrade. It may have more sideeffects than

...ral settings, > including desktop mode, and tried several patches with no luck. > > I have tried this with wine-20010731 and Codeweavers Wine 20010626-4. I > use Red Hat 7.1. > > I am including the result of "wine --winver win95 --debugmsg > +key,+keyboard /mnt/cdrom/JackLaunch.exe>& key.log" Excellent problem report -- but please do NOT post megabyte-sized log files! When they get that big, 1) compress them, and if possible, 2) put them up on a ftp or web server and post the URL instead of the actual file. Many people won't be able to read that message...

Installing alsa and jack libraries places devices for these in the winecfg menus. If I choose jack, what I would expect is that the wine instance would init jack clients for audio in and out and midi in and out (not really jack but jack can connect these as well). The jack out clients might be connected to the default alsa device, etc. This is normal for jack aware applications. I do not see