Re: how to change out system disk?
From: Doug Floer (spam_at_localhost.com)
Date: 05/14/04
- Next message: Bad Head: "Windows XP Pro from IDE Drive to SATA Drive."
- Previous message: anonymous_at_discussions.microsoft.com: "Hard drive problem"
- In reply to: R. C. White: "Re: how to change out system disk?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 13 May 2004 20:53:37 -0700
Hi RC, thanks for taking the time to respond.
> That's why I ask what you see on that very first screen when you power on
> your computer. Do you see an Adaptec banner? Do you get the message
("SCSI
> BIOS failed to load") that looks like an error message but is only
informing
> you that "the SCSI BIOS is not needed this time so I didn't bother to load
> it into RAM"?
There is no need to change the SCSI BIOS. It boots from SCSI ID 0 right now
just fine. All I've done is prepare the 36 GB drive that's on ID 3 as
you've indicated, then remove the other two drives and change the 36 GB
drive to have SCSI ID 0. Should be a no brainer, providing the bootstrap
and other files are in place.
> > To build the contents for the new C: boot volume, I simply copied the
> > boot.ini, ntdetect.com, and ntldr files to it.
>
> NO! NO! NO! (Sorry to be so melodramatic.) That's why I explained
"boot
> volume" in my first message, and why I asked in my second message, "Do you
> mean what common sense would call the 'boot volume', or do you mean what
> Microsoft calls the 'system partition'?" In the typical one-drive,
I think we're getting mixed up with the terminology but I understand your
premise and have setup accordingly. Here's the boot.ini. Note that the
drive is partitioned into 5 volumes: 1GB System (with boot.ini, ntdetect,
etc), 2GB W2K, 8GB Data, 8GB XP, 8GB Programs.
[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(4)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000"
/fastdetect
> numbers, but something might have gone wrong. Did you have more than the
> one drive connected at that time you ran bootcfg?
Nope.
> As I understand your current configuration, you have only a single HD
> connected to the SCSI adapter. It has a single primary partition (C:) and
> logical drives D:, J: (the boot volume, where J:\Windows, the boot folder,
> is located), and two other data volumes. If this is the case, then
> C:\boot.ini should include under [operating systems] the line:
> multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP
> Professional" /FASTDETECT
The only problem with this config is that the drive letters are not assigned
correctly since I haven't been able to boot into an instance of XP or W2K
that will allow me to reassign the needed drive letters. I've been assuming
that XP will find the boot volume via %SYSTEMROOT% with the understanding
that not everything would run, since a lot of the programs are installed on
a separate volume, but enough that I can get the system up and the drives
reassigned.
> and in the [boot loader] section above:
> default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
>
> This would point to the third (C:, D:, J:) partition on the first HD.
NTLDR
> should find J:\Windows there.
This could be the problem. I've been assuming NTLDR will find it at
%SYSTEMDRIVE%\%SYSTEMROOT%\WINDOWS, which should be relative to the system
disk, right? But even if it does require the J: drive to be preset, I
expected it to load the boot menu which is definitely on the system drive at
C:. (Don't understand why microsoft didn't provide for drive letter
chaneges in the recovery console.)
> Maybe your next stop should be at the Tech Support page at www.adaptec.com
> or your mobo maker? I would be very interested in what you learn about
this
> problem.
I'll let you know what I find. You sure earned it! Thanks for all your
help!
Doug
> --
> R. C. White, CPA
> San Marcos, TX
> rc@corridor.net
> Microsoft Windows MVP
>
> "Doug Floer" <spam@localhost.com> wrote in message
> news:ejLWgs6NEHA.4036@TK2MSFTNGP12.phx.gbl...
> > No, I didn't do the F6 key to install SCSI drivers since the drivers are
> > included in XP. The controller is an Adaptec AIC-7890.
> >
> > Never managed to boot from the SCSI drive. What I managed to do was
boot
> > the XP CD and enter the recovery console. I also did the XP system
> > reinstallation by booting from XP CD. Never was able to load XP from
the
> > J:
> > drive. The boot loader never got that far.
> >
> > To build the contents for the new C: boot volume, I simply copied the
> > boot.ini, ntdetect.com, and ntldr files to it. When it wouldn't boot, I
> > used the recovery console to fix the bootblock (fixboot) and MBR
(fixmbr)
> > and corrected the location of Windows with bootcfg. Still no joy. From
> > the
> > console, fixboot complained about the look of the boot volume. The SCSI
> > utility still reports boot from ID0, same as it always has. I have no
IDE
> > drives on this system, only SCSI, so I know it boots just fine.
> >
> > Thanks again for your help.
> >
> > Doug
> >
> >
> > "R. C. White" <RCWhite@msn.com> wrote in message
> > news:OkqF2n3NEHA.664@TK2MSFTNGP09.phx.gbl...
> >> Hi, Doug.
> >>
> >> Two questions:
> >>
> >> 1. Did you need to use the F6 key to install SCSI drivers during
Setup?
> >> The usual symptom for failure to do this is a BSOD with Stop 0x7B,
> >> Inaccessible_Boot_Device, when trying to boot from the new HD, but
> > sometimes
> >> the computer's response is different. Of course, your BIOS must be set
> >> to
> >> boot from SCSI, too, but I'm sure you knew that.
> >>
> >> 2. When you manage to "boot around" the new Drive C:, can you run
WinXP
> >> from your new J:? The point of this question is to confirm that your
old
> >> Registry did in fact survive the move to the new HD and is still there
> > after
> >> the in-place upgrade. In other words, if you can just get that copy of
> >> WinXP booted, you can still run Word, Quicken or whatever without
having
> > to
> >> reinstall them.
> >>
> >> WinXP should not need a boot floppy, but one can be made and used in
some
> >> situations. Here, for example, you can use WinXP to format a blank
> > floppy,
> >> then copy the system files to it, including boot.ini, which will point
to
> >> the full WinXP on your hard drive. When you boot from this floppy, it
> > will
> >> bypass the system files on C: and, following the instructions on A:, go
> >> straight to "disk(0)partition(3)\Windows" (the third volume on the
first
> > HD,
> >> following the primary partition (C:) and the first logical drive (D:)).
> >> This boot-from-floppy method gets around needing to install the SCSI
BIOS
> >> and using it to BOOT FROM your new Drive C:.
> >>
> >> If you can boot from the floppy and run WinXP from your new Drive J:,
> >> with
> >> your previously-installed applications intact, then we can concentrate
on
> >> getting your system to boot from your new Drive C:. If not, then we
have
> > to
> >> figure out why not. Perhaps your implementation of SCSI is more
complex
> >> than mine. What make and model SCSI host adapter are you using?
> >>
> >> > There seems to be a problem with the parameters or
> >> > configuration of the boot volume of the new drive.
> >>
> >> OK, a third question: Do you mean what common sense would call the
"boot
> >> volume", or do you mean what Microsoft calls the "system partition"?
In
> >> your computer: Drive J:? Or Drive C:?
> >>
> >> RC
>
- Next message: Bad Head: "Windows XP Pro from IDE Drive to SATA Drive."
- Previous message: anonymous_at_discussions.microsoft.com: "Hard drive problem"
- In reply to: R. C. White: "Re: how to change out system disk?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
