Article View: es.comp.os.ms-windows.misc
Article #172Re: Problema de arranque
From: Sherkan
Date: Sun, 15 May 2011 23:15
Date: Sun, 15 May 2011 23:15
46 lines
3245 bytes
3245 bytes
Xavi <x@avi.net> wrote in news:kp90t6dqtef2otrf3hkpq40c087aj52cn5@
4ax.com:
> �Qu� procesos o chequeos se llevan a cabo antes de cargar el SO cuando
> se pone enmarcha el ordenador y no se hacen cuando se reinicia? �Hay
> alguno? Porque ah� podr�a radicar el problema...
Lo que me he re�do con el "*ANTES*" :P
No soy la persona m�s indicada para responder a eso, pero, en principio,
se supone que comprobar� todas las controladoras para detectar todos los
dipositivos, empezando, obviamente, por el procesador y la memoria y de
ah� para abajo.
Aqu� te viene m�s o menos lo que busca/hace:
http://en.wikipedia.org/wiki/Power-on_self-test (como siempre, la
versi�n espa�ola no dice nada)
*-*-*-*-*-*-*-*-*
The principal duties of the main BIOS during POST are as follows:
* verify the integrity of the BIOS code itself
* find, size, and verify system main memory
* discover, initialize, and catalog all system buses and devices
* pass control to other specialized BIOSes (if and when required)
* provide a user interface for system's configuration
* identify, organize, and select which devices are available for
booting
* construct whatever system environment that is required by the
target OS
*-*-*-*-*-*-*-*-*
El punto 4 ser�a pasar el mando a las BIOS de controladoras PCI de
disco, por ejemplo.
Aunque con el �ltimo punto no estoy de acuerdo, pues dice que construye
el escenario de arranque para un sistema operativo concreto y, eso, como
que no. La BIOS es tonta en ese sentido. Prepara la mesa, sea quien sea
el comensal.
--
PGP | /"\ ASCII ribbon campaign
(Pretty Good Privacy) | \ / against HTML mail and
UserID Sherkan | X postings.
KeyID 0x52C4F55C | / \ (c) Black Dragon
Technical Details
Message-ID:
<Xns9EE7CD3C812Aikaruskatakrus@127.0.0.1>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!goblin2!goblin.stu.neva.ru!newsfeed.kpn.net!pfeed09.wxs.nl!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mailReferences:
<nqivs652n9nk9hglt3i4k5ofns1bu838sl@4ax.com> <iqokrl$sti$1@dont-email.me> <h400t613uqljpt6mjmrfdn7mg4vovojdrg@4ax.com> <93ahuoFbu7U1@mid.individual.net> <kp90t6dqtef2otrf3hkpq40c087aj52cn5@4ax.com>Show Full Headers
Complete Article Headers
X-Google-Thread: f4a41,e57e8eb995cfa625
X-Google-NewGroupId: yes
X-Google-Thread: fc6c2,e57e8eb995cfa625
X-Google-NewGroupId: yes
X-Google-Attributes: gid2836922074,gid7a4763d6f1,domainid0,public,usenet
X-Google-Language: SPANISH,ASCII
Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!goblin2!goblin.stu.neva.ru!newsfeed.kpn.net!pfeed09.wxs.nl!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Sherkan <alderaan_bay.SIN.SPAM@SPAM.NO.yahoo.es>
Newsgroups: es.comp.os.ms-windows.misc,es.comp.hardware.misc
Subject: Re: Problema de arranque
Date: Mon, 16 May 2011 01:15:39 +0200
Organization: A noiseless patient Spider
Lines: 46
Message-ID: <Xns9EE7CD3C812Aikaruskatakrus@127.0.0.1>
References: <nqivs652n9nk9hglt3i4k5ofns1bu838sl@4ax.com> <iqokrl$sti$1@dont-email.me> <h400t613uqljpt6mjmrfdn7mg4vovojdrg@4ax.com> <93ahuoFbu7U1@mid.individual.net> <kp90t6dqtef2otrf3hkpq40c087aj52cn5@4ax.com>
Injection-Info: mx03.eternal-september.org; posting-host="p8VXdSoiSqOUyMVSDpZQpA";
logging-data="26864"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+aLkWqyFwE8yeeF2kr3/cG"
User-Agent: Xnews/5.04.25
X-Face: Qet(hYxJ4wN\5Rl3Mfy6#1,hTv3Cc16^Q#1(u4kMa|N`dAZ"|oaff)6,CRf~:m'5qR=h/6r4%jXm9k~~{dX{W_.6Dmm)/T5T4>kus7?bPUSRb+qf^tg&{4bJTO<;dNB*H$g^^':>N2;`a-~7>B%)x5M8mVC;Qy\p5eT75&'m??B
Cancel-Lock: sha1:blby16m4AmaOF37lFadzoTwtcXM=