Windows 7, are you ready?  

89 members have voted

  1. 1. Did it change my concept regading OS upgrade?

    • Yes
      47
    • No
      42
    • 0


Recommended Posts

I hope that this time software and hardware companies will take testing more serious with Windows 7

not like they did with windows vista

you can blame microsoft all day (for not testing ALL vendors)

but beta version of vista was out a year before the launch

and even one year after, some companies still do not verify their product is compatible with vista

when it come to windows 7

it will be based on the mini windows core (MiniWin which is edit: significant change to the XP kernel code)

add to the fact that windows 7 is focused on 64-bit architecture and much more secure

you will find many applications and drivers incompatible

it's funny how people put up dreams, and although realistically Microsoft providing it's roadmap.

people tend to take what they want and close their eyes to what actually going to happened

Remember today, early 2008.

The Good:

Windows 7, will be much more secure

have significant change to the kernel

and 64-bit oriented

The Bad:

people who will migrate directly from XP, will suffer the most!

(just like people who migrated from Win95/98 to XP)

Conclusion:

users: upgrade to windows vista, verify your software and hardware are vista ready

vendors: verify your software and hardware are vista compatible, register to windows 7 beta testing. and start testing for compatibility ASAP.

Edited by raindrop
Link to comment
https://www.neowin.net/forum/topic/616766-windows-7-are-we-really-ready/
Share on other sites

Again and again, Windows 7 will not ship with a new kernel!

Windows 7, will be based on Windows Mini core

Mini Win is Windows Vista/Windows Server 2008 based kernel

it will have significant change from Windows vista/Server 2008

and will have almost nothing to do with the kernel code of XP

Windows Mini core is Windows Vista/Windows Server 2008 based kernel

it will have significant change from Windows vista/Server 2008

and will have almost nothing to do with the kernel code of XP

Okay, so why you said:

- MiniWin which is totally *deferent* from the XP kernel code?

- Windows 7 [...] based on a *new* kernel?

Of course kernel changes with every new version of Windows. It did change a lot with Vista, but it is not *new* nor *totally different*

What's the point of getting a newer OS? Are there things XP or Vista can't do? What do you need Windows 7 for?

Do you want a more flexible OS? Faster? Better looking?

I'm happy, because I can run all the software I want to run. I don't need more than that.

Irregardless, I fear the issues with Vista will flow into 7 unless drastic steps are taken.

Kind of like when the Mac OS codebase was getting old and it was finally jettisoned for the BSD based OSX.

with Microsoft bringing out the Hyper-V code, it could be a great time to dump the older code, get something NEW written abandoning the legacy code that is dragging things down and include a "Classic" mode ala Apple.

Code written for this generation of hardware alone mmmmm goodness.

Okay, so why you said:

- MiniWin which is totally *deferent* from the XP kernel code?

- Windows 7 [...] based on a *new* kernel?

Of course kernel changes with every new version of Windows. It did change a lot with Vista, but it is not *new* nor *totally different*

I am happy you agree on the concept

and I agree, *totally different* is too strong sentence, I would rephrase it is significant change to XP kernel

the reason for my post, is for software and hardware companies

as well as for users and organization

not to do the same mistake some users/ companies did with Windows vista

and in one hand start adopting Windows vista

and in the other prepare much better they you did to windows 7

or else, again they will find themselves not ready, and blame Microsoft.....

What's the point of getting a newer OS? Are there things XP or Vista can't do? What do you need Windows 7 for?

Do you want a more flexible OS? Faster? Better looking?

I'm happy, because I can run all the software I want to run. I don't need more than that.

Amen, brother :yes:

Windows 7, will be based on Windows Mini core

Mini Win is Windows Vista/Windows Server 2008 based kernel

it will have significant change from Windows vista/Server 2008

and will have almost nothing to do with the kernel code of XP

Ok, no, no, and again no...

Windows 7 will be just like Vista, XP, Win2k, NT4, NT3.51, NT3.5, NT 3.1..... It will be the same NT architecture and same kernel technology. PERIOD.

Like all versions of the NT platform, there will be minor changes and optimizations in the kernel, but nothing major, or nothing that would make it viably different than Vista.

There are two MinWin concepts running around. Let's explain it out, because people like Mary Jo and even Paul that are devoted Windows journalists don't have the tech background to fully understand the info they are given and bring it out accurately in their articles.

