Announcement

**Andreas** · 10 February 2000, 20:58

Having all kind of problems in the past with my Marvel G400,
I formated my C: partition and did a clean install with the new drivers.
At first all problems seemed to be gone.
But after 80 minutes capturing the picture freezed.
I didn't see this when I was recording, but playing the avi in PC-VCR
or MediaPlayer resulted in frame freeze. Audio is ok. just the same
picure for the rest of the film

Another point is, that after the clean install, there are 2 identical
drivers listed!

So I have to wait again for the next driver version.

Coolfish, so I don't think reinstalling everything will help you!

Andreas.

**T-rex** · 11 February 2000, 07:26

Coolfish , try to do that: (worked for me, no more double vidcap driver)

1. Install Powerdesk 5.41
2. In the control panel -> Multimedia -> Video Compression Codec ,remove (if present) RRicm dmb1
3. Edit system.ini and delete any references to dmb1
4. Exit to Dos Mode, search any rrapi*.* and vcap16*.* and delete.
5. Uninstall previous version of Videotools. (Only at this time reboot)
6. Open Virtualdub and verify, that no Video Capture device is found.
7. Install Video Tools 1.52

**nsd3** · 11 February 2000, 08:52

I'm assuming you have first ran the Matrox uninstall program.

After the PC boots, rather than proceed to install the new drivers, instead choose your graphics adapter from the Windows supplied driver list, and select the standard vga driver. Windows will complain that your card is not suitable for this driver, but go ahead and install it anyway.

Allow the PC to reboot, and then run the setup program for the new drivers, starting with the Matrox desktop drivers then the video tools drivers, with areboot after each installation.

Yous should find everything works fine. It did for me.

Regards,

Steve Donoghue

Steve.Donoghue@ncl.ac.uk

**coolfish** · 11 February 2000, 15:50

Tried the above. Didn't work. Two capture drivers, continues to get the garbage frames followed by black and white.

**T-rex** · 12 February 2000, 00:13

Coolfish, other suggestions:

1. what are date and file-size of RRICM.DLL and RRICMEXT.DLL ?

