Lexmark X9575 won't scan

I've had a Lexmark X9575 all in-one for about 6 months, and have been very happy with it. Suddenly, about 2 weeks ago, it has stopped scanning. Whenever I click on the "Lexmark Productivity Studio" I get a "Printing Application" error message, and everything shuts down. I can print fine, and copy/fax using the console, but nothing else works. I have uninstalled and reinstalled both the printer and the software multiple times under the direction of Lexmark Technical support, and now get a "Printer Card Transfer Monitor" error whenever I get to installing the scanning portion of the install, or whenever the computer is booting up. Technical support has been very little help (over 7 hours on the phone/chat so far). My system is scanned every 2 days for viruses/trojans, etc, and everything is reported as clean. Any ideas?

I run Windows XP SP2. The printer can be attached via wired network cable, wireless and USB. Currently, it is attached via USB. I have the same problems when it is attached through the network.

 

lrcpalmer ... did you ever figure those "Printing Application" & "Printer Card Transfer Monitor" issues out?

I'm struggling with the same printer, same messages, on Win XP Pro SP3 32-bit OS.

Just thought I'd see if you ever resolved the issues ... 8 years ago ... if you are still subscribed to this thread, using the same e-mail and still get Major Geeks notifications.

Thanks, FFF

 

XP - I have not used xp for many years, but, looking around, I hope these links and ideas might help solve the problem.

Resetting printer software to factory default settings--Page 106 of the manual
http://publications.lexmarSSk.com/publications/pdfs/2007/9500/winug/en/lxdouser.pdf
For Windows XP or Windows 2000 users 1 Click Start ŒSettings ŒPrinters or Printers and Faxes. 2 Right-click the Lexmark 9500 Series icon. 3 Click Printing Preferences. The Print Setup tab appears. 4 From the Printing Preferences toolbar, click Settings Œ Load Factory Settings. 5 Click OK. Note: Factory default settings cannot be deleted.
Troubleshooting from around page 191 in the manual.

You might view your Startup under Task Manager and see if Printer Card Transfer Monitor (lxdwamon folder) is disabled- if so, try enabling enable it.

Check .Net framework- .Net Repair tool here - Rhttps://www.microsoft.com/en-us/download/confirmation.aspx?id=30135

Links to .Net if needed
.Net 2 https://www.microsoft.com/en-gb/download/details.aspx?id=1639t
.Net 3.5 https://support.microsoft.com/en-us...dows-vista,-and-windows-server-2008-june-2013
.Net 4 http://www.microsoft.com/en-gb/download/details.aspx?id=39257

 

This thread is 8 years old.

 

Frankenstein asked the same question, at 6.44p. on Tuesday, this week 2017, unless majorgeeks timer made a mistake, so I took time to try to help - That seems relevant to me.

 

That Lexmark link doesn't work in any browser I try it in.
But this one does: http://publications.lexmark.com/publications/pdfs/2007/9500/winug/en/lxdouser.pdf
The OP of the thread never came back since the day posted so they can't answer any questions.
A new thread is always better.

 

Thanks for giving another link- I don't know why the link I gave failed to work , must have been my fault in copying web address, somehow.
I agree that a new post is the best option, but could see no harm in trying to help the poster, as it was done two days ago.

 

Thank you baklogic & MaxTurner for helping out ... indeed, although lrcpalmer's thread is 8 years old, I am still using one of these A-I-O printers and am faced with the identical two errors (due having had to make an emergency migration to an older laptop for daily use while my main Win 7 Pro 64-bit machine is down with a bad Seagate Constellation HDD) ... it was a shot in the dark to see if I could reach out to lrcpalmer to see if she had resolved the issues. I've uninstalled everything related & re-installed several times now ... the named error issues are persistent.
I have been to the link (baklogic &) MaxTurner provided, read over page 106, and, while the Printing Preferences GUI is a little different from what was expected (see attached JPG), that is likely due to my recent use of a more recent Lexmark provided driver update installation package. I did a Profiles > Restore a Profile > Factory Settings command from Printing Preferences ... this has not alleviated the 'Printing Application' error that occurs when attempting to launch the Lexmark Productivity Studio app from a running system tray icon (the systray icon exits following the error), nor, following said exit, when launching manually from Start > All Programs ... I will need to reboot to be sure.
Before I do, I did also look at msconfig > Startup ... the only Lexmark-related items are lxdomon(.exe), lxdoamon(.exe) & fm3032(.exe /s) and they are all enabled.
I'll look at the .Net repair possibility once I'm satisfied the Factory Settings has been thoroughly tested with a re-boot.
Thanks again for the assistance, FFF

 

