Boot Windows Faster, Using Linux 369
BiOFH writes "TechNewsWorld is reporting that InterVideo has a solution for slow boot times runing Windows XP MCE. 'The new Linux-based InstantOn software -- designed to help Windows XP Media Center Edition PCs boot more quickly -- is aimed at taking advantage of the power of Intel's Pentium processors, not at fixing fragmented hard drives. The software integrates into the computer's BIOS and the operating system.'" According to this article, the software uses a small Linux partition on the user's hard drive. I wonder how BIOSes with hard-wired Microsoft-based DRM would cooperate with this scheme.
i want fast pre os booting! (Score:1, Interesting)
Everytime the stupid bios checks the whole system if there is new Hardware, oh and of course every sata or raid controller have to do the same
I wish there would be a fast option which just save your settings one time and when you dont boot with a special key it just skips all the rubbish i dont care about.
troll? maybe
Re:New MS BIOS source code leaked! (Score:5, Interesting)
Windows is already faster than linux (Score:4, Interesting)
Meanwhile, my shiny new RHEL 3.0 box isn't mounting NFS filesystems on boot because the network hasn't finished initializing yet. Apparently it takes the network about 30 seconds to come up. Wonder if that's a gigE thing. :(
The makers of LinDVD (Score:1, Interesting)
Someone should really ask them [mailto] when LinDVD will be launched to the public. It sounds like a more stable player than Xine/VLC/Ogle/mplayer
Seems to work, they've had it shipping on IBM Linux Laptops [intervideo.com] for a while.
This isn't the solution to the problem... (Score:5, Interesting)
Re:Vaporware! (Score:-1, Interesting)
Re:Vaporware! (Score:3, Interesting)
Maybe I'm just ignorant, but I really doubt you can show me a live CD that can hand off to an installed Windows.
Furthermore, live CDs, while great, are not the solution to slow boot times.
And just cause it's related, I set up my VectorLinux (with kernel 2.6.1) to boot right into KDE, and timed it against Windows XP (on the same computer, so there's no hardware advantages). From pressing enter in Grub to being inside the WM, Linux won by about 15 seconds.
Re:Common sense (Score:1, Interesting)
Rundll32.exe advapi32.dll,ProcessIdleTasks
It's supposed to run every few days when your computer is idle anyway. Personally, I prefer Raxco's PerfectDisk [raxco.com] which can handle this boot file defragging itself. BootVis is useful for figuring out the bottlenecks in your boot though.
Re:Common sense (Score:3, Interesting)
The bootvis page explicitely says that it's a poor choice of a tool by end users for improving boot times. So, um... what do you use it for that makes you impressed with it?
It impresses me by shaving significant time off boot times. However Microsoft describe it bootvis can do a lot, depending of course on how fast your boot is already and the factor that is slowing it down. If you load a lot of services at startup then bootvis is a great help.
Or didn't you realise that what Microsoft say, and what actually happens aren't always the same?
Bad Benchmarking Screwed up Windows Design (Score:5, Interesting)
Lo, and behold, more and more initialization work for Office, and then IE, started showing up in the Windows boot sequence.
Merging applications into the OS is BAD DESIGN, but it won the poorly thought out benchmarks that many organizations used to select their "productivity" tools. Now Windows, and Windows users will pay the price. Serves them right.
Sure, leave your Windows machines running 24/7 to avoid the boot delay. Linux and OS X users have that option too, but for them it is truly an option, not something they NEED to do.
Re:New MS BIOS source code leaked! (Score:4, Interesting)
Now consider the scenario where BIOSes get bigger. Remember that BIOSes are on a chip, which makes them damn hard for normal home users to replace or modify. If some DRM crap gets put in there, it's nearly impossible to remove. Now that's the part that's scary. The BIOS might refuse to boot unrecognized OSes, in which case you're SOL. But if it's the OS that's handling DRM, well, someone will have a crack for it a week before the OS comes out. Or you can uninstall the OS and run one without DRM, like Linux. Or you can install Linux and write some DRM software. Or whatever.
Re:New MS BIOS source code leaked! (Score:5, Interesting)
LinuxBIOS project has the right idea by ideally cutting out as much cruft from the system firmware as possible and leaving it up to the OS to perform initialization, but in reality some tasks are forced onto the firmware by design.
Fujitsu Lifebook (Score:4, Interesting)
The only downside is the screen is very small so if you're at all far sighted, it's hard to read. Not a problem for her so she's happy.
Re:Memory images on disk (Score:4, Interesting)
http://www.eros-os.org/project/novelty.html#persi
There's an interesting story regarding Novell there. Anyway, that OS would take snapshots of the entire memory state every N seconds so that even if you pulled the plug out of the wall while the machine was running, you'd be back up to where you left off (minus some seconds) as it simply reloaded everything from disk again.
MS already has their own BIOS.. (Score:5, Interesting)
If MS was to start producing BIOSes, which Im sure they could do, they would have to maintain compatability with the existing BIOSes of the world.
There are pleanty of things that are not MS OSs that use the BIOS. Ghost. PXE. DOS before Netware (do they still do this?). Recovery CDs. And of course the OSS OSs.
I have no idea how much the license for something like Phoenix BIOS costs. Less then a dollar per mobo, Im sure. Lets say that MS starts giving away their BIOS: How many PC hardware manufacturers are going to switch, to save pennies, at the risk of no longer making PC hardware? The hardware world has settled on using industry standards a long time ago. Not even MS can change that.
Re:Bad Benchmarking Screwed up Windows Design (Score:4, Interesting)
In a character mode system you can put a prompt up for the user almost immediately. You don't actually have to be ready to process his input yet, just grab keystrokes. You finish initialization while the user is still thinking and typing. You don't need to initialize memory at all. Unless your code is buggy to begin with and you need zeros there for debugging, allocate space as needed and allow it to start out random. I know most modern systems don't do this, but it's been done.
GUI systems are of course a lot more involved. Can the part of the system that draws the screen and all the icons be isolated so as to get that up before loading all the common elements from Internet Explorer, Word, etc (and NO, they don't show up as separate entries on the task list!)? Yes, they probably could, but as those components get more and more bloated they each have their own initialization requirements.
I'm quite sure people at Microsoft don't sit around twiddling their thumbs and TRYING to make the system less efficient. They DO have a vested interest in making ordinary PCs less and less desirable each year so that the hardware upgrade cycle needs to continue. Every new version of Windows has a larger memory footprint and that has to do with putting more and more stuff on the critical path between turning the system on hand handling that first mouse movement.
I was doing my OWN benchmarking of these systems during the NT 3.5-4.0 timeframe and I DO know what I am talking about.
Re:The makers of LinDVD (Score:1, Interesting)
I don't know if it's significantly better than the alternatives though. The GUI looked like their old WinDVD 2000 program from '99.
Re:Vaporware! (Score:3, Interesting)
I'm afraid I've been feeding a troll who came in yelling "moron," but who clearly has never measured current draw of computers in various states.
If the computer consumed no power how would it be possible to Wake-on-Lan and/or without a full software reboot.
Any form of "Instant On" is using some power for something somewhere. There aren't little power pixies hiding in the machine to take care of these things.
For most people these little bits of power dribble are irrelevant, but if you're out in the middle of an ocean (or even a larger lake) on a small boat with no engine, completely dependent upon sun, wind and muscle for electricity generation you learn to completely disconnect anything you aren't intending to use for awhile.
KFG
Apple (Score:2, Interesting)
Re:Vaporware! (Score:3, Interesting)
Your may very well be right, but what exactly is the 2 or 3 watts used for when the computer is powered off? I can put my (fairly new) Linux-laptop into hibernation (writing all memory pages to disk and turn off), remove its battery and go mountain climbing for a week. It will still power up and recover quite nicely. Of course the battery to keep the clock running is there, but in my experience it uses a great deal less than 2 watts, as it might be powering the clock for years. Same goes for my workstation. I have a good'ol AT power supply which physically turns the power off with the power switch. Doesn't consume a single watt from my power lines, to my knowledge.
Come to think of it, newer motherboards than my workstation has LEDs on them, but I can't imagine them to consume more than a few milliwatts.
Re:Apple (Score:2, Interesting)
But, to sort of answer your question in a half-assed way, it's my understanding that there is a lot going on in the boot ROM, instead of from disk, that speeds up a New World Mac's startup.