AIO 964 All In One printer

What model of PC do you have, and what is the Operating System?

Message Edited by DumbDan on 02-28-2006 07:39 PM

Yes!!  I have that in my registry

Could you give me PRECISE directions so I get it right?

Ok I went to Regedit and highlighted the entry and deleted it.  Hope that was OK?:smileywink:

Oh, and I already removed the software so I just want to make sure I edit the registry correctly.  Thanks,Dan

Ok, that's the entry that is causing the .dll issue with your 964 printer.  You need to first completely uninstall your printer software/drivers from Add/Remove programs.  Then go back into your registry and manually delete the 'wow6432node'.  Reboot the PC and then perform a re-install of the 964 drivers/software.  This should cure your .dll error message woes. ;)  Let us know how it works!

I am absolutely amazed at the incompetance of Dell tech support.  I made a call to them in the beginning of DECEMBER with this same problem.  You would think that 3 months later, they would at least recognize that there is a problem.  It appears many of you were guided through the loading and reloading time and time again with no solution to be offered, only complete incompetance on the other end of the phone.  If the tech support at Dell actually read this message board, it would be quite obvious to them that there is a problem and it cannot be resolved by merely installing and uninstalling the software.  Thank you to the person who came up with the temporary solution (deleting dlcjcats) and a great big double thank you to the person who determined the permanent fix.  I am going to try this the first chance I get. 

I'm glad it worked out for you!  The problem is with the Creative Labs soundcard you have, for some reason that piece of hardware is creating the Wow6432node in the registry.  This is usually reserved for 64 bit Operating Systems, not 32 bit (like the OS you are running).  When the 964 installation is run, it sees that node in the registry (and thinking it's a 64 bit OS) attempts to run the 64 flavor of SW/driver installation.  By deleting the affected registry entry, you are clearing the installation confusion for the 964 AIO and allowing the proper 32 bit installation to run.

Well, feel free to spread the word to whoever may need it!  The problem is, this may not be the fix for all of the people out there who are experiencing the time.dll error messages, but it will fix probably 90% or so.  You fell into that 90%. ;)  There are a couple instances of this happening on Windows XP Pro machines (not Media Center Edition), and this may be due to another registry key (not the wow6432node) that is fooling the 964 install into attempting to run the 64 bit flavor of software installation.  If I hear of any additional/new info regarding this problem, I'll be sure to post it in this thread.  Good luck!