search for: timeendperiod

...10 and lastest wine rpm from winehq Here is wine log: > fixme:user:EnumDisplayDevicesA ((nil),0,0x67f9e4,0x00000000), stub! > fixme:user:EnumDisplayDevicesA ((nil),0,0x67fa14,0x00000000), stub! > fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum > fixme:mmtime:timeEndPeriod Stub; we set our timer resolution at minimum > fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum > fixme:dsound:IDirectSoundImpl_SetCooperativeLevel level=DSSCL_PRIORITY not fully supported > fixme:sync:CreateIoCompletionPort (0xffffffff, (nil), 00000000, 00000000):...

I have an application ("The Rosetta Stone" 2.0.7a) which segfaults during the startup splash screen. According to strace() it is trying to munmap() an address (0x7a6b3000) which was never mmap()'d. I get identical behavior with Wine 20050111 and kernels 2.6.9 / 2.6.10 (I use gentoo-sources). I noticed some people had similar issues upgrading from 2.6.9 to 2.6.10.

...imes] This sound card's driver does not support direct access The (slower) DirectSound HEL mode will be used instead. fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum fixme:dsound:IDirectSoundImpl_SetCooperativeLevel level=DSSCL_PRIORITY not fully supported fixme:mmtime:timeEndPeriod Stub; we set our timer resolution at minimum On a hunch, I tried changing it to winxp and got the same as 2k. So, is there anything I can do to get this program to run?

...g ! err:ddraw:d3ddevice_unlock_update Wrong surface type for locking ! err:ddraw:d3ddevice_lock_update Wrong surface type for locking ! err:ddraw:d3ddevice_unlock_update Wrong surface type for locking ! fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum fixme:mmtime:timeEndPeriod Stub; we set our timer resolution at minimum fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum fixme:dsound:IDirectSoundImpl_SetCooperativeLevel level=DSSCL_PRIORITY not fully supported wine: Unhandled exception (thread 0014), starting debugger... WineDbg starting...

Dear all: I have found a big bug on xen concerning time virtualization. Please let me show you the whole process: 1 Phenomenon when I run a JVM based program in IE browser in my Virtual Machine, I have found clearly that time at the right bottom corner in my VM gets more slower and slower. I studied the bug deeply, and found something below. 2 Xen vmx_vmexit_handler --> ......... -->