s1m0n

hrmm, thanks for your advice Unimatrix-Zero... well, to tell the truth, I am quite familiar with computers and stuff so I do defragment regularly... I am what people called "power user" hehe... I use Disk Keeper 7 to defragment... and for pagefile... I have none 'caused I disabled it (i have 512mb of ram...) anyways, thanks for the input!

sorry i wasn't clear before, but i do have my hdd partitioned into 3 drives. specifically at 19547MB, 19547MB, and 19538MB. Drive C: IS my XP drive. I use my E: drive for downloads... although I have been slippin some files here and there into C: & D: cuz E: ran outta space, hehe.

you are probably right, my hdd is very full right now, luckily, i got myself 100 blank 720 mb cd's today... hehe, happy burnin' for me!

I myself have a 24x10x40x burner, and I gotta tell you: When you have the speed, there's no turning back! Honestly to say, 6 min isn't much, but think, just think, a cd in about half that time! Hehe, it's all in the speed baby. Besides, some people really has the need for fast speed burners... take myself, I can't seem to burn fast enough, as of now, I only have 3 Gig left on my 60 Gig drive because of "stuff"

no, i am talking about the actual saving process. btw, i have a ibm 7200 60 gig drive.

I don't know if this is a serious problem with some people... (or maybe just my system), but sometimes, when i am saving image to my hdd, usually the 1st pic saved in a directory that has thousands of pics, the reaction in XP is slow. It kinda just sits there, thinking or something. NOt really a big problem, but I am impatient with this sort of things. System Spec btw: Athlon Tbird 1.02 GHz PC150 512MB Ram Windows XP Pro 2600 Final Problem only seem to exist in IE6? Btw, I have the pre-Service Pack for IE6 installed. It happened before and still after the SP, so I guess that's nothing. Any ideas would be cool.

heh, thanks, i was looking for audio shell player for the longest time... lost it when i formatted. thanks again, much appreciated

hrmm, odd... i rebooted my comp and it's fine now. maybe winxp does self-heal... haha... thanks for the reply tho.

ok people, this is a weird error i got today trying to run gpedit.msc: Failed to Open Group Policy Object group on this computer. You may not have appropriate rights. Details: The file or directory is corrupted and unreadable. ok i never had that problem couple days ago. what the heck is up with that error? and i am on an administrator account and the only person to use this comp. anyone help?

here's the deal, my hard drive is ibm deskstar 60GB and i currently have 3 partitions. they are C:14.3, D:17.6, and E:25.2GB. i have winme installed in C: and winxp installed in E:. and currently i use D for downloads and etc. so what i want to do is shave maybe 10GB or so to D: and convert the E: to NTFS. How can this be done in a safe manner without having to risk losing data?

ok, i know some peepz gonna think i'm a nut but i am still gonna say it: i believe winxp is much more sensitive towards hardware and if any part of it is failing, (even if it runs fine in win9x) it'll croak out. for me example, i solved my problem thru loweing the clock speed, which equals less heat given off by the card, etc and that worked. and i even went further to attach a bigger 5400 rpm fan to my vid card and now everything is fine. so basically, what i am saying is make sure it's not your vid card itself giving heat to xp, know what i mean? laterz all

I want to convert my current XP partiton from fat32 to NTFS using Partition Magic 7. But I want to know if it's safe and will I encounter any problems. By the way, I want to preserve all my current files, a simple conversion, nothing like a format, etc. Thanks.

to clear things up: i lower the "default" speed of the bios... which i had bumped up myself using a bios tweaker. so in reality i did not lose or lower its stock speed, just my oc'ed speed. hope that clear some things up.

hmm, for me, like i said, the problem was solved when i lower the clock speed on my vid card. although the bsod says it's something wrong with the drivers, that wasn't the case for me. have you tried lowering your clock speed?

like i said, in winme that clock speed worked fine, that's why i didn't think of it. besides, i totally forgot about it because that clock speed is my default speed because i set it in the bios.

hahaha! omigod, i was such an id***!!! i solved the problem, muhahaha! i can't believe i didn't think of it. alright, here's the solution my friends: lower the clock speed on your vid card! i totally forgot that i had overclock my vid card thru modding the bios. haha, ****, i guess the reason i didn't think of it was because winME handled the speed fine, but i guess winxp is more sensitive. alritghy! there's the answer to all peepz! leave me a msg if you wanna know how to lower your vid card speed by bios! laterz and thankz to all who've tried to help!

LouCypher is correct, i don't use any burning prog. my burner croaked on me a while back, and since i have a pretty fat drive, i was too lazy to get myself a new burner. (for those who are wondering how i installed xp: i extracted the iso and install from hd... whole installation process took less than 30 min)

my system spec: 1 GHz K7 Via 133 chipset pc150 512mb ram maxi sound muse geforce 2 gts/pro d-link lan ibm deskstar 60GB 52x cdrom winxp 2600 corp tried all nv4 detonators and some older dets. LouCypher: i've read that post already, using different det doesn't help... although i notice 21.88 tends to crash more than 20.80. and i don't think it's irq prob, i've pulled out my cards, etc, no avail. ...maybe this has to do with geforce 2 gts/pro's bios? anyone point me to a place where i can find the newest gts/pro's bios? (datewise please) i don't care much for the manufacture, i can modify it so it'll work on my card. thanks peepz!

I am running WinXP Pro final corp. The friggin O/S crashes like a b***h, hangs at hella random times. I then see the BSOD and the error message says nv4_disp has cause infinite loop error. What the f*** does that mean?!? I've tried alot of different detonators, but it's still the same thing. help anyone?