Windows 7 to add native support for Virtual Hard Disks


Recommended Posts

  Tom Servo said:
And booting from VHDs? What's the point? Windows ****s all over itself if main components like mainboard chipset or CPU change (the emulated environment in a VM is a different one than your real one). Not to mention the funky performance loss on disk IO due to NTFS -> VHD -> NTFS, especially with Windows' ****ty IO scheduler.

Riiiiight... the IO scheduler that Linux has taken over a decade to come close to catching up with. Uh huh.

I swapped out a motherboard + CPU a few weeks ago on this very system. Vista had absolutely no problems detecting the new hardware and booting up just fine. On my Macbook I can boot between VMware and the native partition via BootCamp, and have no troubles at all.

  Brandon Live said:
Riiiiight... the IO scheduler that Linux has taken over a decade to come close to catching up with. Uh huh.

Yeah, right, the Windows SCAN scheduler is the pinnacle of IO scheduling. Go away.

  Brandon Live said:
I swapped out a motherboard + CPU a few weeks ago on this very system. Vista had absolutely no problems detecting the new hardware and booting up just fine. On my Macbook I can boot between VMware and the native partition via BootCamp, and have no troubles at all.

I switched mainboard and CPU too a few weeks ago, coincidentally. Vista however decided to do a boot loop. That did really help, so much for that. And I didn't even change CPU architecture, e.g. from Intel to AMD or the other way.

  Long said:
Maybe not so impossible.

I've already posted that this driver is available since quite some time now. That screenshot means exactly squat.

  Quote
New Features in Virtual Server R2 SP1

VHD Mount Command-line Tool and APIs

Provides the ability to mount a virtual hard disk file (.vhd file) as a virtual disk device on another operating system.

http://www.microsoft.com/technet/virtualse...vsoverview.mspx

  Tom Servo said:
Yeah, right, the Windows SCAN scheduler is the pinnacle of IO scheduling. Go away.

Yeah, because you obviously know so much about how NT works.

Seriously, don't most Linux systems still lack I/O prioritization? Cancellable I/O? Last I recall they still don't support propogating I/O completion tasks to user-mode threads, either.

I was mainly talking about how far behind Linux used to be, before the 2.6 kernel, or before AIO started to become adopted. Things seem to be more evenly matched, these days.

  Brandon Live said:
Yeah, because you obviously know so much about how NT works.

Then tell me how the scheduler works! You're always telling me I'm full of myself, yet never spill the beans to actually correct me. Until then, I rely and believe what I find elsewhere, and they tell me it's a crappy SCAN algorithm.

  Brandon Live said:
Seriously, don't most Linux systems still lack I/O prioritization? Cancellable I/O? Last I recall they still don't support propogating I/O completion tasks to user-mode threads, either.

I was mainly talking about how far behind Linux used to be, before the 2.6 kernel, or before AIO started to become adopted. Things seem to be more evenly matched, these days.

How would I know? Does it look like I'm a Linux user?

But seriously, Linux comes with prioritization and cancellable IO. Who the hell knows about completition tasks, ask an actual Linux user. But hey, good job picking arguments that are completely silly, because it took the release of Vista for Windows to get the stuff you're holding against me as an argument. Linux had at least the two things I mentioned around Vista's release timeframe already.

  doncoyote.cl said:
... and Microsoft promises this... and then promises that... and then the promises are not accomplished

The same story over and over again.

Let's see the final product, then we talk.

-Rodrigo

You do know this is an advert for employees not a "LOOK HOW SHINY THIS IS!" thing, right?

  zer0l0gic said:
Sounds great. But, we should all take a deep breath, remember all the promises of Vista?

So, if Microsoft delivers. Top marks.

  doncoyote.cl said:
... and Microsoft promises this... and then promises that... and then the promises are not accomplished

The same story over and over again.

Let's see the final product, then we talk.

-Rodrigo

Microsoft isn't promising anything. Read the article.

  Quote
