From: "Glenn Meadows" 

Yea, tried the winnt/? and there was no option to make the boot floppies.
I'll go download them now.

Yes, latest Bios for this MB was installed sometime ago.  An identical
system sits right above this one (same MB, same HD's, same CDROM, same ram,
etc, and it runs fine. .

I removed the 2 USB2 HD's, and that of course made no difference.  I've
connected them to the other system so I can work for now, while I deal with
this madness. I'm going to copy off the audio that's on the second
partition of this HD from a working system over to one of the USB drives,
and move the 2nd HD that has audio into the other system as well, so all
audio is there while I work on getting this beast back alive again.

Can systems boot from USB floppies?  Might be worth having one around (I
believe the answer is yes, as there is a bios option for that too).

--
Glenn M.


"Robert Comer"  wrote in
message news:41c1d300{at}w3.nls.net...
> > Strange, at best.  The drive chkdsk's clean, so where is it getting
> > "inaccessible boot device" from?
>
> Something else is damaged, maybe the driver for whatever disk controller
you
> have. (maybe not damaged, but not right for the system)
>
> Also you may have your boot.ini messed up.
>
> > Boot set of floppies is create how again?
>
> Now that I look at it, that way doesn't work anymore.  (It was type WINNT
> /OX)
>
> You have to download them from Microsoft now;  See:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;310994
>
> >Have to do that on a
> > system with a floppy installed, and working, and then move the floppy to
> > the
> > other system and get it all up and going.
>
> That's why I still have floppy drives in all my desktops. 
>
> >Do you think the drive itself is
> > toast?
>
> Probably not.
>
> It might be a hardware problem on the PC itself, but not the drive, more
> like a bios problem.  Have you upgraded the bios to the latest on this
> machine?
>
> You CD drive might be toast or misconfigured and that would explain why
you
> could boot from it.
>
> >OR, do you think a
> > Format/re-install of the OS to that partition will clear it up?
>
> Probably, but then you might hit it again the next update go'round.
>
> I'd check your IDE cabling scheme and maybe try another CDRom drive and
> update the machine's bios, and then try a repair...
>
> >(So many questions, so few
> > answers....LOL....)
>
> PC's can be dreadfully frustrating at times, can't they...
>
> - Bob Comer
>
>
>
> "Glenn Meadows"  wrote in message
> news:41c1cf6a$1{at}w3.nls.net...
> > Strange, at best.  The drive chkdsk's clean, so where is it getting
> > "inaccessible boot device" from?
> >
> > No floppy drives on this audio system, although I can scarf one from
> > another
> > system and hang it out the top (it's a rack mount system, and the
supplier
> > didn't build in floppies to the system at all).
> >
> > Boot set of floppies is create how again?  Open the CD into the i386
> > directory and type setup /something, if I recall.  Have to do that on a
> > system with a floppy installed, and working, and then move the floppy to
> > the
> > other system and get it all up and going.  Do you think the drive itself
> > is
> > toast?  As in, replace the drive, and ghost over the second partition
with
> > the audio files on it? (About 60 gig worth).  OR, do you think a
> > Format/re-install of the OS to that partition will clear it up?  Or,
make
> > a
> > second install of the OS to the same drive?  (So many questions, so few
> > answers....LOL....)
> >
> > --
> > Glenn M.
> >
> >
> > "Robert Comer" 
wrote in message
> > news:41c1cc62{at}w3.nls.net...
> >> Ouch, 7B is "inaccessible boot device".
> >>
> >> Repair time.
> >>
> >> > Any idea why I can't get the system go boot from a CDROM drive?
> >>
> >> Has to be something about the bios, so no.  You can make a boot set of
> >> floppies though.
> >>
> >> > Also, how would I do a new install on this version of the OS in
another
> >> > computer?
> >>
> >> Can't do that.
> >>
> >> >Have to boot from the CD to be able to tell it which directory to
> >> > install to, I guess.  That makes sense, as I don't think
booting from
> > the
> >> > booted OS will give me the option of selecting which install to
> > re-install
> >> > to.
> >>
> >> Floppies....
> >>
> >> > Hmm, maybe I can boot to the recovery console from a CD boot on
another
> >> > system with this drive attached, and then get to the bogus/dead
install
> >> > and
> >> > try a recovery from there.  Thoughts/comments?
> >>
> >> I doubt it.
> >>
> >> - Bob Comer
> >>
> >>
> >>
> >> "Glenn Meadows"  wrote in message
> >> news:41c1c996$1{at}w3.nls.net...
> >> > OK, I've reset the autoboot option to 0, let's see what BSOD gets
> > created,
> >> > and I've also unplugged the 2 USB HD's
> >> >
> >> > Here's the failure message:
> >> >
> >> > (Usual standard stuff).
> >> > No driver file mentioned in the BSOD.
> >> >
> >> > Technical Information:
> >> >
> >> > STOP: 0x0000007B (0xF789E528, 0xC0000034, 0x00000000, 0x00000000)
> >> >
> >> > That's all that it displays.
> >> >
> >> > Any idea why I can't get the system go boot from a CDROM drive?
> >> >
> >> > Also, how would I do a new install on this version of the OS in
another
> >> > computer?  Have to boot from the CD to be able to tell it which
> > directory
> >> > to
> >> > install to, I guess.  That makes sense, as I don't think
booting from
> > the
> >> > booted OS will give me the option of selecting which install to
> > re-install
> >> > to.
> >> >
> >> > Hmm, maybe I can boot to the recovery console from a CD boot on
another
> >> > system with this drive attached, and then get to the bogus/dead
install
> >> > and
> >> > try a recovery from there.  Thoughts/comments?
> >> >
> >> >
> >> >
> >> > --
> >> > Glenn M.
> >> >
> >> >
> >> > "Robert Comer"
 wrote in message
> >> > news:41c1c280{at}w3.nls.net...
> >> >> > The next thing I'm going to try, is to rename
mup.sys to mup.sy_
and
> >> >> > see
> >> >> > what happens.  There is an older version of
mup.sys in the service
> > pack
> >> >> > uninstall directory, that I could try, and
probably will, to see
if
> >> > that's
> >> >> > what's holding things up.
> >> >>
> >> >> Don't do that, mup.sys is just the last driver loaded and most
likely
> >> > *not*
> >> >> what's failing -- it's something that loads after
the drivers that's
> >> > causing
> >> >> your problems.
> >> >>
> >> >> First things first, you gotta see what BSOD's happening.
> >> >>
> >> >> Use this FAQ to turn off the rebooting:
> >> >> http://www.jsiinc.com/subb/tip0500/rh0526.htm  They
don't describe
> >> >> that
> >> > you
> >> >> can do it from a second PC, the say use another
install on the same
> >> >> PC,
> >> > but
> >> >> it really would work the same.  That should get you
the BSOD and
then
> >> > maybe
> >> >> we can figure out what to do then.
> >> >>
> >> >> This is just a FAQ on the crashcontrol stuff,
interesting and maybe
> >> >> for
> >> >> future use: http://www.jsiinc.com/suba/tip0300/rh0312.htm
> >> >>
> >> >> - Bob Comer
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> "Glenn Meadows"
 wrote in message
> >> >> news:41c1bf53{at}w3.nls.net...
> >> >> > Yo guys.  Need some guru help here.
> >> >> >
> >> >> > Have one XP SP2 machine, Athalon 2100+ system,
that after the last
> >> > patches
> >> >> > (and it did this once before), goes into a reboot loop.
Everything
> >> >> > I've
> >> >> > found, so far, has been fruitless to resolve
this.  I can move the
> >> >> > HD
> >> >> > to
> >> > a
> >> >> > working system, and access the drive. I've done
a commandline
chkdsk
> >> > /f/r
> >> >> > on
> >> >> > the drives 2 partitions.
> >> >> >
> >> >> > What I've done:
> >> >> >
> >> >> > Tried to boot into SAFE mode, hangs at the
display of the driver
> >> > mup.sys.
> >> >> >
> >> >> > Added /sos and /bootlog to the boot.ini file, as well as
/basevideo
> >> > That
> >> >> > gets me the same displayed list of driver
names, then I get a
plain
> >> > style
> >> >> > VGA screen that lists the boot OS version,
etc., and then displays
> > Boot
> >> >> > logging enabled.  BUT, in the spot where the
boot log is supposed
to
> >> >> > be,
> >> >> > %systemroot%\ntblog.txt, there is only one
dated back in August,
not
> > a
> >> >> > replaced one from today and that boot.
> >> >> >
> >> >> > After that screen displays, the computer goes
back to the bios
start
> >> >> > screen,
> >> >> > and initiates a reboot again.
> >> >> >
> >> >> > How, when putting the HD into a working system,
does one uninstall
> > the
> >> >> > fixes
> >> >> > that were applied during the latest patch application?
> >> >> >
> >> >> > Where is the list and order of the drivers to
load stored, so if
the
> >> >> > driver
> >> >> > that's hanging/crashing is after the one
displayed, you can see
what
> > it
> >> > is
> >> >> > to try to replace it, or rename it so you can
attempt to bypass
it?
> >> >> >
> >> >> > Also, I am unable to get this system to boot
from the CDROM of
> > Windows
> >> > XP.
> >> >> > The Boot from CD question appears for about 1 second, but
> >> >> > immediately
> >> > goes
> >> >> > right past to the HD boot.  Even if I turn OFF
the HD in the Bios,
> > the
> >> >> > computer STILL finds it, and tries to boot from it.
> >> >> >
> >> >> > The next thing I'm going to try, is to rename
mup.sys to mup.sy_
and
> >> >> > see
> >> >> > what happens.  There is an older version of
mup.sys in the service
> > pack
> >> >> > uninstall directory, that I could try, and
probably will, to see
if
> >> > that's
> >> >> > what's holding things up.
> >> >> >
> >> >> > --
> >> >> > Glenn M.
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>

--- BBBS/NT v4.01 Flag-5