MinWin 1: This is a minimal core NT kernel with limited subsystem interfaces that was originally both the starting point for part of the WinCE project (split from NT years and years ago), and is also part of the Embedded project for WindowsXP embedded and Windows Vista embedded. This is the one you will see Paul talking about on supersite, as it has been around a while and has been used in various internal testing and forking for NT concepts. For example WinCE used concepts from the MinWin NT kernel, but is not the same code exact code, as WinCE was designed as an appliance OS and hence many modifications and reductions were made to it, striping levels of security the layering, etc.

MinWin 2: This is the minimal corel NT kernel that was presented at a lecture by a Microsoft employee. It was referred to Windows 7 by the press BECAUSE THEY THOUGHT IT WAS DIFFERENT OR NEW, but if you watch the presentation/lecture you will understand that it is nothing more than the a fork of the Vista/Win2008 kernel with all subsystem interfaces removed and a simple HTTP host subsystem in place for I/O. It is no where near Windows 7, being almost exactly the same NT core that is in Vista instead.

What seems to have mislead journalists, is the size of the MinWin that was being demonstrated was under 40mb, and they thought, wow this is so tiny compared to Vista; however, if you strip the APIs and subsystem interfaces from the Vista NT Kernel and compile it, it would also be under 40mb.

NT is inherently a very well designed and compact kernel architecture. People forget that it was designed by the BEST VMS and UNIX people in the industry back in 1990-1992, and they had full permission to make it however they wanted. They inherently didn't want to work around the baggage of how Unix is designed. It was also designed to be tight, portable, and very extensible. Instead of textual messaging and pipe concepts it is a full object oriented based OS design that treats all I/O and internal process as Objects, and also uses token passing for security and processes.

It is also a hybrid client/server kernel architecture with a multi-layered OS design. For example Windows as we know it is really Win32 or Win64 and runs in its own subsystem that sits on top of the NT kernel, this is also how you can run BSD Unix on NT as it runs in its own subsystem as well. (Go look up Unix Subsystem for Vista - it is included as an optiional install on the Ultimate DVD.)

So the NT kernel and architecture is very robust - technically beyond Linux, OpenBSD, & OSX in terms of kernel technology and OS architecture.

Back to MinWin. It is tiny in Vista, as well, but people don't realize that Win32 sits on a fairly small NT kernel technology. If people remember NT (that hasn't changed much) ran great on a 486/33 with 16-32mb of RAM, and this up to the NT 4.0 days.

When they designed NT the HAL (Hardware Abstraction Layer) was under 64KB and today the NT HAL in Vista is still under 256KB, and in XP it is under 150KB. In terms of OSes and kernels - both are still VERY tiny in comparison to other HALs constructs, and very tiny when compared to the massive that is Windows Vista as a whole.

So Windows 7 will be an update version of the same NT kernel that has always been around, just like Vista is, as the NT design is STILL very extensible for many years to come.

Also regarding 64bit, MS has been pretty clear that unless the market has a massive change, there will still be a 32bit version of Windows 7, even though they will try to push the 64bit as the default install for OEMs and Users. With Vista 64bit Microsoft has already made it virtually identical to Vista 32bit, where XP 64bit wasn't quite a full featured or complete. Microsoft has also pushed hard for all hardware MFRs to provide 64bit drivers and ensure their applications are compatible on 64bit in addition to start writing 64bit versions of their applications.

However, by the time Windows 7 comes around, Vista 64bit will probably be the default OS installed for the majority of users, as 4GB is becoming the new 'minimum' RAM configuration for a lot of MFRs, and this means more and more systems will support 16-128gb and also beconfigured with 16gb or 32gb of RAM in high end system in just a couple of years, thus requiring Vista 64bit to use all the RAM.

Even now for users with 2gb or more Vista 64bit is a better choice, as it is faster than Vista 32bit, just due to the 64bit optimizations and the extra 64bit registers and the fact the OS is pushing data around in bigger chunks even if the applications themselves are not, which still makes the OS running under the applications faster and thus provides more speed to the applications.

I really do hope people get the MinWin thing cleared up and stop thinking it is something new, or that Windows 7 is any tighter than Vista, because by falling for that line of thinking you don't get that Vista's NT kernel is already very small, fast and tight, the 'big' comes from Win32/Win64, etc.

Irregardless, I fear the issues with Vista will flow into 7 unless drastic steps are taken.

Kind of like when the Mac OS codebase was getting old and it was finally jettisoned for the BSD based OSX.

with Microsoft bringing out the Hyper-V code, it could be a great time to dump the older code, get something NEW written abandoning the legacy code that is dragging things down and include a "Classic" mode ala Apple.

Code written for this generation of hardware alone mmmmm goodness.

Irregardless is not a word

