Two things. First, you are going to need to repair the installation.
If you do not have a CD of any kind, I would contact HP for one. They
should have given you at least a recovery CD if not an OEM copy of XP to
be installed on your computer. Now you run into the problem that OEM
copies of XP like you have are only supposed to be installed on the
original machine it was on, which means it would not be legal to use it
on your new computer. Before everyone flames me, this is how most OEM
EULA's are written and I really don't care what it says because in my
opinion you paid for the OS when you paid for the computer.
Anyways, if you really want to try to hack your way in, you can still
use the recovery console without having the CD. You will need several
floppies though.
For XP Home without any Service Packs:
http://www.microsoft.com/downloads/r...eleaseid=33290
For XP Home with Service Pack 1:
http://www.microsoft.com/downloads/r...eleaseid=42818
For XP Home with Service Pack 2:
http://www.microsoft.com/downloads/d...displaylang=en
For XP Pro without any Service Packs:
http://www.microsoft.com/downloads/r...eleaseid=33291
For XP Pro with Service Pack 1:
http://www.microsoft.com/downloads/r...eleaseid=42819
For XP Pro with Service Pack 2:
http://www.microsoft.com/downloads/d...displaylang=en
I really don't think it is possible to repair an installation using
these disks, but you can still try. I would boot into the recovery
console and try fixboot. It is worth a shot, but you probably need the CD.
----
Nathan McNulty
NoSpam wrote:
> Ruairi Glenn wrote:
>
>> Any ideas on how to get round this agp440.sys problem? I *really*
>> don't want to do a clean install as I have no win xp cd's. My hp
>> pavilion system contains it's setup files on some hidden partition on
>> the drive.
>
>
> I had this issue so disabled it via recovery console, it's possible to
> disable services and drivers thatta way, but to do this you'll need an
> XP CD to boot into it.
>
> I'm sure there was soomething else that stopped me booting the machine
> as well though, so still ended up flattening it.
>
> XP doesn't like a change of motherboard IME/IMHO, the only way to do
> things right it is installing a fresh.