Search options (Page 94 of 99)

you weren't browsing the temp folder during slipstream, were you?

hehe, I done that couple times...

Hi Fragbert

when you connect a RAID striped array to the ICH7R channels, and ICH7R is set to AHCI, and you boot to the hard disks... then you get an Error during Boot.
A disk Read Error occured,
press CTRL-ALT-DEL to restart.

That is perfectly normal.
A user should always see that, even when BIOS is set to Silent or Quiet.
(OEM screen hiding POST data on screen)

the drives are ready to be blanked, so I could launch setup from DVD.
I already know what happened when both drives were there and booted to DVD.
(The unnatended automatically formats, and it saw the full size of the array, and setup would then loop to setup when it did its first reboot.)

so I'll disconnect just one of the stripe, set this to AHCI, load the DVD, and see what happens..

hi
have you used this one, Muiz3?

I heard some cards produced stutter. maybe this fixes it.

Well,
I was too optimistic.
changed setting to AHCI after windows got fully loaded, and it tries but fails to boot to windows...
changed it back, and I got the safe boot options screen.
(come to think of it, these single modes use a different driver, so this is understandable).

next is a striped RAID, then try a single drive out of the stripe.
Just found a twin to the 250 drive I ran in single mode. This one is probably fully loaded with data...
be patient, it will get tested tonite.

Oh, if it ever was a member of an array, and was not reset to NON-member, then it will still be a member disk.
I'm almost sure it would either show a wrong size, or an error, or maybe with the newest, not show up at all..

it is something I intend to find out, using the newest, and after this with my 5.00.1032.

testing a change like from AHCI to single disk on RAID setting should be easy.
in that 945, I recall it runs in AHCI right now?
All I have to do is connect it to a monitor and get in BIOS..

At the moment, I have to free up a used 250 Gb drive so as to have two "erasables".
(I do not want to crack the wrap on the new ones if I do not have to.)

the 945 testrig has three unconnected drives, one of wich only contains some data I think I have on other drives as well, but I will first look at it before I start messing on it.
the other two in there are a RAID running windows X64, which could actually be erased.
(I think I will not keep on using any OEM X64 windows versions after al. This one was installed many months ago, and can already be activated in other rig with no problem, so I could sell it as used but usable.)

.the 955 rig will run a first test on a single sata in twenty minutes or so.
(I want to test for the desktop.ini error, with locale settings removed from winnt.sif)
with any luck, I will run four or six tests tonight.

when I get it, all I do is get to start, programs menu, and Rightclick/delete it out of startup...

have just built the Royale machine.
Unfortunately, the shop had used the ATI card I had ordered for a quick repair, and I got an Nvidia 7300GT with some discount.

interesting mobo for tests, I dare say
it has IT8212F  (Raid 0+1 or JBOD), has ICH7R (0+1 and 5), and SIL3132 (0+1), which makes connections possible for 6 IDE drives and six SATA...
the case can accommodate plenty drives...
this will become a workhorse after I tested its guts.
it had HDaudio too... what better things to do for burnin tests than running variants of setup with various builds.

and yes, with RVM hotfixes and addons, plus base6086 these updating screens also come up (one of wich is updating desktop), but the ini does not launch in notepad.
(did not do KTD with 6086. the first test was with a really slow hard drive, so I could see what came up... with RAID drives in it it just goes a little too fast to read the updating popups)

OOPS
post 21 proves my memory is not reliable

winnt.sif somehow triggered the corruption of svcpack.in_

the desktop.ini launching from startup in programs is triggered by something I have not found yet....

Hi Zac_Caz

you need driverpack BASE to integrate the mass storage driverpack into a copy of your CDRom

copy CD to folder
run base610 download
copy mass storage download to driverpacks folder in the folder where you let base extract to
I would also get chipsets driverpack, and put that in there as well.
then you can run DPsBase

you have to use TXTmode

make a bootable ISO from that slipstreamed copy
after this, you burn yourself a bootable CD
and it should be able to see the hard disk.

Hi Wim
yes, to get to the RAID setup utility for my INTEL ICH7R chip, I had to disable ITEraid.
(otherwise I would not get the CTRL-I option during boot. It would only show CTRL-G for Gigabyte aka ITEraid)

with AHCI, there is no CTRL-I option at all, and after deleting the array, the two non-member SATA drives are still connected.
Setup used one of them.

Oh dear,
I think I know how Mikhelm feels.

there's that other thread, where I started that elimiation process by using halves of half.
Back home, when I was doing exactly that, I almost started swearing at myself because, well, because...
When I thought it over, I figured out where I broke the process, so I dood it all over.
But I would still bust my head against the wall when the process broke for reasons I could not remedy nor look into.
However, I don't swear at Wim.
I dragged an 95 year young bloke off the street and vented my frustrations on him...
Little did I know he got called Sue...
Mr Yang is now my sensei...

btw, opened a new one in forum feedback

Hi Fragbert

it is currently running setup with version 6.xxx floppy

it wouldn't see the drive, at first.
but, then I followed up on the suspicion I had.
went into RAID configuration. (BIOS)

to get to the intel BIOS setup screens, I had to disable ITEraid in BIOS(Gigabyte mobo calls it GiGaRaid)
then, I had to set the intel chip to RAID to be able to delete the array.

Then I set it to AHCI
(not in a RAID config, at the moment)
and V6xxxx did allow me to access the now blanco drives
we'll see how it reboots in ten minutes...

edit; it is not an intel mobo, but I could report at intel as it does have an intel chipset ...
setup asked me for the windows key (next time I will use a semi-unattended)

edit 2; windows loaded on a single drive

next thing I will try is to set up the drives in RAID array while in AHCI