Irregardless, I fear the issues with Vista will flow into 7 unless drastic steps are taken.

Kind of like when the Mac OS codebase was getting old and it was finally jettisoned for the BSD based OSX.

with Microsoft bringing out the Hyper-V code, it could be a great time to dump the older code, get something NEW written abandoning the legacy code that is dragging things down and include a "Classic" mode ala Apple.

Code written for this generation of hardware alone mmmmm goodness.

Someday NT will be replaced, but what you don't seem to realize is that the architecture and kernel technology are very extensible and rather new in terms of OS theory and OS engineering. So even if MS comes up with a better design, it will probably be several years before it is introduced as the consumer level of Windows.

NT really isn't dragging around legacy code in the way you are thinking, and also you really don't get how NT is designed if you think Apple moving to BSD was moving to the future.

Tehcnically NT is newer and based on newer OS kernel and OS architecture designs than BSD. In fact, when compared to ALL OSes on the market, NT is the newest design since Linux is a modified microkernel version of Minux and OSX is BSD based which goes back beyond before most of us were born.

I suggest anyone interested in NT, pick up a copy of Inside NT or a variation of the book. As it describes the process, and the team that designed NT and what they were working with and working for and how it relates to *nix, VMS and even OS/2 OS architectures and kernel designs.

NT was truly designed by some of the best VMS and UNIX people of the time to be a 'better' OS technology than *nix and a better kernel technology than the standard Mach and microkernel technologies.

As for legacy code, the legacy code in Vista or XP is in the Win32 subsystem, as it is what people think of when they think Windows. NT is strange in that Win32 runs on top of, but separately from the NT kernel underneath it, and NT and the NT kernel APIs handle creating the subsystem environment for Win32 or Win64 to run. Microsoft could throw out Win32 completely and put a BSD compatible subsystem on NT, load X11 and KDE and it would still be Windows NT, but with a *nix Subsystem interface instead of a Win32 subsystem interface as the default subsystem. (In fact Vista ships with a BSD compatible Unix subsystem already, if you have the Ultimate DVD, it is included as Optional Components in the Control Panel and installs a FULL and real BSD compatible subsystem that runs INDEPENDANTLY of Win32. -You can also download the Unix subsystem for Voista for free from microsoft.com)

So ya, the Win32 API is aging, and carries some legacy code, but it is not obsolete and certainly the NT kernel under Win32 is not obsolete nor carrying any baggage or legacy code. If you look at Vista, notice there is the new WPF and other new API sets in the OS that could be split away from Win32, so in theory future applications could run in a separate Win32 API free subsystem as well.

Also back to Apple and their move to BSD. It was a regression, as they were UNABLE to create their own OS kernel and architecture from scratch as they had attempted to do several times in the 90s, and even with IBM's help. So when Jobs came back to Apple, he went with what he had been working with, and that was NeXT and they cleaned up NeXT added in Mac code and dropped it on Darwin which is a BSD based kernel interface to a MACH kernel. Both BSD and MACH are 'old' technologies dating back to the 70s and 80s, and by using them, Apple saved a lot of time and development, but also gave up creating a 'new' OS construct for Mac, and instead is patch up BSD and the *nix model and tyring to put Mac lipstick on it.

BSD and even Linux concepts are already starting to become outdated, and as for moving to a new architecture, Apple is in danger of having to make a giant leap long before Microsoft ever has to leave NT.

Here is a quick example. NT moved the Video driver to kernel mode in 4.0, and back to a hybrid user kernel mode in Vista, and then added in a GPU scheduling driver model that handles Video and games several magnitude above what OS X does and what OS X sitting on BSD will EVER be capable of doing without a major rewrite of many core kernel aspects. With Vista, MS just tacked on the new technologies to NT, and they work without rewriting NT, and they also kept the XPWM (XP Driver Video Model) as well, so Vista can still use XP based video drivers for compatibility even though the two video systems work ENTIRELY different and normally would need to be emulated or a different OS if it wasn't for NT.

The existence of Windows 7 never changed my philosophy of operating system upgrades, especially when it comes to Windows. Upgrades are always inevitable, it drives the industry, it drives consumers and businesses to spend money while also benefiting in the process by making things easier to do or offering new functionality. Also, innovation is a big reason for upgrades and from innovation comes breakthroughs from this we get something thats easier to use. DOS (CLI) > Windows (GUI) 'Breakthrough'

I personally have been aware of Windows 7 since 2000 when it was once known as Blackcomb so, it was definitely expected. Personally, I am an enthusiast so I am always yearning to be on the cutting edge, anticipating the 'what next'. For the average consumer their perspective might be a whole lot different, maybe not, but this does not change the fact that Microsoft is always working on the next version.

