Question

Locked

Q re: XP Pro Sp3 DeviceMgr "Non-Plug & Play Drivers"

By TerryGH ·
I posted this question on the MS Hardware Newsgroup earlier so excuse the duplication. I'll save a long winded description for now, but essentially as a result of a major trojan virus infection (now deemed clean by Trend Micro), serious
damage was done to my network adapters (all showing yellow ! marks) and some of the non-plug and play drivers (e.g., AFD, IPSEC driver, TCP/IP Protocol
Driver). My tech friend and the manuf. of the Mavell Yukon PCI/PCI-E controllers have already walked me thru trying to update the drivers from the
Marvell site (mssg says no better driver found), so the next step seems to be to see if the non plug and play drivers are the underlying culprit.

So my initial question is since right-clicking on the non plug and play drivers only gives me a choice between disabling or uninstalling (no option
to update drivers), and the properties for each of the flagged drivers says "this device is not present or working properly etc (code 24)" ----- how do I go about reinstalling them? Will XP Pro automatically try to add them on a reboot like the main network adapters (which are reinstalled ok but still are
yellow ! flagged). Or maybe the on reboot I will be prompted to insert the XP install disk?

Or... am I doomed to having to reformat the HD and do a complete re-install of XP Pro since I see in the details tab of properties that the Device Instance
Id is something like "ROOT\LEGACY_TCIP\0000"?

Thanks in advance for any ideas ....

This conversation is currently closed to new comments.

37 total posts (Page 3 of 4)   Prev   01 | 02 | 03 | 04   Next
| Thread display: Collapse - | Expand +

All Answers

Collapse -

LOL

by Jacky Howe In reply to Jacky's Q & Preparing for ...

KillDisk is new to me and I've always been able to get by with DBAN, even with Sata drives. So long as you can boot into the KillDisk software I don't think that it would matter which version that you use. Someone will correct me if I'm wrong.

Create your CD and run it. You may have to change the Boot order in the BIOS.

Follow these instructions to recreate a Primary partition after wiping the drive.

How to partition and format a hard disk in Windows XP

http://support.microsoft.com/kb/313348

You keep the Thumbs coming and we will be happy to supply answers.

Rob

Edit: to add

fdisk has been replaced with DiskPart. It does a better job when you get the hang of it. You shouldn't need to use it if you follow the link.

Collapse -

Qs re Cont'd Prep for Killdisk/Reinstall & Repair Attempt

by TerryGH In reply to LOL

Well I think I have the Killdisk bootable USB device setup ok (it wouldn?t write to my CD on the XP pro even though I was able to copy doc files to the CD). The process didn?t work as shown in the pdf manual (it went straight to format then stopped), but I do see on what I hope is the Killdisk bootable flash drive the killdisk.exe file along with 6 other files (including autoexec.bat) so unless told otherwise I guess I am also ready for that the reinstall eventuality, right?

Oh ... and I would appreciate clarification that the XP Pro (Sp2) install disk will also handle the partitioning/formatting after Killdisk is done (Edit note 11/17 11am cdt: verified yes by article: http://www.theeldergeek.com/formatting_drives_using_xp_cd.htm ).

And re the XP repair attempt, am I correct in assuming that if I try the repair on my Sp3 machine with the Sp2 install disk, the worst case is that the repair procedure won't run at all and then I can see about creating the slipstream CD mentioned in the link that Sean gave me: http://michaelstevenstech.com/XPrepairinstall.htm#RI -- or might the repair effort crash my machine and I won?t have a chance to make the the slipstream XP CD. Just trying to see if there is a quicker way to see if the repair option is even viable, before doing the clean install (yeah yeah I know ? I shouldn't take shortcuts but almost there ...*s)

Thanks again ... Terry

Collapse -

Maybe

by Jacky Howe In reply to Qs re Cont'd Prep for Kil ...

You could test the USB drive to see if it will work. You should be able to back out of the KillDisk program.

What were you formatting, the USB drive?

Is your USB drive able to be made bootable? Have you booted from it before?
<HR>
This is how I test them:

Just drop to a Command Prompt, then type these commands, pressing Enter after each command. WARNING! This is assuming that you only have one hard drive installed. Disk 0 is the primary hard drive and each drive that you have will increment, disk 1, disk 2 and so on..


diskpart
sel dis 1

If it shows up as a Drive, I then run these commands to create an active, formatted partition.

cle
cre par pri
for FS=Fat32 quick
act
***

exit 'to exit DiskPart

Run your software again to create the KillDisk bootable USB.

<HR>
The only problem that I can see is with a Sata drive. If XP can't see the drive you will have to slipstream the drivers. To test, just boot up with your XP CD and go to the recovery console by pressing the first R. Do a dir C: and if you get a response you are good to go. But surely if the XP CD that you have, came with the System you would think that it was compaible.


