The site also explains that the fix is not for Win 10. So no, it doesn't cover Win 10. Gray Riders has Win 8.1, not Win 10. I believe I explained in a previous post what the problem is; the article gives the same account, though with more detail. But in any case, there is no solution for Win 10, other than to use a VM.
However, as you might note, the problematic update is for September 2015, but we started posting about our problems a month earlier in August 2015. Also, the site notes that the problem is for Win 7 and Win 8.1. It seems very likely that having purposely removed support for the DRM in Win 10, Microsoft decided to expand the blocking of that DRM in Win 7 and Win 8.1 because the DRM is seen to be a security issue, and so that update was launched a couple months after Win 10 came out.
I see that you did say right off the bat to use a VM, and thank you for reminding me; I am sorry that I have not given you your due credit in my previous posts. What I did give is a more detailed account. For instance, I explained that Hyper-V won't work, but what would. I suppose you're savvy enough to know how all that stuff works, but for someone who isn't, I offered more of an idea of what to do, so that no one else has to go through the painful experience I did.
Btw, I understand that such a solution is obvious to you, but please try to understand that what is obvious to you is not obvious to everyone. It wasn't obvious to me. What seemed obvious to me was to either 1) Use the no-CD crack as had been suggested on some sites or 2) use compatibility mode. Setting up a VM takes more work, and is a bit less obvious, at least to me.
That's interesting that Win XP is the best choice for this game. I didn't know that. Does it have less glitches, crash less, look better? I don't really want to get a copy set up now that I have it on Win 7 on my VM, but if it's worth the while, I might give it a shot.
Besides, their workaround might still be necessary if you're using Win 7/8 in your VM under Win 10.
What bothered me is that you've turned up your nose at bellelda contribution and, at least to me, seemed too cocky over "your solution"
But then, it doesn't make it an accomplishment worth of a Pulitzer.
Sure you try compatibility mode first, but heirtothestar had already said it wasn't working for him
(I know, I know, you haven't noticed the game was that old and released under XP)
So yes, on Win XP you have less bugs/crashs (although still far from perfect)
Sorry if I look aggressive
but more than anything else I'm alerting to the fact that even using Win 7/8 in a VM under Win 10 many people will still have to do that workaround, be it because they updated their virtual Win7/8, be it because they downloaded an updated iso somewhere to put in their VM.
I'm sorry, I didn't mean to sound cocky, or 'turn up my nose' at bellelda. I began by thanking bellelda for the info (and then thanked bellelda again for the advice later in the post). I then offered feedback by proceeding to explain why it would not help those with Win 10, which is the topic of the thread. I don't see why this is turning up my nose?
As far as being cocky about my solution, it is pretty much the only solution for Win 10, right? I don't see why that makes me cocksure, though I do feel certain of the truth of it, and the linked article doesn't suggest anything different for a Win 10 user. But it's also true, as you pointed out, that updated Win 7 and 8.1 will be affected, and if they are used in VM, that can become a problem for the solution I support. I overlooked this consequence, and I apologize for that.
Oh come on man, I'm advertising a solution that worked, nothing more. It's the fact that there's a workable solution that's important, not that it came from me.
Of course, I had already been working on the problem myself before heirtothestar had posted, and had tried compatibility mode, which is why I mentioned that as one of the things I tried first. You'll see that I tried to confirm with heirtothestar if our problem was the same in all details when trying to work with compatibility mode.
Okay, now it seems to me like you are the one who is cocksure. I have been playing these games since the first installation in the series. So not surprisingly, I'm quite well aware of how old it is (and that it is still the best version, imho). I don't know why you should think you knew that I hadn't noticed such a thing. Just because it's old doesn't mean compatibility isn't worth a shot, and wouldn't be the easiest solution, though perhaps not the best.
That's great to know! I haven't had too much of a problem with Win 7 yet, and from reading around, I see the unfortunately endless "building/destroying" phenomenon with the AI is a bug that will appear even if I use Win XP. I just try to avoid delegation, though I found this bug can appear if a human player's ruler is turned over to the AI at some point in a game. Very annoying.
I had seen the translation of the changelog before, but I thought perhaps the updates had been included from the outset with the English version, since it came out after the updates (I think?).
Very. I'm quite thankful for your work and contributions to translation, as well as the save information you've shared, but I have been very surprised by what I feel is an overly aggressive reaction to my posting. It makes me feel like you don't want to count my efforts as helpful or appreciated, which is funny, since you're accusing me of doing the same to bellelda. After all, you make a point of saying that you suggested the solution first, it's supposed to be the obvious solution, and you reference it as my solution with scare quotes. I did thank bellelda for the info, but I overlooked how it affected the solution I offered (the hosted Win 7 in VM), and so I'm guilty of not seeing how the info was genuinely helpful. I don't see that it makes me guilty of other things, like being arrogant or thinking I'm owed a Pulitzer. That's a bit over the top, don't you think? I just made an honest mistake.
Again, this is a great point. I just wish you hadn't felt it necessary to try taking me to task along with this great point. Or really, it's the tone you take that I feel is undeserved. You could have pointed out my mistake, and I would have acknowledged it and offered an apology, and it would have proceeded and ended amicably. I'm sorry that you found my response to bellelda was somehow morally inappropriate, and I certainly didn't mean to demean bellelda or the offered advice. I do think it's a good thing that you spoke up to show how bellelda's advice is relevant for a Win 10 solution and that it's a valuable contribution.
Users browsing this forum: No registered users and 1 guest
Copyright © 2002–2008 Kongming’s Archives. All Rights Reserved