Installing OS on new computer

[guest]

So, I just bought a new barebone computer w/ a asus mother board, PS, core 2 processor.

So I throw a new hardrive in it, from the same place, CD ROM and floppy. Throw in a XP disc, it starts to install, loading files etc. then I get a blue screen before it gets to partioning and formatting, etc.

Is there something your supposed to do to install a new OS other then simply just throwing in a xp disc??? or does new cpu's know it's not a real copy of xp???

HOLA BACK Y'ALL!!!!

o yeah, I took it back to them saying it didn't work and they were talking some BS about checking it out for a min. of 2 hours for like $70 and $20 to install a OS. I was like hell no cause the shit is brand new. and its got me thinking what there going to be using, disc, to install xp on the cpu and what could be possibly wrong on it if its new. Also, they put a new memory stick in it and it still wont work..........

[ddd4114]

what does the BSOD say?

Were the motherboard, power supply, and processor all in that barebones package?

Are you using an IDE or SATA hard drive?

[99ctrhatch]

check your ram

[guest]

what does the BSOD say?

Were the motherboard, power supply, and processor all in that barebones package?

Are you using an IDE or SATA hard drive?

BSOD??

The barebone came w/ everything installed but the harddrive, SATA, that I bought from them new, CD ROM and floppy.

[Richie_A_19]

BSOD = blue screen of death

What error do you get?

[ddd4114]

I assume the SATA hard drive came with a driver?

There's one point when XP setup first starts when it loads a whole bunch of drivers for a minute or so. I'm pretty sure that sometime during that sequence, it prompts you to load any third party SATA drivers. If you don't do this, and the generic driver doesn't work, setup will start complaining.

That was my first hunch. My second was that the hardware isn't compatible with each other, but since you got everything in a package deal, I doubt that's the case.

[Haysoos]

DDD has a point, sometimes you have to use the SATA driver disk that comes with the motherboard to load drivers at the beginning of setup, but that would not cause a BSOD.

Guest, that bluew screen error you got at first is called a blue screen of death. We need to know what that screen said, it'll have file names or something like "STOP: 0X000000A0 (0XFD84AF74, ...)"

Usually this is caused by bad ram or a bad CPU. Pull the memory stick and put it in a different slot, try it again.

[guest]

Well the harddrive didn't come w/ a disc. The motherboard did. I'll try loading that disc when it asks.

The screen gives me a
STOP 0x0000007 I believe
pci.sys, something

I wrote it down but I dont have the paper at this very moment. I tryed the other mem. slot w/ the original mem. not with the new one they gave me. I did some research on it and people were saying bad mem., disable pci something in the bios, upgrading to the sp2.

Like the main thing I wanna know is that if you can use the original xp pro. with the new core 2 processors? and if it's possible for the cpu to know I'm using a copied version. I the hardware driver sounds like a good idea, though I did get an official copy of 98 second edition on it?????

[Haysoos]

XP will work with any x86 CPU, that includes the core 2 duo. In fact, let me set your mind at ease, I'm running a corp. copy of XP pro on a core 2 duo right now. So thats not the issue.

I'll try to hunt down that error code. If you can post up the whole thing, i can be a lot more help. :D

[Richie_A_19]

http://support.microsoft.com/default.aspx?scid=kb;en-us;330182

[SOHC_STUDENT]

try resetting the BIOS to factory defaults

sometimes computer shops will play around with a mobo and then sell it

or like the others have said you may need to supply the SATA drivers by hitting F6 at the beginning of the XP install when it asks about hard drive drivers...

[guest]

what do you mean, by reseting the bios? plugging the cmos battery??

[guest]

The error message is

STOP: 0x0000007E
pci.sys address F75760BF base at F756F000, Datstamp 3B7D855C

I ran the disc that came with the motherboard on this computer and it has the option to make a disc w/ raid something, I'll put the disc in and check exactly what it is. Well I ran setup and loaded that and nothing. The harddrive didn't come with any software. I try pulling the cmos battery and putting the memory in a different slot (only two slots).

[green_hornet_96]

Knew someone at school a long time ago who had one of those copied XP pro discs. He couldn't get it to install at all from bootup, rather it absolutely had to be installed through the CD autoplay in Windows 98.

I stick with genuine OS myself, (or Linux when I get around to formatting one of my old drives for it...) don't want the computer phoning home saying "ah! I'm a CLONE!! auto insert virus delete format BSOD BIOS flashed 0's ok power off."

Any RAID 1 install needs windows and the driver for RAID installed, then go into the asus utility for RAID on bootup and copy the existing data drive to an empty data drive.

