Just Installed Xp Sp3 Over Vista And Bsod On Bootup

I think my problem's similar to tigala's, except I don't have Vista drivers (at least I'm fairly sure I don't) and I didn't install SP3 over Vista. In fact, I purchased my laptop last summer from Dell and made sure to have XP Professional SP3 on there and not Vista whatsoever.

As of two days ago, my computer crashed and BSODed to simply this:

STOP: C0000139 {Entry Point Not Found} The procedure entry point GdiGetBitmapBitsize could not be located in the dynamic link library GDI32.dll.

No safe mode booting or any other booting of any other kind allowed. Googled around (from another compy obviously) and saw that I was not alone. However, everyone else seemed to have newly installed SP3, whereas I never had this problem until just two days ago. Found fixing instructions on MS Support and on the blogs/websites of other frustrated users.

The instructions are simple enough, and I followed along swimmingly until I got to the instructions which read this:

"At the Recovery Console command prompt, type the following commands. Press ENTER after each command. ren %windir%\system32\gdi32.dll %windir%\system32\gdi32.dll.old
copy %windir%\servicepackfiles\i386\gdi32.dll %windir%\system32\gdi32.dll"

I know that "%windir%" means the directive as to where the file will be located, which is usually C drive and is C drive on my lappy, but no matter what I type in "the paramter is not valid". Here is everthing in full from the Recovery Console (including my command entries):

Quote

Microsoft Windows XP™ Recovery Console. The Recovery Console provides system repair and recovery functionality. Type EXIT to quit the Recovery Console and restart the computer. 1: C:\WINDOWS Which Windows installation would you like to log onto<To cancel, press ENTER>?1Type the Administrator password: *so on and so forthC:\WINDOWS>REN C:\Windows\system32\gdi32.dll C:\Windows\system32\gdi32.dll.old
The parameter is not valid. Try /? for help.

I get the same thing every time. Tried tweaking the command to a dozen different things, but to no avail, all the same thing.

I am no good at DOS to begin with, but I have a feeling that the problem is because the command line starts out by default as "C:\WINDOWS>", which means I'm already in the drive.

PLS SEND FOOD AND HALP. :thumbsup:

Thanks in advance!

Now off the Internet to de-brain and get my eyesight back after spending way too many hours trying to fix this.

BleepingComputer.com: Just Installed Xp Sp3 Over Vista And Bsod On Bootup