Jump to content

WMP7 fails to open a AVI File using H.264 on NT 4.0


Recommended Posts

I tried to view a video i made which is a AVI File which used H.264.

 

When i tried,it opened,but it fails,giving me a error that the instruction called "0x080cee72" referenced memory at "0x0a4388f8" could not be written.

 

Is there a solution to that? Is there any codecs that could fix that?

Link to comment
Share on other sites


It depends upon which module that instruction is in. Any process viewer can tell us. I use ProcWin v1.6 (my build) or TaskInfo2000 v2.1. Dependency Walker in profiling mode will also reveal module load addresses.

Or try a different codec pack. If it works, great. If the error is different, it's probably the codec; keep trying. If the error is the same, it could be WMP7's AVI file parser or splitter; not good, the file is invalid or otherwise incompatible.

 

Link to comment
Share on other sites

8 hours ago, jumper said:

It depends upon which module that instruction is in. Any process viewer can tell us. I use ProcWin v1.6 (my build) or TaskInfo2000 v2.1. Dependency Walker in profiling mode will also reveal module load addresses.

Or try a different codec pack. If it works, great. If the error is different, it's probably the codec; keep trying. If the error is the same, it could be WMP7's AVI file parser or splitter; not good, the file is invalid or otherwise incompatible.

 

Is there a codec pack for nt 4.0?

Link to comment
Share on other sites

If you are using x64 ALPA build I have a possible solution only if you use a 32 bit player.

First try and undo changes made by the KLite Codec Pack 2.73. I think from my memory 2.73 did not include codec for H264 playback. I am not going to install it to find out though. Use Dependency Walker to profile WMP7 and find out what is going on. I am not sure that WMP7 or 7.1 is compatible with NT40 but WMP 6.4.9 should be. There is WMP9 for NT which can be found here http://www.oldversion.com/windows/windows-media-player-9-nt WMP7 here https://www.windows-media-player.com/wmplayer-7/ Any codec that is incompatible with NT40 could be of fault as it could have been registered by an installer and not manually with regsvr32. Use GSpot Codec information to try and render the file. GSpot downloaded here https://www.headbands.com/gspot/ If no Codec for h264 then you need to download DivX h264 decoder here https://www.pconlife.com/viewfileinfo/divxdech264-ax/ 8.2.026 does not need MSVCR80. Register DivxDecH264.ax using regsvr32.exe from within the command prompt or run command window. Video should be able to play if a working splitter is available. If AVI registry problem then renaming the container from .AVI to .MKV or MP4 etcetera could negate the error.

Link to comment
Share on other sites

6 hours ago, Goodmaneuver said:

If you are using x64 ALPA build I have a possible solution only if you use a 32 bit player.

First try and undo changes made by the KLite Codec Pack 2.73. I think from my memory 2.73 did not include codec for H264 playback. I am not going to install it to find out though. Use Dependency Walker to profile WMP7 and find out what is going on. I am not sure that WMP7 or 7.1 is compatible with NT40 but WMP 6.4.9 should be. There is WMP9 for NT which can be found here http://www.oldversion.com/windows/windows-media-player-9-nt WMP7 here https://www.windows-media-player.com/wmplayer-7/ Any codec that is incompatible with NT40 could be of fault as it could have been registered by an installer and not manually with regsvr32. Use GSpot Codec information to try and render the file. GSpot downloaded here https://www.headbands.com/gspot/ If no Codec for h264 then you need to download DivX h264 decoder here https://www.pconlife.com/viewfileinfo/divxdech264-ax/ 8.2.026 does not need MSVCR80. Register DivxDecH264.ax using regsvr32.exe from within the command prompt or run command window. Video should be able to play if a working splitter is available. If AVI registry problem then renaming the container from .AVI to .MKV or MP4 etcetera could negate the error.

I tried but its the same error i had

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...