Newsgroup: it.comp.hardware.cpu
Titolo: nuova cpu

sono quasi sul punto di acquistare una nuova cpu da installare sulla be-ma 
asus A7V600-X in seguito al
probabile decesso del barton xp 2500+ .... dico probabile perchè non ne ho 
la matematica certezza....
(sarà catalessi?) ma dico probable anche perchè quando accendo il pc le 
periferiche vengono controllate
anche se il monitor però rimane spento.....ed ovviamente non escono fuori le 
schermate del bios....
ho optato per l'acquisto di un amd barton 3000 fsb 400 trovato su 
ebay.....ma se anche la be-ma fosse rotta?
chi mi consiglia qualche altro test da fare? 

 chi mi consiglia qualche altro test da fare?
per prima cosa prova un altro alimentatore ..
poi testa la vga ram ecc su un altro pc.. e poi ne riparliamo...ripeto
dubito sia la cpu bruciata... 

 hai provato un clear cosmos?
sarebbe il reset con i jumpers?

 sarebbe il reset con i jumpers?
si
la prova di un altro alimentatore l'hai fatta?

ho provato a sostituirla non succede nulla....
Togli del tutto la sk video, la sk madre deve cominciare a bippare
come una pazza
Da mia esperienzxa quando non c'è nulla a video al 75% è andato l'ali
e di situazioni come la tua dove ventole e dischi partono ma non si
accende il sistema me ne sono accaduti molti, nel restante dei casi la
colpa è stata della ram.

 Da mia esperienzxa quando non c'è nulla a video al 75% è andato l'ali
quoto.. è per questo che insistevo sulla prova alimentatore..

 quoto.. è per questo che insistevo sulla prova alimentatore..
e se fosse dipeso da un virus? 

 e se fosse dipeso da un virus? 
un virus che non ti fa piu' accendere il computer facendoti rimanere lo 
schermo tutto nero al bios? Azz.. se conosci un programmatore in grado 
di fare una cosa del genere.. fammelo conoscere:)

 ha scritto nel messaggio 
news:dacgre$16r$1...@area.cu.mi.it...

non ci sono virus che attaccano il bios mettendolo ko? 

 ha scritto nel messaggio 
news:dacgre$16r$1...@area.cu.mi.it...

subito:
http://www.citynotebookcentre.com.au/vendors/anti-virus/virus_cih_chernoble.htm
................
Software cannot damage (well-designed) hardware. About the worst payload 
that most people imagined was a complete hard
drive reformat.
......................
This was the naïve view. Fortunately, it was also what we saw in `everyday' 
viruses. The afternoon of 25 June 1998 changed
our view of things.
Late that afternoon, our worst fears were confirmed. The payload of a virus 
Sophos had received from a US customer a few
days earlier was designed to, and could successfully, overwrite part of the 
BIOS code stored in common Flash BIOS chips.
At that time, the virus was indisputably in the wild. In fact, one of its 
variants made it onto the July 1998 WildList! Several
anti-virus developers that VB staff were in regular contact with confirmed 
receiving samples of at least two variants from
customers. Across those contacts and from samples sent to VB, field reports 
of all four currently known variants that have the
BIOS flashing payload were confirmed.
The BIOS is a special program in an IBM-compatible PC that `gets the PC up 
on its feet'. More accurately, it finds the PC's
feet, then gets it up on them. The payload of the Win95/CIH family, if 
successful in messing with the Flash BIOS of an infected
PC, will leave the machine unbootable. The part of the BIOS that is 
overwritten is the very first part of the BIOS program that
runs at power-up or system reset.
PCs on which the Win95/CIH payload has triggered require the BIOS to be 
replaced. This is where a rash of Win95/CIH
infections within a company can quickly become expensive.
With many PCs this involves opening the case, removing the current chip and 
inserting a replacement one. Obviously the BIOS
has to match the motherboard: BIOSes tend to be designed for a range of CPUs 
and for particular `chipsets' (all the other logic
circuitry needed to make your expensive CPU co-ordinate with all the other 
components inside your PC).
Alternately, a BIOS chip that has been flashed by the virus is not actually 
damaged. However, it requires a fairly specialized
piece of equipment to reprogram it with the correct BIOS image. This is an 
option for people with the right contacts and a
backup copy of their BIOS' contents. (Admit it - you seldom backup your data 
often enough and have never heard of
backing-up your BIOS!)
These first two fixes assume that your BIOS is installed in a socket. 
Unfortunately, it is increasingly common (and almost
universal in laptops) that the Flash ROM chip holding your BIOS is soldered 
to the motherboard. In such machines, a
motherboard replacement is effectively necessary. Although surface mount 
Flash ROM chips may be able to be removed and
replaced by a suitably skilled technician, it is unlikely to be cheaper and 
likely to be slower to effect this kind of repair. With
some laptops it may be more economic to buy a new machine.
Who needs to worry about this virus? If you run Windows 95 or 98 you are at 
risk. The virus infects PE format executable files
(`programs'). This includes Windows NT programs, but the virus will not run 
and its payload cannot trigger under NT. Should
you be running Windows 95 on a 386 or early 486 your are most likely safe - 
storing the machine's BIOS in Flash ROM
became popular towards the tail end of the 486 era. Most, if not all, 
Pentium-based machines will have Flash ROM.
We are still working with the chipset and motherboard designers to ascertain 
exactly which combinations of chipset and Flash
ROM are susceptible to this payload. We know some Flash ROMs cannot be 
overwritten because the payload uses activation
sequences known to not work with them. We hope to make more details 
available as we piece things together.
What should you do in the meantime? If from the above you suspect that you 
may be susceptible to this virus, please download
(or obtain through your standard means) the very latest update to your 
anti-virus software, install it and scan your PC. Most
major anti-virus vendors have updates that detect this virus. The safest way 
to scan is from Dos only mode using a DOS
scanner.
That is not the same as running a scanner at a DOS Prompt under Windows 9x. 
To be sure, select `Restart the computer in
MS-DOS mode' from the shut down menu. If starting from power-up, press F8 
when the `Starting Windows...' message is
first displayed and select the `Command prompt only' option. Another 
possibility is that your anti-virus developer may have
provided an emergency boot disk. Lastly, if using your own emergency 
recovery disk, ensure it is from an appropriate version
of Windows to avoid possible FAT32 problems.
If you have NT servers or workstations, it is safe to check them with native 
NT scanners. CIH cannot go resident under NT, so
cannot infect nor trigger its payload on such systems. Thus, few of the 
concerns that must be considered when testing a
Windows 9x machine apply. However, note that you should not scan a network 
share exported from a Windows 9x machine -
in that case, an active infection on the machine exporting the share can 
spread further. In a similar vein, to check servers running
non-Win32 operating systems, either run updated scanners native to that OS, 
or scan them across the network from anything
other than a Windows 9x workstation.

 
http://www.citynotebookcentre.com.au/vendors/anti-virus/virus_cih_chernoble.htm
humm.. questa non la conoscevo, grazie della segnalazione :)
Comunque dubito fortemente che sui pc odierni possa funzionare..