On Tue, 24 Jul 2007 20:10:01 -0700, Mason
I have checked the reliability log, and the only errors in there have to do
with when I was working very hard at getting Nero 7 to work.
Did it work in the end? Was this the bundleware Nero 7 Essentials?
No other errors other than that. Also in the other error log, there
are many, but none relate to system restore.
AFAIK Vista calls many things my different names, and that may apply
to SR (may be called System Protection now). Also, event logging
(which "Reliability" is rooted in) may refer to such events as Shadow
Copy or something... I've always found those logs to be heavy going,
which is why the Reliability facility is really good!
Even the error I get on restart after doing a restore wasn't there.
Hmm..
This mother board is 14 months old.
OK, possibly old enough to have "bad capacitor disease" as well as
gunked heat sink and fan, but you wouldn't have such a clean problem
(all well except SR always deleted) in those cases.
I actually have flashed it to try to clear up errors with the S3(str)
suspend mode, it only sleeps for a few minutes before it comes
out of sleep with nothing to cause this happening
That sort of thing could affect shutdown, too, so fits. If you said
"...and I keep losing settings that I make during a Windows session,
on the next boot, they're gone", I'd suspect that a bit more.
OTOH, elsewhere in this thread I saw something about dual resident av,
which is known to be a Bad Idea. Do you really have two different
resident av installed?
I am forced to always shut it down... Very disappointing.
Hm. What mobo is this? What chipset?
I am not sure what you mean by the ACPI support. What exactly do you want
to know? I know it has something to do with CDROMs...
CD-ROM sounds more like something else (IKWYM, but it's not ACPI).
AFAIK, ACPI is a hardware standard that defines how BIOS and power
management works with the hardware, and that in turn ties into ATX
power shutdown, suspend, hardware resource allocation etc.
In older NT-based OSs, the initial HAL would be based on a particular
type of hardware setup and could be invalidated if that was later
changed after the fact - much as Vmm32.vxd would be a similar point of
failure in Win9x in similar circumstances. Dunno how Vista handles
that... when you flashed BIOS to fix S3 modes etc. did Vista decide it
wasn't on the same PC anymore, and require (re-)activation?
On Vista waking up all the time; look in CMOS Setup for what hardware
events can awaken the PC and disable the ones you don't want. For
example, a UPS or other device plugged into a serial port may be
mistaken for a modem signalling an incoming call, etc.
No, there is no over clocking.
Guuud.
If it helps, this computer was built with XP, and because I work in a
computer store, I was kinda forced, as well as wanted to update to vista so
that I can learn the ways we have to go about fixing it and how differently
it works so I can give consumer demonstrations and sales. This computer ran
with out hiccups for a full year until I installed vista two months ago. I
mean zero problems.
Cool! I've been building Vista boxen a while too (well, since Jan
2007) and it's been a bit of a learning curve, and frustrating waiting
for Nero and DVD writer vendors to get their act together. I only
build with Intel motherboards these days - it's a motherboard chipset
rather than a processor thing - and SF,SG.
--------------- ----- ---- --- -- - - -
Tech Support: The guys who follow the
'Parade of New Products' with a shovel.
