File size

File size

File size

What happens, exactly, when you turn your computer on? Yeah, you see the black screen and words scroll by, then, finally, the Vista startup sound... But, there's a good deal of code that runs in this preOS environment, much of it composed in languages
you've probably never written (like 16-Bit Real Mode code). What does the BIOS do, anyway? Why do we need a BIOS? Vista can run without a BIOS: It supports UEFI. What's UEFI, anyway?

This is a rare interview with some of the developers nobody sees during the day (), who live and breathe in the preOS space (this is the single threaded world of pre-operating system start-up context where there is no memory manager, no object manager, no
kernel period - it takes highly skilled developers to write code in this memory confined space, the land of real mode code and the BIOS).

Meet Jamie Schwartz, Development Lead, Windows Kernel Dev team, and Andrew Ritz, Development Manager, Windows Kernel Dev team. They tell us all about the wonderful world of preOS. Enjoy.

Got a couple of questions:- Why do we have to create a dos floppy to flash a bios?- Is EFI now supported or not in Vista?- Are there any motherboard manufacturers that are going to ditch the bios and put EFI on it?- Can I boot to Linux using the Vista bootloader (without using a Linux bootloader)?

Like with my skillset, I'm seriously considering wether there's any opportunity for someone like me, creating "addons" to WinRE, or perhaps convincing them into allowing some kind of addon API.

Now a direct question for Jamie/Andrew.

I ran into an issue a couple of days ago which I thought had been fixed since Windows 2000 sp2. That is 48-bit LBA on ATA (IDE) Hard disks.

In this case, there was an existing Windows 2000 Server where the Admin needed to setup a parrallel install of Windows on a second D: volume. Now this was a 250MB basic disk volume, and was ~60-70% full. The Admin booted off his Windows 2000 sp4 CD (slip-streamed)
and proceeded to through the text-mode setup, installing to D:\WINNT. Upon reboot, entering what should be the 2nd stage, GUI part of the installer, you get a BSOD and a message about D:\WINNT\SYSTEM32\NTOSKRNL.EXE being missing.

Upon my investigation, it became apparent that NTOSKRNL.EXE was well beyond the old 28-bit LBA limitation (~128GB point). But I wasn't able to investigate any further, due to urgency. Is this likely an issue of a bad service pack integration of the Windows
2000 Server CD. That is, the CD was still using the old, pre 48-bit LBA IDE/ATAPI driver(s) ?

PS: I side-stepped the issue by resizing and moving the partition up, leaving a 2GB partition at the start of the disk for the new parallel install.

Thank you for this video i was dreaming of it this weeks end and here it is

Just a few notes here.

Vista does NOT run on PowerPc, Mac have switched from PowerPc to x86 and that is why it can run on them.Some early edition of Windows NT worked with PowerPc but it was never releasted to the public i belive.

ZippyV wrote:﻿Got a couple of questions:- Why do we have to create a dos floppy to flash a bios?- Is EFI now supported or not in Vista?- Are there any motherboard manufacturers that are going to ditch the bios and put EFI on it?- Can I boot to Linux using the Vista bootloader (without using a Linux bootloader)?

Yes Vista supports loading from EFI.Yes the bios is beeing ditched VIA and other chip manufacture are working on EFI's to go into pc motherboards as we speek (type).

The grate thing about EFI is that you can have it use hardware better alowing to run the hardrive at full speed on boot up, but sound like the Vista bios bootloader partialy is cabable of this.

I would think that most mainboard vendor's will take the hybrid (EFI - BIOS) approach as they can't be sure the person who purchases their MB will have the necessity to boot Linux (or some other OS) along with Vista.

I would guess this because I am assuming a strictly EFI approach (at least currently) will not allow Linux to boot. Is this assumption correct?

We have a product that has its own boot code, which pre authenticates the user before allowing boot. Is possible to hook in some form of authentication into the boot loader, other than from a keyboard menu item at the pre boot time, say from a USB device or
user name and password or other devices, X509 Certificates ? etc.. this would really help our development onto vista? without having to use bespoke boot code?

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums, or
Contact Us and let us know.