[MPlayer-cygwin] config problem

[Sascha Sommer]

On Thursday 02 December 2004 21:33, Radek Cervinka wrote:
> Hi,
>
> I used precompiled binary for windows MPlayer-mingw32-1.0pre5.zip and
> MPlayer-mingw32-dev-CVS-041104.zip (and on linux use mplayer too) and found
> this problems in windows version:
>
> with both version:
> > C:\mplayer>mplayer
> > MPlayer 1.0pre5-3.2.3 (C) 2000-2004 MPlayer Team
> >
> > CPU: Advanced Micro Devices Duron Spitfire 622.2 MHz (Family: 6,
> > Stepping: 0) Detected cache-line size is 64 bytes
> > CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0
> > Compiled with runtime CPU detection - WARNING - this is not optimal!
> > To get best performance, recompile MPlayer with
> > --disable-runtime-cpudetection. Reading config file
> > /usr/local/etc/mplayer/mplayer.conf: No such file or directo ry
> > Reading config file f:\/mplayer/config
>
> why mplayer try read from f:/ ?, when is installed on c:/mplayer (with
> early version did work) - see comman line.
>

Strange. And your HOME environment variable isn't set to f:\?

> > Reading f:\/mplayer/codecs.conf: Can't open 'f:\/mplayer/codecs.conf': No
> > such f
>
> again
>
> and in CVS version realtime information about progress move out (in
> pre1.0.5 stay on one line)
>
> > A:   0.1 V:   0.0 A-V:  0.094 ct:  0.004   2/  2 ??% ??% ??,?% 0 0
> > A:   0.2 V:   0.1 A-V:  0.090 ct:  0.008   3/  3 ??% ??% ??,?% 0 0
> > A:   0.2 V:   0.1 A-V:  0.058 ct:  0.013   4/  4 ??% ??% ??,?% 0 0
> > A:   0.2 V:   0.2 A-V:  0.034 ct:  0.016   5/  5 ??% ??% ??,?% 0 0
> > A:   0.2 V:   0.2 A-V:  0.020 ct:  0.018   6/  6 ??% ??% ??,?% 0 0
> > A:   0.3 V:   0.3 A-V:  0.012 ct:  0.019   7/  7 ??% ??% ??,?% 0 0
> > A:   0.3 V:   0.3 A-V:  0.005 ct:  0.020   8/  8 ??% ??% ??,?% 0 0
> > A:   0.3 V:   0.3 A-V:  0.008 ct:  0.020   9/  9 ??% ??% ??,?% 0 0
> > A:   0.4 V:   0.4 A-V:  0.000 ct:  0.020  10/ 10 ??% ??% ??,?% 0 0
>

Yes, this bug existed for a short time in cvs. Seems like it made into my 
build. I'll try to update it tomorow if I find the time. At least this 
problem is already fixed.

Sascha