Re: Is this an easy fix or complicated one?

You were still able to get to device manager, so that's good, but I may not
have given good instructions. Go to Start.> My Computer ..highlight MY
Computer, and while it's highlighted, right click, then at the bottom of
that box that opens, properties will be listed..if it isn't working, post
back.

Okay, with device manager open, and the image device selected , go to the
Driver Tab, and update the driver.

If that doesn't do the trick,, remove your digital camera..you may have an
icon in your system tray..it's located in the lower right corner of your
screen, near the time, and other entries might be Zone Alarm, your
Antivirus..anyway it's green and if you click on it will say Safely remove
hardware..or something like that. Before you remove your camera, see if
it's listed there..follow the instructions about remove the camera, and when
that's done it's safe to unplug it from your computer. Then uninstall the
software, it should have an uninstall file. See if the error is corrected.

Now, as far as those errors you posted..you did a good job! Everything you
need to know, or do is right there.
The printer...fro example..

To find the vendors

In Control Panel, open Printers and Faxes.
Right-click the appropriate printer and then click Properties.
On the Advanced tab, clear the Enable advanced printing features check box.
Rather than going thru all this...are you able to uninstall your printer for
any length of time? When you're not working? Because, if it's a hardware
conflict, in my opinion, the easiest way to pinpoint it is to remove each
piece of hardware, one at a time, waiting in between to see if the problem
persists. Process of Elimination.
Sadly, it likely is bad ram...don't panic, it's no big deal. But, it might
be that your cpu is overheating...it might need to be cleaned, lots of dust
can build up and cause the fans to not work as well as it should. You pc
must be powered off,, unplugged and then you need to ground yourself, touch
the case or something before you open the cpu...then, having purchased a can
of air from a computer store ( of course you'll want to do that before you
open the cpu ;) ) spray the dust out of your pc. And if your tower is kept
in a closed compartment of a desk, open the door to let the air vent
better.
Back to ram..
Get your Dell manual, look for Ram..it will tell you what type you have, and
how to remove and replace it. If you go to a computer store, like Best Buy,
or Circuit City..I don't know what you have in your neck of the woods.. they
will be able to help you. Your pc either came with 1, or 2 sticks of ram.
If it came with two, you can, after reading your manual, remove one...then
wait to see if the pc acts up. If it doesn't, then you know that stick is
bad...if it does, then replace that stick, and remove the other..elimination
don't ya know!.. If one, or both are bad, you can replace them with new.

