You're right about the core OS, of course. What I didn't make explicit was that I was talking about the underlying hardware design that has been shaped as much by the popular operating systems as it has shaped them. So we don't have automatic redirection/copy of POST and boot data to a serial port at power on (As well as listening at them) as a common standard for x86 PCs.
That still wouldn't make the job of remote BIOS update child's play, but it would increase the remote management and troubleshooting options quite a bit. ----- Original Message ----- From: "Nick Palmer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, 2002-10-14 09:46 Subject: RE: Bios access > With respect, I think that's overstating the case a little; NT has always > had a multi-user-aware kernel, and this has been taken advantage of since at > least 3.51 (by NTrigue) through 4 (Terminal Server Edition), and where the > issue of BIOS updating is concerned, Windows isn't really the issue. The > problem would be the same whether the box was running Windows Whatever or > Linux or any other OS; the BIOS is inaccessible from a remote location > before the OS (and thus the VNC-or-whatever server) has loaded. > > Nick Palmer > IT Manager > > > > > -----Original Message----- > From: Alex K. Angelopoulos [mailto:[EMAIL PROTECTED]] > Sent: 14 October 2002 15:23 > To: [EMAIL PROTECTED] > Subject: Re: Bios access > > > This is still an "undiscovered country" as far as I'm concerned. I think a > big fundamental issue here is PC history; its only with the far-end of Win2K > that we've started seeing Windows dealing with the concept of users not > being on-console. > > I've had a lot of success with using WMI for _checking_ things; an actual > flash is out of the question via WMI, unfortunately. > _______________________________________________ _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
