wtf

[VMFA-Blaze]

All I can say is that I havn't any problems with Star Force so far.... (LOL)

 

~S~

 

Blaze

[169th_Dredd]

If people want to be negative about LO:FC just because it has SF protection, then too bad for them. They miss out on a great title and hours of fun, that we as LO:FC users' are already having! :)

 

I have no griefs with SF. It protects my purchase as a customer. For every game obtained that's pirated. those that paid their hard earned money, lose out, in turn so does the game developer.

 

ED as a company, has every right to protect their product.

 

Heck most companies target their games now for XBOX or PS market, because PC market sales are more likely to be pirated and the company would potentially lose $$$$ instantly.

 

Do a search in google. And tell me how many people are complaining about their systems being destroyed/DVD's not working.

Then compare that to how many people possibly have the game. First up they think 'SF did it', because it has a bad rep by some. If Doom3 had SF, I'd bet all those Doom3 users that had problems when it first came out(SF non-realted or course), would most likely be pointing the finger at SF as well. Ironic.

 

Dont forget no russian users have reported any damage to hardware related from SF. So SF put up a competition to prove that SF can damage your system. You could win big $$!!

 

All in all, flame my post.. but I have no quifs with SF whatsoever.

I can understand your fustration Scotsman. I hope a solution is found for you.

 

by the way, I recall if you hold ctrl or alt- whilst lockon prepares to load, it will prompt you for activation. could be wrong.

[Pilotasso]

Its true that starforce has issues but why 30 threads full of posts of the same (nonsense) stuff?

 

I vote one should open a stickie "Starforce sux" thread. It would work like radiated flies, released them sterile in a chosen spot so that the pest doesnt spread.

[Guest EVIL-SCOTSMAN]

Ok, as I said before, I had 0 problems with starforce before, when all other peeps were saying bad stuff about it etc, never once did anything happen to me, this is the first time it has did anything weird.

 

I wouldnt of been so mad had it not been for the fact that I only had 2 keys left and that no hardware changes were made.

 

I read that SF is now upto version 3.**, when i look in device manager and see what version of SF, it is 2.**.

 

maybe if ED are gonna continue with keeping SF in there products, then maybe they should update it with the latest patch so that when you installed 1.12a then version 3.** of SF would also be installed.

 

I got no clue asto how it thought more than 50% of my hardware had changed, but there ya go.

 

Mods, I be sorry for my creative language last night, I was pissed off and should of thought about it before posting.

 

Also, I feel something similar as to what pilotasso says, make a stickie of why we hate SF, so that we can keep them all in once place, but saying that, if we had a SF stickie, no one would read it thus it would defeat the purpose...

 

but yea, main thing is, last night i was pissed off, today its all good, but surely there must be a better way of security, even if they had Steam like security, so when you install you games you make an account and only that account will make the game work, but that would involve ED having a database/server running which would involve even more costs and they probably wouldnt do it.

 

the main thing is, the game is re-activated and it works, but it confuses me the logic thats coded into the program ?

[GGTharos]

Do you have other SF games? Maybe another SF game installed an older driver?

[Guest EVIL-SCOTSMAN]

neg, only games i have installed atm, are bf2 with sf addon (special forces and not starforce addon :p) cod2 and farcry and the obligatory slomac.

[169th_Dredd]

the main thing is, the game is re-activated and it works, but it confuses me the logic thats coded into the program ?

 

It just worked all of a sudden after all those re-activations?

[Guest EVIL-SCOTSMAN]

no, i had to use up another key.

 

so in other words, i re-activated it, i still dont know why it didnt accept the last key which was only 3 weeks old ? with the exact same hardware except new widescreen monitor.

 

i am at a lose asto why it didnt like the old key, but there ya go, not much can be done about it, atleast i had 2 keys, i would of been even more pissed had I not had any keys left.

 

but the situation is over and here's hopeing it never happens again.

 

I still think shutting off the firewire port , parallel port and serial port in my bios did it, as when i shut them off, all my hardware acquired new irq's.

 

If that is the case, then SF seriously needs to be fixed in order to take that into account, I know from ages ago when I flashed mobo bios that I need to re-activate as SF+ED said so, but this irq thing is new to me.

 

but the main thing is, i can get back to flying :p

[169th_Crusty]

...I still think shutting off the firewire port , parallel port and serial port in my bios did it, as when i shut them off, all my hardware acquired new irq's...

 

 

I didn`t have time to read the entire thread, perhaps you explained it already.

After shutting off these ports, the blue screens stopped?

 

When I overclocked my 4400+ (using AI in bios, initially) to the max.

allowed by AI (10% :/) I would occasionally get a blue screen with

a message "IRQL number not less or equal". When I backed down to 8%

it stopped !!!? I have no idea if that was the reason why it stopped but

I never got this BSOD again. I didn`t do anything else!

BTW, what does "L" in IRQL stand for?

[Guest EVIL-SCOTSMAN]

Yes the bluescreens stopped due to the fact that they were now using an irq to themselves and not sharing it with anything else.

 

the overclocking had nothing to do with your irq not less or equal error.

 

the reason you get that error is because the motherboard has more features and pci slots etc than it can possibly handle smoothly.

It could be, that when you overclocked the info wasnt getting to the cpu quick enough due to the shared IRQ's, thus giving you that error and when you didnt OC the irq wasnt been clogged up with more info than usual thus not giving you the error, but if you get the error then chances are its cause of shared irq's more than because of OCin. So the chances are if that specific irq gets clogged up again due to anything then you will get that error again, unless you have changed irqs or let the bios sort them out auto which might change the irq's of certain hardware making them unshared.

 

 

I dont know what the L is for, maybe its the Less part, maybe there is an IRQE error aswell, i dunno.

 

but to get things running without having shared IRQ's, I turned off everything in my bios that I dont need, like serial, parallel, firewire, I kept the nvraid, and the other raid one, I turned off onboard sound etc etc.

 

basically, its just the nvraid and the network stuff thats enabled on that page.

 

It helps to keep things running smooth on mobo's that have a load of features but just cannot handle them all turned on at the same time with really fast hardware.

 

I would suggest turning the serial and parallel ports off unless you use them which in this day and age its very doubtful unles you have old hardware or some home made hardware. as turning them 2 off will free up 2 irq's, and you dont get alot of irq's 20 odd for your whole pc, and everything has to go threw them.

 

with fast video cards, you dont want a shared irq with them, you want your video card to have its own irq, same with your soundcard if possible, the soundcard doesnt really matter as much as the vid card.

[Greenies]

Hey Evil, do you know what I would do if I were you? I would write an email to ED and ask for more activation keys right now, so that you have your keys ready the next time you need to reinstall. Then you won't have to wait for 3 weeks for the new keys to arrive in your inbox. Just my two cents :)

[169th_Crusty]

Thanks for the advice Evil, I`ll try that.

[StrikeMax]

Crusty

 

interrupt request Level (IRQL)

 

As I understand, The BSOD err "IRQL number is not less or Equal" is due to 2 major Causes:

1- Incompatible Driver (usually unsigned)

2- Faulty Ram ( a-physical Ram chip, or b-corrupted Paging file)

 

Now ,knowing that, imagine how tedious isolating the real cause is.

[MonnieRock]

Whew, Glad I got the cd-rom version. Do not think I could take all of those headaches just to play a game.

 

I often wonder what people do that are not good with computers. I mean, not everyone is into computers and all the little quirks like we are here. Some people, say a pilot even, would like to just install the game and go not edit this config file, change this setting, turn off force feedback, save activation keys, etc...

 

Dual Core Poll Please Vote