Irregardless, I fear the issues with Vista will flow into 7 unless drastic steps are taken.

Kind of like when the Mac OS codebase was getting old and it was finally jettisoned for the BSD based OSX.

with Microsoft bringing out the Hyper-V code, it could be a great time to dump the older code, get something NEW written abandoning the legacy code that is dragging things down and include a "Classic" mode ala Apple.

Code written for this generation of hardware alone mmmmm goodness.

lol yeah irregardless isn't a word. it reminds my of an episode of family guy when stewie takes over the world and says "Anyone who uses the terms irregardless, a whole nother or all of the sudden shall be sent to a work camp."

Windows 7, will be based on Windows Mini core

Mini Win is Windows Vista/Windows Server 2008 based kernel

it will have significant change from Windows vista/Server 2008

and will have almost nothing to do with the kernel code of XP

Who said that they will use mini core? That's just experimental, last time I checked

How many threads about Windows 7 do we really need. It's not due this year, or next year, and possibly not even the year after that. Why prepare for it now making threads about "ohh i should wait for Windows 7".

Windows 7 is about putting ideas together to get ready for the next operating system, so people don't complain about it's delays, and unfinished code, and blah blah blah, all the stuff Vista was bashed for.

Give it up people, there are no pre-alphas, or testing going on, wait until the alpha before discussing Windows 7.

The Good:

Windows 7, will be much more secure

have significant change to the kernel

and 64-bit oriented

The Bad:

people who will migrate directly from XP, will suffer the most!

(just like people who migrated from Win95/98 to XP)

I disagree.

Everything is slowly moving to 64-bit, but alot of people just don't wan't to. For people who use computers just for general home use, probably wont want to spend alot of money going to a 64bit system as of yet, and if M$ are going to push OS updates onto users, then they will be forced to upgrade to 64bit, and won't be offered a 32 bit alt. When I say forced, I mean, as the OS moves on, older 32bit OS's (2000/XP/Vista) support/updates will be unsupported.

And I don't think there will be a 'significant' change to the kernel at this point.

And Secure? Lets hope. Vistas security system is a joke.

I don't nessisarily agree that people who migrate from XP to Win7 will suffer the most, simply because, there wasn't a 'world' of difference between Vista and XP, so there is going to be ALOT of change in 7 to make the migration all that bit harder.

