CF-29 MKIV touchscreen issue

I'm going nuts trying to figure this out. The other day I had some spyware that Malwarebytes Anti Malware successfully removed. Now my touchscreen doesn't work, it just pins the cursor arrow to the right. I can go to calibrate and it acknowledges the presses on all the +'s, but it comes up with a parameter error when completing the calibration. I've tried reloading the driver and it still does this. Anything else I should try?

Thanks,

Mark

 

See if there is anything that is stuck in the lower right screen bezel....

 

Tried cleaning out the screen edges and no debris came out. I did get this unit in exceptionally clean condition though. Not sure if I've got some file corruption going on or what, but I'm considering doing an XP repair install to see if that helps. The TS worked great up until malware files were deleted. I'm sort of dreading doing a full re-install because I don't have resto disks, I'd be doing it all manually.

 

RESTORE...RESTORE...RESTORE...

I know you don't want to hear it, but it is most likely what you are going to need to do. You CAN try to uninstall/reinstall the TS drivers, or roleback your PC to a known working date prior to the maleware clean, but I don't think it will work or that you would be happy with the results even if it did.

Just my suggestion...

Paul

 

Mark,
Find someone who has purchased a new Dell with XP in the last 18 months or so. Install the operating system from the Dell disk, should be SP3, then the drivers. It will be faster than the restore disks as it will take you forever to download and install all the updates which have been released for windows since the restore disks were made.
CAP

 

Thanks for all the input. What I ended up doing was a repair install from a slipstreamed OEM XP SP3 CD (I have the license and genuine OEM XP SP1 cd). Only had to do one MS update after the repair install. The problem remained. Then I dug a bit further and I found an uninstall file for the mouse driver and utility. I ran that and rebooted (with no mouse support). Then I re-ran the mouse driver/utility install and re-booted. Calibrated the TS and got a parameter error only it was "Error A" this time instead of "Error Dtp" or something like that. I re-booted, and then retried the calibration and it worked. It's been working since. Weird. I think I may just re-install the whole deal for peace of mind.

 

Hence this comment. I have had similar issues and even though uninstalling/reinstalling seemed to work, it just never quite ran the same afterward. This was, as in your case, after removing maleware/viruses/spyware. To this day, if I EVER get those that need to be removed seriously, I nuke and pave (restore). If I were you, I would keep a close eye on it for about 2 weeks. If it starts acting weird in any way, then bite the bullet and do a restore.

 

I was sort of thinking the same thing. If the fix lasts then thats great, but if it messes up again, reload time. At least it bought me some time to mess with nLite some more and I can make an even better OEM resto CD that will be a more complete/seamless restoration.

 

Do a reformat....

 

It went back to acting up today, so as Doobi put it, "Nuked and paved". BTW what is PRunOnce.exe for? I backed up all my driver and utility files and found that file in there, can't seem to find any reference for it. I downloaded fresh driver files from Panasonic to ensure I've got no corrupted files, basically just using my backed up files as a roadmap.

I'm going to end up re-loading the OS tonight though because the TS problem manifested itself yet again while screwing around with my wireless (PROset) drivers. Finally figured out that getting the PROset driver directly from Intel saves you the headache of loading weird files to make the Panasonic PROset driver work Look at the whacked out instructions for loading Panasonic's file, wlan_d080215.exe

 

Ahem...

Nuke & Pave is a dwagon-ism, yessir...

mnem
Now why would you pave over a nuke? I mean... it would still go off, but you couldn't have the fun of watching idiots try and defuse the d@mn thing...

 

Absolutely! I liked that phrase that YOU INVENTED, so I .... well, I stole it!!!

 

Don't use Proset
Unistall Proset if installed with a restore disk right away
Then download intel wireless drivers and install driver only Not proset and let windows control wireless
Falure to delete proset causes BSOD errors


Alex

 

Interesting that there are so many issues with proset. I use it on 3 TB's, 2 of which are MK4 with no problem. I did have reception issues though with windows managed. Go figure.

 

I too have been using proset on all my Toughbooks with no issues whatsoever for the last 7 years...

 

