- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Try "right clicking" the installer, then left click "properties" on the menu that appears; this should open the "properties" window. Now click the "compatibilities" tab and see if you can set the system to run "windows XP or Windows 98 mode, this may solve the problem, if not >>> Certain versions of Windows 7 have "Windows XP compatibility mode" programming available for free download from Microsoft.com which should allow your older printer software to run on W-7. Just download and install Windows XP Mode and Windows Virtual PC . Failing all the above, you can probably update the printer for what a "chat" would cost !
It is very easy to install the printer for windows 98. All you have to do is plug in the printer connector to your computer properly and also the power cord of it. After setting it, turn on your computer and also the printer. Use the support cd of the printer to install the needed driver. Just follow the on-screen software installation.
I have the 150C and the software installation menu has a repair installation at the bottom of the menu somewhere. I rarely use it so you may have better luck here and searching for the answer there but it may also be the service just needs restarting manually from the services in the system services menu- find the service that matches the message your getting and stop 'n' start, restart it. good luck
I?m assuming this is happening on a Windows machine. This is one of the really vague error messages that Microsoft give for an incredibly large number of problems. I typically see this on servers but have seen it occur on workstations. If you?re running XP, 2000 (server or Pro), or 2003:
- Check and make sure your Remote Procedure Call Service is running.
- There is an older vulnerability that tries to use a flaw in the RPC services. It is fixed if you copy of Windows is up to date so make sure it is.
- Review your application log for any clues.
If you need more assistance let us know your operating system, if it is fully patched and what is showing in your log file around the time you receive the error message.