Thats my opinion anyways.

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

    • No registered users viewing this page.
  • Posts

    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
    • Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
    • BATorrent 4.1.0 by Razvan Serea BATorrent is a lightweight, open-source BitTorrent client built with modern C++ and Qt 6, offering a clean, fast, and privacy-focused alternative to traditional torrent apps. It supports magnet links, .torrent files, resume data, sequential downloading, per-file priorities, and even imports from qBittorrent. Power users benefit from integrated RSS auto-download with regex filtering, duplicate detection, and automatic tracker lists from Stremio. Streaming is seamless thanks to auto-detected players like VLC and IINA. BATorrent includes robust VPN tools—interface binding, auto-detection for WireGuard-based services like Mullvad and NordLynx, kill switch, proxy support, and IP filtering. A full WebUI enables remote control, while integrations with Plex, Jellyfin, and Emby automate library updates. With themes, speed scheduling, system-tray alerts, and cross-platform support for Windows, Linux, and macOS, BATorrent delivers a polished, high-performance torrenting experience. BATorrent features: Core .torrent file and magnet link support Resume data — picks up where you left off after restart Import torrents from qBittorrent Create .torrent files from any file or folder Sequential download mode Per-file priority control (skip, low, normal, high) Seed ratio limits with auto-pause DHT, PEX, UPnP, NAT-PMP RSS Auto-Download Subscribe to RSS feeds — automatically download new torrents as they appear Regex filters — match only what you want (e.g. 1080p|720p, S01E\d+) Per-feed settings — custom save path, check interval (5–1440 min), enable/disable Auto-download — matched items are downloaded automatically in the background Supports magnet links, .torrent URLs, and tags Tray notifications when items are auto-downloaded Duplicate detection — never downloads the same item twice Stremio Stremio Addon System pre-installed — works out of the box Auto tracker list from ngosang/trackerslist Streaming Play while downloading — stream video files before the download is complete Supports mp4, mkv, avi, mov, wmv, flv, webm, m4v, ts Auto-detects installed players (VLC, IINA, system default) VPN & Privacy Interface binding — lock torrent traffic to a specific network interface (e.g. tun0) Auto VPN detection — identifies VPN interfaces (tun, tap, WireGuard, Mullvad, NordLynx, ProtonVPN) Kill switch — automatically pauses all torrents if the VPN interface drops Auto-resume — resumes only the torrents paused by the kill switch when VPN reconnects Proxy support — SOCKS5 and HTTP proxy with optional authentication IP filtering — load P2P blocklists to block unwanted IP ranges Protocol encryption (enabled / forced / disabled) WebUI Remote management — control torrents from any browser at http://localhost:8080 REST API with JSON responses Add torrents via magnet link or .torrent upload Pause, resume, remove torrents remotely View peers and files per torrent Dark theme matching the desktop app HTTP Basic Auth with SHA-256 password hashing Configurable port and remote access (localhost vs 0.0.0.0) Interface 3 themes: Dark, Light, Midnight (bat/vampire aesthetic) Real-time speed graph Detailed panel with tabs: General, Peers, Files, Trackers Filter bar: search by name, filter by state (Active, Downloading, Seeding, Paused, Finished) Drag & drop .torrent files and magnet links Drag & drop reorder in torrent list System tray with notifications (download complete, kill switch events, RSS auto-downloads) Splash screen with bat animation Bilingual: English and Portuguese (BR), auto-detected from system locale Bandwidth Scheduler Alternative speed limits — set different download/upload limits on a schedule Time range — configure active hours (e.g. 01:00 to 07:00), supports overnight ranges Per-day control — choose which days of the week the schedule applies Automatically switches between normal and alternative speeds Media Server Integration Plex — automatically trigger library scan when a download completes Jellyfin / Emby — same automatic library refresh via API Configure server URL and authentication token/key in Settings System Cross-platform: Windows, Linux, macOS Auto-shutdown — automatically shut down PC when all downloads complete (60s cancellable countdown) Auto-update system (AppImage on Linux, installer on Windows, DMG on macOS) CLI arguments: pass .torrent files or magnet: URIs directly Keyboard shortcuts: Space to toggle pause, Ctrl+A to select all, Ctrl+O to open BATorrent 4.1.0 release notes: A community-driven release: everything here came straight from your reports and requests. It closes the remaining gaps with qBittorrent and fixes the Windows settings/tray/splash issues several of you hit. Fixed Settings now actually save. A whole class of preferences — speed limits (and the alternative limits), max active downloads, seed ratio, listen port, max connections, DHT/uTP/encryption, VPN interface, kill switch and proxy — weren't being persisted and reset to defaults on every launch. They now round-trip correctly. (Thanks to everyone who reported "the upload limit always goes back to 0".) Splash and tray toggles stick on Windows. Turning off the startup animation (or "close to tray") no longer reverts — the Windows registry stored these booleans as integers and the UI was misreading them. Close-to-tray hint. The first time the window hides to the tray you get a one-time notification, so the app doesn't look like it vanished (Windows 11 tucks new tray icons into the overflow). macOS Dock icon size. The icon filled its canvas edge-to-edge and rendered larger than neighbouring apps; it now uses the standard safe-area padding. Native file picker language. The "Torrent file / All files" filter in the open dialog follows the app language instead of being hard-coded. Added — qBittorrent parity Alternative speed limits toggle — a turtle button in the toolbar flips your throttled limits on/off instantly, independent of the scheduler. Follow system theme — switch light/dark automatically with the OS (Settings → Appearance). Pre-allocate disk space — reserve the full file size up front to reduce fragmentation (Settings → Downloads). Recheck data on add — optionally force a hash check when adding a torrent, so existing or partial files on disk are detected. Port status indicator — a 🔴 dot in the status bar shows whether your listen port looks reachable (UPnP/NAT-PMP + listen state; fully local, no external check). Add torrent from URL — File → Add torrent from URL (Ctrl+U) fetches a remote .torrent and routes it through the normal add dialog. Export .torrent — right-click a torrent → Export .torrent to save its metadata file. Already there (in case you missed it) Watch folder — auto-add .torrent files dropped into a monitored directory (Settings → Files). This release just surfaces it. Incomplete files already carry a .!bt suffix until they finish. Under the hood Regression tests for the settings-persistence and Windows boolean bugs. A new Qt Quick Test harness covering the startup splash and the design-system widgets. Download: BATorrent 4.1.0 | 37.5 MB (Open Source) Download: BATorrent Portable | 51.7 MB Links: BATorrent Website | Screenshot | Changelog Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      163
    3. 3
      PsYcHoKiLLa
      162
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      78
  • Tell a friend

    Love Neowin? Tell a friend!