Windows 7 Activitation Keep Failing

You need to login to view this posts content.

 

@ Alfa
One tiny issue with that. The installation of the loader from whats been said appears fine, and while the other loader installers use an older loader version of the GRLDR I'm using version 0.97 R3 which is slightly tweaked compared to whats being used by others. So what I'm saying is is that if it doesn't work via the newest version non of the previous created by zsmin should work either.

I actually haven't seen zsmin in a little while now, every time I sign in to talk hes not been around.

@ Hakan
From what I have said above that kind of spells "doomed", but saying that your setup is a little odd. 1.5GB wasted and your Vista drive thats labelled "recovery"? Normally it's recovery OEM partitions that interior with loaders. In this case I suggest you look at a different activation solution such as a BIOS mod, RemoveWAT or ChewWGA.

 

Your machine likely is modified in one way or another, maybe you play around with services or settings. I stick with the standard and expect a half decent setup. By design I have it refuse to install on any machine that has been tampered with. I mean lets face it, slmgr.vbs and any activation services should be enabled by default on 99% of users systems so having any kind of alternative in that area for me is useless, I don't want to force installation on systems that could have had other files modified. Why? well what if activation fails because its had some DLL's tampered with and then the user comes back saying the loader doesn't work. It makes debugging something 10x harder when it wouldn't even be my problem, it would be the users setup.

I believe I did say in my thread a while back that I don't agree with some of the things people are trying to make loaders do now. It's not so much which loader does what but for example Carl's forces installation and trys alternative routes where as I pick to just say "no" and refuse installation. In my personal opinion as a developer it shouldn't be up to me to workaround a users personal setup issues which can then lead to false loader activation results if forced.

With the amount of installations and feedback I have had I think it's safe to say my method works too. Nobody with a fresh clean setup has ever reported an installation failure, simply put because it won't ever fail because everythings there and as it should be.

So I'm saying its not that it's right out failing, it's that I'm deliberately having it bail out if something doesn't match up somewhere during installation. So it's not an error, its a feature

 

I just did. Carls using alternative routes, thats his decision to do as a developer. I however have a totally different view on it and refuse to force installation if anything is off.

I can say with 100% accuracy that if you format and run my loader it will install without fault (as it does with pretty much every users system, thus why I have little to no complaints from anyone with a standard setup). That means something on your system right now has clearly been changed and so I have it bail out of install. So thats not an excuse or placing the blame, I'm telling you I have it do that choice by feature so that debugging is easier and no failed activation faults can be blamed on the loader itself.

And yes I know, the alternative forced way Carl supports on some faults can work on some systems as it does yours but I stay away from it due to the other changes that may have been made on some users systems (modified DLL's etc.).

Besides I don't know why you are bringing this up here, the OP says installation went fine under all modes but the loader failed to activate the system. The keyword is loader, which every single person is using the same version of but me.

 

If the loader installs which you didn't say it does, just that it "refuses to work" it may be because some of the modes were switched around. Remember now I keep previous versions of the loader which I think are good releases uploaded so I'm not saying people should just use 1 version. Heck allot of people stuck with my 1.5.5 release since that was pretty much fail proof when it come to loader selection.

Does activation on R3 fail under all modes? Can you get a debug output to show its failure?

It's not that I don't believe you, it's just that your saying the loader version is failing and nobody else has reported that it fails. Although I think there may be a slight fault with null padding that some systems don't like, that depends on if 1.7.6 worked for you.

But I know it doesn't force, but I mean it trys alternative methods where as if the first method fails on my application then I have it stop as 99% of the time it will be a fault/modification made to the system. So if slmgr.vbs is not found then theres a good chance other system files have been tampered with, this is why I don't support an alternative backup method of installation which is what im calling "forced".

 

My guess is because on versions before that I used spaces to pad where as on 1.7.7 I used nulls. You may be able to install 1.7.7 and strip the nulls, although I'm not sure where the start point of the padding is since im on the laptop and half asleep It would explain why all modes now fail, I would question it it even gives you access to the GRUB 4 DOS menu at the moment if you were to test.

 

Yep, sounds like a padding issue. Most machines accept it but like an executable some machines think it's corrupt and refuse it. So I think for 1.7.8 I will put it out with spaces again, they seem more reliable and it doesn't make a whole lot of difference anyway