"Lady In Need" <LadyInNeed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B4699ACE-27A5-4624-9E17-C804E2AEA966@xxxxxxxxxxxxxxxx
> Okay.. this is weird. I couldn't get to Device Manager in the way you
> told
> me. When I clicked on My Com there was no 'Properties' there that I could
> find. After some looking I found it this way. Start; Control Panel;
> Performance & Maint; System; Hardware; Device Manager That brought up
> its
> own little box which has all the different part etc... I opened them all
> and the only thing I saw was one yellow exclamation point. Under
> imaging
> devices:
> Agfa e photo 1280 Digitial Camera
> hp psc 1310 series
> **Yellow !** Unknown Device
>
> Did I do this correctly?? One other thing. I've not unistalled the HP
> All
> in One yet. I'm a PS on eBay and have to ship daily and need it to print
> shipping labels. I will catch up today on all printing and unistall it as
> suggested. No shut downs since the last time I posted one. A couple days
> ago I believe.
>
>
>
> "Lady In Need" wrote:
>
>> Good morning Ivee... Thank you for your condolences. It's the first
>> close
>> death for my girls and even though teens they're taking it much harder
>> than
>> expected. Sorry for the delay. Now...
>> It's very strange that the errors are mainly coming up as win 2000. When
>> I
>> purchased this system from Dell (supposedly new.. it came with XP) So I
>> never
>> upgrdaded Makes me wonder about Dell now. Hmmmm......
>>
>> Here's the very first warning error, 3/15 I honestly can't remember if
>> this
>> is when it started or not. :( I'll post another from beginning of
>> April
>> when I know it was happening. But here's the first:
>>
>> The Application Management service terminated with the following error:
>> The specified module could not be found.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>> Details
>> Product: Windows Operating System
>> ID: 7023
>> Source: Service Control Manager
>> Version: 5.0
>> Component: System Event Log
>> Symbolic Name: EVENT_SERVICE_EXIT_FAILED
>> Message: The %1 service terminated with the following error:
>> %2
>>
>> Explanation
>> The specified service stopped unexpectedly with the error indicated in
>> the
>> message. The service closed safely.
>>
>>
>> User Action
>> To troubleshoot the error:
>>
>> Review the error information displayed in the message.
>> To display the WIN32_EXIT_CODE error that SCM encountered, at the command
>> prompt, type
>> sc query service name
>> The information displayed can help you troubleshoot possible causes for
>> the
>> error.
>>
>>
>>
>> Version: 5.2
>> Symbolic Name: EVENT_SERVICE_EXIT_FAILED
>> Message: The %1 service terminated with the following error:
>> %2
>>
>> Explanation
>> The specified service stopped unexpectedly with the error indicated in
>> the
>> message. The service closed safely.
>>
>>
>> User Action
>> To troubleshoot the error:
>>
>> Review the error information displayed in the message.
>> To display the WIN32_EXIT_CODE error that SCM encountered, at the command
>> prompt, type
>> sc query service name
>> The information displayed can help you troubleshoot possible causes for
>> the
>> error.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Now here's an error from April 2 when I know for certain this happened.
>>
>> The server {F3A614DC-ABE0-11D2-A441-00C04F795683} did not register with
>> DCOM
>> within the required timeout.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> Details
>> Product: Windows Operating System
>> ID: 10010
>> Source: DCOM
>> Version: 5.0
>> Component: System Event Log
>> Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
>> Message: The server %1 did not register with DCOM within the required
>> timeout.
>>
>> Explanation
>> The Component Object Model (COM) infrastructure tried to start the named
>> server; however, the server did not reply within the required timeout
>> period.
>> There might be a deadlock, or the program might not have responded to the
>> server initialization code within the timeout period of two minutes.
>>
>>
>> User Action
>> If the problem continues to occur, contact the program vendor.
>>
>> To determine the program vendor
>>
>> Using Regedit, navigate to the following registry value
>> HKCR\Clsid\clsid value\localserver32
>> The clsid value is the information displayed in the message.
>> In the right pane, double-click Default. The Edit String dialog box is
>> displayed. Leave this dialog box open.
>> Click Start, and then click My Computer.
>> Using the information displayed in the Value data box of the Edit String
>> dialog box, navigate to the program.
>> Right-click the program name, and then click Properties.
>> The Properties dialog box for the program is displayed.
>> To determine who the vendor is for this program, refer to the Version
>> tab.
>>
>>
>>
>> Version: 5.2
>> Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
>> Message: The server %1 did not register with DCOM within the required
>> timeout.
>>
>> Explanation
>> The Component Object Model (COM) infrastructure tried to start the named
>> server; however, the server did not reply within the required timeout
>> period.
>> There might be a deadlock, or the program might not have responded to the
>> server initialization code within the timeout period of two minutes.
>>
>>
>> User Action
>> If the problem continues to occur, contact the program vendor.
>>
>> To determine the program vendor
>>
>> Using Regedit, navigate to the following registry value
>> HKCR\Clsid\clsid value\localserver32
>> The clsid value is the information displayed in the message.
>> In the right pane, double-click Default. The Edit String dialog box is
>> displayed. Leave this dialog box open.
>> Click Start, and then click My Computer.
>> Using the information displayed in the Value data box of the Edit String
>> dialog box, navigate to the program.
>> Right-click the program name, and then click Properties.
>> The Properties dialog box for the program is displayed.
>> To determine who the vendor is for this program, refer to the Version
>> tab.
>>
>> ~~~~~~~~~~~~~~~~~~~~~~
>> Remember I talked about my HP all in One not being able to scan? This
>> looks
>> like a Warning error pertaining to it thought I'd post it as well.
>>
>> Details
>> Product: Windows Operating System
>> ID: 10010
>> Source: DCOM
>> Version: 5.0
>> Component: System Event Log
>> Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
>> Message: The server %1 did not register with DCOM within the required
>> timeout.
>>
>> Explanation
>> The Component Object Model (COM) infrastructure tried to start the named
>> server; however, the server did not reply within the required timeout
>> period.
>> There might be a deadlock, or the program might not have responded to the
>> server initialization code within the timeout period of two minutes.
>>
>>
>> User Action
>> If the problem continues to occur, contact the program vendor.
>>
>> To determine the program vendor
>>
>> Using Regedit, navigate to the following registry value
>> HKCR\Clsid\clsid value\localserver32
>> The clsid value is the information displayed in the message.
>> In the right pane, double-click Default. The Edit String dialog box is
>> displayed. Leave this dialog box open.
>> Click Start, and then click My Computer.
>> Using the information displayed in the Value data box of the Edit String
>> dialog box, navigate to the program.
>> Right-click the program name, and then click Properties.
>> The Properties dialog box for the program is displayed.
>> To determine who the vendor is for this program, refer to the Version
>> tab.
>>
>>
>>
>> Version: 5.2
>> Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
>> Message: The server %1 did not register with DCOM within the required
>> timeout.
>>
>> Explanation
>> The Component Object Model (COM) infrastructure tried to start the named
>> server; however, the server did not reply within the required timeout
>> period.
>> There might be a deadlock, or the program might not have responded to the
>> server initialization code within the timeout period of two minutes.
>>
>>
>> User Action
>> If the problem continues to occur, contact the program vendor.
>>
>> To determine the program vendor
>>
>> Using Regedit, navigate to the following registry value
>> HKCR\Clsid\clsid value\localserver32
>> The clsid value is the information displayed in the message.
>> In the right pane, double-click Default. The Edit String dialog box is
>> displayed. Leave this dialog box open.
>> Click Start, and then click My Computer.
>> Using the information displayed in the Value data box of the Edit String
>> dialog box, navigate to the program.
>> Right-click the program name, and then click Properties.
>> The Properties dialog box for the program is displayed.
>> To determine who the vendor is for this program, refer to the Version
>> tab.
>>
>> Details
>> Product: Windows Operating System
>> ID: 54
>> Source: Print
>> Version: 5.0
>> Component: Application Event Log
>> Symbolic Name: MSG_BAD_JOB
>> Message: Document %1 was corrupted and has been deleted. The associated
>> driver is: %2.
>>
>> Explanation
>> The print job caused the print spooler to stop more than once, so the
>> print
>> spooler deleted the job and will not try to print it again.
>>
>> To force spooling with the RAW data type
>>
>>
>> In Control Panel, open Printers and Faxes.
>> Right-click the appropriate printer and then click Properties.
>> On the Advanced tab, clear the Enable advanced printing features check
>> box.
>>
>>
>>
>> User Action
>> Try updating the printer driver with a newer version from the vendor if
>> one
>> is available.
>>
>> If updating the driver does not work, try forcing the print queue to
>> spool
>> with the RAW (ready to print) data type.
>>
>> To force spooling with the RAW data type
>>
>>
>> In Control Panel, open Printers.
>> Right-click the appropriate printer and then click Properties.
>> On the Advanced tab, clear the Enable advanced printing features check
>> box.
>>
>>
>> ~~~~~~~~~~~~~~~
>> I'll post this and then do the device manager. Again THANK YOU so much
>> for
>> all your time and effort in helping me. :o)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> "lvee" wrote:
>>
>> > If your
>> > > copy and paste function does not work for that, just click and
>> > > highlight
>> > > the text, then, from your keyboard press the Ctrl key and the 'CO
>> > > key.
>> >
>> >
>> >
>> > Correction, when copying, press Ctrl plus the C key, not CO....sorry,
>> > major
>> > typo!
>> >
>> > "lvee" <notmesothere@xxxxxxx> wrote in message
>> > news:uOiC952QFHA.356@xxxxxxxxxxxxxxxxxxxxxxx
>> > >
>> >
>> >
>> >


.

Relevant Pages

  • Re: Is this an easy fix or complicated one?
    ... Question about the driver update. ... > that box that opens, properties will be listed..if it isn't working, post ... >>> within the required timeout. ... >>> If the problem continues to occur, contact the program vendor. ...
    (microsoft.public.windowsxp.help_and_support)
  • HELP CRASHING
    ... The server %1 did not register with DCOM within the required ... timeout period. ... If the problem continues to occur, contact the program vendor. ... The Edit String dialog box is ...
    (microsoft.public.windowsxp.hardware)
  • HELP CRASHING
    ... The server %1 did not register with DCOM within the required ... timeout period. ... If the problem continues to occur, contact the program vendor. ... The Edit String dialog box is ...
    (microsoft.public.windowsxp.hardware)
  • CRASHING PLEASE HELP!!!
    ... The server %1 did not register with DCOM within the required ... timeout period. ... If the problem continues to occur, contact the program vendor. ... The Edit String dialog box is ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Is this an easy fix or complicated one?
    ... > server; however, the server did not reply within the required timeout period. ... > If the problem continues to occur, contact the program vendor. ...
    (microsoft.public.windowsxp.help_and_support)