Live Windows Bootable CDs for Sysadmins
WhoDaresWins writes "Ever wonder how to make a Knoppix-like live Windows bootable CD (or DVD)? Well its now possible using Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD. It's basically an expansion of the Microsoft's own Windows PE (Preinstallation Environment) idea which is a minimal Windows (XP/2K3) based bootable live CD with a command prompt and the ability to run some basic Windows GUI. Bart's PE allows anyone to make a bootable CD using their own Windows XP/2K3 media with Bart's PE Builder. What's more many people have contributed quite a few plugins that allow you to use the BartPE discs as quite a nifty system administration tool and with some work an almost usable quick system."
Read subject.
Like, 8 years ago?
Needless to say, this is good news for Microsoft as it may increase the acceptance of Windows as an alternative to Linux on the desktop ;-)
Way to go MS - stifle creativity, advancement, technology.
I'm choosing to reply instead of moderate, because this is a *huge* pet peeve of mine. I've always thought NT-the-kernel was pretty elegant (especially compared to some *cough* Unix clones).
Actually, the actual Nt_ interfaces *are* documented, but (afaik) incompletely, and without source it's really of very limited utility.
In their quest for One True API (Win32 and now WinFX) they do seem to have killed off all innovation on top of one of their most technically impressive assets.
I had hoped the MSDN academic alliance and shared source licensing would encourage some work, but as long as MS adopts a more liberal download-from-website model for source licenses, innovation on top of the NT kernel is likely to remain a pipe-dream. (When the competition (Linux) is available nicely cross-referenced, you'd have to be crazy to fill out the paperwork for an NT source license.)
Go somewhere random
Lessee...
Only programmers care about that shit, and at least 99% of computer users are not programmers.
I've had managers who wouldn't touch closed-source apps because they didn't trust them and/or couldn't extend them. I've had non-developer colleagues who wouldn't touch closed-source apps because they cost money whilst open-source was a free-download away (and "why pay for something you'll only use once?", and "if it's closed source will people develop plug-ins for it?")
Ah, the joys of being able to choose your own hardward. I told my boss I wanted a beowulf-cluster of SPARC-stations. She laughed at me. Seriously, back in the real-world, some of us don't get any choice about the hardware we use. Seriosuly, back in the real-world most of us don't get any choice about the hardware we use. If open-source software can be stable on the same hardware as a closed-source BSOD-generator, which should I choose?
I run XP at home on the GF's laptop. I've got numerous driver install CDs. Strangely, I never received the one magic CD you hint at, the one with all the drivers for the hardware I've not bought yet. OK, XP comes with a lot of generic drivers, but every new piece of hardware I buy comes with a driver CD for Windows. Strangely, Linux typically "just works".
A. I assume you're joking. Firstly, MS didn't license (eg. with the GPL) their leaked source code, so no one legit will touch it lest they "contaminate" themselves or open themselves up to prosecution. Secondly, it's only a fraction of the complete source.
B.See statements regarding #1.
I've installed very few apps on XP that didn't edit the registry. Sure, I didn't do it by hand - the installer did it, and I pray that the uninstaller will also do it (I live in hope...) Fixinf Registry foul-ups after botched uninstallers run amok terrifies me because like many Windows users I don't feel comfortable editting the Registry. Firing up vim (or Emacs, I suppose...
Yup, a pretty weak troll attempt. Try harder.
This is where the serious fun begins.