-----Original Message-----
No problem at all,
Quickbooks could be using the same Quicken Download manager... I really
don't know if it does as I'm not familiar with the products. You should
follow the instructions listed in the link Jim posted and if those don't
make sense on your computer (because you aren't using the download manager)
I would go to the Dell link and try the Bios upgrade.
There should be instructions on backing up your bios before upgrading it,
and that is highly recommended.
Dell
Link:
http://support.dell.com/filelib/Devices.aspx? Category=1&OS=NAA++&OSL=EN&SvcTag=&SysID=INS_PNT_P4_5100
Quicken Link:
http://support.microsoft.com/default.aspx? scid=kb;EN-US;245835
--
-Anthony Procissi [MSFT]
US-Application Experience & Compatibility
This posting is provided "AS IS" with no warranties, and confers no rights.
Thank you, Anthony.
I am not getting the specific message that was referred
to by Jim on the web site he listed. I don't have Quicken
(that I know of), but I do use Quickbooks.
What would be my next step?
Thanks, Michael
-----Original Message-----
Do you have Quicken installed, Michael?
This article is for Quicken users that get the
following
stop code:
STOP 0x0000009f Driver_Power_State_Failure
If that's you, then I would just follow these instructions and not mess with
the bios... the bios you only really want to upgrade if you're having a
problem...
--
-Anthony Procissi [MSFT]
US-Application Experience & Compatibility
This posting is provided "AS IS" with no warranties,
and
confers no rights.
US;245835
or search again for your complete error in microsoft.com
-----Original Message-----
I have been getting the following message when I boot
up: "Windows could not start because the following file
is missing or corrupt: <Windows root>\system32
\ntoskrnl.exe"
Pressing Ctl/Alt/Del will resume start up, and windows
seems to operate properly after that. I searched and
found that this file does exist in my windows directory.
Is it corrupt? How do I replace it? Or how do I remove
the cause of the error message?
Thanks for listening,
Michael
.
.
.