I would not worry so much about "honoring my opinion"; worry about listening to and following direction.

Quote: Originally Posted by
Fumz
... If you want people to see the picture, you're going to have to host it online somewhere... like imageshack.com

Quote: Originally Posted by
johngalt
Hi,
drumtrucker, and welcome to the forums.
BTW - when you want to post and image, you can also upload them here (within reason - don't try my 8 MB desktop pic :P) and then use the paperclip icon to show it in your post - but you cannot use the fast reply, you have to use the advanced mode reply, and you have to manually upload (using manage attachments below the message entry box) and then use the paperclip after uploading it.
I think that's enough on the topic of pictures?
To your problem. I'm not sure that simply renaming a folder is going to stop those services from running? How's that working for ya so far?
My idea was to stop the services and see how the machine runs, sound good? Go into msconfig and uncheck all the crap you listed a few posts ago to prevent them from being loaded at startup. Then bring up the services.msc menu.... look for all the items you just unchecked in msconfig and set them to manual, at least for now. Reboot the machine and try and recreate the error.
I can already tell you that you've got some crap software on that machine, really crappy crap of the crappiest kind. I hate software that feels it should be automatically loaded when you boot the machine... hate it.

Clearly, that CD writing software you have is of that type... and did I mention it was crap?
I would personally take all the crap off that HP installed.... because it's crap. Then head to the Software section of this forum. There isn't anything that HP has that you can't find here:
Free Software List for Vista or here:
Short List of Utilities for Vista
This list has the added value of not being crap.
If you're hell-bent on finding out exactly which piece of crap is causing the problem, then you can one by one recheck the items in msconfig, reboot and try and recreate the error. Eventually, having loaded enough crap, I'm sure you'll come across the guilty stinker.