cluberti

Screenshot? The highlight color in my Vista install is pretty easy for me to see, so perhaps it's the theme/color scheme you chose?

That's because XP overwrites the new Vista bootloader. Once you've got XP installed and repaired, you'll need to repair the Vista bootloader as well to get BCD back. There's a sticky about how to do this right at the top of this Vista section itself, so I suggest you search the forums next time.

I believe this is the case, and the problem was originally that the servicing engine was changed from Vista RTM to Vista SP1, and it appears that Vista SP2 requires Vista SP1 due to the new servicing engine.

Honestly, the crash stack I'm seeing (again, this is cursory - I won't know more until I see a real full .dmp file) seems to indicate you have bad RAM. Sometimes, *sometimes* (I can't emphasize enough how infrequent this is in my experience) a prototype PFE via PFN lookup failure is due to a bad driver somewhere on the system - but the VAST majority of the time I see this type of error, you have a bad stick (or more) of RAM, or the mobo memory controller's started to go bad, or both. I'd consider that removing a stick of RAM giving you some stability may indicate you've got some bad memory there.

Not sure, you'll probably have to attach your lastsession.ini file. Moving to the vLite section.

I would suggest enabling verbose MSI logging and try again. The resultant log will probably have a better insight than an error message in a dialog box, although it's not a guarantee.

Dear day_chess: As an admitted Microsoft shill (not for all their products, most definitely, but yes for Windows itself), I would suggest you take your concerns up with Microsoft. As you so rightly point out, they do spend untold millions on research and development, and it seems at least fairly certain that their research found that the new start menu was something people preferred over the old or they would not have changed the user interface paradigm so. It seems the folks who are voicing their concerns are not doing so directly to Microsoft, and this is a pity. Honestly, I'm one of those voices who prefer the new start menu, and I don't think it's a coincidence that lots of other people (who are not me, by the way, I can assure you) say the same thing. It's what Microsoft does - they try to make software that the vast majority of people will want to use (otherwise product doesn't sell, aka Vista). It would seem the vast majority of people DO like the new start menu, myself included, but if you want the old one back you really should complain to Microsoft (and perhaps start some online petition to bring the old start menu back). I'm being serious, if you feel that strongly about it that you'd change your entire computing architecture and software loads because of a simple start menu, you really should be making yourself more public where Microsoft will see it. A post on a random Internet forum is sound on the moon to Microsoft - however, some sort of grass-roots movement (if there really is that big a crowd, you should be able to get it started) that has a public face and can be easily found is FAR better than chopping a tree down in a vacuum, and at least has a better chance of producing results. It's a pretty fair assumption they don't really care about us here .

In the states I've lived in (NY, IL, WA, FL, and NC) here in the US, that is also the case, and they do so on their own time (they can't go to court for a ticket they wrote while they're working). However, they get 3 strikes - if they don't make it on try #1, you get a new date - lather, rinse, repeat. If they fail to appear the 3rd time, you're out of the ticket (if you plead not guilty, you have the right to confront your "accuser", in this case the officer, on your own time for the both of you). However, I've always found that the cop shows up the second or third time, and you lose (the court will almost always believe an officer of the court over you, especially when his gun says you were speeding and so does he) and you're out 2 or 3 days of your own time. It's always best to plead "not guilty" (always! even if you *are* guilty) and see what the court offers. Honestly, they would rather plead you out then go through a "trial" for a little speeding ticket. You will end up paying a fine, but you'll keep a speeding ticket off of your record and save on insurance money when you turn 21 and 25, respectively. It's *always* better to play the system.

Honestly, I'm not seeing the problem (I built an XP x64 VM the other day, so I dropped IE8 on it and tested your steps). I saw a bit of memory increase during the download (makes sense), but it went back to the original demarcation point pretty soon after it was done. Usually, in my experience, IE increasing in memory usage over time is caused by a misbehaving add-on. You could try using the IIS DebugDiag toolkit to trace iexplore.exe for leaks (there's a rule for it in debugdiag, pretty easy to use).

Either the EU is in a world of hurt for money and wants to hit the Microsoft bank again for a freebie, or Operwaaaaaaaah is really paying someone off, because this is getting ridiculous.

True, but that set can just be copied into a folder and re-ISO'd via oscdimg. It's not the only CD set, and some of the OEM sets cannot be copied this way and still work on the other side.

Well, considering the error code it gave you was the below, I'd say yes, it's a registry problem (as to what, hard to say - probably need to run a process monitor log logging only registry accesses when attempting to start the service manually to see what's actually happening). Here's what the error means: # for decimal -1073741288 / hex 0xc0000218 STATUS_CANNOT_LOAD_REGISTRY_FILE ntstatus.h # {Registry File Failure} # The registry cannot load the hive (file): # %hs # or its log or alternate. # It is corrupt, absent, or not writable.

Perhaps if we knew where you got the CDs we might be able to help.

Who said anything about getting rid of Windows? We're talking about removing IE here and leaving the rest of Windows intact. Keep your fanboi'ism to the relevant sections of the forum.

Well, sort of. IE is there, but all of the possible ways to execute IE other than hosted in a WBControl app will be gone. As far as getting IE8, you'll probably still be able to download it from Microsoft ultimately, and OEMs will be free to install it on machines if they so choose (along with any other browser). At least that's what the current plan is documented as, publicly. I wonder if it'll change before release.

Also, a bit more info about the machine in question would be helpful. Not sure how much, as it does sound like a hardware problem, but it might help anyway.

Unfortunately, at this point XP is in extended support, so getting a fix for XP is impossible unless you've got a premier support agreement, have an extended support and extended hotfix support agreement for XP, and are willing to file and wait to see if they're even going to consider fixing it.Can you reproduce this on the same hardware with something newer, like Vista or Win7 (as a test)?

Win7's firewall is a subset of the firewall in ISA server, so it should be a pretty good two-way firewall. It's not as featureful if you like the popups and alerts as Win7's firewall, but I've not had any real issues with it. I do my firewalling at the egress point, and just use the Windows firewall to protect it from inbound connections anyway.

Well, first things first - do you know which svchost is crashing? There are quite a few, all containing lots of services. You are going to have to break apart the svchost into multiple individual svchosts to host each service it normally contains to figure out which service is actually crashing, so you're going to need to know which is causing it.

I don't know about Canada, so perhaps someone who knows the courts there can pipe up. However, here in the US, I always contest the ticket. Since traffic courts are *very* busy here what with all the horrible drivers on the road (I haven't gotten a ticket in 8 years, knock on wood), it's always best to go and plead not guilty and get that second court date. Usually on or before the court date, you will be contacted by the state's attorney (in some jurisdictions you can actually do it on the date you plead not guilty - it was odd, to say the least) and you can plead it down to something that costs about the same, but won't be a moving violation (parking tickets, etc). The state gets their "driving tax", you get to keep your insurance down. It's a total f*cking scam, but those are the rules you play by when you don't follow the law, I guess. My mother in law always asked me why I never went more than 5 over on the highway and *never* on side streets, until she got a ticket last week for going 7 over in a 35. The fine? $436 dollars for the ticket and her insurance went up almost $20/month. So, those points won't come off for 3 years, so she'll be paying $720 over the next 3 years in insurance increases, the $436 dollars for the ticket itself, and she'll be out at least 2 days of work for court (here you have to appear, no matter where you're tagged - even out of state). That's why .

I'd also make sure that defragmentation is a part of your disk cleanup regularly, maybe once a week or even more frequently especially if the disk is becoming full. I don't concur on the reinstallation "fixing" anything, unless you're constantly uninstalling and reinstalling programs (in that case, it would make a difference - otherwise, no).

I'm not sure - nvidia makes it very hard to determine the specs of their chipsets, and I don't have one to test. However, I do know that the driver does determine what res and color depth settings you can set (whether that be the video driver or the monitor restrictions, but in this case it would be a video driver restriction as it's color depth and not max res or refresh). I'd guess the driver doesn't think you have the memory bandwidth to the video chipset to handle 1080p at 32bit color, which may be a driver bug (if you in fact actually can support that depth at that res) or an actual chipset limitation (it takes quite a bit to run that many colors on that many pixels, and the 8200 isn't exactly a great video chipset). Nvidia does make a point to say it supports "HD resolutions" over HDMI, but not the color depth. That may be on purpose (1920x1080 is still HD, even if it's 1080i and not 1080p).

No, this particular user registers, posts in a busy post with misinformation (on purpose, it seems), and then tells the OP (it was me this time, but it has been others) that they're wrong and tries to convince others he (or she?) is right. While opinions really don't weigh on banning or not, stuff like this does. It seems on purpose to reduce the quality of info here at MSFN, and we won't allow it.

As did I, and I can't with any build I've tried (RC1 or newer), so this is really wierd. I even enabled the odd setting and I still didn't get a boot menu, so I'm wondering what happens if I use, say, RC1 to install over an XP install? Not sure. This is pretty bizzare, at least currently.

The only thing I see different from the bcdedit on my Win7 boxes is that you have an extra setting: usefirmwarepcisettings. Not sure how or why that got there either, and I don't even know if it's the cause. However, what you have listed is the same (well, the GUIDs are different, but that's expected) from my VMs and real Win7 machines, so it's at least worth looking into how that got there. Also, the timeout default is 30 seconds and it's changed, so not sure what's been done to your bcd either, specifically.