<HR>
By all means try the Repair with your XP SP2 disc. You will have to reinstall SP3 later. You could slipstream SP3 but if you are having problems burning on this System, it might be a no go, unless you have access to another System.


<HR>
Whatever you do don't Activate XP straight away, if it asks you to. You have 30 days to test the System after the Repair. This should be ample time for you to decide whether or not the Repair was a success.

Collapse -

Quick Pre-Repair Update & Thanks

by TerryGH In reply to Maybe

Once again big time thanks, Jacky (and of course, Sean) ... I have some real-time biz to attend to but I think I have all my questions answered for now: per the edit in the previous note (#23?) the XP install disk will handle partitioning and NTFS formatting of HD if needed, I tested (ok) advice from a TR article and on setting the XP Pro BIOS to boot the Killdisk flash drive (if needed), and I finalized/printed my excel file with the updated software list and screenshots of the desktop, Outlook email settings, etc. Oh and of course all data is backed up.

Hopefully will be reporting back later that all went well with the XP repair per your suggestions .... Or a progress update on the re-install process.....

Collapse -

I hope everything goes smoothly

by seanferd In reply to Quick Pre-Repair Update & ...

throughout the procedure, when you get to it.
:)

Collapse -

Good Luck

by Jacky Howe In reply to Quick Pre-Repair Update & ...

and keep us posted as to your progress.

Rob

Collapse -

XP Pro Repair Status --- Hung up on reboot?

by TerryGH In reply to Quick Pre-Repair Update & ...

Things were going along fine it seemed -- the repair process started as explained here >>
http://www.webtree.ca/windowsxp/repair_xp.htm#How to Repair Windows XP by Installing Over top of Existing Setup: (not sure if link copies over ok) ... and it prompted me to add the motherboard and sound blaster CDs to get files, reinserted the XP install disk and it asked for the product key and then the screen timer counted down to 1 minute and then it automatically rebooted.

It seemed to start up ok (skipping the Xp install disk) and started to load the WinXP logo etc but now for the past half hour or so the system seems to be hung up and just showing the logo and a mssg ala "Please Wait..." and no activity is apparent for the HD or DVD rom where the XP install disk remains.

Since I have to head out for a meeting shortly I will leave it be until I get back in a couple of hours and try a reboot, and of course if that fails ... well thanks to you guys I have the Killdisk ready to go. I think Sean said to let it run overnight anyway so the timing works out just fine ... kinda sorta @#%%# -

Collapse -

Ugh.

by seanferd In reply to Quick Pre-Repair Update & ...

Probably best to go for a full wipe and reinstall then.

If there is a difference between the current service pack, and that of the install disk, I can only assume that something has not behaved as expected. My condolences.

By the way, for running Killdisk or DBAN overnight, the general suggestion is to set it to do 3 passes (wipe 3 times). This should eliminate the possibility of any malware reanimating itself.

Collapse -

KillDisk & XP Pro Reinstall Notes & Qs

by TerryGH In reply to Q re: XP Pro Sp3 DeviceMg ...

Thanks for the good wishes / condolences *s* --I just got Killdisk working and the 'welcome' mssg said the free version only supports 'One PassZeroes' then selected the SATA drive and now have "Erase All Data" working. The obvious next step is to "wipe out free space" but wondering if it makes sense to see if I can manually try what Sean suggested (3 passes), and see if Killdisk will let me run the erase process a 2nd and 3rd time before doing the wipe?

On the reinstall side of things -- I plan on re-downloading TrendMicro since I have that subscription in place before going after the SP3 and other downloads, do you guys have a suggestion on a 2nd A/V software to install before or after the MS updates have done their thing and I start re-installing my other software?

Thanks ... TGH

Collapse -

As I said earlier

by Jacky Howe In reply to KillDisk & XP Pro Reinsta ...

I'm not familiar with KillDisk, I know that DBAN will do three passes by typing Autonuke. It should be enough to remove any virus activity. You could manually run it again if it dosn't take too long.

I normally disable automatic updates until I have my Antivirus installed and Updated.
If this System is no used in a business you could try using the Antivirus that I've been using for over twelve months for free. Avast

<a href="http://www.avast.com/eng/avast-free-home-antivirus-antispyware.html" target="_blank"><u>Avast-Free-Home-Antivirus</u></a>


It is never a good idea to run two antivirus scanners simultaneously. However, if only one of the scanners has real-time protection enabled and the second scanner is used only to manually scan selected files, they may possible co-exist peacefully. In some cases, an antivirus scanner will not install if it detects another antivirus scanner already installed on the system.

Back to Malware Forum
37 total posts (Page 3 of 4)   Prev   01 | 02 | 03 | 04   Next

Related Discussions

Related Forums