Keep us posted, on your progress - all the best.
Rebooting after printer driver installation can often help.

 

Hey all ... and ... baklogic / MaxTurner ... just to update my progress with these Lexmark X9575 printer issues ... the Factory Settings followed by a reboot did not cure the issues that I share with the O.P.
Likewise, the .NET Repair tool run followed by a reboot did not cure them either.
I am at a loss with what to try next ... other than trying a telephone call to Lexmark Tech Support ... I would imagine they won't want to talk long about a printer that is 10 years old ... but ... you never know 'til you go. I'll post back if I get anywhere with this.
Thanks again for all the assistance to date, FFF

 

From the manual- It could be useful to run through the following- possibly setting more space for temporary files.

"Changing the Productivity Studio temporary files preferences 1 From the desktop, double-click the Productivity Studio icon. 2 From the Tools menu, click Preferences. 3 Click Temporary Files. a Use the slider to set the maximum disk space you want to allocate for temporary files created by the Productivity Studio. b Click Browse to choose a different folder for saving the temporary files. 4 Click OK.
Working with photos 118
Changing the Productivity Studio searched folders preferences 1 From the desktop, double-click the Productivity Studio icon. 2 From the Tools menu, click Preferences. 3 Click Searched Folders. 4 If you want to exclude system folders when looking for photos, select Ignore system folders. 5 Click OK.
Changing the Productivity Studio library preferences 1 From the desktop, double-click the Productivity Studio icon. 2 From the Tools menu, click Preferences. 3 Click Library. From here, you can choose how you want to sort photos. You can also set the minimum file size for the photo to appear in the library. 4 Click OK.
Changing the Productivity Studio transfer settings 1 From the desktop, double-click the Productivity Studio icon. 2 From the Tools menu, click Preferences. 3 Click Transfer Settings. a Select “Skip Save option and go automatically to”, and choose to Automatically Save, Manually Save, or Print your photos from the photo storage device connected to your computer. b Click Browse to choose a different folder to transfer your photos to. c Select “Always erase photos from my media after transferring” to automatically delete photos from your photo storage device after transferring them to your computer. 4 Click OK."

 

