Problems Installing Drivers in W2K

[Zampa]

OK... So I tried that -
flush the dllcache, do all the regedit stuff, delete mga*.*, g200*.*,reinstall PD in safe mode
reboot
now at this point back in safe mode again
now vt is all in cabs so you can't MANUALLY do anything with it (winzip won't allow you to open the cabs) and it tells you that it doesn't detect powerdesk being installed and disallows installation.
so I go back to normal mode and try installing - still says no PD installed...
so i try reinstalling PD in normal mode - goes fine
then tried reinstalling the vidtools again - STILL says no PD installed....
what gives???
This is a headache and a half...
I sure hope these beta drivers get finalized and fixed soon!

-Zampa

[Walrus]

Zampa: Only manually copy over the power desk files. (and this is only if after installing the files, the driver details reports you are still running the old drivers) Actually, running the update driver and poining it to the directory with the new power desk files, in the hardware manager appears like it may get around this problem. I had to reload W2K again, and I was able to properly install the Power Desk by using that method instead of the long dllcache, manual copy method, and it seems to work. (it seems to work better than running Powerdesk's setup.exe) Once you are certain that you have the correct G200 drivers loaded, then run the Video Tools setup. It should install "properly" then. (though be sure you do not have any MJPEG codecs already installed or it won't install the dmb1 codec correctly) That said, I am now getting random freezes on my system, and the system temp is quite low. I'm pretty certain my problem is related to these drivers as it's the only new factor (well that and beta drivers for my tape drive... but I've had these lockups before the beta tape drivers and after the new Marvel drivers.. so I'll guess this is related to these beta W2K drivers) Of course, this is a beta, so problems are to be expected.

[Technoid]

This problem is realy strange!

W2K should let you do any thing you want as long as you are loged in as administrator!

------------------
INTEL PIII550 MSI 6163
G400Mill 32MB SGRAM + RRG
SBlive
256 MB RAM CAS2
43GB HDD Space!(Actual 40GB) (13+30 Quantum drives)
Pioneer 104S DVD 10x CD 40x SLOT IN
SONY CRX100E 4/2/24 CDRW

[Walrus]

Technoid:
Not really... Windows 2000's architecture is such that it does its best (even in the Administrator account) to make sure you never delete certain files or do some things that it thinks could be damaging. (for instance it really won't let you delete certain files under system32, it copies them away and back instantly without you being able to stop it) In the case of the problems installing the new Power Desk, I think that's a bug in the beta setup.exe included with Powerdesk that isn't properly forcing W2K to take the new drivers. That said, there are some real flaws W2K's attempts to make installing drivers "idiot proof"

[dgcom]

Dealing with dllcache is easy - just delete/rename file in dllcache folder first and then do the same with the file in system32 folder. Press cancel when WFP dialog pops up.

I been able to replace protected files in w2k without any problem.

You may have problems with deleting files, if they are open. In this case, rename it first, put new file in place and reboot. You'll be able to delete renamed file then.

As far as an original problem goes, there may be a different PCI vendor ID, which is not in the driver's inf file. It will refuse to update in this case.

DGCom

[Walrus]

dgcom: I fixed the problem already through other means, but THANK YOU for posting that information about dllcache. I run into problems all the time with clients' computers, and I'm sure I'll need to deal with dllcache again.

[Zampa]

Well I can rule out my memory going bad because everything runs great in win98... I can actually keep 98se running straight for 3 days with no lockups w/o rebooting... BUT there are progs that I need to run in Win2k that keeps me trying to get it working!

Yeah I turned off the check for "Automatically reboot upon errors" in Startup and Recovery and that seemed to stop total rebooting but not all the time... still have yet to see a BSOD fault dump in Win2k... always a freeze like you said...

I have the latest beta and I tried everything you said...

I think that it has to be the drivers... they are the only thing that seem to cause the problems... One guy told me his sblive caused all win2k problems but I don't believe it...

I just hope that Matrox gets cracking hard on getting stable at least vidtools in Win2k cuz it would be nice to use win2k more than 98se... but without stability, why would anyone use Win2k??

-Zampa


[This message has been edited by Zampa (edited 25 May 2000).]

[Rick6612]

Hi,

I don't know if anyone is still interested, but I finally figured out what my problem was. It seems my old motherboard was somehow incompatible with Windows 2000.

W2K never gave me any indication that it didn't like my motherboard. The only thing I knew was wrong was just that any time I did ANYTHING in W2K (install drivers, change settings, even delete files), what ever changes I made would be lost after rebooting. It almost seemed like any changes I made were only getting written to the disk cache in RAM, and never actually getting written to the hard drive itself.

Anyway, I put in a new motherboard recently (ASUS P3B-F). I decided to try booting up W2K (the same installation on the same disk partition) with the new motherboard, and now everything is normal!

Pretty weird, eh?

Rick

------------------
http://www.Hogans-Systems.com

[KRSESQ]

Rick6612:
Just out of curiosity, what was your old mobo?

I was having probs installing PD 6.04 in win 98. It wouldn't detect my Marvel G200. I tried copying and pasting the files from my PD 5.41 folder and clicking No for overwrite. PD 6.04 would then install and work okay, but Video Tools 1.52e (the most stable version I've found so far) insisted "no Powerdesk software found" and refused to install.

So much for "certified drivers!"

Ah, well. No biggie. It's back to PD 5.41 for me. At least my system no longer suffers frequent random lockups!

Kevin

[Rick6612]

Hi Kevin,

The old board was a BCM QS440BX - the older 1 Mb BIOS version of the QS440BX.

I see on their web site that they have BIOS updates for the new 2 Mb BIOS version of the QS440BX for W2K. So, presumably, the newer version of the board should work with W2K.

Rick

------------------
http://www.Hogans-Systems.com