MGAtweak1.20 + g200 + win2k

[neil2000]

i'm running pd 5.14
i setup as per instructions,
but when i run it i get:
Faliure:StartService(0x05)

Can't get a handle to \\.\HWACC95.VXD

Cannot load VXD,error 00000002.

this util runs sweet on another 2k box with
g400 and pd 6.11.030

does anyone have any suggestions?

cheers

[kjliew]

Check if you have HWACCNT.SYS and HWACC.DLL in \WinNT\system32\.

Have you read the user guide (MGATWEAK.PDF)on installation procedures?? If not, read it first.

[neil2000]

thanks for the rapid response.

the app was setup just like the pdf says.

i have emailed you with further details and log files from regmon and filemon.

they may contain a clue.

cheers,

neil.

[kjliew]

Do not e-mail me. I am unable to check any of my personal e-mail account, including that of matroxusers.com.

Let's communicate through the forum. If you absolutely think you should e-mail me, then use kjliew@hotmail.com. However, my Hotmail account is heavily spammed. I am afraid I may lose you mail.

Have you made sure there is no multiple copies of HWACC*.*?? If you have used previous version of MGATweak, have you deleted all of them?? Do you have administrator privilege??

[neil2000]

whoops!!
i only sent the email because of the logs i generated - i will edit and post on here.
here is the body of the email:

"greets Liew,

thanks for the rapid response in the forum.

mgatweak1.2 is setup exactly as instructed in the pdf.

here are the errors when i run it:
Faliure:StartService(0x05)

Can't get a handle to \\.\HWACC95.VXD

Cannot load VXD,error 00000002.

the files MGATweak.exe, HWACCNT.SYS, HWACC.DLL and HWACC95.VXD
have system, everyone and administrator full privileges.

system info:
win2000(2195) sp1
pd 5.14
g200
abit bx6
pII 450
sblive 1024
realtek 8139 network card

it's a very fresh install too.

i'm not running any debug software, but i got these logs from RegMon
and FileMon - see attachments

the win2000 event log said:
the HWACC95.VXD service failed to start due to the following error:
access is denied.

installing the latest driver on top of the microsoft ones was a bit tricky-
but q3 runs pretty damn well now.

unfortunatley this machine has gotta go head to head with a t'bird 1k
and a gforceII ---basically i need all the help i can get!

thanks for taking the time to help me out.

cheers,
neil."

the logs are prob too big for the forum so here's a link to them
www.dvmachine.co.uk/mgatweak.html

thanks again,

neil.

[orangejulius]

Regmon's a great tool, but you could of made it even easier. Try EasyClean Logger.

[kjliew]

Where do you put MGATweak.EXE, HWACC.DLL and HWACCNT.SYS?? Show me their pathnames. Also show me your PATH= enviroment variables.

HWACC95.VxD is not used in NT/2K. You can delete it if you're with full Nt/2K system. Do you log on as administrator?

[neil2000]

Nice one!
My path was already c:\winnt\system32 etc.
I was logged on as administrator.

Deleting hwacc95.vxd sorted it out.

Many thanks.

i was using powerstrip to overclock it the meantime- that let me take the memory timing fron 113(84.9graphic clock) to 154.8(116.1) - i didn't push any further.

i'm looking forward to using your little beauty now.

you're a star!

[kjliew]

I am sorry that I don't get you right.

Have you been able to run MGATweak now in Win2k system after deleting HWACC95.VxD??

If that's the solution, it is wierd. I also have an Win2k (non-SP1) machine running at home, and it's running fine. HWACC.DLL should be able to detect which Window it's runnning now, and open the correct device driver.

Perhaps the StartService API accidentally open the real HWACC95.VxD, if it exists in the search path, rather than the device name "HWACC95.VXD" in HWACCNT.SYS. Hmm... got to check this out when I get back to home.

Anyway, let me know.

[neil2000]

Yes, it is working now.

I'm pretty sure it was deleting the hwacc95.vxd that fixed it.

HOWEVER - when I put hwacc95.vxd back in the winnt\system32 directory it still worked.

So, unfortunately, that confuses the issue further.

I will investigate a little - before I deleted it originally I found an entry in the registry to a network drive with a MGATweak file on it. When I removed that it still did not work, however, it may have been a combination of the two that caused the problem.

Very strange.

But it is definitely working fine now - I can take the PLL to 250 - which definitely improves Q3.

Cheers.

[QFoam]

FYI:

The first time I ran MGATweak, it added hwacc95.vdx as a driver in my registry. Once I deleted the both the file and the registry entry *and* reboot, did it work.