MM2 Playback Issue...

I successfully captured/created/edited/produced/burned a
10 minute movie to CD using MM2, but the PC locks up
(randomly) during playback... so I tried running it on my
wife's (2 year older) PC, and it runs perfectly
everytime !!!

After reviewing most of PapaJohn's debug stuff I'm
thinking I might have a codec problem, since both PC's
have the same set of codec files in the same order --
EXCEPT that her PC has an additional one, 6th from the
top of the list (the last one below):

iccvid.dll
Indeo video 5.10
ir32_32.dll
ir41_32.ax
iyuv_32.dll
LEAD MCMP/MJPEG codec (VFW)

Is there reason to believe that the "(VFW)" codec file
might be the difference here ?

If so, how do obtain/install such a file ?

Harry

I should have profiled the two PC's. The one having the
problem is:

2.6GHz P-4; 512MB RAM; 120MB SATA HD; HP cd/dvd300i burner

the "good" one is:

1.3GHz P-4; 512MB RAM; 120MB SATA HD; HP cd burner

Also, the "good" one has the faster FSD RAM (800MHz) vs
the "bad" one's 400MHz... not sure if this matters.
Finally, all drive channels are set to "DMA if available".

Harry

>-----Original Message-----
>I successfully captured/created/edited/produced/burned a
>10 minute movie to CD using MM2, but the PC locks up
>(randomly) during playback... so I tried running it on
my
>wife's (2 year older) PC, and it runs perfectly
>everytime !!!
>
>After reviewing most of PapaJohn's debug stuff I'm
>thinking I might have a codec problem, since both PC's
>have the same set of codec files in the same order --
>EXCEPT that her PC has an additional one, 6th from the
>top of the list (the last one below):
>
>iccvid.dll
>Indeo video 5.10
>ir32_32.dll
>ir41_32.ax
>iyuv_32.dll
>LEAD MCMP/MJPEG codec (VFW)
>
>Is there reason to believe that the "(VFW)" codec file
>might be the difference here ?
>
>If so, how do obtain/install such a file ?
>
>Harry
>.
>

Harry,

Are you playing the movie file from the CD on both, or did you copy it to
the hard drive and are playing it there? If it's playing from the CD, you
might try it on the hard drives.

PapaJohn

"Harry" <anonymous@discussions.microsoft.com> wrote in message
news:907301c40858$b99747a0$a601280a@phx.gbl...
> I should have profiled the two PC's. The one having the
> problem is:
>
> 2.6GHz P-4; 512MB RAM; 120MB SATA HD; HP cd/dvd300i burner
>
> the "good" one is:
>
> 1.3GHz P-4; 512MB RAM; 120MB SATA HD; HP cd burner
>
> Also, the "good" one has the faster FSD RAM (800MHz) vs
> the "bad" one's 400MHz... not sure if this matters.
> Finally, all drive channels are set to "DMA if available".
>
> Harry

PJ

Yes -- from the CD itself. I'll try it from the HD and
let you know... so, I take it that the "VFW" codec did
not look suspicious ?

Harry
>-----Original Message-----
>Harry,
>
>Are you playing the movie file from the CD on both, or
did you copy it to
>the hard drive and are playing it there? If it's playing
from the CD, you
>might try it on the hard drives.
>
>PapaJohn
>
>"Harry" <anonymous@discussions.microsoft.com> wrote in
message
>news:907301c40858$b99747a0$a601280a@phx.gbl...
>> I should have profiled the two PC's. The one having
the
>> problem is:
>>
>> 2.6GHz P-4; 512MB RAM; 120MB SATA HD; HP cd/dvd300i
burner
>>
>> the "good" one is:
>>
>> 1.3GHz P-4; 512MB RAM; 120MB SATA HD; HP cd burner
>>
>> Also, the "good" one has the faster FSD RAM (800MHz) vs
>> the "bad" one's 400MHz... not sure if this matters.
>> Finally, all drive channels are set to "DMA if
available".
>>
>> Harry
>
>
>.
>

PJ

I tried it from the HD and got the same result -- only
quicker (???)

If you don't think the "missing" codec file could be an
issue, do you think that the "accelerator" bug might be
biting me ?

The graphics card on the "bad" PC is an ATI 7000/64MB and
the one on the "Good" PC is an nVidia TNT Pro/32MB.

Harry