The driver issues ,which show up because of incompatibility with the newer windows service packs are one reason why I deleted proset and let windows handle the wi-fi connection
The standard windows utility works for me, and Vista’s seems even better
Note: proset will not work in Vista

Alex

 

From what i found in my searches PRunOnce.exe seems to be some kind of spyware. On a few sources I found that malware programs can actually disguise themselves as this file to kinda fly under the radar, especially since it's found in the windows or windows/system32 file. I'd suggest getting rid of this file.... Google search does wonders sometimes

Daniel

 

PRunOnce.exe is Panasonic Run Once - it's a customized version of the MS oobe.exe (Out Of Box Experience). It, as the name implies, runs once after install at the first boot - where you see the "Welcome to Windows" animated presentation and it asks you for the essential information needed to set up the default user account; I believe it also launches the Touchscreen Calibration Utility at this time as well.

While the process name CAN be hijacked for use by malware, so can ANY executable found in that directory. I would NOT recommend deleting it, as I believe it replaces the oobe.exe, which is used every time you create a new user account on the machine to populate the same information and personal settings as it did for the default user account. If you are concerned that it may be malware, scan it with a standalone virus/spyware scanner.

mnem
The road less travelled... is usually full of crap that gets in your way.

 

I heard of this new virus on the news - it's called the "Windows" virus... Anyways, I ran a scan, and sure as hell my computer was definitely infected with this virus, so I just deleted it and now my computer doesn't run at all... Any ideas?

 

Buy a tube of KY, then buy a Mac.

mnem
Windows is the world's SECOND best marketed virus software...

 

Did you delete the whole windows folder?

That’s where I think you went wrong

I think you can fix it with a deletion of the system 32 file in windows ( there is lots of stuff in that folder that a bad virus can hide in)

Just joking DO NO DELETE AND FILES UNLESS YOU ARE SURE

Alex

 

Well, then... CARRY ON.

mnem
Snurching - just another service we offer...

 

HAHA... I thought I'd get you guys going

 

Well I got everything working right again after a second re-load of the OS. On the last OS load I had the mouse flying all over the screen whenever the GPS was on (more on that below). Tried all the fixes on here, nothing. So I reloaded it and it's all good now.

It turns out my original TS issue was in fact hardware related. I opened the lid and re-seated the TS cable and it still had the un-responsive cursor. So next I did what you're always told not to do, I messed with it while running. I discovered that flexing the cable while it's plugged in caused the cursor to respond. I added some tape to the back side of the ribbon/plug to make it just a hair thicker and plugged it back in. Been working since.

Apparently when I messed with it while powered on it caused the com ports to go nuts and it got the MS ballpoint mouse syndrome. Then when I used the Panasonic GPS patch file the mouse settled down but software couldn't find the GPS even though device manager was reporting Com1, 2, and 3 as active/enabled.

I reloaded again and now everything is good. I'm posting this off it right now, working touch screen and all.

BTW, who needs recovery disks? Get out your old OEM XP disk, grab nLite, and slipstream that bad boy to SP3 and as an added bonus add all your drivers to the disk too. When I get done loading XP now, I only have to run Intel PROset to load up WiFi and I'm done! Oh and I made mine on a DVD so I have my standardized "pallet" of software I usually load on there too. All on one convenient disk.

 

Ahhh... I suspect I know what happened to you then...

The ribbon connector is supposed to have an extra layer of thick plastic right at the connector end; it's there to make that part rigid for ease of connection. Sometimes the glue will not hold so well, and when you unplug it, that little bit of extra plastic goes south. Now your connector doesn't have adequate thickness to provide proper connection, and you get these kinds of problems.

mnem
Of course YMMV, IMBW, BSOD, DILLIGAF...

 

Actually, the thick white plastic end was firmly attached, but the gold tracks looked very grooved instead of flat. Hopefully the extra thickness of the tape will be a somewhat permanent fix. At least if this happens in the future I'll know what to go after.

 

Those "grooves" show that you have/had a good connection... Usually...

 

Ummm... Did you try staples?

mnem
Sorry... having a Scrooged moment there...