2. In the file rrunner.ini in the latest videotools there is a list of files (in the sections [OldRRfiles] and [Ocxfiles].
Uninstall the videotools, and if Powerdesk 5.41 is installed don't remove it, and reboot.

Open regedit and verify if in the section
HKEY_LOCAL_MACHINE\Software\Matrox\ have been removed the keys: RainbowRunner, rrpath, Matrox Video Tools, Vidpres.

Now, exit to dos mode and verify if all the files listed in rrunner.ini are really been removed (please search also .bak or .old versions)
If someone of these files are present, manually remove it.
At this point return to windows and install the videotools.

Test, and make us know how has gone.

**coolfish** · 12 February 2000, 11:09

Here is the info on the RRICM*.DLL files I currently have installed.

RRICM.DLL - 192,512 bytes . right-clicking reveals that it is Version 1.00 (c) 1998..

RRICMEXT.DLL - 77,824 bytes - no version info there.

I followed the above procedure. There continues to be two vidcap drivers listed in Virtual Dub. In control panel, multemedia, video compression, I double clicked RRICM DMB1 -- it says it's version 1.00.

Matrox people - it's blatant that the uninstall procedure is not correct for some people, and even all these extra efforts that we've tried here are failing to work for me. Is there anything I can do, besides formatting C (which someone even mentioned failed to work for them) or is this yet another bug ? I should mention that while capturing, I no longer have this green junk at the top of the screen where I used to have it with Vid Tools 1.51. However, I continue to get garbage frames followed by Black and White frames when capturing in desktop resolutions higher than 800x600x16bit.

coolfish.

[This message has been edited by coolfish (edited 12 February 2000).]

**T-rex** · 12 February 2000, 14:23

I hope that this is the right solution.

With Powerdesk 5.41 and Video Tools 1.52. already installed: (rricm and rricmext are the rigth versions, equal to mine)

Search if In Multimedia -> Video Compression there is a codec called Pvmjpg20 [Mjpg], and if present remove it.

If also this doesn't work I think that only Haig or Olliver can find a way to solve the problem
(If you want to be sure that they read the message I suggest you to start a new topic with their name in the subject)

**coolfish** · 12 February 2000, 22:28

The PicVideo codec? ooooookay, i'll try...

update - this removed the second capture driver in VidCap.. however..... 5 minutes into the capture, garbage frames followed by black and white when playing in Media Player. It plays back fine in PC-VCR. However, when loading it up in Ulead, it crashes with the same old RRICMEXT error as before.

[This message has been edited by coolfish (edited 13 February 2000).]

**Mark F** · 12 February 2000, 23:30

Just an idea-

You might try revoving both codex. Then do the driver uninstall reinstall dance again. That would give you a 'true' fresh start.

Hey can it hurt at this point?

Mark F.

------------------
OH NO, my retractable cup holder swallowed a CD

**Pertti** · 12 February 2000, 23:42

Coolfish,

You must have some old HD around to make a test installation of your OS, Ulead and the latest drivers, why not try it.

Cleaning the system can be done, but is not simple and not something that can be tought over the Net.

Look here for some tips in installing the OS: http://forums.murc.ws/ubb/Forum2/HTML/002847.html

Pertti

**Gandalf** · 13 February 2000, 09:03

Hi Folks
I am new here (but I am a Matrox-User cince
the Mystique 170).
I have the same trouble as coolfish
(I have g400-32mb-dh and the RR-G).

I think one of the main points is:
the bad recordings are often only visible when played back in Software mode, when played back thru hardware (ie. VCR-Remote or Media Player (it started as only one instance)) often the video shows up okay,
but playing it in Software-mode (ie MS or
MediaPlayer with PC-VCR still active, it gets worse).

Greetings
Thomas

**coolfish** · 13 February 2000, 10:07

damnit, formatting is NOT the solution to every dang problem that pops up in windows. If that was Matrox (or any other company, for that matter) solution to when their install procedures or software failed to work, I don't think they'd be in business
for very long.

The fact is, I've done what appears to any logical person everything (short of formatting) to remove any previous Matrox components. If I missed something, it's only because Matrox hasn't revealed any hidden files or registery settings that I don't know of.

As it stands, my system is a dual boot right now, and it's MUCH more difficult to install win98 as a second operating system than as a first. I don't know about you, but I don't have extra harddrives laying around.

That's it. i'm starting a new thread with Haig's and Olliver's names in it.

**Pertti** · 13 February 2000, 10:40

Coolfish,

Did I talk about formatting ? No I didn't.

You could remove your normal system disk for the time it takes to make a test installation on another HD.

In order to have a proper NLE system, you should have at least two HD:s anyway... so what's the big deal ?

Without going into details, there are lots of reasons why you are still seeing the problem that has been fixed (some having nothing to do with Matrox or their drivers).

Pertti

[This message has been edited by Pertti (edited 13 February 2000).]

**Gandalf** · 13 February 2000, 12:17

hi
quick-n-dirty way for a "second Windows"
1) copy the full install stuff to a temp-dir on HD
(this saves You trouble when windows ask you
to insert win-cd because it wants to install
cd-drivers... *_* )
2) boot to dos
3) rename c:\windows\win.com to something like win.old
4} rename c:\windows to something like
c:\winold
4b} have enough free space on C:\
5} install new Windows to c:\windows
6} rename win.old back to win.com
now you have two windows-directories, just
rename them properly, in case You want to use the other one...
7) TIP: in c:\ there is a textfile "msdos.sys", make it writeable, then
change
> BootGUI=1
to
> BootGUI=0

now windows will not start up (just like in
Win 3.11), now, before starting "win", you can rename the two c:\win*-Dirs

------------------
++++++++++++++++++++++++++++++++
k7-500, 128 MB, MSI-6167, g400-DH-32mb with RR-G,
AHA2940U2W, Terratec DMX, ...
and trouble recording Videos...
++++++++++++++++++++++++++++++++

Announcement

troubles still. :(

troubles still. :(

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment