Recommended Posts

This is so typical of Microsoft. They continue to use older technology and simply slap an (arguably) prettier face on it. Forget about the Intel Mac's - this is simply Microsoft deliberately holding people back from the future. We've all waited nearly 6 years for Vista - the very least Microsoft could do it use technology that isn't two decades old. It's pathetic.

And can someone please clear something up for me; is it just the Longhorn Server that won't support 32-bit machines, or Vista as a whole?

If anything, MS wants Windows on Mac's, that then increases their market share to PC and Mac users, making them more money.

Exactly what I was going to say. :yes:

And I care why ? Vista sucks anyways. I can assure you vista will cause people to move to mac. Apples move to intel doesn't exactly help Vista in anyway either. I personally made about 20 people switch to OS X in the past week or so. Is this huge, yes, yes it is. Why is this huge to me? Thats 20 people that are stuck in the s**t hole know as Windows. They can do everything on a mac that they can do on a PC, but in a more productive, less stressful enviroment. Now this is just indivdual users. I have made two small businesses switch aswell. So far, they love it. One is even buying me a MacBook Pro, which should be here soon. So what do I say to Microsoft killing the EFI support? Idiots, instead of slacking, start working. I know developers on the Vista team that agree Vista is crap, also Paul Thurrot, which I had a mini interview with while playing COD2 on 360, agreed that Vista is complete s**t from the ground up.

/end rant.

Sorry about that, a bit offtopic but I am totally chocked at Microsoft lately, it's constant cut this, cut that, take to much time and get no where crap. What has Vista done for Windows? Nothing! It's just XP with some pretty graphics and a side bar, and oh ya, that annoying, CAN I OPEN CONTROL PANEL, PERMIT, ALLOW, crap! ITS CONTROL PANEL, YOUR OWN APP!!!, JESUS CHRIST!111! Not to mention you can disable that, which, well, can be disabled with a batch script. Doesn't that render that pointless? If CMD is enabled, a batch can run... That service can be disabled, now a virus or malicous software can run. Wow nice and secure Microsoft (Y).

This is definitely political. They want to push WMP 11 and are afraid that dual booting macs would take away from potential market share in music sales as people would have access to a fast native version of iTunes in OS X and games through booting into windows.

I know of several people who would have bought macbooks and only booted into Vista to play games.

There is still hope of an OS X port of cedga for games and darwine X86 for applications. You could always run apps in a virtual environment. Here's hoping for VMware on OSX soon.

this is pretty depressing how they can't get it to work.....i mean it didnt take that long for tiger to do it..

I guess you missed this part:

It is responsible for initialising hardware in the PC, and importantly, device drivers are stored in the EFI flash memory rather than being loaded by the operating system. It is a major change for the PC industry and both PC makers and Microsoft have been slow to make the switch. Because the Apple Intel Mac platform is entirely new, it does not have any legacy support concerns.

I guess you missed this part:

I guess you missed the part where Apple switched from Bios to EFI between 10.4.3 (intel transition kits with bios) and 10.4.4 (Intel Core Duos with EFI)? Apple was able to quickly switch over.

They could have included drivers and bootloader for both and installed the appropriate on during installation.

I guess you missed the part where Apple switched from Bios to EFI between 10.4.3 (intel transition kits with bios) and 10.4.4 (Intel Core Duos with EFI)? Apple was able to quickly switch over.

They could have included drivers and bootloader for both and installed the appropriate on during installation.

haha that's exactly what i was going to say :p

Besides dual booting OSX, EFI have numerous advantages for users (PC users) such as faster booting, system independent drivers, etc.

MS simply will launch a feature incomplete OS just not to slip the 2006 release date without this one & some others.

