Re: Dual Boot

Your reply is somewhat confusing but if I understand you
correctly then this is what you have:

Western Digital Disk
==============
- WinXP Home
- Visible as drive C when WinXP is running.
- No other partitions

Maxtor Disk
=========
- Windows server
- Visible as drive C: when the WD disk is unplugged and Windows Server is
running.
- No other partitions

Questions:
=======
1. Where is your XOSL partition?
2. What type is it? (FAT/FAT32/NTFS)
3. How large is it?
4. Did you label your WinXP partition on the WD as 'WinXP"?
5. Did you label your server partition on the Maxtor disk as "Server"?


"Vince" <Vince@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9BFA6BA8-47E6-456C-B0E4-5B84A1481B8A@xxxxxxxxxxxxxxxx
> I like plan B, when I boot into windows Home edition; I see disk 0 The
Maxtor
> with server 2003 Disk C: and Disk D:Disk C has the operating system on it
and
> the MBR Disk 1 is F: and E: with xp Home, E: has the operating system on
it
> with the MBR. Now when I boot into Server 2003, I see Disk 0 J: and K:
server
> 2003 J: Having the operating system and the MBR and Disk 1 XP Home D:and
C:
> C: having the operating system on it with the MBR.
> When I run the Set Systemdrive, both say system Drive=C: Here is
> the Bootloader for server 2003: [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=""WINDOWS SERVER 2003
STANDARD""
> /fastdetect
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
Standard"
> /fastdetect /NoExecute=OptOut
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home
> Edition" /fastdetect
> C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
> Now here is the Bootloader for XP Home: [Boot Loader]
> Timeout=5
> Default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
> [Operating Systems]
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home
> Edition" /noexecute=optin /fastdetect
> C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003,
Standard"
> /fastdetect The operating system for XP Home is on E: the other F is for
> recovery. server 2003 system is on C: and Thanks in advance.
> "Vince" wrote:
>
> > I will get right back to you, I have to go pick my son up. Give me 45
min. I
> > will get right back to you. Thanks
> >
> > "Pegasus (MVP)" wrote:
> >
> > >
> > > "Vince" <Vince@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:1122BC67-0F44-44AD-9224-D1F443227666@xxxxxxxxxxxxxxxx
> > > > Okay, here is what I did.. I used my sons computer, It is a Compaq
> > > sr1300nx
> > > > and loaded the windows server 2003 on to a Maxter 20gb hard drive
set as
> > > > slave. The operating system that is on his computer is windows xp
home
> > > > edition that is on a Western Dig 60gb set as master. It loaded just
fine
> > > but
> > > > when I checked to see what letter the computer gave my maxtor, I
could
> > > not
> > > > see the 60gb hard drive with windows xp home. All I could see is the
> > > Maxtor.
> > > > The letters were c and d, I split the hard drive. I rebooted and it
booted
> > > > fine to the Server 2003. What happened was that when I put the
Maxtor hard
> > > > drive in I must have loosened the IDE cable that went to the
Western
> > > > dig/master, well, to my surprise, I had loaded the server 2003
> > > succesfully
> > > > onto the 20gb maxtor while the 60gb Western Dig was diconnected. Now
after
> > > I
> > > > plugged the IDE cable in, I can boot to windows Home edition which
is now
> > > F,
> > > > but when I try to boot to the windows server, I get an error
message;
> > > Windows
> > > > could not start because the following file is missing or corrupt;
<windows
> > > > root> \system 32\ntoskrnl.exe. Pleases re-install a copy of the
above
> > > file. I
> > > > can put the server cd in and it will bootup, or I can unplug the ide
cable
> > > to
> > > > the 60gb and it will boot to server 2003, and I can boot to windows
Home
> > > > edition fine. How can I install ntoskrnl.exe. I re-installed server
2003
> > > and
> > > > I also have updated all the updates for server 2003. Any suggestions
on
> > > how
> > > > to remedy this? I never put XOSL on the end of the hard drive like
you
> > > told
> > > > me to, but I did partition for it:(
> > >
> > > Your problem is caused by a shift in partition numbers.
> > > This is superficially easily fixed, by adjusting the file
> > > c:\boot.ini. However, it will lead to other problems
> > > that are much harder to fix.
> > >
> > > There are two ways to recover from this mishap:
> > >
> > > a) Connect both disks, and reload Windows Server.
> > > b) Start using XOSL.
> > >
> > > If you lean towards option b) then you need to post
> > > more information.
> > > 1. When you boot into WinXP Home, what drives do
> > > you see in "My Computer"?
> > > 2. Click Start / Run, type cmd {OK}, then type this:
> > > set systemdrive
> > > What do you see?
> > > 3. When you boot into Server, what drives do
> > > you see in "My Computer"?
> > > 4. Click Start / Run, type cmd {OK}, then type this:
> > > set systemdrive
> > > What do you see?
> > > 5. Describe in detail the partitions of both disks.
> > >
> > >
> > >


.

Relevant Pages
Loading