Welp!

[Vovik]

Well as of 2:00am right now I was able to somehow install XP onto my new HD and I'm actually installing CS right now and there hasn't been one problem yet.....I'm jinxing it, oh yes.......My pc is still all in the open on the big table and I'm not going to be putting it together forawhile.....jinxing it....honestly, if this thing stops working again i'm going to cry like a baby

[Cujo]

what did you change?

[Vovik]

what did you change?

<{POST_SNAPBACK}>

 

I don't really know. What I did was plug in my old IDE (the one that I reformatted and somehow installed XP earlier and the one where SB didn't want to go on with installation). Well, that was the first step in getting into XP. Then, I put my XP cd and installed Windows anew on my new 74 Gig Raptor SATA. It went on to restart and when the screen came up with the same choices (Install new, Repair, Quit) I said install new and it decided to go through with the install....go figure

 

I've been officially n00bed in hardware, and I'm probably never going to claim I'm an 'expert' in this stuff.

[mookie]

Oh about the SoundBlaster install... it does that on my machine too sometimes, I wouldn't make anything of it. It's probably just a buggy installer. At this point I much prefer to download a driver from Creative rather than use the CD, and if I do use the CD I'm usually hand picking an INF file and running with it.

[EbilDustBunny]

Just a thought about the sata drive, and the inability to load XP.  I had that same issue with my system when I built it last Jan.  I had to load SATA/RAID drivers from a floppy, even though I wasn't setting up a RAID array.

 

I don't know if RAID is an option on your system, but you might want to check that.  I tried to install XP 4-5 times, before a friend asked my about the SATA/RAID drivers.  After loading the drivers, it installed like it should. 

 

Anyone else?

<{POST_SNAPBACK}>

 

I have the same sata drive and never had trouble... installing XP.

[Vovik]

Well....I put my comp back in the case and what do you know? the CMOS reset again...now I guess it will go through the operation I had before (reinstally XP on SATA using old IDE) but wouldn't load them properly even when they're plugged.

 

If I plug only SATA (new WD74) drive it doesn't want to load the XP installed on it or install it over again (same problem of not going through the installation). But then, when I plug IDE as well in the BIOS it will only recognize the WD74 as the boot option and wouldn't boot from IDE. So, then I unplug SATA (WD74) and then it loads properly into a IDE install that I don't want to use.

 

So as I see it I have an option of reinstalling that SATA again through IDE drive, then it'll go through. But with CMOS resetting at random (every time I change something on my mobo) I'd have to do it every time it resets.

 

There's gotta be something else I can do to install XP straight to the SATA drive.

[ScubaDan]

Vovik, is it possible that the jumpers that reset the bios/cmos are somehow being shorted together when you put it all in your case? Or maybe your cmos battery is unserviceable?

[Vovik]

Vovik, is it possible that the jumpers that reset the bios/cmos are somehow being shorted together when you put it all in your case? Or maybe your cmos battery is unserviceable?

<{POST_SNAPBACK}>

 

where do find the jumpers?

 

I'll check the battery

[Brillow_Head]

Yeah, it sounds to me like something in your case is hitting or shorting your mobo.

 

Dan: What is the significance of

1001100 1100101 1100001 1100110 1110011 100000 1010011 1110101 1100011 1101011 100001

???

 

In decimal its "76 101 97 102 115 64 83 117 99 107 65"

In Hex its "4C 65 61 66 73 40 53 75 63 6B 41"

[mookie]

Yeah, it sounds to me like something in your case is hitting or shorting your mobo.

 

Dan:  What is the significance of

1001100 1100101 1100001 1100110 1110011 100000 1010011 1110101 1100011 1101011 100001

???

 

In decimal its "76 101 97 102 115 64 83 117 99 107 65"

In Hex its "4C 65 61 66 73 40 53 75 63 6B 41"

<{POST_SNAPBACK}>

41 53 43 49 49 32 4E 30 30 42

[Brillow_Head]

huh?

[Wentz]

Gonna use some of those numbers and play the powerball, got you covered if/when I win.

[Brillow_Head]

I knew you'd post a wisecrack.

[Vovik]

I think I fixed it. Don't ask me cause I don't know how, just did a bunch of random stuff (including yet another full install of XP) and it works now. I still feel that my CMOS is screwed up and it shorts the motherboard when I rebuild and stuff so in the future I'll be cautios of that.

[ScubaDan]

Yeah, it sounds to me like something in your case is hitting or shorting your mobo.

 

Dan:  What is the significance of

1001100 1100101 1100001 1100110 1110011 100000 1010011 1110101 1100011 1101011 100001

???

 

In decimal its "76 101 97 102 115 64 83 117 99 107 65"

In Hex its "4C 65 61 66 73 40 53 75 63 6B 41"

<{POST_SNAPBACK}>

 

In ASCII text it's "Leafs Suck!"

[mookie]

Yeah, it sounds to me like something in your case is hitting or shorting your mobo.

 

Dan:  What is the significance of

1001100 1100101 1100001 1100110 1110011 100000 1010011 1110101 1100011 1101011 100001

???

 

In decimal its "76 101 97 102 115 64 83 117 99 107 65"

In Hex its "4C 65 61 66 73 40 53 75 63 6B 41"

<{POST_SNAPBACK}>

 

In ASCII text it's "Leafs Suck!"

<{POST_SNAPBACK}>

Haha, I guess Brillow translated from binary to decimal wrong. I was fairly convinced it said "Leafs@SuckA". It's tricky when you don't make all your bit strings the same length.

[mookie]

Anyway Brillow, if you want to look 10100111001 to us coder-types all you have to do is learn to look at binary.

 

Numbers that start like this:

010x xxxx are upper case ASCII numbers and the xxxxx is the # of the letter in the alphabet.

Numbers that start like this:

011x xxxx are the same but lower case.

 

They're easier to read in hex though because upper case just starts with 4 or 5 and upper starts with 6 or 7.

 

Also FYI numbers look like 0011 xxxx or start with 3 in hex. They're even easier to read: e.g. 30 = 0, 31 = 1 ... 39 = 9.