svl7

Remove the battery and AC, power drain, press and hold FN, plug AC back in, press power (still hold FN) wait. That might do the trick.

... and M15x

Excellent, what system are you using it in svl7? sli then (you said cards)?

980m and 970m, AW17 and M15x

svl7 could you upload your 344.75 drivers and share them with us?

Sure, see attached files. Will only work for AW17 and M15x though. I don't know the AW18 and other device ideas by heart...

nvcvi.zip

Finally got the cards, time for some testing.

[quote=mitchellpeixer;114421

I've got a SLI 880M kit but the cards are not found by the system.

What kind of error do you get respectively where / when do you notice that there's a problem?

@godfafa: Dude, you never replied to the email regarding the vbios mod I sent you...

I wonder how SVL7 is getting on..

Back home and waiting for a card. Hope I get one by the end of the next week. Will see.

What's your vbios version?

You need to modify the .inf file to allow installation of the driver. This thread contains a guide: http://forum.techinferno.com/nvidia/5249-%5Bguide%5D-modding-nvidia-oem-inf-files.html

A slow windows installation does not hint at infected firmware, neither does a slow boot time.

I don't know why, but for some reason you seem to be convinced that your system is infected by one of the most complex malware type that could possibly exist, even though other explanations exist and are much more likely. Before I can continue discussing about your system being infected by such kind of malware you need to deliver some proof, else it's all a big waste of time. Just stating or assuming things as one likes is simply not constructive, keyword here is also Russell's teapot.

AW17 3d, will be back home at the end of the week.

While persistent BIOS malware is technically possible it is for many reasons highly unlikely that is what happened to your system.(E.g. the attack would have to be written especially for your hardware).

A slow boot is much more likely to be caus d by hardware failure, or messed up firmware settings, e.g. if you previously used an UEFI installation combined with optimized fast boot settings vs a legacy installation now, a 3 - 10x longer boot time would be perfectly normal.

What's your hardware setup at the moment?

my vBios version is:

80.06.54.00.1F

It won't let me upload the bios.rom file

Put it in a zip, click on "go advanced" when replying and add it as attachment.

I'll look into that when I'm done with military service and worked up on the stuff I missed during that time. One more week and then I should be back only more often.

Which BIOS version was installed on the systems?

Just tell me what the current status is, I don't have time to go all the posts of a random thread. Currently have to do some military service and I already need enough time to catch up on other things that have been going on during the past weeks.

There's no Dell vbios. Anyway, I don't have a card yet, but if anyone is willing to flash some stuff, let me know. Can't guarantee functionality though since I can't test anything myself atm.

any word out about 970m in alienware machines?

You can safely assume that it behaves exactly the same as the 980m when it comes to compatibility.

There are reasons for me to think there is a primary/secondary vbios.

Believe as much as you want, several people here already told you that this is not the case.

I was communicating with one of the Clevo resellers today (who is also an Alienware reseller) that is offering 980M upgrades for Alienware systems. Apparently, there is something with the Clevo vBIOS that ONLY works with Optimus enabled when install in a non-Clevo machine.

Clevo resellers (especially eurocom) are talking a lot of bull when it comes to things like this. I don't believe a single word anymore I hear from eurocom. They're also the company that published a press release a while ago stating full MXM compatibility on their machines, which is not the case AT ALL.

Resellers don't get customized vbios or bios files, all they get is what Clevo provides them, they're just resellers and not manufacturers.

Haven't had a lot of time recently, but I was told that the 980m works perfectly fine in the AW17, M17x R3 and R4 but apparently not in the M18x R1. Don't take my word for it though, but I have no reason to mistrust the guy who told me this.

Might know more from first-hand experience next weekend.

You could do the same with the Windows tool from within Windows if you prefer that...

You need version 9.x or later of fpt, use the link in the first post, that should be the proper one.

Commands stay the same for the new versions. So use whatever works. The latest definitely should work perfectly fine.

On screenhots you can see what error i have when im trying to backup bios, also what hardware/os im using and what bios i have now.

Can't see any screenshots...

Details? Is there an error message?

Thread necro - closed.

So, what's the error?