whats linuz?

He ment Linux.

to say this has been a bumpy ride would be an understatement.

having actually got it working properly, i thought cool, cracked it. i had setup both sides of the comp correctly. correct video adaptors, sound drivers, RAID, LAN, USB2, the works for the mobo.

reference: c = family / d = me.

i was using D like i had been for numorious times, and i updated some stuff, i cant remember exactly but i did uninstall intel application accelerator because i had installed it in 'Program Filesd'; so i was intending on uninstalling it and then reinstalling it correctly. the only other thing i can remember doing on that boot up, was updating norton AV. it asked me to reboot, so i agreed.

since then, (c boots fine), if i select the second windows 2k boot option (d), before it gets to the white screen with the blue progressing meter, a BSOD appears giving this fault:

***STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)

INACCESSIBLE_BOOT_DEVICE

the same RAID drivers are installed on both C, and D. i took these from abit's site from my mobo ID. i had the RAID drivers installed on D for a good 2-3 boots before this happened, and i didnt change them settings. all i did was uninstall intel app xl, and update norton and boot. i found this webpage, but its all abit above my knowledge - http://www.windowsreinstall.com/ins...rd/problems.htm

i really do not want to have to format, i see no logical explination for this. i cant boot into safe mode (in D), nor can i find any way of being able to load the windows setup from my win 2k cd. ive selected boot the cdrom first from the bios/cmos settings. but for some reason it doesnt do that anymore, not since this happened. before this happened, it used to scan my rom and floppy before asking me to choose a windows, now it does not.

any help?

did you edit c:\boot.ini?

i say beat the crap outta your brother
he sounds as annoying as mine
apart from that im afraid i cant help much

___________________

All the weekend rockstars in the toilets
Practicing their lines

This post is better than your post

i did not need to edit it. it edited itself adding the extra line after i installed the second windows. i double checked it matched what u said and it did. i edited the timeout so it would boot into C quicker if they turned it on and walked away. here are the contents now:

[boot loader]
timeout=7
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Professional" /fastdetect

quote:

Originally posted by Coup i did not need to edit it. it edited itself adding the extra line after i installed the second windows. i double checked it matched what u said and it did. i edited the timeout so it would boot into C quicker if they turned it on and walked away. here are the contents now: [boot loader] timeout=7 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Professional" /fastdetect

Is the other WINNT from partition(2) a second HDD? or a second partition?

- neoh

a second partition. we only have one hdd, a 60 gig. i turned the 60 gig C drive into a 30gig C:, and a 30 gig D:. then, i booted up the pc with the windows cd in it, and installed a new version of windows onto the D drive.

What files are in C:\?
Do you see a bootsect.dos, bootsect.2k, etc? anywhere?


- neoh

aside folders, i have:

arcldr.exe
arcsetup.exe
AUTOEXEC.BAT
boot.ini
CONFIG.SYS
IO.SYS
MSDOS.SYS
NTDETECT.COM
ntldr
pagefile.sys

i dont see how this could happen personally.

What about D:\?

i cant get into it. i made D invisable from windows booted into C to stop my brother being able to touch my files. D "device isnt ready" in dos.