Announcement

**Peter B** · 15 October 2001, 14:07

Well I’ve tried the following with no success:

Moved the PCI cards to different slots,
Updated the Marvel BIOS from 1.12 to 2.08
Tried Powerdesk 5.34
Remove VIA AGP drivers

I did manage to recreate the problems before installing VT204 so it must be a problem with the marvel drivers and the motherboard. Perhaps disabling or enabling something in the Award BIOS?

I also put the 4GB drive back in the carriage and it insists on booting to that faulty w2k OS from a previous attempt?

The Marvel works fine in win98, I have tried capturing etc and it works well in both slots I have had it in and with the BIOS update. It still seems to be something with w2k. Perhaps a different order of driver and service pack installations? Any suggestions would be welcome, a best guess would be appreciated!

**Frank Marshall** · 16 October 2001, 09:05

Hi Peter,

The G200 has serious issues under W2K. The Sound Blaster is problematic for many editors here as well.

Recommend you try the search function to get clued up but you'll find the G200 is best with Win98SE. SB will be okay if you stick with h'ware MJPEG compression otherwise it could get in the way.

Hope this helps.

**Peter B** · 16 October 2001, 18:03

Thanks for your thoughts, and the tip about SB, I was going to try YUY2 capture and will now be aware of the possible issues. Overall I am very happy with MJPEG compression from the G200, it's win98 that is more of a problem!

I should say though that until a few months ago, my PIII was using the G200 happily with w2k, with video capture only in win98, but was very stable for 2D and 3D in w2k. I have only had problems with this new processor and motherboard, and the disply is unstable before installing any video tool drivers!

**mynx** · 16 October 2001, 19:48

Try using Via drivers 4.34. Make sure the jumpers for master and slave are set properly on the hard drives. If they are both set to master they will seem okay in the post, but windows will be confused.

384 MB RAM (256mb/133/slot 1, 128mb/133/slot 2, 128mb/100/slot 3

**Peter B** · 24 October 2001, 15:06

Yes your right, that adds up to 512mb RAM, the last 128mb/100 is in another machine.

I think I have solved most of the problems.

The HDD issue was caused by a user error (surprise, surprise), I inadvertently set the boot sequence to HDD1 instead of HDD0 during one of the many changes when booting from a CD and changing back etc.

As far as the graphics card goes, I think I have stumbled on the problem. I had a AGP card in this Mobo (Soltek 75MAV) originally (and it disables the on board graphic card automatically when the AGP slot is used). After giving up on w2k and installing WinMe I had some problems with installing a scanner driver and noticed an extra VGA card and Sound Card in the device manager listed as not functioning.

I disabled the sound card in the BIOS but windows still sees it? I can't see where the VGA card can be disabled so have just disabled it in the device manager. I did try to install the drivers and attach another monitor, but it didn't work. I know the marvel must be the main boot graphics card to capture properly and the on-board probably wants to be as well.

Now if I can only work out how to disabled it... as WinMe had become unstable as well! Back to my retailer I think.

Thanks for the advice.

**Phil Pugh** · 25 October 2001, 00:43

Hope they were empty Peter !

Put 17GB back into Athlon, boot into win 98 installed on 40GB HD and test with Norton Utilities disk software, no errors. Boot into DOS run FDISK, find two non-dos partitions on 17GB drive before 17GB partition of ridiculous size? Delete these partitions.

I hope these didn't have useful stuff in - like system maintainance software. Some system manufacturers put a load of diagnostic stuff into hidden partitions.

**Peter B** · 25 October 2001, 12:25

This was a drive I was using before, not a new one, so I had already fromated it a couple of times. Orginally it was my video drive a year or so ago when 17Gb used to be quite a big drive and ata 66 was the fastest. Plus the partions where not there before. I assume they where created during some of the many crashes.

I am taking it back today to my supplier and will probabaly swap the Mobo for something without built in VGA or sound, or at least the VGA. They are a pretty accomdating lot so I will see what they suggest.

**Phil Pugh** · 26 October 2001, 00:44

It's unlikely that the partitions were created by crashes etc - it takes quite a bit of deliberate effort to create partitions. They may have been part of the disk's own management process - to keep track of bad block replacements etc.

**Peter B** · 29 October 2001, 15:40

I think I have identified the cause of my problems as the monitor! After changing the Mobo to an Asus A7V-E and experiencing the same problems.

After installing any Matrox Powerdesk software problems occur. The same selection options do not appear to be available for monitors in w2k (as they are in win98) so I have settled for capture in win98se and editing with MJPEG software codec in w2k (playback works but I haven't tried much else yet).

W2k seems to have satisfactory drivers for the G200, it recognises it and allows me to change resolution and refresh rates etc which is all I need as I am not playing games or anything, (it won’t allow install of VCR though) so I think I have a working solution.

The hard drive seems fine thanks Phil, the partitions where not there in Fdisk before hand so I don't know how I managed that one?

Thanks for all the suggestions and tips.

Announcement

Help, I'm drowning...

Help, I'm drowning...

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment