Jump to content

cluberti

Patron
  • Posts

    11,045
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

Everything posted by cluberti

  1. It's genuine. Vista and Win7 share the same kernel thusfar, so it's 6.1.xxxx currently. And no, there aren't many differences between the two other than the "under the hood" changes - if you sat down to a Win7 desktop, you wouldn't know for sure if it was Vista or not.
  2. I don't think this will happen yet until more software and drivers become *stable* under x64. I'm not sure about Win7 yet, but you can still run it in both flavors, so perhaps Vista wasn't the last x86 OS after all...
  3. Unexpected reboots. If you see 6005 and 6009s without 6008s, it means the reboot was expected, and should tell you why.
  4. Looks like vlite.net got slashdotted . Congrats on the recognition, though, very cool.
  5. If you look in the windows logs > system event log (eventvwr.msc), do you see any 6008 events at or around the time of the reboots?
  6. If you disable the Windows Time service, and the problem still occurs, this means an underlying hardware problem or software on the machine is messing with the time. Have you made sure the CMOS battery is good, and that the time in the BIOS is correct?
  7. What kind of wifi card, what kind of access point, is the SSID being broadcast or is it hidden, and what security level did you choose (WEP, WPA/WPA2, etc)?
  8. The problem with WinSXS in it's current form is that you don't have any way to determine what to clean out/remove/delete/whatever and what to leave, as app uninstalls RARELY remove their SXS data. I've used vLite to remove the non-English stuff, and I've deleted some things without issue (like .exe files) - yet. I think what I'm going to do is reinstall with SP1 when it hits the web, and start paying attention to EVERY install, including windows updates, what files/folders get put there by which application and update. Then, I'll know what I need and what I don't (at least I'll know better - whether or not I can do anything about it is still anyone's guess).
  9. Welcome to the new DLL hell - now there's a way to avoid the old replacement of DLLs causing it, but the WinSXS folder grows tremendously. And deleting it is frought with danger - I've got a 20GB SXS folder, so 6GB to me would be wonderful .
  10. I have the same behavior, because that's the design of the address bar. If you click the arrow to the far right, you get an MRU list - if you click the arrows between or at the end of the sections in the bar itself, you get a drop-down of the folder locations within that folder.
  11. If it was a registry problem, it would happen on all drives. If it only happens on one partition and not others, I third the previous motion - you have a file on the root of that drive (autorun.inf or otherwise) causing the issue.
  12. You assume it's the same software in both, when in fact it isn't - the 360 isn't even intel-based.
  13. I actually have no idea on this - I'd contact the vendor or the ISP (or both) and get their opinions on this. If you're using 802.11b or 802.11g, the only channels that actually matter are 1, 6, and 11 because those are the only 3 that are 22MHz wide (see the wikipedia doc on this for why, if you're interested).
  14. I doubt you'll see a Microsoft console support DivX, as it's not free, just like it'll never support encrypted AAC content, RM or MOV files, etc. However, the MCE page on the 360 extender does bear out what I've found thus far: I've actually seen some things that aren't on this list work, but not 100% of the time. Also, the spring 2007 update brought about H.264 support, so that should work too (which means Blu-Ray DVD support is likely in the future too, as that's the codec required for it). Since I store most of my music in MP3 or WMA Lossless and my video is WMV, I've not noticed anything - plus, I generally am watching TV or movies on the extender itself, or downloading them from the marketplace. It's too bad about the HD-DVD drive and the format's ultimate death, but since the console does support H.264 as of the spring of last year, I'm guessing a Blu-Ray player attachment will be forthcoming this year or next (a guess, but an educated one).
  15. There are ways to use script (documented well in a google search) on how to open a user's ntuser.dat file from his profile path (ntuser.dat is the user's HKCU hive, in file form) and make modifications without being logged in as that user via the reg.exe utility. I would look into this, as this command-line utility will allow you to do what you are looking to do.
  16. In looking at the dump files, I would have to agree that it looks like faulty RAM. Each time, we're accessing memory via win32k.sys to draw data on the screen or handle window functions, and the memory address referenced is partially gone, but not fully bad. Meaning we had a fault either reading in, or writing to, the page in memory, most likely.
  17. Honestly, while this is a fun academic adventure, I would still strongly suggest using a wired or wireless router to utilize the internet instead of monkeying with ICS almost every time. It makes much more sense (and is far more secure) to bring the internet connection directly from the ISP into a wired or wireless router first, and then have all of your machines connect to that router directly.
  18. The problem is, you can't share an INTERNAL wireless connection (well, not easily) via ICS. However, I'm not sure this has ever been tried where the connection to the internet is actually the wireless link, and the connection to the internal machines is actually the wired link (this is backwards from what the poster in the linked thread was trying to do). I'm honestly not sure if it would work - my hunch is no, because it doesn't work the opposite way, but one has to try to find out.
  19. Well, the Xbox360 does HD just fine, and costs about what I would pay for a PC to do the job (and I can play 360 games on it, which the PC can't do ). My MCE machine is Vista, so I've got some OTA HD broadcasts and some HD video that works well too.
  20. That's the only reason those directories are installed to C:\, so it was there at one point (and if you can't delete these, sounds like it still is installed). Do you have a folder %windir%\system32\inetsrv, perchance?
  21. I am quite sure you did download it, but there was a link on that page you should have clicked. You'll note that a lot of the text there speaks to this being a time-limited package, that there are steps to install this RC that will not be necessary when the final SP1 package is actually released, Microsoft does not recommend you install this on primary or mission-critical machines (Microsoft would NEVER state this of a real, RTM service pack, only betas and RCs), and most importantly that you downloaded and installed a Release Candidate - an RC is a package that MIGHT become the RTM version of the package, if nothing changes between the release date of the RC and the RTM cutoff. Release Candidate and the final package are actually two different things. From that link, under the "time-limited" software section link:
  22. No, this is a kernel error. It could be an application working with a kernel-mode driver, but the app itself isn't the problem if this is the case. It could be - if you could post the .dmp files here, we can open them in the debugger and try to tell you what's wrong.
  23. If those directories exist, it's because you have IIS installed. WFP has nothing to do with those folders - remove IIS or disable the services, and the folders can be deleted.
  24. More to the point, how do you NOT know that you're installing a pre-release of SP1, considering the code hasn't hit RTM yet?
×
×
  • Create New...