Inaccessible_Boot_Device
Teilhard Knight
I am trying to install Win 2K on a PIII 550MHz with 384 Meg RAM. I am not
very Knowledgeable about hardware, but Win XP reports a VIA IDE controller.
The problem is, I start installation in DOS, and when the system passes to
full Win 2K mode, I get:
Stop: 0x0000007B (0xF2463848, 0xC0000034, 0x0..., 0x0...).
I have researched the error, and I know the string outside the parenthesis
means I cannot access my HD (partition). The meaning of the first string
inside I haven't been able to spot. The references are too technical for me.
So, perhaps you guys can tell me what exactly the problem is. The second
string inside has a clear meaning which I sadly forget, but the cures based
on this information alone I undertake never got me to solve the problem. The
other two strings, as I understand are always zero.
I paid 10 bucks only to be told that the most probable cause is that the
installer does not have drivers for my IDE controller. I find hard to
believe this because I have partitioned the HD to have Win XP, Win 2K, and a
distribution of Linux together (80 Gb HD), and both Win XP and Linux
installed without a hitch. Besides, VIA does not provide IDE drivers one
could feed in a diskette to the installation, they claim they are always in
the installer of all flavours of Windows.
Any feedback to solve my problem will be greatly appreciated. I have spent a
great deal of time reading and trying (virus, etc.) and nothing.
Teilhard.
Bernard Peek
<tei...@privacy.net> writes
>Hello:
>
>I am trying to install Win 2K on a PIII 550MHz with 384 Meg RAM. I am not
>very Knowledgeable about hardware, but Win XP reports a VIA IDE controller.
>
>The problem is, I start installation in DOS, and when the system passes to
>full Win 2K mode, I get:
>
>Stop: 0x0000007B (0xF2463848, 0xC0000034, 0x0..., 0x0...).
>
>I have researched the error, and I know the string outside the parenthesis
>means I cannot access my HD (partition). The meaning of the first string
>inside I haven't been able to spot. The references are too technical for me.
>So, perhaps you guys can tell me what exactly the problem is. The second
>string inside has a clear meaning which I sadly forget, but the cures based
>on this information alone I undertake never got me to solve the problem. The
>other two strings, as I understand are always zero.
IME the usual cause is that the hard disk is connected to a RAID
controller rather than a standard IDE controller. It's often a problem
with Promise controllers.
I suggest that you check whether there are multiple IDE controllers on
the motherboard and move the boot drive to another controller, or find
driver software that you can provide to the W2K installation process.
--
Bernard Peek
London, UK. DBA, Manager, Trainer & Author. Will work for money.
Teilhard Knight
"Bernard Peek" <b...@shrdlu.com> wrote in message
news:G8JA9zO8...@shrdlu.com...
Thank you. Actually, I do not think my computer contains a RAID controller.
Remember it is a PIII 550MHz. I have heard a lot of Promise controllers, and
I have never heard of VIA controllers, except that my Win XP lists my IDE
controller as VIA. I know VIA is the chipset, but if the controller
manufacturer is different, how do I know? I have tried two diagnostic
programs and both stop short in VIA.
Teilhard.
Teilhard Knight
news:j6SdndxabMj...@athenet.net...
>
> "Teilhard Knight" <tei...@privacy.net> wrote in message
> news:2qgasnF...@uni-berlin.de...
>> Hello:
>>
>> I am trying to install Win 2K on a PIII 550MHz with 384 Meg RAM. I am not
>> very Knowledgeable about hardware, but Win XP reports a VIA IDE
>> controller.
>>
>> The problem is, I start installation in DOS, and when the system passes
>> to full Win 2K mode, I get:
>>
>
> it's best to load smartdrv first
> i'd really suggest not installing from dos
> and just boot from the cd
Smartdrive is loaded with a Win 98 boot diskette, the one I am using. I
agree with you, I should start from the CD or at least from the 4
initialitation diskettes, but my computer refuses to read either. It boots
fine from the Win XP CD, but not from the Win 2K CD. As for the 4 diskette,
it gives a non-readable error. Remember, my machine is old.
Teilhard
Teilhard Knight
"Dave Patrick" <ma...@Nospam.DSPatrick.com> wrote in message
news:%23pnv03A...@TK2MSFTNGP09.phx.gbl...
> Nothing really to do with the drive. The issue is with the drive
> controller.
> So you'll want to check the HCL for your controller and or mother board.
OK, I'll check. Thanks again.
Teilhard.
Teilhard Knight
> "Teilhard Knight" wrote:
> | OK, next time I'll do as you say. I come from groups where it is highly
> | disapproved to cross-post,
> * I think you may have this backwards. You do see the advantage of
> cross-post over multi-post?
I do not think so. I see the advantage here. But think in groups where some
people "intrude" cross-posting. People you do not know, having a flame war
or posting nasty things, or attacking someone, and you want your answers to
remain in your own group only. The scenarios can change with the subject
matter.
Teilhard
Zontag
Core3 have problems sharing large hard disks withXp
Zontag
http://slashdot.org/articles/04/05/23/1448209.shtml?tid=110&tid=187
Also applies to other 2.6.x kernel distros such as Mandrake 10
There is now a workaround.
Teilhard Knight
news:41433fd3$0$22756$db0f...@news.zen.co.uk...
I installed Mandrake 10.0 Official, which I guess by the choices of packages
I made and consistency issues, installed with kernel 2.4. I have this
distribution coexisting with Win XP in 3 other machines and haven't had any
problems. Actually, one of them (the most equipped) has also Fedora
installed on it and everything is working fine. Perhaps it is due to the
fact that I am using more than one drive. But thanks for the info, it might
be needed sometime.
--
Teilhard Knight
The Extraterrestrial
Change "privacy" for "softhome" if you want to intrude my inbox
Teilhard Knight
Actually I installed Win XP first, then I tried to install Win 2K (To avoid
editing boot.ini to get rid of $ill Gate's "boot manager"). Only after I
found I could not install Win 2K, I installed Mandrake 10.0 with kernel 2.4.
The problem occurred before Linux was present in the computer.
By the way, what is the workaround?
Teilhard.
Teilhard Knight
"Kylesb" <m...@privacy.net> wrote in message
news:2qgn48F...@uni-berlin.de...
> |
> | I am trying to install Win 2K on a PIII 550MHz with 384 Meg RAM. I
> am not
> | very Knowledgeable about hardware, but Win XP reports a VIA IDE
> controller.
> |
> | The problem is, I start installation in DOS, and when the system
> passes to
> | full Win 2K mode, I get:
> |
> | Stop: 0x0000007B (0xF2463848, 0xC0000034, 0x0..., 0x0...).
> |
> | I have researched the error, and I know the string outside the
> parenthesis
> | means I cannot access my HD (partition). The meaning of the first
> string
> | inside I haven't been able to spot. The references are too technical
> for me.
> | So, perhaps you guys can tell me what exactly the problem is. The
> second
> | string inside has a clear meaning which I sadly forget, but the
> cures based
> | on this information alone I undertake never got me to solve the
> problem. The
> | other two strings, as I understand are always zero.
> |
> the
> | installer does not have drivers for my IDE controller. I find hard
> to
> | believe this because I have partitioned the HD to have Win XP, Win
> 2K, and a
> | distribution of Linux together (80 Gb HD), and both Win XP and Linux
> | installed without a hitch. Besides, VIA does not provide IDE drivers
> one
> | could feed in a diskette to the installation, they claim they are
> always in
> | the installer of all flavours of Windows.
> |
> | Any feedback to solve my problem will be greatly appreciated. I have
> spent a
> | great deal of time reading and trying (virus, etc.) and nothing.
> |
> | Teilhard.
> |
> |
>
> installed ok then win2k would also. Is there a slave device on the
> IDE channel with the HD? perhaps you might disconnect it during the
> installation. Just a couple of stabs in the dark.
> --
> Best regards,
> Kyle
I partitioned with Partition Magic, not the best tool there is, I know. I do
not remember whether I checked with DFSee, but I routinely do it to make
sure there are no errors.
Good idea of disconnecting the slave. I shall do it presently and inform you
what happens.
Teilhard.
Teilhard Knight
> "John Freeman" <qua...@mail.ru> wrote in message
> news:chvq84$ehk$1...@news.rol.ru...
>> INSTALLED , c: -first , from left to right , then modify your boot
>> ini,according to it , it's rare bug with nt family, caused by when you IN
>> DOS YUO CAN'T SEE NTFS PARTITIONS AND partition PARAMETER IN BOOT.INI
>> BECAME WRONG , yuo can see smthng like
>> multi(0)disk(0)rdisk(0)partition(x) , where x must be number - look on it
>> and correct.
>
> Thank you for your feedback, but actually I haven't been able to install
> Win 2K. The problem arises during installation. Just after starting Win 2K
> mode, where it is supposed to ask you to accept the license and so on.
> Still, I will check in Win XP to see whether its boot.ini has some info
> about 2K.
This is what I foud. In Win XP, I have the boot.ini as:
%%%%%%%%%%%%%%%
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect /NoExecute=OptIn
%%%%%%%%%%%%%%%
The 1 in the reference to the partition is correct.
For win 2K the boot.ini is:
%%%%%%%%%%%%%%%%%%%%%%%%
[Boot Loader]
Timeout=5
Default=C:\$WIN_NT$.~BT\BOOTSECT.DAT
[Operating Systems]
C:\$WIN_NT$.~BT\BOOTSECT.DAT = "Windows 2000 Installation/Upgrade"
%%%%%%%%%%%%%%%%%%%%%%%%
I am puzzled by the "NoExecute" entry in the XP boot.ini.
Any ideas?
Teilhard
Clint Sharp
<53...@zen.co.uk> writes
misconstrued as tasking the p*** out of another NG poster.
--
Clint Sharp
Teilhard Knight
Kyle: You were right on the spot. I disconnected the slave drive and I was
able to install. After that, the problem was that if I connected back the
slave I got the same blue screen again. I then disconnected again, booted
into Win 2K and installed the VIA Hyperion 4in1 drivers. That solved the
problem completely.
I got a bit alarmed because in first boot I couldn't see the secondary
channel nor in 2K or XP. The problem was that I was booting with a flash HD
in a USB port. As soon as I booted without it, everything was visible in
both operating systems and after booting I can plug the flash disk and have
it as well. Do not think I am really dumb. I installed and did everything
without the flash disk in. Only after install, I fed the drivers for my USB
2.0 card and plugged the flash disk to check. Then I actually was a bit dumb
in leaving it in in the next boot.
You solved my problem and I am grateful to you. I wish I could take you for
a beer.
Cordially,
Teilhard.
Zontag
The question is who's design although is due to Xp not recognising valid
hd parameters the Fedora team and I presume the Linux kernel guys knew
about it and the very simple work around before release but left it out
because it was "Microsoft s fault".
Likewise SAMBA windows file sharing is broken in Fedora Core 2 but it is
not rated by the Fedora team as a serious problem -- Linux is a better
more secure easier to install OS than Windows but the attitude of some
Linux geeks causes immense damage to the credibility of Linux.
Ian
"Teilhard Knight" <tei...@privacy.net> wrote in message
news:2qh853F...@uni-berlin.de...