Can't help you on RAID 0, never done it.

Doubt the original pre-SP1 XP can support 2nd generation SATA without 3rd party driver. I do know that an XP SP2 disc can without a problem.

[guest]

well, it's funny, cause it wont even work with a IDE drive. plus i've used this xp disc to install xp on a bunch of computers...

I think I'm going to have to just brang it back to the place I bought it from and have them fix it.... *fart noies with my mouth*

[ddd4114]

Knew someone at school a long time ago who had one of those copied XP pro discs. He couldn't get it to install at all from bootup, rather it absolutely had to be installed through the CD autoplay in Windows 98.
He probably didn't have the correct boot order in the BIOS. With old computers, you have to be sure the CD-ROM is first on the boot priority list in the BIOS. Even worse, some old motherboards or BIOS versions don't support booting from a CD-ROM, only from a floppy disk.

I stick with genuine OS myself, (or Linux when I get around to formatting one of my old drives for it...) don't want the computer phoning home saying "ah! I'm a CLONE!! auto insert virus delete format BSOD BIOS flashed 0's ok power off."
You should be fine as long as you don't install the "Microsoft Genuine Advantage Tool", or whatever it's called. That's the thing that "phones home" and starts bitching at you. I know there are ways around this, but I haven't had time to try them out. I just can't justify paying $300 for an OS that I curse at on a semi-daily basis. I should use Linux too, but last time I tried Red Hat, I discovered that I'm not man enough for it. :-P When I reformat this summer, I think I'm going to stick with dual-booting a pirated XP and Ubuntu.

@ Guest: To me, it sounds like a bad stick of RAM (although you said you tried different sticks in both slots) or a bad motherboard. If you can, try to get an RMA number and replace the components in the kit.

[green_hornet_96]

He probably didn't have the correct boot order in the BIOS. With old computers, you have to be sure the CD-ROM is first on the boot priority list in the BIOS. Even worse, some old motherboards or BIOS versions don't support booting from a CD-ROM, only from a floppy disk.

Good try, but a simple switch to a genuine CD and it would go to town from bootup without a hitch. Maybe a bad CD lol

Validation... pain in the butt... takes sooooo long when working on 56k.

It could be RAM, I know some asus's are kinda picky about what they can run. A friend of mine with an A8N5X can't run Corsair Valueselect any more than a cup of coffee, but its possible its a bad slice. XMS is nice, I run gskill PC4000 myself (just couldn't pass up 2GB for $145!).

His computer had the weirdest symptoms too-- we got windows to work, then the integrated sound wouldn't install. He bought a sound blaster, that worked. Within a week it would crash out of the blue every once in a while. We tried to reformat, it kept freezing, and about the 6th time XP installation finally was successful. Swap the memory with XMS, everything works...

[guest]

I bought a new copy of xp w/ SP2 and it worked. yay!!!!!

It's pretty fast. Boots to the password prompt before the monitor turns on. thanks for all the help.


What about registering my copy of xp?????

[green_hornet_96]

Hook up to the internet and activate it. I never do the actual registration ;) Activation... bleh if its an OEM cd (like from newegg or something) microsoft will deny activation on any other computer. Retail CD is transferrable if you ever discard your current computer (don't leave your OS on it haha, someone might try to do windows update and MS could throw a fit!)

[guest]

anybody else actually register there copy. I'm super paranoid, thats the only reason I'm kinda scetchy about doing it.

[speedfoos]

Damn, I wish I had seen this thread a while ago. I could probably have saved you a few bucks. I've been running with the same "gray" copy of Win XP Pro since I got it in 2001. Don't bother registering, they'll just ask if you want to participate in blah, blah and receive information about stuff you'll delete without opening.

Couple quick notes. Unless you're going to run some SATA drives in a RAID array (0,1, JBOD, whatever) you don't have to worry about mashing F6 to add a SATA driver during setup. I know you're past this stage already, but its good info to know.

Correct boot order in a BIOS has nothing to do with it. The PC will check each one as it goes along the boot sequence to see if it finds the 'hook' to load an OS or a DOS prompt.

Your error was probably due to your install disk being corrupt. If it was a CD-R, those things do deteriorate over time especially when all the data on an OS disk is so important. The slightest glitch will hose things up during an install.

Anyway it sounds like everything worked out in the end, but if you have any other problems, give me a shout. I used to be a Windows and a Unix sysad and have also built multiple computers over the years.

[guest]

it is an old disc, but I've just recently used it to install windows on a few harddrives......

good to know you were a sysadmin.