Ferenc Wagner <[EMAIL PROTECTED]> writes:
> Scott W Gifford <[EMAIL PROTECTED]> writes:
>
> > I ported to Winelib because I had a hard time capturing
> > stdout from the Windows console program properly just
> > running the .exe under Wine.
>
> Try wineconsole instead of wine, that may
> work be
Scott W Gifford <[EMAIL PROTECTED]> writes:
> I ported to Winelib because I had a hard time capturing
> stdout from the Windows console program properly just
> running the .exe under Wine.
Try wineconsole instead of wine, that may
work better.
--
Feri.
On 1 May 2004, Scott W Gifford wrote:
> > Do you have a similar behaviour if you just run the Windows executable
> > under Wine?
>
> No, it uses a normal amount of CPU and works normally. I ported to
> Winelib because I had a hard time capturing stdout from the Windows
> console program properly
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> On 30 Apr 2004, Scott W Gifford wrote:
>
> > I'm not really sure what my next step is in figuring this out. Any
> > ideas?
>
> Do you have a similar behaviour if you just run the Windows executable
> under Wine?
No, it uses a normal amount of CP
On 30 Apr 2004, Scott W Gifford wrote:
> I'm not really sure what my next step is in figuring this out. Any
> ideas?
Do you have a similar behaviour if you just run the Windows executable
under Wine?
--
Dimi.
Hello,
I recently ported a small application from Windows using winelib. The
app uses a third-party DLL that I don't have source for (which is why
I'm using winelib instead of just writing a Unix program). It seems
to work fine, but it takes up 100% of the CPU all the time:
24916 activewv 25
