From: Davoud on 29 Apr 2010 21:44 Latest MB Pro 17, Core i7, 8GB RAM. The Boot Camp/Win 7 Pro (retail package) 64-bit install seemed to work properly. The Boot Camp Drivers downloaded and installed properly. Win 7 activated normally. Ran it for about an hour with no problems. Then it crashed. Now it will run only a couple of minutes before crashing with a black screen and memory dump. Start from scratch I know about. Any other ideas? Any reason 64-bit should be a problem? TIA! Davoud -- I agree with almost everything that you have said and almost everything that you will say in your entire life. usenet *at* davidillig dawt cawm
From: Warren Oates on 30 Apr 2010 07:33 In article <290420102144035160%star(a)sky.net>, Davoud <star(a)sky.net> wrote: > Latest MB Pro 17, Core i7, 8GB RAM. The Boot Camp/Win 7 Pro (retail > package) 64-bit install seemed to work properly. The Boot Camp Drivers > downloaded and installed properly. Win 7 activated normally. Ran it for > about an hour with no problems. Then it crashed. Now it will run only a > couple of minutes before crashing with a black screen and memory dump. Did you "activate" it? Microshaft have a very stupid and hysterical anti-piracy mechanism. -- Very old woody beets will never cook tender. -- Fannie Farmer
From: Davoud on 30 Apr 2010 10:14 Davoud: > > Latest MB Pro 17, Core i7, 8GB RAM. The Boot Camp/Win 7 Pro (retail > > package) 64-bit install seemed to work properly. The Boot Camp Drivers > > downloaded and installed properly. Win 7 activated normally. Ran it for > > about an hour with no problems. Then it crashed. Now it will run only a > > couple of minutes before crashing with a black screen and memory dump. Warren Oates: > Did you "activate" it? Microshaft have a very stupid and hysterical > anti-piracy mechanism. I wrote "Win 7 activated normally." I fact, one has 30 days after installation to activate Windows. I used to think that Microsoft's anti-piracy mechanism was stupid and hysterical, too, but I now think it is unfair to say that. Of course it may _sometimes_ be inconvenient for the user, but just as we note that Apple is a hardware company--the one whose designs are the most stolen in the world--and is extremely aggressive (some would say hysterical) in protecting itself against imitators, so should we acknowledge that Microsoft is a software company--the one whose products are stolen more than any other software. Independent sources place the percentage of Windows installations world-wide that are stolen (so-called pirated) at between 20 and 33%. In certain countries it has, at times, approached 100%. I don't have at hand the figures for MS Office and more specialized MS software, but they are also very high. No sane company would fail to take measures to limit such large-scale theft of its intellectual property, and any fair minded person would have to concede that. It just happens to be much more difficult to protect software than to protect hardware. A hacker can't turn a Yugo into a BMW by swapping badges, but he can make tools that enable a stolen Windows installation to work. The initial activation of MS Windows is effortless. Connect to the network and click the activate button. The process required about five seconds. I can't call that draconian. Re-activation after a hardware change _may_ be more complex, but I still wouldn't call it draconian--remember that we're talking about a company whose software is stolen more than that of any other company. Here is my recent experience with re-activation. I have Win XP Pro on a previous-generation MB Pro. The logic board failed while the MB Pro was under AppleCare protection. The local Apple Store sent it off to a depot to be repaired. When I got it back, XP Pro detected that it was not the "same" computer as before, and required re-activation. It failed to activate on line, and provided a toll-free number. The person at the other end asked some sort of question about the hardware. I said that it was the same machine with a new motherboard. She asked me for the original Product Key, which I provided. She gave me a new activation code. It didn't work. Don't worry, she said. She guided me through a series of commands to reset something or other in the software, then gave me a new code. which activated the software. The above was not entirely convenient, but it took about as long to write as it took to accomplish. The next day I loaded Windows through Parallels Desktop 5 and sure enough, it needed to be re-activated. For some reason, I felt certain that on-line activation would work this time--and it did. I'm not known as a huge defender of MS, but fair is fair. Finally, an individual who can't abide the activation requirement can stop using Windows and switch to the Mac OS, Linux, or another OS. If it so happens that the software that person needs to do his or her job isn't available except under Windows, then that person can quit their job and find a new job. I refrained from saying "can simply quit their job..." IMO, just clicking the "activate" button--or even making a phone call-- is a whole lot simpler. Now, reinstalling Windows--which I'm going to have to do because the first of the needed programs that I tried to install caused Windows to tell me that the program was not 64-bit ready--is a different matter, much more time consuming (though Win 7 is a much easier and faster install than XP Pro). I'm certain that some of my other software is not 64-bit ready, either, so I'll install as 32-bit. Davoud -- I agree with almost everything that you have said and almost everything that you will say in your entire life. usenet *at* davidillig dawt cawm
|
Pages: 1 Prev: Great use for System-7 on my Mac Next: Snow Leopard on iPad? |