This is just disappointing :(

IMO all fundamental features like EFI, WinFS should be in inital release; not to come with a service pack later.

Service packs should be just for bugfixes, improve stability & maintenance...

Besides dual booting OSX, EFI have numerous advantages for users (PC users) such as faster booting, system independent drivers, etc.

MS simply will launch a feature incomplete OS just not to slip the 2006 release date without this one & some others.

This is just disappointing :(

IMO all fundamental features like EFI, WinFS should be in inital release; not to come with a service pack later.

Service packs should be just for bugfixes, improve stability & maintenance...

Service Packs shouldn't have to exsist.

I had written a blog entry for the story but I am more dissapointed in both comapnies. Also Microsoft is not all to blame as OS X also uses a custom implementation of EFI and Im sure they are being less than forthcoming for details.

What has Apple to do with the fact Windows Vista won't boot natively on any EFI system?

People are forgetting one thing in the "OSX has it, why not Windows?" argument. That OSX is designed to run on a fairly minimal amount of hardware, where as Windows is designed to run on every possible configuration of computer... old or new.

I was quite looking forward to this EFI stuff, although I know little about it.

People are forgetting one thing in the "OSX has it, why not Windows?" argument. That OSX is designed to run on a fairly minimal amount of hardware, where as Windows is designed to run on every possible configuration of computer... old or new.

I was quite looking forward to this EFI stuff, although I know little about it.

Yes, but to support a wide range of hardware, you normally have to support things, not remove support for them. :p

there is nothing stopping Windows from supporting EFI and classical BIOS, this just means Vista wont run on native, EFI only (no CSM) systems.

is anyone getting these error messages? its driving me nuts!

when i click on a post on the home page it redirects me to this:

IPB WARNING [2] Invalid argument supplied for foreach() (Line: 3525 of /sources/ipsclass.php)

then nothing.

so i have to go to the message boards and this is at the header:

IPB WARNING [2] Invalid argument supplied for foreach() (Line: 3525 of /sources/ipsclass.php)

IPB WARNING [2] Cannot modify header information - headers already sent by (output started at /home/neowin/public_html/forum/init.php:269) (Line: 445 of /sources/classes/class_display.php)

IPB WARNING [2] Cannot modify header information - headers already sent by (output started at /home/neowin/public_html/forum/init.php:269) (Line: 446 of /sources/classes/class_display.php)

IPB WARNING [2] Cannot modify header information - headers already sent by (output started at /home/neowin/public_html/forum/init.php:269) (Line: 447 of /sources/classes/class_display.php)

People are forgetting one thing in the "OSX has it, why not Windows?" argument. That OSX is designed to run on a fairly minimal amount of hardware, where as Windows is designed to run on every possible configuration of computer... old or new.

I was quite looking forward to this EFI stuff, although I know little about it.

Then forget about OSX and talk about Linux, which runs on far more hardware architectures than Windows and supports EFI.

Running on more hardware is certainly not the reason why they're dropping this feature.

Call me crazy, but I think this is all politics.

I think this has something to do with the Intel Macs and the fact that many people were going to purchase them only because they could run both OS X and Windows.

Does anybody else feel like this is just a stab at Apple from MS? It seems so... Before, MS had every intention to do it, then the craze set in that people would be able to run Vista on their shiny new Intel Macs, and now MS isn't going to support it...

Strange, very strange.

Exactly what I was thinking! The people who were waiting since a long time to get an Intel Mac was so that they can dual boot.. if they did not care so much, they could have gotten an iBook or a Powerbook. They want Windows and they know it. This will hurt Apple's business a little bit imo...

I don't know if anyone mentioned this already, but I believe Vista, and XP64, and possibly Server 2003 already or will natively support booting with EFI on 64-bit chips. The problem is that the Mac implementation boots with a 32-bit chip, so it isn't as much as Vista scrapping or not having features as it is that the Mac isn't using 64-bit chips.

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

    • No registered users viewing this page.
  • Posts

    • VS Code 1.123 introduces massive upgrades for persistent AI developer workflows by Paul Hill Microsoft has just released Visual Studio Code 1.123 alongside its annual developer conference, Build 2026. This release, as always, has a heavy focus on advanced AI agent integration and making the built-in browser more robust. Notably, this update brings big sync changes that keep your AI agents persistent across sessions. With this update, VS Code now supports cross-machine syncing for chat histories, touched files, repository contexts, and related PRs via GitHub accounts, tying users even more into Microsoft’s developer ecosystem. This update also introduces the new /chronicle command that allows you to query past sessions using natural language, generate instant standup reports, and get personal productivity insights. Microsoft has also made some improvements to network-dependent operations, it explains: “When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.” Microsoft has not stopped there; in this update, it also allows developers to drag, drop, and pin multiple agent sessions side-by-side for easy code comparisons in real-time. It also introduces the Research Agent, accessible via /research. This is a read-only, depth-optimized tool that gets data from the web, local codebase, and GitHub to give you a Markdown report on complex APIs or unfamiliar code. Now, let’s talk about the integrated browser and some security enhancements. VS Code 1.123 features enhanced screenshot capture tools that allow for targeted Area Screenshots and Full Page Screenshots to send layout context instantly to AI chat. The address bar has also been revamped, supporting favorite pages and tab management. Finally, on the security front, this update introduces a safety-first two-hour delay on third-party extension auto-updates to safeguard against compromised or buggy releases. This release is now available for Windows, Mac, and Linux. If you have VS Code, keep an eye out for the update availability notification. If you still don’t have VS Code, you can get it here.
    • I'm hoping with the Surface Pro 12, I can use either USB-C for my Xreal One Pro glasses. With my Surface Pro 11 OLED X Elite, I have to plug them into the top port. The bottom port will power it, but nothing shows on the screen. Maybe it's my setting. When I plug in the glasses, I have it output only to the glasses. So maybe I need to turn on both displays with it in the top port, then switch the glasses to the bottom port and set it to output only to the glasses. And then hopefully Windows remembers the settings for either the top port and bottom port (one of the awesome features of Windows where it remembers the exact configuration when plugging in external monitors.
    • Forgive my ignorance, but the only difference I see here is that a USB-A is now a USB-C, so there are two of them. For the modern age (and I'd argue since 2020), most products would now come with USB-C as an option, if not the default. Display, charging, devices, etc on TWO connectors, sometimes all combined! So having 2 of those powerful ports is great for something this size! Meanwhile my Surface Pro (5) has a single USB-A port which I cannot even get display out to, instead relying on some Surface Connect dock which I don't have. That is a poor experience, not to mention expensive and not compatible with other devices. Thank God USB-C is mainstream!
    • wow. that color finally comes to Surface Pro. was always a little jelly when a friend had the sandstone Surface Laptop. I wonder how different this dune is from the sandstone. I'll be getting the dune version. always thought black and platinum were a little boring. I'll still have access to my blue Surface Pro 11 as it'll be a hand-me-down.
    • Looks a very subjective aren't they!? I like its simple design. I love the way Apple designs their products with function over form, minimalization, and simplicity over cluttered complex designs. Many, not all, of their products follow this trend, and the device becomes a tool rather than dominating the space. I do not however like their OS. I have never bought a Apple product, and while I'd consider the Neo for my wife, I am hoping there are better alternatives out there when her failing MacBook Pro 2017 finally stops. Fischer-Price is famously plastic, garish, and poorly made. Basically you're describing the Window Laptops the Neo competes against! This is how product design should be, and what Apple have often followed in recent years: https://tenprinciples.design/
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      227
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      60
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!