fresh copy of xp wont work

  • Thread starter Thread starter Ivan Tang
  • Start date Start date
I

Ivan Tang

Alright, this is weird. I have done XP Pro installation many times but this
one is by far the worst one yet. I have two computers, one generic brand
with all generic parts and the other one a HP i bought from Future shop. I
have done XP installation on the Generic one many times and every time it
works like a charm. but on the HP machine, installation was ok but once it
finishes setup and boots into desktop it is weird. I tried to run msconfig
and Regedit, both would closes on me after about 10 seconds of use. I
installed Norton ANtivirus but it would not start. the worst is, i get the
RPC shutdown (Looks like the blaster effect) but it could not be because I
am not connected to the Internet during an after the XP installation. so I
take the same copy of XP and installed it on the other generic brand machine
i have and everything is normal so i know for sure my XP installation disc
is not infected with blaster. My guess is because i bought the HP machine
from future shop with HP's version of XP Home installed and they did some
customization to XP. and now I Install XP pro in and weird things happen.

what do you guys think? please give me some suggestions!! thanks
 
I also bought an HP pc and formatted the disk and did a clean install of XP
Pro with no issues at all.
What model of HP do you have?
 
You do have all the symptoms of a virus that I ran into last month. But ,
with a clean install that rules that out. I know that install do not go
perfect every time , they should , but they don't , I can not explain it.
Do a repair install and that should fix it. Jym
 
I dont know either. i have installed it about three times now and each time
with a full NTFS format and the symptoms just resurface right after it
finishes setup. yeah maybe i should try to do a repair install. one more
thing though is that none of those symptoms surface if i boot in safe mode.
i am confused
 
If it works in safe mode , that would lead me to believe it might be a
driver issue . You could go into the device manager and delete the hardware
drivers one at a time and see if you can find the cause. Jym
 
Back
Top