Boot Times

I've been having some really bad boot problems with my computer lately. A couple of weeks ago, I was unzipping a file and explorer.exe crashed. I tried to restart the process, but I couldn't open anything without it crashing. I couldn't run anything, so I rebooted the computer. Upon reboot, I was fucking greeted with a message prompting me to run chkdsk. It was at a screen before it started up the desktop enviroment. It said that $MFT was corrupt, which meant the master file table was corrupt, and unless I wanted XP to start writing over my files, I had to reformat. I backed everything up, and reformated and reinstalled Windows. I updated to SP2, and this is where the problem I'm having now starts. As soon as it reboots, it progresses past the IDE and memory check in the BIOS. Then, the screen goes completely black for about a minute and a half. Then, a gray loading bar appears at the bottom of the page and takes about 5 minutes to dissappear. After that, it boots in about 12 secs, and I ran bootvis to confirm that. I have a Maxtor 250GB SATA drive and a (shitty) PM800M2 motherboard from ECS. I have the latest drivers on and I'm running Windows XP Pro SP2. This problem only happens when I install SP2. Do you guys have any suggestions about what I should do to fix this?

Do you guys have any suggestions about what I should do to fix this?

Install this patch: http://www.opera.com/ oh wait wrong link lol, here it is: http://www.kernel.org/

>>2
LOL Fuck you, but thanks anyway. I can't run a good-sized chunk of my porn on Linux, so that's out of the question.

Stay away from (shitty) Maxtor from now on. [and ECS while you're at it]

>>2

Why opera?

>>4

I bought this computer off of eBay while I was moving. The motherfucker I got it from replaced some really good parts with some really shitty ones. I was getting a new seagate drive instead of a refurbished piece of shit maxtor, among other parts he replaced. Needless to say, I made him refund half of my money.

>>4

Amen.

lol

>>3
LIES!
mplayer is the porn viewers best friend.

>>3
Why do you think you can't run a good-sized chunk of your porn on Leenox, huh?  Use VLC.

>>5
I said it was the wrong link, ok.

>>10

It's porn streamed from web pages that only work inside of Internet Explorer with Windows Media. Every alternative I've tried to use to play the movies in either Mac or Gentoo Linux have not worked.

>>11
Link me and I'll fix it, or not post back.

>>12

Sorry, but it's porn I actually paid a couple bucks for, which means you can't get in to fix it without wasting monies.

>>13
Manure fetish?

>>14

Sorry, no schieza.

Don't pay for porn. In addition to getting your money and card information they get install their own little services that replace the already sufficable programs on your computer. (Spyware)

>>16

Trust me, there are no services. Also, I stole the pass off a friend's computer, so I don't have to spend 10 bux.

Check your bios if you have support for RAID, if so (and your not using raid) disable it.

>>18
Thank you, Mr. Anon. That makes perfect sense, and I'm going to try and disable it right now.

>>18

no luck :(.

RAID was already disabled. Also, I already installed all the drivers from ecsusa.com.tw for this particular motherboard, after I put on SP2.

OP FAILS FOR PAYING FOR PORN

HEY >>21

LOOK AT >>17 MOTHERFUCKER

ASSUMING MAKES AN ASS OUT OF YOU AND ME

Run a MemTest-type program. There might be something wrong with the RAM.

It's probably the Maxtor AIDS you've got, though.

>>23

I'm gonna run Memtest soon. But you're right, I prolly took the Maxtor knot.

don't blame Maxtor for you lame ass boot times - that's window's fault DUH - atleast i got hit with a virus WHILE SLEEPING. i wouldn't let no nigger zip file kill my entire computer!! ROFL

i got hit with a virus WHILE SLEEPING

zomg haxors got ur pc?

get pc-cillin now

>>25
fuck you. i just switched out the drives and set the maxtor as a slave after installing windows on another drive. the problem is solved, no more fucked up boot times. So take your "nigger" virus and go fuck yourself.

>>27
The problem was resolved after you booted into a fresh Windows installation, how does that disprove anything the others said?

Try again.