The long and short of this story is my 7 month old computer won't boot. It's in a loop. No safe mode, no any mode, it just wont boot. This all happened one lovely day in October 2005 when I decided to start my computer so that I could use it. Crazy, I know, hitting the "on" button can certainly stress out a machine, but I did it anyway. So it starts to boot and them "whamo" it freezes up. Huh, thats weird. So I do what most people do, I hit "ctrl,alt,delete" to get it to reboot. Yah, well that was the beginning and the end of it. It's now stuck in this loop that won't boot in any mode.
We called HP Tech Support. We've spoken to 5 people now. All of them say just wipe it out. That's all the warrenty covers. Nobody wants to look at it to see if they can fix it without losing my data, that's way out of the question. They have no trouble with us taking it to one of their "authorized service centers" - Best Buy - and paying out the nose for them to look at it but they themselves at HP have no interest in the customer, service or holding up their warrenty. They happily offered us the option to buy a warrenty upgrade which we promply asked "Why in gods name would I pay anymore money to you people when you cant honor the warrenty we have now"???

Here's sonmething you guys will love too, the QA guy, Darren, said he didn't even own an HP, he built his own computer. What does that tell you? Their own employees don't buy their crap, So why should we??

http://h10025.www1.hp.com/ewfrf/wc/genericDocument?lc=en&cc=us&docname=c00063456

Motive Directory has caused an error in kernel32.dll. Motive directory
will now close. If you continue to experience problems, restarting your computer.

Dell told me to reinstall my op system (Win ME). When that did not work, they told me the re-install disk was bad and to get a another one. Microsoft does not carry WIn ME anymore since it's a legacy system. When I hooked-up my hard drive to a friend's computer, it worked fine. I bought the XP upgrade and I can hear the disk running but nothing shows up on screen to install the op system, and then I get the error again.

Any ideas on to what to do?

Any help would be greatly appreciated.

Thanks.

"To resolve the problem, disable hpcmpmgr.exe running from the MSConfig utility. Follow these steps to disable hpcmpmgr.exe file:

1. Click Start and Run.
2. Type MSCONFIG and press Enter.
3. Click the Startup tab.
4. Clear the checkboxes for hpcmpmgr.exe.
5. Click OK.
6. Restart the system.

After disabling the hpcmpmgr.exe file from the MSConfig utility, check whether you are experiencing the same problem or not."

Did that - and then the printer did not print!! So had to recheck the box and so still get the error message.

Any idea how to fix it?

Could the SBC Self Support Tool be the problem? or is it Outlook Express, as one SBC techie told me?

sorry to hear that the HP PSC 2510 all-in-one generates a "HPOSM"
error message and after downloading the update patch exception errors are generated.

The utility update that you have downloaded and installed is to disable the HP Solution Manager and the error messages are generated are from the HP Component Manager.

To resolve the problem, disable hpcmpmgr.exe running from the MSConfig utility. Follow these steps to disable hpcmpmgr.exe file:

1. Click Start and Run.
2. Type MSCONFIG and press Enter.
3. Click the Startup tab.
4. Clear the checkboxes for hpcmpmgr.exe.
5. Click OK.
6. Restart the system.

After disabling the hpcmpmgr.exe file from the MSConfig utility, check whether you are experiencing the same problem or not.

If still you are experiencing the same problem, then try to download and install HP Component Manager patch from the following web site:

<UNKNOWN> caused an exception c0000006H in module <unknown> at 0000:bff86eac.
Registers:
EAX=00435000 CS=0167 EIP=bff86eac EFLGS=00010202
EBX=00000000 SS=016f ESP=82ac9c00 EBP=82ac9c88
ECX=00000010 DS=016f ESI=00000000 FS=2ae7
EDX=c1597350 ES=016f EDI=00000001 GS=0000
Bytes at CS:EIP:
66 8b 48 0e 83 c0 10 66 8b 50 fc 89 45 a4 8b 45
Stack dump:
00000000 81740070 8172f4ec 00035000 000040e8 00000000 00000000 00000000 00000000 00000000 00000000 00027420 00000000 00000000 00000000 00000000

In some cases, this problem is caused by an incorrect version of the Windows file Oleaut32.dll file. This can happen if, when you install new software, it installs a version of this Windows file that was not designed for your operating system. You must determine the version of this file, and replace it if it is not the correct one for your operating system.

To determine the version of the Oleaut32.dll file:
1. Click Start, point to Find, and then click Files or Folders.
2. Make sure that "Look in" is set to (C:) and that Include subfolders is checked.
3. In the "Named" box, type--or copy and paste--the following:

oleaut32.dll
4. Click Find Now. It may find more that one copy.
5. Right-click the Oleaut32.dll that is located in the C:\Windows\System folder and then click Properties.
6. Click the version tab and read the version number.
7. What you do next depends on what you find: For Windows 95/98, the version of Oleaut32.dll should not be 3.50.5014.0 or 3.50.5016.0. (There are various versions that can be used by these operating systems, but this is not one of them.)
· If the version is not 3.50.5014.0 or 3.50.5016.0, then skip to the section Import a registry key.
· If the version is 3.50.5014.0 or 3.50.5016.0, then you must obtain a compatible version of this file, rename the original, and then install the downloaded file. Go on to the section Obtain a compatible version of Oleaut32.dll.

To obtain a compatible version of Oleaut32.dll:
1. Download the Microsoft DCOM package for your operating system, which will update the Oleaut32.dll file as part of the installation:
· Windows 98
a. If you are using Windows 98, go to:

http://www.microsoft.com/com/dcom/ dcom98/download.asp
b. Click the Download link in step 3.
c. Save the file to the Windows desktop.
2. Rename the old Oleaut32.dll file:
a. Click Start, and then click Shut Down
b. Click Restart in MS-DOS mode.
c. Click OK. The computer restarts to a command prompt at the \Windows folder.
d. Type the following, pressing Enter after each line:

cd system
ren oleaut32.dll oleaut32.old
win /d:m

This changes to the \System folder, rename the Oleaut32.dll file, and then restart the computer in Safe mode. When you see the message that Windows is running in Safe mode, click OK.
3. Locate the file that you downloaded to the Windows desktop and double-click the file to install it.

I've just installed an HP Photosmart 7260 under Win 98 SE, now I get HPOSM caused illegal operation error whenever I boot up. Anyone got any suggestions or managed to find any info on this?

When I reboot - I get the Motive Directory fault and the same messages that everyone else is getting. I did discover that my USB was not enabled in the BIOS - that is now enabled. I've also tried resetting the parallel port - but so far, none of those changes have done the trick.

All I want is to be able to stay online and print more than one thing. As it is now - I have to CCP all of my information into Word and do one huge print job before I shut down the PC. Not a very easy way to do things.

I have contacted HP Online tech support - that was a lesson in futility - they are clueless.

While performing "Ctrl+Alt+Del" to bring up the close program dialog box, I noticed that several of the listed items were duplicated. I cleared everything from the list and forced a re-boot.

I also have an all-in-one hp. I am getting the same msg on boot into windows. The motivedirectory app is listed as being in the HP directory. I am not sure what it is used for. I did see info stating that overclocking video or mobo can cause this type of Kernel error. I do not get it every time but I do get it often.

Anyone know of any solutions?

Thank you,

If anyone has a clue about the above, would really appreciate it. Have already checked with HP and Microsoft regarding kernel32 errors and motivedirectory. Neither was much help.