Hey baklogic ... thanks for the additional info from the manual ... unfortunately, the Productivity Studio app will not launch successfully in order to try any of the tweaks you reference ... when I try, I get the "Printing Application" error message (see attached JPG) ... I find it maddening that I cannot select (Ctrl-A doesn't even work) and copy the Error Report Contents - all I can do is scroll down to the bottom of a very long log. There is no clue given in the series of three GUI messages as to where this log file is located (I searched my machine for *.wer - no luck) and the application error event does not show up under Event Viewer > Application.
I have determined that upon a fresh boot, I consistently get the "Printer Card Transfer Monitor" error message (see attached JPG) ... as everything finally loads in a new session. The Productivity Studio icon loads in the systray and remains stable if left undisturbed, however, if you try to launch the P.S. app from the systray icon (right-click) or by double-clicking on the Desktop icon, that's when you get the "Printing Application" error message.
Thanks again for helping me with this ... I will see if I can get through to Lexmark T.S. ... FFF

 

FWIW...
There's nothing in the manual refering to 'Printer Card Transfer Monitor'.

Typing 'Printer Card Transfer Monitor problem' brings up this:
http://support.lexmark.com/index?pr...hlibrarykbchannels&locale=EN&userlocale=EN_US
I doubt it will be of any value.

Try to contact Lexmark.
Phone: (800) 332-4120
Monday-Friday 9:00am to 9:00pm
Closed on Saturday and Sunday.

 

Thanks Eldon ... I will get back to this thread after speaking with Lexmark ... FFF

 

On lexmark faq- firewall might need to be closed-even antivirus, to see if it will then work- if it does you will need to allow exceptions in them for it to work.-under solutions tab
http://support.lexmark.com/index?pr...librarykbchannels&locale=EN&userlocale=EN_US#

 

So ... Lexmark International wasn't much help ... they claimed they had no specific KB articles on 'Printer Card Transfer Monitor' or 'Printing Application' errors for their applications software (also no firmware update for my printer was confirmed) and would have to refer me to paid support. It was suggested I follow an older KB article (target OS': Windows; Microsoft Windows NT 4; Microsoft Windows 2000) regarding purging the Windows registry of all references to Lexmark (software /) drivers and then re-install. I followed the registry edit portion of the procedure (in broad strokes - I searched 'Lexmark' from beginning to end and deleted everything I found, as the T.S. (applications) agent had initially alluded to, leaving whole keys alone if 'Lexmark' was found amongst other non-'Lexmark' items within a key and only deleting the 'Lexmark'-specific items in that key) but stopped at step '29.', upon Registry exit, as the procedural references beyond this point were NT-specific.
Then I did the legacy applications / driver install (from the original software CD), followed by the updated driver package ('cjb9500en.exe') downloaded from Lexmark, this time with exceptions in place for 'lxdoamon.exe' & 'frun.exe' in my AVG AV Free (16.141.7998 - also disabled until restart) and ZoneAlarm Free (10.1.079.000) exited. The 'Printing Application' error surfaced within both install phases and had to be dealt with to conclusion (reporting or not reporting) in order to allow the installation routines to finish, which they both did.
Upon reboot, conditions remain the same, I still see the same two errors in exactly the same fashions (see 2nd para. & JPGs in post #12).
On a different tack, I found reference to the elimination (and auto-regeneration) of an XML file ('LXDOPDS.xml' in my case) in the Application Data\Lexmark Productivity Studio directory ... however this did not work for me either.
For the moment, I'm out of ideas here ... annoying to not be able to run this issue down ... FFF

 

1. Turn off and disconnect the printer from the PC.
2. Download Revo Uninstaller Free - first download link.
http://www.majorgeeks.com/files/details/revo_uninstaller.html
3. Run Revo and select the Advanced scanning mode. Deleted everything it finds.
4. Restart the PC.
5. Disconnect the PC from the internet and disable all security software.
6. Install cjb9500en.exe without connecting printer to PC - you'll be prompted when to do so.

 

Eldon's way is the way, when there is anything left in the registry, as it can make re-installation a pain.
I use advanced system care uninstaller, but Revo is well recommended.

 

... ummm ... small glitch Eldon (BTW, thanks to you and baklogic for your continued help with this) ... just thought I'd check before pressing on here ... don't see Advanced scanning mode in Revo Uninstaller 2.0.2 (Free) ... FFF

 

Here it is - look closely, last option of three 'safe', 'moderate' 'advanced'
You wont see it until you START the uninstall process:

 

Run the uninstaller.
Before you click the Scan button, you select Advanced.

 

Those options (safe,moderate, advanced) only appear after the standard uninstall has actually completed.

 

Ahhh ... thanks guys ... FFF

 

... well ... sorry to say that didn't work ... same error messages, same timing of them ... but I did make a couple of observations ... notably, because I was not connected to the internet during inst., Windows Error Reporting had to offer me the option to Report Later on the Printing Application error ... which I did, and, this time it told me the error report CAB file name, its' location and its' contents ... which I copied before I allowed WER to send ... essentially, the meat of the report is an MDMP file & a HDMP file ... (screenshots below illustrate the directory structure and TXT file contents) ... interestingly, in the third last line of '115EF5.txt', "EventLogSource=.NET Runtime 2.0 Error Reporting" is cited ... is this coincidental? FYI - I ran Microsoft's .NET Framework Setup Verification Tool yesterday and all files verified OK.

Let me know if you guys think the CAB file containing the MDMP & HDMP files can be utilized to zero in on the cause of the error(s) ... perhaps I can Forward it / them via P.M. or something ...

... something else I noticed (that has occurred previously after a Lexmark P.S. uninstall / re-install), is that when I go to run an Excel XLS file (Excel 2007, part of Microsoft Office Enterprise 2007) for the first time after a unins. / reinst., I get brief 'Windows Installer', then 'Microsoft Office Enterprise 2007' GUIs ("Please wait while Windows configures M.O.E. 2007") running automatically (to completion, whatever it is that's happening) before my XLS file will actually open ... this only occurs once and does not recur 'til another uninst. / reinst. of Lexmark P.S.

This may be unrelated, however, the Lexmark P.S. inst. / unisnt. routines are seemingly having some kind of effect on my M.O.E 2007 installed product - perhaps Office 2007 updates are to blame here somehow? FFF

 

Sadly the screenshots are not properly focussed so that they can be easily read. You need to use the 'alt + Prt Sc' combination to get a focussed single window screen shot, and if the window is large you would need to create several screen shots and crop them. If they are not easily readable in detail to you when you look at them, it's the same for us.

 

MaxTurner ... thanks for pointing that out ... I'll Upload the files as thumbnails (so they load in a separate page full res) ... now that I examine them more closely, I agree that adding them full size in the body of the post does not make them all that readable. Sorry about that. FFF

 

That's still not too good ... the forum interface is not allowing the screenshot attachments to display full size, as captured. I've added the two TXT files that are shown opened in the screenshots.

Anyways, the upside meat of my post #24 is whether the MDMP or HDMP files are useful in terms of isolating causative factors. Those are available in raw form. FFF

 

The forum does allow posting 'full image' but the images you sent, in full size, were not readable.
Before you upload any image here you must look at it first. If you can't read each line of those shots, nor can we.
That's the issue.

 

If you click the little arrow t top right-open in new window -then use the magnify top right to 150%, it is quite readable.

 

No thanks. It is very easy to take a readable screenshot, even if it means taking more than one creating parts. This isn't a kindergarten.
If the screenshot details are not easily readable by the user who took it, as is, nor can we.

 

Is your XP up to date ? Just a question, as we ran through .net updates, earlier-
Mdonah posted this on a thread we wer working on, and I thought it may be useful- the link was working a short time ago, so it may well be something missing-lik C++ etc; and my knowledge on that is minimal.

1. mdonah, Sunday at 8:56 AM Report
2. #9 Like Reply
3. 
   
4. http://forums.majorgeeks.com/data/avatars/m/303/303513.jpg?1469643596
   mdonahMajor Geek Extraordinaire
   Once you've re-installed XP and gotten all of the updates through 4/8/14, there's a way for you to get Microsoft Updates for XP until 2019 (unless Microsoft decides to pull the plug).
   
   It involves incorporation of a registry key:
   
   https://drive.google.com/open?id=0B1JJmWFrL8Tvdms1bDF3YnVSWEE
   
   Double click the file you download and confirm you want to install the registry key.
   
   Windows Embedded (what is used in ATMs) is a version of XP SP3. What this registry key does is "change" your XP SP3 to POSReady 2009. It functions exactly like XP SP3 but, as I stated, you'll get Updates for XP, Internet Explorer, etc. until 2019. I did the registry entry on my XP SP3 laptop the day it became available (5/25/14) and have gotten updates every Patch Tuesday (the second Tuesday of each month) ever since.
5. This link will give direct download to the registry fix- if you want to chance a try.

 

The other thing is your office 2007- is it fully updated - sp3- https://www.microsoft.com/en-gb/download/details.aspx?id=27838
As this.net runtime error is showing with the office application, if office is updated- did this happen before it was updated.
From that link , you can also get the office compatibility pack ,if you need to .

 

Thanks baklogic for the added ideas / suggestions ... the POSReady 2009 / XP SP3 update thing is interesting ... but I think I'll focus on the Office Update angle first (even though I'm at SP3 MSO [see screenshots] and no further updates are offered through Microsoft Update), as I kept Windows XP updated constantly while it was actively supported by Microsoft ... I'm still offered six optional updates that I don't really want (see screenshot), as well as a NIC card driver update that I don't really need. FFF

 

The link by Mdonah, is an extension to XP updates, apparently only available with the linked registry tool- XP, as you know, is otherwise not supported anymore, and that is why I offered it.- your choice.

 

baklogic ... Mdonah's link still works and I downloaded the REG file ('xp-security-updates.reg') available there ... I better first do some in-depth reading on POSReady 2009 and see if I can figure out if adding it to my Registry will have any kind of a downside for me ... from what I can see no Microsoft Office updates are available to me through Microsoft Update, so, I'm hesitant to run the Office SP3 package ('office2007sp3-kb2526086-fullfile-en-us.exe') when I can see it is ostensibly already there (along with a slew of other Office 2007 updates, before and after SP3) in Add/Remove Programs (see screenshot) . FFF

 

If you are happy with your updates, then, fair enough- worth checking which update came last in both XP and office, in case they had anything to do with the problem.-look up the update number and read what it did.

 

Plodr might be more help with the updates,
Plodr, I had thought that as office is also playing up with this, would C++ be a possible cause of the problem ?
https://www.microsoft.com/en-gb/download/details.aspx?id=3387 (c++ redistribultle 2005 for office 2007)
From reading , I understand that C++ is better entered before installing office, or, if re-installing office, as it sits in the core-perhaps I am going adrift-Plodr ?
Just a thought if office has been re-installed recently, and it could have a link to tis problem.

 

Thanks for the C++ idea baklogic ... that may be the next thing I try ... but first ... Plodr, if I understand you correctly, I should still be getting Office 2007 updates through Microsoft Update, when and as they are available, right? ... as you are ...

... unfortunately, the thumbnail screenshot of my Office 2007 updates in Post #35 doesn't view well in any browser I've tried ... the crisp JPG screenshot images I upload as thumbnails are degraded upon display in a frame or new tab/window and the full-size post option versions are not much better, as MaxTurner points out ...

Plodr, would the most recent Office 2007 updates appear at the top or bottom of the list of updates, or, are they listed by some other ordering factor? Perhaps if you could identify for me the most recent known update to Office 2007 on your system (by KB #), I can look for it on my system. If it's also on mine, then I can rest reasonably assured that I have (and am still getting) all Office 2007 updates, and, rule that out as a causative factor for the two errors I am seeing.

On another more direct tack, are there any relatively simple open source utilities that can parse/decipher causative factors out of the MDMP & HDMP files within the Windows Error Reporting CAB files I have captured? (which is only possible when the two types of errors occur while the system is not NIC-connected and I am given the WER 'Send Later' option - then the CABs/TXTs are stored temporarily in: <user>\Local Settings\Application Data\PCHealth\QRegular\)

Thanks, FFF

 

OK plodr ... thank you for clarifying the post-XP support MSO 2007 update situation and listing all the updates by month and KB that you've had to search out and install ... so ... after obtaining and running all 14 of the MSO 2007 update pkgs you have referred to, I find that each update pkg has an initial detection routine that ultimately says I already have the update I am attempting to install ...

... yet, after parsing the list of existing updates to my MSO Enterprise 2007 installation in Add or Remove Programs, I find that some, but not all of those I ran are actually present ... i.e.

October: KB3118308 (not in my Update list, yet detected by update pkg run routine), KB3118301 (was present in my Update list)

November: KB3118395, KB3118396, KB3127889, KB3127948 (all not in my Update list), KB2986253 (present), KB3127949 (not in my list)

December: KB3128019, KB3128025, KB3128020, KB2883033, KB3128024, KB3128022 (all present in my Update list)

So, while I cannot account for the "The update is already installed on this system." message for updates that do not show up in Add or Remove Programs (perhaps that is the default response by the update pkgs for non-applicable updates), I think the update status (and overall status) of my MSOE 2007 installation is probably OK.

And, further to the status of my Microsoft Visual C++ 2005 Redistributable installation, as mentioned earlier by baklogic, while I cannot find any file verification tool online for Microsoft Visual C++, my Add or Remove Programs does list 2005, 2008 (x 3) & 2010 (plus a KB2565063 update):

So, unless there is some kind of Visual C++ 20xx Redistributable installation verifier available, I don't think I should run the 'vcredist_x86.exe' pkg baklogic found for me ... just yet.

I think I should now focus on deciphering the error messages causative factors within the MDMP & HDMP files I have referred to earlier.

Anybody have any thoughts on how to read what I need from them? Thanks, FFF

 

We are in an area that I am not clued up on, but I can try looking at the file showing error Bpo=clr20r3 , and it seems it can be to do with . net framework, (Net Runtime 2.0 Error Reporting ) and
One solution was to turn on MS-MESSAGING QUEUE IN SERVICES. (In your upload ----QueueMode=268435458)
Also reference to a stack overload on error Bp0=clr20r3.
Further I feel it could well be to do with 'permission' in Net framework,
http://www.hivmr.com/db/kxccfsdxfmac73dsj1387k9k9c3xck83
Luis here said

Microsoft .Net Framework Configuration from theAdministrative Tools,( Configwizard.msi ) if you dont have this console installed.

Expand the items My computer, Runtime Security Policy, Machine, Code Groups and All Code.
Right click on Internet_Zone, Properties; Click on Permission Set
and choose Full Trust.
- Apply, OK. Its done.

Luis Dominguez.
I have no idea if that would be the answer, but as my name (baklogic=backwards logical) ther seems some logic there.

 

Looking up stack overflow
https://msdn.microsoft.com/en-us/library/windows/hardware/ff540620(v=vs.85).aspx
Seems you need someone who knows about debugging will b of more help.

 

OK plodr ... thank you ... I don't know why I didn't think of Microsoft Update History myself ... good one ... I was able to capture my available update history to a PageManager PDF Writer PDF file (attached) ... all of the December, 2016 MSO 2007 updates you listed were found in my history list, but none of the October or November, 2016 ones ... I think my Microsoft Update History record is truncated (not sure why, nothing prior to 15DEC16 shows up) ... I also think we've pretty much put the MSOE 2007 update angle to rest ...

I think some kind of C++ verification tool may still be worth pursuing though ...

baklogic ... I don't have 'MS Messaging Queue' listed as an available service (to turn on) in 'Services.msc' ... is that what and where you meant?

I do have 'Microsoft .NET Framework 1.1 Configuration', 'Microsoft .NET Framework 1.1 Wizards' & 'Microsoft .NET Framework 2.0 Configuration' under Administrative Tools. I followed Luis' advice that you found for me (in my 'Microsoft .NET Framework 2.0 Configuration'), however, the 'Printing Application' error (specifically under discussion) still occurs (albeit without having fully uninstalled / reinstalled the Lexmark Productivity Studio application suite, nor rebooting - I guess I'm hoping for a magic bullet solution ... they are quite often the case).

Re: debugging, I found WinCrashReport v1.25 at NirSoft.net, I am currently pursuing expert interpretation of the exception report it produces following a WER crash of 'Printing Application' (FRun.exe) (JPG & TXT attachments, HTML version of exception report not eligible for upload). I will further advise here as this progresses. FFF

 

I notice you have 3 updates for office 2010 in December........You have office 2007 ? Possible problem ? Try uninstalling those 3,to see if that has anything to do with it. This would follow ---I see it shows as a runtime error......
In my searching, I did notice that the .net 1.2 and .net 2 had a slight difference in how they handled things, so Luis blog might be near answering it. (exception)

 

it is possible that the ms messaging is not installed, or, if it is it might need a look at.......
http://www.microsoft.com/resources/...roddocs/en-us/snap_desktop_msmq.mspx?mfr=true
Apparently message queueing is administered in several MMC snap -ins (as per that page)

 

baklogic ... thanks for hangin' in there and helping out ... the MSO 2010 updates are to do with Microsoft PowerPoint Viewer (see below) ...

... the Microsoft Update History (PDF uploaded here yesterday) lists update KB2889841 twice for some reason ...

I have looked on this PC for an MSO 2010 PPTX / PPT* file that would have caused me to install this 2010 PPT Viewer ... I can only find one PPTX file, Date Created 23DEC12, that would have specifically required it ... looking back, I put the Viewer on here (same day, 23DEC12) prior to installing MSOE 2007 (on 19MAY14) ... so ... I could have done without the Viewer ever since ... how likely is it to be a / the problem do you think?

MSOE 2007 > MS Office Tools includes a utility called 'Microsoft Office Diagnostics', which I hadn't been aware of 'til I went looking for the 2010 app you questioned ... I ran it ... see results, attached:


... so, it found something and repaired it, however, no more clues were offered than what are shown above ... the 'Printing Application' error still occurred following (again, albeit without having fully uninstalled / reinstalled the Lexmark Productivity Studio application suite, nor rebooting) ... I wonder if I should be putting myself through that whole exercise for each of these potential fixes?

I added the 'Message Queuing' service (installed with all options available under Windows Components Wizard > Details selected), however, although it is an Automatic service, it was not Started and will not manually Start, generating the following error:



I have been thinking ... I didn't need to modify any .NET settings or add any services on a different, older (Pentium III 667 MHz) XP Pro SP3 machine (no longer in daily use) that has this same Lexmark Productivity Studio app suite installed (and working properly, without errors) ... so ... I think I should focus on the app crash debugging angle, and, possibly, the 2010 PPT Viewer uninstall angle, as neither it nor MSOE 2007 are present on the older PIII 667 PC. FFF

 

You probably need to restart the pc for message queueing application to start it (like other programs, it might need to start (and set to automatic setting) from startup.)
Uninstalling those 2010 updates that are not on the machine seems a good way forward.
All before trying re-installing Lexmark.
When uninstalling the printer, This might be a useful read ---- http://winhlp.com/node/199
Sometimes a clean up of the driver will help - Also, If you still have a copy of the older driver-......

 

baklogic ... oy vey ... the Message Queuing service ain't gonna' start on its' own (have re-booted several times in the interim since Wed the 15th) the way I had it configured (with all 4 options selected under A or R Programs > Windows Components > Message Queuing > Details when done successfully [so I thought] on Wed ... now that I've been back to A or R Programs > Windows Components for a look today, there is no check mark next to Message Queuing [see screenshot, below] and it will not re-install now - with all 4 options selected or with only the 3 defaults [all except 'MSMQ HTTP Support'] ... the error message flashed by and immediately disappeared each time, so, I have no idea what its' problem was ... likely has something to do with the fact that Message Queuing is already / still listed as a service in Services.msc ... this all likely also means the listed Message Queuing service won't be straightforward to remove, as I'm guessing I'll eventually want / need to do).


Thanks for the driver cleanup article link baklogic ... the Windows XP section's reliance on DOS commands to find and remove relevant INF & PNF files seems somewhat convoluted, however, I got a good DOS refresher and I do get how the author was circumventing the apparently typical read-only attributes of XP PNF files ... in this particular case, plodr's recommendation of the use of Revo Uninstaller had successfully stripped away all 'lxdo*.*' files in C:\Windows ... so ... no need to go further with my current uninstall.

As much as I hate to go through the uninstall again, I'll wait on uninstalling 2010 PPT Viewer for the moment and try re-installing the Lexmark P. S. app suite so I can definitively rule out the Microsoft .NET Framework 2.0 Configuration change made Tuesday.

I don't expect success, however, I should only be changing and testing one thing at a time ... then I can revert the change(s - Message Queuing will be another matter entirely) made and move on. FFF