>-----Original Message-----
>Harry,
>
>Are you playing the movie file from the CD on both, or
did you copy it to
>the hard drive and are playing it there? If it's playing
from the CD, you
>might try it on the hard drives.
>
>PapaJohn
>
>"Harry" <anonymous@discussions.microsoft.com> wrote in
message
>news:907301c40858$b99747a0$a601280a@phx.gbl...
>> I should have profiled the two PC's. The one having
the
>> problem is:
>>
>> 2.6GHz P-4; 512MB RAM; 120MB SATA HD; HP cd/dvd300i
burner
>>
>> the "good" one is:
>>
>> 1.3GHz P-4; 512MB RAM; 120MB SATA HD; HP cd burner
>>
>> Also, the "good" one has the faster FSD RAM (800MHz) vs
>> the "bad" one's 400MHz... not sure if this matters.
>> Finally, all drive channels are set to "DMA if
available".
>>
>> Harry
>
>
>.
>

It can't hurt to add a codec and see if it helps, but I thought getting a
bit more info about the file you were having problems with would help,
before concluding or changing anything.... what are the properties of the
WMV file?

PapaJohn


"Harry" <anonymous@discussions.microsoft.com> wrote in message
news:bd8101c4085c$7257b2e0$a301280a@phx.gbl...
> PJ
>
> Yes -- from the CD itself. I'll try it from the HD and
> let you know... so, I take it that the "VFW" codec did
> not look suspicious ?
>
> Harry

PJ

Aaaaa-pparently ("he sez"), the problem vanished when I
followed up with the advice on your website re:
the "accelerator" setting -- set that puppy at "3" (was
on "6") and everything seems to work just fine.

Harry

ps: screw the "PJ bashers", keep up the good work

>-----Original Message-----
>It can't hurt to add a codec and see if it helps, but I
thought getting a
>bit more info about the file you were having problems
with would help,
>before concluding or changing anything.... what are the
properties of the
>WMV file?
>
>PapaJohn
>
>
>"Harry" <anonymous@discussions.microsoft.com> wrote in
message
>news:bd8101c4085c$7257b2e0$a301280a@phx.gbl...
>> PJ
>>
>> Yes -- from the CD itself. I'll try it from the HD and
>> let you know... so, I take it that the "VFW" codec did
>> not look suspicious ?
>>
>> Harry
>
>
>.
>

So maybe your Direct X version is the thing to zero in on for now, as
upgrading it let me turn the acceleration back up to full from 3 when I had
the problem with my older desktop.

Just set a restore point first if you upgrade it.

PapaJohn

"Harry" <anonymous@discussions.microsoft.com> wrote in message
news:916301c40868$2cf80810$a601280a@phx.gbl...
> PJ
>
> Aaaaa-pparently ("he sez"), the problem vanished when I
> followed up with the advice on your website re:
> the "accelerator" setting -- set that puppy at "3" (was
> on "6") and everything seems to work just fine.
>
> Harry

PJ

I just did a Microsoft Update check and it did not
recommend any DirectX updates -- is there a quick way to
tell what I do have for DirectX at this point, since the
download looks like it could be huge ???

Harry

>-----Original Message-----
>So maybe your Direct X version is the thing to zero in
on for now, as
>upgrading it let me turn the acceleration back up to
full from 3 when I had
>the problem with my older desktop.
>
>Just set a restore point first if you upgrade it.
>
>PapaJohn
>
>"Harry" <anonymous@discussions.microsoft.com> wrote in
message
>news:916301c40868$2cf80810$a601280a@phx.gbl...
>> PJ
>>
>> Aaaaa-pparently ("he sez"), the problem vanished when I
>> followed up with the advice on your website re:
>> the "accelerator" setting -- set that puppy at "3" (was
>> on "6") and everything seems to work just fine.
>>
>> Harry
>
>
>.
>

Harry,

Run Start > type in dxdiag and press enter

That'll start the diagnostic tool that's in Windows XP.

The current version of Direct X is on the first page (I'm looking at DirectX
9.0b (4.09.0000.0902) now, on the desktop that I had a long-standing issue
with. The various tests will also help you assess your system.

You could run your system a bit the way it is and go back later to do the
update.... but the test and version check will help you know how your system
is working.


PapaJohn


"Harry" <anonymous@discussions.microsoft.com> wrote in message
news:92ba01c4087b$868acee0$a601280a@phx.gbl...
> PJ
>
> I just did a Microsoft Update check and it did not
> recommend any DirectX updates -- is there a quick way to
> tell what I do have for DirectX at this point, since the
> download looks like it could be huge ???
>
> Harry