Windows 7 Build 695x revealed at WinHEC 2008 China


Recommended Posts

i disabled ACHI in the BIOS (apparently the OS wasn't installed with ACHI enabled onw hatever machine they got it from (i'm guessing) so turning it off allows the system to boot. As a result i got the full boot up screen (on video) instead of just 2 seconds then BSOD. I still however get a BSOD after changing the BIOS to standard IDE mode. I am now getting error 0x00000012F or something like that.

(will post video shortly)

yeah, safemode and all. I have one more idea though so i'll test that in the morning. Copying all the data from the VHD to the partition then edit the boot tables to point there and then repair the instalation and go from there.

(zip file with 2 videos from my AT&T Fuze. LOL Sorry it's not better quality. The first one is when i had AHCI enabled then the second is without)

VIDEO0001.zip

Your video 2 is pretty much what happens to me, It goes through the full video and then blue screens. I can't get it to but into safemode, the only options are start windows or boot into the recovery partition for 6801. I guess I will just wait until beta 1 in mid january unless something better gets out their.

Right, everyone, I'm pleased to tell you all that I got it working, with no problems whatsoever. haha!

I must be the lucky few. But all I did was mount the image via Disk Management, copy all the files except the 'System Volume Information' folder. To my second hard drive (I guess a separate partition would be completely fine). After that, I booted straight into my 6801 DVD and did a 'Start Up Repair'. It found that something was wrong, and asked to reboot. I let it. I then booted back into the DVD again and ran 'Start Up Repair' again, and I could see the 'Windows 7 (Recovered)' and my normal Windows 7 (6801) installation was two of the options I could select. So I selected the 'Windows 7 (Recovered)' and it did some repairs. I restarted, select 'Windows 7 (Recovered)' and I booted into Windows normally. I didn't need to go into safe mode or anything like that. It picked up most of my drivers and asked to restart. I did that, and I'm posting within the latest build. And I must say, there is some definate speed improvements.

Aero peak works. The WEI takes longer (At least for me), nearly 5 minutes. But my CPU score went from 5.3 (from build 6801) to 5.8, so it looks like Microsoft are changing the rating scores.

If anyone has any questions about 6956, don't hesitate to ask.

Right, everyone, I'm pleased to tell you all that I got it working, with no problems whatsoever. haha!

I must be the lucky few. But all I did was mount the image via Disk Management, copy all the files except the 'System Volume Information' folder. To my second hard drive (I guess a separate partition would be completely fine). After that, I booted straight into my 6801 DVD and did a 'Start Up Repair'. It found that something was wrong, and asked to reboot. I let it. I then booted back into the DVD again and ran 'Start Up Repair' again, and I could see the 'Windows 7 (Recovered)' and my normal Windows 7 (6801) installation was two of the options I could select. So I selected the 'Windows 7 (Recovered)' and it did some repairs. I restarted, select 'Windows 7 (Recovered)' and I booted into Windows normally. I didn't need to go into safe mode or anything like that. It picked up most of my drivers and asked to restart. I did that, and I'm posting within the latest build. And I must say, there is some definate speed improvements.

Aero peak works. The WEI takes longer (At least for me), nearly 5 minutes. But my CPU score went from 5.3 (from build 6801) to 5.8, so it looks like Microsoft are changing the rating scores.

If anyone has any questions about 6956, don't hesitate to ask.

just liked to point it out if you clicked F8 before windows boot screen , you get the option to repair the computer

you don't need the disc for diagnostic/repairing the boot

just liked to point it out if you clicked F8 before windows boot screen , you get the option to repair the computer

you don't need the disc for diagnostic/repairing the boot

I was loosely following a guide on another forum. That method probably works, some other methods don't with others. It seems to be a mixed bag.

- Start Menu button has been changed.

- Windows Media Centre has had a bit of an update. Though, these updates are pretty much in 6801, there is just less bugs.

- Task Bar yet again has had a small UI change. When you are viewing a window, you get a proper highlight on the task bar. It's nothing major, just something noticeably better.

- Notepad is still the same.

- When you right click on a Task Bar item, you get the old standard right click context menu. This has been removed and replaced with the 'Up Arrow' menu which was in 6801. The Arrow menu next to the Task Bar Item which it's related to. It's a little bugged. For example. When I click to 'Close' a window, I would expect it to close the menu, but it doesn't. And I need to click off onto something else to force it to hide again.

- Library functions have changed slightly, how it's layed out is different, but I don't like how they've done it. They have improved the speed of the Library itself. But rather than combine all the folders (like multiple download folders as an example), it puts them in sub categories. While I guess that's useful for others, I preferred it how it just combined everything together so I could view it as one big folder.

At the moment, I'm just browsing around, I'll try and write down any more changes. But so far, the only real difference is that it 'feels' faster. For example. I was tested Counter-Striker Source before, and closed it etc. Browsed a few websites and so on, then I decided I wanted to play a bit of Counter-Strike online. As soon as I double clicked 'Counter-Strike' in the Steam window. I waited literally a second or just after and Counter-Strike was loaded. So it looks like they've improved the Superfetch feature. :)

Just to add-on. My method of installing meant I couldn't have the new Boot Screen, I still have the old Vista one. So I tried the 'No GUI' boot option, and as we all know from Vista, it gave a different boot screen. But Microsoft literally meant 'No GUI' with this option. Completely black.

Also, they've removed the 'Aero' boot screen for when Windows starts up. So it looks like the new GUI boot screen is going to be an actual boot screen this time and not some stupid progress bar and then the 'Aero' boot screen.

Some of you will be wondering what the resource usage is like with the latest build. Currently, just before I opened up this Firefox window. Windows was using 29% of my 2GB RAM, with Windows Live Messenger 8.5 running and uTorrent. Not bad! :)

Just to add-on. My method of installing meant I couldn't have the new Boot Screen, I still have the old Vista one. So I tried the 'No GUI' boot option, and as we all know from Vista, it gave a different boot screen. But Microsoft literally meant 'No GUI' with this option. Completely black.

the change has been there in 6801 . i tried it , it give the same result ==> black screen

29% with 2 programs running, not bad, and still not fully optimized/tweaked I bet. Probably have to wait for the first RC to get a true indication of resource usage. But how does that compare to 6801?

Someone posted before me that Aero feels 'lighter', I agree with that assessment, it is feeling pretty much perfect. Compared to 6801, I find that speed has increased, but there are some bugs to be worked out. We'll have to see how it goes over the next week or so. :)

Any more questions?

Also to add-on, Windows Live Messenger 9 (can't remember the build number, but it's one of the latest ones) doesn't work properly. Keeps saying that the service is unavailable. I've installed 8.5 and it's working fine. Even though they are both alpha/beta products, I'm not going to start complaining.

We're not allowed to link or talk about it really here on neowin but i'll say the usual places.

There is to be NO talk, discussion, hints, or links to warez of any kind.

Community Rule #2- No Warez (links) & Cracks.

Help, requests or posts that discuss circumvention. This includes linking to illegally obtained software, movies & music files - posting about it, and suggesting obtaining it.

Thank you!

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

    • No registered users viewing this page.
  • Posts

    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
    • OK so SearXNG is a meta search engine that you can install locally or use via a public instance. It scrapes other search engines which you choose and then sorts the results. Not as complicated as multiple relays
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!