Recommended Posts

this has to be the fastest fresh install i have ever had ! !!

12 min from start to desktop WOW !

i did notice that the send feedback button is GONE !

I thought you meant thats how long it took you to BOOT.

12 mins, good for you ;)

Good to hear its nice and quick.

SuperZod, I noticed that even in pre-7000 builds - if I added in my main music location into the library, it would take ages to add all of the files. Its as if the "force rescan" mode you could invoke in Vista/XP where you select your folders and it adds them all there and then with a progress bar is gone. We can only add files by adding "monitored locations", and have the indexing function slowly pick up on everything. From start to finish on 7022, it took 2 hours to begin and finish indexing my one location of about 16000 files (mix of MP3 and WMA lossless files).

Sad to hear this is gone, but its not hard to put up with manually playing files instead of using the library temporarily after a clean install.

Meh what is this, 1999? Why bother leaking the legacy build, need the real version.

I dont understand what you are talking about. Using the words "Legacy build" when talking about the as-yet unreleased, brand new, Windows 7, doesnt make a whole lot of sense.

I dont understand what you are talking about. Using the words "Legacy build" when talking about the as-yet unreleased, brand new, Windows 7, doesnt make a whole lot of sense.

I think he means 32bit is legacy and 64bit is what should be leaked.

found something new

in Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings you can now change encryption settings for file sharing.

That is sweet, but would only be useful if XP and Vista would update to support such a thing. I'd have to share between 7 and 7.

Hm, the only thing I can think of is that one of your RAM sticks is bust, 0x1A is common for that.

Its quite possible, but if you run VMs a lot it would have shown up beforehand I expect.

Memtest86?

I have never got a 'Memory_Management' blue screen before, in VM or running for real.

I'll run memtest86 if the install fails again. Don't really want to know if my RAM is bust at the moment though, I'm so broke! :(

So you are saying that virtually 95% of all Netbook computers are "legacy". The fastest growing segment of the computing industry, is legacy. Yeh mate sure.

Regardless of whether you think x86 is already a legacy architecture or not, Windows 7 is being designed to run with lower requirements, so having an x86 build out there to test with is just as important as having an x64 build which would definitely run on all x64 computers (assuming nobody has an x64 PC with something like 256MB RAM).

I have never got a 'Memory_Management' blue screen before, in VM or running for real.

I'll run memtest86 if the install fails again. Don't really want to know if my RAM is bust at the moment though, I'm so broke! :(

Might have a warranty left on them ;)

I have never got a 'Memory_Management' blue screen before, in VM or running for real.

I'll run memtest86 if the install fails again. Don't really want to know if my RAM is bust at the moment though, I'm so broke! :(

I dont think it would be if youve used a lot of VMs and havent had this happen before.

Ive had 1 BSOD for W7 so far, and that was installing 7022 x86 on a Mac Mini. When it came to installing the boot camp drivers, I was daft and tried to do other things at the same time - normal stuff like browse the net download antivirus etc, but I really should have left it to it. It BSOD'd really quick so didnt see the message, rebooted, and I "repaired" using the MSI installer. Worked/still works fine.

It may just be bad luck, try again. Possibly a duff CD, but Im guessing if your in a VM you are using an ISO, no?

I dont think it would be if youve used a lot of VMs and havent had this happen before.

Ive had 1 BSOD for W7 so far, and that was installing 7022 x86 on a Mac Mini. When it came to installing the boot camp drivers, I was daft and tried to do other things at the same time - normal stuff like browse the net download antivirus etc, but I really should have left it to it. It BSOD'd really quick so didnt see the message, rebooted, and I "repaired" using the MSI installer. Worked/still works fine.

It may just be bad luck, try again. Possibly a duff CD, but Im guessing if your in a VM you are using an ISO, no?

Yeah I am using an ISO. I just tried again and it installed fine. I think I will run memtest on my computer anyway soon as I have been having some other weird problems with it that could be RAM related.

Ah well, now i can play with this build! :)

Boo.

Now what... to install or not to install, that is the question.

I am using it since last 12 or so hours. It is as stable as 7000 for me if not better. In fact my 7000 BSODed just as it finished burning 7057 DVD. :p (First and only BSOD after it was installed in January).

The LogonUI graphic looks like it's straight out of DeviantArt. It looks quite nice, just not very Microsofty. No doubt it'll look beautiful on Best Buy's shelves, gleaming on rows of glossy laptops, but it just doesn't seem to match the toned-down simplicity the rest of the UI seems (seemed?) to be reaching for. :-/

It's way different from current, yeah, so it's unfitting. For the old style. If they are trying to create a new style, I don't see what would be the problem. I like this new one way better than that abstract one.

Currently listening to Windows Weekly with Paul Thurrott and he's saying that 7057 has been crashing like crazy for him. :huh:

Sorry...sorry...he was talking about 7048 which has been crashing non stop, documents are disappearing, wordpad closing for no reason, etc.

He says 7057 has been very stable.

I dont, he's a knob, but he does probably have a lot of gear to test with, and I dont know why he would cry wolf.

Unless of course its just him, which is why I was doubtful up there.

Given that nobody on here has reported anything show-stopping, Im probably gonna install when I get home. Its downloaded there, just need to complete this damn 12 hour shift.

**EDIT**

Ah thats cool, yeah I didnt bother with 7048 and kinda glad now.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
    • So how did you solve the problem? Disabling Secure Boot isn’t a solution.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!