• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

xp installation woes

I

InvisableMan

n00b
Joined
Jul 14, 2004
Messages
30
i'm familliar with problems with windows, being a user since 3.1, but this one confounds me.

i've been running an athlon xp, and was given an athlon 64 with a ecs 755-a2. swapped the mobo out, plugged everything in, booted up, tried to boot once normally, no dice, automatically shut down, so i went to do the coustomary repair install to take care of all the drivers and start from scratch. ok. boot into the cd, start the repair install, drivers are having problems copying over. i try to complete it anyways, and once the install completes, it bluescreens. ok, i clean the disc assuming it was the scratches and smudges on it, and try a full install since that messed up my os. same problem, after install, bluescreen. now whenever i try to boot normally it just goes blank after the bios screens recognising all the drives and everything. whatever. i get a fresh copy of xp from my grandfather and try it again, this time i checked the disk and it had no errors in it just to make sure, and now when i boot into the cd, and i come to the screen wether to do recovery console or contunie installing windows normally, nomatter what option i press, bluescreen:

*** STOP: 0x00000024 (0x001902F8,0xF79B2740,0xF79B2440,0x807EA9E0)

is this an indication of a problem with my harddrive, or is it still a problem with the cd? or something else?
 
ok, when it scans the first disk, it bluescreens. maybe there is a problem with the disk afterall. i hope not.
 
Stop 0x00000024 or NTFS_FILE_SYSTEM
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives.

I recommend you to run the hard disk diagnostic software, all brands have their own tool, all included in the ultimatebootcd, if the disk is ok, then you may need to wipe with 0's and create a new partition and reformat (the wiping part is done with autoclave or dban included in ubcd)

Dont forget to try a new ata100 ide cable, those little bastards are cheap as hell :D

Good luck

oldmx
 
ok, another update. sorry about not using edit, i'm on a 6 year old laptop that's barely running and takes 5 minute to load a webpage, with one of those crappy little nub mice between the GHB keys on the half broken keyboard that i had to replace with a pencil eraser and i hate it... um anyways, i switched the primary harddrive to the slave, and i got to the install process, so i figured i would install it temporarily on this storage disk and when i started the install, it started with the same problems not copying files properly.... now i am really confused, because this is a fresh disk. is windows smart enough to break my computer because im trying to install a invalid copy of xp?



ok, update again. thanks for the info, however i am in no position to try that tonight with a brand new cable, however i can swap out the cables i have for various old spared and such and maybe that will work. can you link me to this ultimatebootcd? i cant really get around easily on the internet for said reasons above.


update again: found a brand new cable, same problems in the original configuration (STOP screen, going to try it with the storage drive as the master to do a temporary install, and see if i have the same file copying problems.. do you think windows installing with problems may have messed up the filesystem bitself, even though i didn't tell it to mess with the filesystem upon installing?

update again x3: tried to do a install on the storage drive, didnt get a stop screen as before, but STILL having the file copying issues.i don't know anymore. i'm not going to let the install go this time, to prevent the apparent problems that i caused on my main drive doing that. i'll continue when i wake up, the last thing i'll do is mess around more falling asleep at the keys. any help and speculation and flaming will be appreciated, if it helps. :(
 
It's more than likely the cdrom or the ide cable(s).
Replace cables first. Then try a different CDRom
 
well ok then. i guess i'll have to go somewhere and have someone else burn it for me. any other suggstions while i wait to do that? does anyone know why two install disks have done this in a row?
 
Sorry, I meant cdrom drive. Not the CD itself. I'm still guessing its IDE cables, though.
 
RavenD said:
http://www.ultimatebootcd.com/
I would also try running memtest, to rule out a problem with the ram
Click to expand...


Have you bothered to try what this guy suggested? Or maybe just download Memtest86 ISO burn it and run from that?

For me 99% of the time when windows has trouble copying over files it is a memory issue.

Now this doesn’t mean you memory is bad. It may just be incompatible with your new motherboard and CPU. In some cases it isn’t even the memory’s fault that it is erroring. These errors can come from a PSU that is not up to the task and or issues with the capacitors on the motherboard.
 
good good, this is what i need. info info info speculation info, :)

this all helps, i'm gonna try and get that burnt tonight, my only burner is a dvd burner on my main computer

also, i didnt think about it beingf a bad ide cable for the cd, good. i'll try that later. :D
 
There are so many things that could be going wrong here it's not even funny. If the hard drive turns out ok, and the cables are working, it's bound to be something else. My personal belief is it's a bad burn on the copied XP CD you're apparently pilfering from relatives.

Invisableman said:
is windows smart enough to break my computer because im trying to install a invalid copy of xp?
Click to expand...

I'm not a Mod here but I know from experience they don't appreciate or tolerate any discussion of using, installing, upgrading, troubleshooting or flat out admissions of you working with pirated software. If that's what you mean by "invalid copy of xp" then so be it; if not then I apologize for making that assumption.

Just my $.02.
bb
 
no, we have tons of legal licenses and keys that we own, but only one original disk of xp itself. it turns out that i hooked up the computer to my old storage drive (the original drive with system on it is not connected, i'll get to that)

what i was wondering was if xp knows that it's been burnt to a non valid cd and messes itself up because it isnt on the right type of media since this is the first time i havnt installed it from the original disk. you know, like how ps1 games were when you tried to copy them on to just any old disk. i guess not, as i was saying, i put the old motherboard back in and hooked into the old storage disk, made a temporary install of windows on that and i am running on it as we speak. ok, fine. i guess it was a memory problem. i
ll put the 64bit stuff into a old chassis and make a test machine and play with some new memory i'll buy later. the problem is now, the main harddrive. whenever i have it hooked to the computer, even as a slave on the jumpers and on the cable, when my computer boots up it bluescreens with the same ntfs STOP.

since it's a slave, why would windows bluescreen upon boot since it shouldn't even care about what it has on it? apparently something with the filesystem is corrupted, but as i said, why should the computer care? i should be able to boot up as i am now and play with it.... however, bluescreen bluescreen bluescreen. any help? (also i'm burning ultimatebootcd as we speak. i'll check the disk out on that when it's done, but i like speculation and ideas from you guys. it helps me see things i don't think of)



edit:
testdisk sees the partition information fine, didnt need to search or anything for it, so i can't figure out what's wrong with that harddrive. i don't want to format it AGAIN unless i absolutly have to. i just did that back in feb and it hasn't been long enough to recover from the tedium of reinstalling everything yet. i still need 5 or 6 more years before i'm willing to do that again. i'll mess with it more, i guess, and see if i can find any bad ebil problems lurking on it causing it to have that specific error.
 
You must log in or register to reply here.
Back
Top