I'm in installation hell!

[Paddy]

Question: What made you want to rebuild??? Was this just a spring cleaning attempt, or did you run into problems???

[Sasq]

This might sound strange, but i seem to run into problems everytime i install another hard drive into XP.
Try setting your bios speed/memory settings to the least aggressive possible. I do that and then it will install/recognise the drive, after that I can bump the settings back up

Dan

[Rags]

Originally posted by Sasq
This might sound strange, but i seem to run into problems everytime i install another hard drive into XP.
Try setting your bios speed/memory settings to the least aggressive possible. I do that and then it will install/recognise the drive, after that I can bump the settings back up

Dan

I use ghost 2002 and have zero problems converting xp over to a new drive. Quick and painless to say the least.

Rags

[Sasq]

Rags: for some reason even if I add an extra drive in (either my abit or asus system) it spits with a new drive unless I really turn my mem settings etc down for the first boot. I don't do it so often so i'll see if i can find out exactly what it is next time i do it

Also I'm unfamilure with ghost 2002 - any good?

[The PIT]

Norton ghost 2002 isn't bad. However I've noticed if you use pc dos as an option for you boot disk I get an invalid partition table error message when I try to access the hard drives. Using Msdos cures the problem. This doesn't happen with ghost 2001.

[Rags]

Originally posted by The PIT
Norton ghost 2002 isn't bad. However I've noticed if you use pc dos as an option for you boot disk I get an invalid partition table error message when I try to access the hard drives. Using Msdos cures the problem. This doesn't happen with ghost 2001.

I have used both PCDos and MSDos. I prefer using the MSDos it seems to give fewer problems.

With XP it's rather easy to get the MSDOS files you need anyhow.


But Sasq, yes Ghost 2002 is a very good program. It will clone drives better than anything I have seen thus far.

As to your problem, it doesn't sound like an XP issue, it sounds like a setup issue.


Rags

[Helevitia]

Originally posted by Paddy [MU]
I get the same message whenever I forget to hit F5 (or whatever) to install a specific SCSI adaptor driver.

From reading your posts, i'd say that you did have an inaccessable boot device.... odd how it worked before.... have you changed the BIOS on the RAID controller??? I guess that might make it want different drivers....

A couple of things everyone should know:

1. Although I got the 0x7b stop message, it wasn't the inaccessable boot device message up top. It just told me that there was a problem with my system and it halted the computer to prevent any damage.

2. The problem happens right after the F6 option but before it asks which drive you want to put it on.

3. I hit f6 and tried different drivers as well.

4. Have I changed the BIOS on the RAID controller? That is a good question and one that I have been trying to figure out. why you ask? Read below for more info.

Question: What made you want to rebuild??? Was this just a spring cleaning attempt, or did you run into problems???

Hehe, the 64 thousand dollar question OK, I left out this part of the story on purpose.

This all started because I wanted to update my Asus BIOS from 1004b to 1006 final. Once I did this, the system would not boot anymore. I don't know what my raid bios was before the update so i dont know if it updated that bios as well. Once I realized I was SOL, I downgraded back to 1004b, but my problems persisted. After several attempts of getting it to boot, I decided that I needed to do the dreaded startover. This is when I started running into problems.

Dave

[Helevitia]

Originally posted by Sasq
This might sound strange, but i seem to run into problems everytime i install another hard drive into XP.
Try setting your bios speed/memory settings to the least aggressive possible. I do that and then it will install/recognise the drive, after that I can bump the settings back up

Dan

Tried that, didn't work.

I should mention that I since tried it without RAID and it works fine, so it comes down to drivers or BIOS in my opinion.

Dave

[Ali]

Since you flashed your BIOS, have you set your boot order to SCSI first? The promise controller pretends to be SCSI, and if you are booting IDE0 first, then thats probably your CD-Rom.

Well, thats the way it works on my gigibyte.

Ali

[Helevitia]

Originally posted by Ali
Since you flashed your BIOS, have you set your boot order to SCSI first? The promise controller pretends to be SCSI, and if you are booting IDE0 first, then thats probably your CD-Rom.

Well, thats the way it works on my gigibyte.

Ali

Yes, in my BIOS, I set the boot sequence to ATA100/SCSI which is the same thing according to my BIOS. and yes, I've set this up many times before so that is the correct setting. Thanks Ali.

Dave

[Helevitia]

I think I figured out the problem. After I installed XP and got it all booted up, I went to 'My Computer' to take a peek at the second 40GB drive and my other 15GB drive. What I found was that the second 40GB drive(other half to the raid setup) only has an option to format in NTFS. I am thinking that NTFS screwed up my HDD somehow. Has anyone ever seen this? BTW, my Primary 40GB drive is currently FAT32 and my 15GB drive formatted with FAT32 without any problems. So everything points to this other drive that will only format with NTFS, weird Anybody else see this before?

I already fdisked it and formatted in DOS with FAT32 which is really weird. Something ****ed it up. If i can figure out how to format it in XP with FAT32 I may ghost my system then try again

Dave

[Helevitia]

I found this:

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

It states that you can't format a HDD larger than 32GB during the setup of WinXP and that you should use NTFS. I am assuming this apllies to the format feature once the OS is installed. Anybody have this problem? Also, it further states that I should use FDISk to fomrat it, but I already tried that Myabe I'll try it again.

Dave

[ALBPM]

I just fdisked and formated a new 40G with FAT32 and converted it after the XP install. I thought I'd keep it at FAT32 in case I wanted to Dual Boot or recover anything on the old Hard Drive.

I know I wasted a couple Gigs but I've never come close to filling even a 13G drive up before.

So my C: drive is NTFS and my 2 back up drives are still FAT32.

Paul

Is this another one of those Via Features???

[Snake-Eyes]

Originally posted by Helevitia
I found this:

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

It states that you can't format a HDD larger than 32GB during the setup of WinXP and that you should use NTFS. I am assuming this apllies to the format feature once the OS is installed. Anybody have this problem? Also, it further states that I should use FDISk to fomrat it, but I already tried that Myabe I'll try it again.

Dave

Hmm.. That's strange, because I've formatted my 2x60GB IBM RAID array (a single 120GB volume at present) when installing XP (Pro) several times, and I've also formatted a single 60GB (one of the pair that's currently in the RAID array) during one of my clean reinstalls (mostly all done as part of hardware upgrades).

[Snake-Eyes]

Ooops. Someone needs a ruler across the knuckles here.

I just reread here, and checked the links. My formats were straight to NTFS. I have formatted to FAT32 before, but only using WinME's emergency boot disc (this was for the very first time I was going to install XP Pro), and I did the FDISK/Format from the WinME floppy, then ran XP Pro's installation, and let it convert the FAT32 volume to NTFS.

Sorry bout that.