I have a nice hat that you might be interested in... it's made from tin foil!

lol

VHD native support would be a more than welcome addition.

Also the virtual drive or disc for mountin disc images would be great. Or at least native support for creating virual folder that run on ram.

Um, isn't that a feature that was supposed to be in Vista already? I remember I read somewhere that Vista will have the ability to mount vhds that are used by Virtual PC.

Later when I got my hands on Vista, I was quite frustrated when I found out it didn't work.

This is just one of the features that should have been in Vista, and now is coming in the next version.

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

    • No registered users viewing this page.
  • Posts

    • Going to quote myself from a comment I made to a related article: It's not about the OS, it's about the workflow. OS fans consistently miss this. People have work to do and they've invested a lot of time, effort and even money building their workflows. It's expensive to change, so that change has to offer real benefits that compensate for the cost of updating workflow and sorry, Win 11 just doesn't. Win 11 breaks workflow in weird and pointless ways seemingly either to dumb down the OS (with the same results as we saw when MSFT tried to dumb down Office's menuing system with "SmartMenus") or make it look more like macOS. MSFT seems to have completely lost the basics of UI/UX like FITS and muscle memory in Win 11. If they had made these optional - then sure, but they aren't. That's the same reason most users won't just jump to an entirely new OS - which has an even bigger workflow cost - until there's just no other option. Not only is there the core workflow cost, but the cost of finding new parallel software for the new OS, transferring and possible converting files and dealing with incompatibilities and then redeveloping workflows. It's just not as simple as "switch". And now there IS another option, stay on Win 10 for another year and pray for Win 12 (much as Win 7 users did with Win 8 - which happened when Win 10 came out).
    • At least that album was really good. I don't know if F1 was $200 million well spent yet...
    • PC manufacturers used to trick BIOS copyright strings to get full editions of trial software by Usama Jawad You may have noticed that when you purchase a new PC, it comes with certain software pre-installed. Sometimes, when you open this software, it activates, and you receive the full version of it without paying any additional cost. This is because that PC's manufacturer is a licensee of that software and the fact that a customer gets the full version of a trial software for free serves as a perk for potential buyers. However, many PC manufacturers tried to trick this process in its infancy. During the days of Windows 95, when the Plug and Play specification was still in development, the OS' engineering team was trying to figure out ways through which it could identify PCs that existed prior to the inception of this specification. To that end, one of the methods they tried was searching for copyright strings and firmware dates in the BIOS. Through the course of this investigation, they discovered a rather oddly named copyright string "Not Copyright Fabrikam Computer" in a PC that was actually manufactured by Contoso. In this case, both Fabrikam and Contoso are fictional names that are used to describe this scenario without revealing the actual identity of the OEMs involved. Microsoft engineer Raymond Chen explains in a blog post that these odd copyright strings were actually appearing because Contoso PCs contained a trial version of a software and the company wanted the full version to be activated for customers even though it was not an official licensee. In order to bypass the costly licensing process, what the firm did was that it added the following text to its copyright string: "Copyright Contoso Not Copyright Fabrikam Computer". The trial version of said software would search for the string "Copyright Fabrikam Computer" and end up finding it within the substring of the convoluted copyright string mentioned above, accidentally activating the software's full version. While more robust ways were adopted later to avoid this problem, it's certainly interesting to see that OEMs would go to this length in order to distribute software that they are not officially allowed to. Well, as they say, the past stays in the past.
  • Recent Achievements

    • First Post
      Myriachan earned a badge
      First Post
    • Week One Done
      DrRonSr earned a badge
      Week One Done
    • Week One Done
      Sharon dixon earned a badge
      Week One Done
    • Dedicated
      Parallax Abstraction earned a badge
      Dedicated
    • First Post
      956400 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      615
    2. 2
      ATLien_0
      227
    3. 3
      +FloatingFatMan
      170
    4. 4
      Michael Scrip
      166
    5. 5
      Som
      148
  • Tell a friend

    Love Neowin? Tell a friend!