dueal boot - blue and white screen

A

aa

On ASUS notebook with Windows XP Home attempted to make it dual boot to
install W2K. Before dong any changes I copied original ntldr (245K) and
ntdetect.com(47K).
With Partition Magic created an NTFS primary partition and installed W2K Pro
which went smoothly, and W2K was running OK
XP Home would not start at all because, as I seem to remember, ntldr(211K)
and ntdetect.com(34K) generated by W2K would not load XP, -so I replaced
them with the those of XP Home I copied earlier.

Now after selecting XPHome it produces the screen suggesting several modes
of loading XP Home, but whatever mode I select it just restarts the
computer.

I replaced ntldr and ntdetect.com with ntldr(230K) and ntdetect.com(47K)
from my working desktop. The first - booting into XP gave the same result,
i.e. list of loading optioons and restarting the computer.
But now W2K would not start. After shortly flashing that screen of starting
W2K, it produced a blue_and_white screen of some gobbledegook among which
there are english patterns like
STOP: 0x000000A5 (0x00000002, 0x8907DE88,0x88FB23ó8,0x00000001)
ASPI BIOS
"readme.txt"
http://www.hardware-update.com
<F&>
(I guess the remaining gobbledegook represent Cyrilics as the computer is
localised for Russia)

I placed the screenshot here:
www.pifpaf.front.ru/blue_white_screen.jpg

What might be the problem and the remedy?
 
D

Dave Patrick

It might depend on what you used PM for. You shouldn't have needed to use it
in order to install a second operating system. You might try creating a boot
disk.

For the floppy to successfully boot Windows XP the disk must contain the
"NT" boot sector. Format a diskette (on a Windows XP machine, not a
DOS/Win9x, so the NT boot sector gets written to the floppy), and copy
Windows XP versions of ntldr, ntdetect.com, and boot.ini to it. Edit the
boot.ini to give it a correct ARC path for the machine you wish to boot.
Below is an example of boot.ini. The default is to start the operating
system located on the first partition of the primary or first drive
(drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\Windows
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Windows XP 0,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\Windows="Windows XP 0,2"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\Windows="Windows XP 1,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\Windows="Windows XP 1,2"
/noexecute=optin /fastdetect

(watch for line wrap)



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
A

aa

Thanks, David.
I am aware that XP allows installing another OS withour Partition Magic
(PM), but with PM I made perhaps 15 dual boot computers and never had
problems with it. First thing I came across is the XP would not run w2k
installation disk on the grounds that it is an older version than itself. So
I opted they way I know - using PM. When PM suggested making boot disk I
skipped that for this notebook has no floppy drive

As to editing boot.ini - how do I access it if I cannot boot in?
With W98 booting CD I can boot into DOS prompt, but it does not see NTFS
partition where boot.ini is sitting
The w2k installation disk goes directly to installation and does not seem to
offer booting to DOS prompt

Dave Patrick said:
It might depend on what you used PM for. You shouldn't have needed to use it
in order to install a second operating system. You might try creating a boot
disk.

For the floppy to successfully boot Windows XP the disk must contain the
"NT" boot sector. Format a diskette (on a Windows XP machine, not a
DOS/Win9x, so the NT boot sector gets written to the floppy), and copy
Windows XP versions of ntldr, ntdetect.com, and boot.ini to it. Edit the
boot.ini to give it a correct ARC path for the machine you wish to boot.
Below is an example of boot.ini. The default is to start the operating
system located on the first partition of the primary or first drive
(drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\Windows
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Windows XP 0,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\Windows="Windows XP 0,2"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\Windows="Windows XP 1,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\Windows="Windows XP 1,2"
/noexecute=optin /fastdetect

(watch for line wrap)



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

aa said:
On ASUS notebook with Windows XP Home attempted to make it dual boot to
install W2K. Before dong any changes I copied original ntldr (245K) and
ntdetect.com(47K).
With Partition Magic created an NTFS primary partition and installed W2K
Pro
which went smoothly, and W2K was running OK
XP Home would not start at all because, as I seem to remember, ntldr(211K)
and ntdetect.com(34K) generated by W2K would not load XP, -so I replaced
them with the those of XP Home I copied earlier.

Now after selecting XPHome it produces the screen suggesting several modes
of loading XP Home, but whatever mode I select it just restarts the
computer.

I replaced ntldr and ntdetect.com with ntldr(230K) and ntdetect.com(47K)
from my working desktop. The first - booting into XP gave the same result,
i.e. list of loading optioons and restarting the computer.
But now W2K would not start. After shortly flashing that screen of
starting
W2K, it produced a blue_and_white screen of some gobbledegook among which
there are english patterns like
STOP: 0x000000A5 (0x00000002, 0x8907DE88,0x88FB23ó8,0x00000001)
ASPI BIOS
"readme.txt"
http://www.hardware-update.com
<F&>
(I guess the remaining gobbledegook represent Cyrilics as the computer is
localised for Russia)

I placed the screenshot here:
www.pifpaf.front.ru/blue_white_screen.jpg

What might be the problem and the remedy?
Click to expand...
Click to expand...
 
P

Pegasus \(MVP\)

If you follow David's recommendation of booting the machine
with a boot diskette then you won't have a problem modifying
a:\boot.ini.

It appears from your post that you frequently use multi-booting.
If so then having a Bart PE boot CD (www.bootdisk.com)
is IMHO an absolute must. It gives you full access to any NTFS
(and FAT32) partition, regardless of the current state of you
Windows installation.


aa said:
Thanks, David.
I am aware that XP allows installing another OS withour Partition Magic
(PM), but with PM I made perhaps 15 dual boot computers and never had
problems with it. First thing I came across is the XP would not run w2k
installation disk on the grounds that it is an older version than itself.
So
I opted they way I know - using PM. When PM suggested making boot disk I
skipped that for this notebook has no floppy drive

As to editing boot.ini - how do I access it if I cannot boot in?
With W98 booting CD I can boot into DOS prompt, but it does not see NTFS
partition where boot.ini is sitting
The w2k installation disk goes directly to installation and does not seem
to
offer booting to DOS prompt

Dave Patrick said:
It might depend on what you used PM for. You shouldn't have needed to use it
in order to install a second operating system. You might try creating a boot
disk.

For the floppy to successfully boot Windows XP the disk must contain the
"NT" boot sector. Format a diskette (on a Windows XP machine, not a
DOS/Win9x, so the NT boot sector gets written to the floppy), and copy
Windows XP versions of ntldr, ntdetect.com, and boot.ini to it. Edit the
boot.ini to give it a correct ARC path for the machine you wish to boot.
Below is an example of boot.ini. The default is to start the operating
system located on the first partition of the primary or first drive
(drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\Windows
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Windows XP 0,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\Windows="Windows XP 0,2"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\Windows="Windows XP 1,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\Windows="Windows XP 1,2"
/noexecute=optin /fastdetect

(watch for line wrap)



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

aa said:
On ASUS notebook with Windows XP Home attempted to make it dual boot to
install W2K. Before dong any changes I copied original ntldr (245K) and
ntdetect.com(47K).
With Partition Magic created an NTFS primary partition and installed
W2K
Pro
which went smoothly, and W2K was running OK
XP Home would not start at all because, as I seem to remember, ntldr(211K)
and ntdetect.com(34K) generated by W2K would not load XP, -so I
replaced
them with the those of XP Home I copied earlier.

Now after selecting XPHome it produces the screen suggesting several modes
of loading XP Home, but whatever mode I select it just restarts the
computer.

I replaced ntldr and ntdetect.com with ntldr(230K) and
ntdetect.com(47K)
from my working desktop. The first - booting into XP gave the same result,
i.e. list of loading optioons and restarting the computer.
But now W2K would not start. After shortly flashing that screen of
starting
W2K, it produced a blue_and_white screen of some gobbledegook among which
there are english patterns like
STOP: 0x000000A5 (0x00000002, 0x8907DE88,0x88FB23ó8,0x00000001)
ASPI BIOS
"readme.txt"
http://www.hardware-update.com
<F&>
(I guess the remaining gobbledegook represent Cyrilics as the computer is
localised for Russia)

I placed the screenshot here:
www.pifpaf.front.ru/blue_white_screen.jpg

What might be the problem and the remedy?
Click to expand...
Click to expand...
Click to expand...
 
A

aa

Thanks, Pegasus.
I cannot follow David's recomendation for the notebook in question has no
floppy drive
What is the alternative?


Pegasus (MVP) said:
If you follow David's recommendation of booting the machine
with a boot diskette then you won't have a problem modifying
a:\boot.ini.

It appears from your post that you frequently use multi-booting.
If so then having a Bart PE boot CD (www.bootdisk.com)
is IMHO an absolute must. It gives you full access to any NTFS
(and FAT32) partition, regardless of the current state of you
Windows installation.


aa said:
Thanks, David.
I am aware that XP allows installing another OS withour Partition Magic
(PM), but with PM I made perhaps 15 dual boot computers and never had
problems with it. First thing I came across is the XP would not run w2k
installation disk on the grounds that it is an older version than itself.
So
I opted they way I know - using PM. When PM suggested making boot disk I
skipped that for this notebook has no floppy drive

As to editing boot.ini - how do I access it if I cannot boot in?
With W98 booting CD I can boot into DOS prompt, but it does not see NTFS
partition where boot.ini is sitting
The w2k installation disk goes directly to installation and does not seem
to
offer booting to DOS prompt

Dave Patrick said:
It might depend on what you used PM for. You shouldn't have needed to
Click to expand...
use
it
in order to install a second operating system. You might try creating a boot
disk.

For the floppy to successfully boot Windows XP the disk must contain the
"NT" boot sector. Format a diskette (on a Windows XP machine, not a
DOS/Win9x, so the NT boot sector gets written to the floppy), and copy
Windows XP versions of ntldr, ntdetect.com, and boot.ini to it. Edit the
boot.ini to give it a correct ARC path for the machine you wish to boot.
Below is an example of boot.ini. The default is to start the operating
system located on the first partition of the primary or first drive
(drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\Windows
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Windows XP 0,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\Windows="Windows XP 0,2"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\Windows="Windows XP 1,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\Windows="Windows XP 1,2"
/noexecute=optin /fastdetect

(watch for line wrap)



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
On ASUS notebook with Windows XP Home attempted to make it dual boot to
install W2K. Before dong any changes I copied original ntldr (245K) and
ntdetect.com(47K).
With Partition Magic created an NTFS primary partition and installed
W2K
Pro
which went smoothly, and W2K was running OK
XP Home would not start at all because, as I seem to remember, ntldr(211K)
and ntdetect.com(34K) generated by W2K would not load XP, -so I
replaced
them with the those of XP Home I copied earlier.

Now after selecting XPHome it produces the screen suggesting several modes
of loading XP Home, but whatever mode I select it just restarts the
computer.

I replaced ntldr and ntdetect.com with ntldr(230K) and
ntdetect.com(47K)
from my working desktop. The first - booting into XP gave the same result,
i.e. list of loading optioons and restarting the computer.
But now W2K would not start. After shortly flashing that screen of
starting
W2K, it produced a blue_and_white screen of some gobbledegook among which
there are english patterns like
STOP: 0x000000A5 (0x00000002, 0x8907DE88,0x88FB23ó8,0x00000001)
ASPI BIOS
"readme.txt"
http://www.hardware-update.com
<F&>
(I guess the remaining gobbledegook represent Cyrilics as the
Click to expand...
computer
is
localised for Russia)

I placed the screenshot here:
www.pifpaf.front.ru/blue_white_screen.jpg

What might be the problem and the remedy?
Click to expand...
Click to expand...
Click to expand...
 
A

aa

I borrowed another w2k installation disk and it allowed me to get to the DOS
prompt
Using Help I got a list of cpmmands available and cannot figure out which
one is for opening and editing boot.ini
 
P

Pegasus \(MVP\)

aa said:
I borrowed another w2k installation disk and it allowed me to get to the
DOS
prompt
Using Help I got a list of cpmmands available and cannot figure out which
one is for opening and editing boot.ini
Click to expand...

DOS is an operating system introduced some 30 years ago.
It does not exist under Win2000. I suspect that you got into
the Recovery Console. AFAIK, the Recovery Console has
no tools to edit boot.ini. Here are a couple of options:
- Boot the machine with a Bart PE boot CD, as explained before.
- After creating (and testing!) a Windows 2000 boot diskette
on a machine with a diskette drive, burn a bootable CD from
that diskette, preferably on a CD/RW CD in case you don't
get it right the first time.
 
A

aa

yes, i got into something looking and working like dos prompt, but it must
be something else.
I will try you advice (here in Russia credit cards are not common and I need
to find the way to pay $4 to www.bootdisk.com to get access to download)
But your advice is based on presumption that my boot.ini is corrupted - is
that correct? This might explain why XP restarts the computer instead of
loading. But corrupted boot.ini will not explain the blue_and_white screen
on starting w2k (www.pifpaf.front.ru/blue_white_screen.jpg) will it?
 
P

Pegasus \(MVP\)

Downloads from www.bootdisk.com are free!

David never said that your boot.ini file was corrupted -
he merely showed you how you can use boot.ini to invoke
different operating systems in a multi-boot environment.
The blue/white screen issue may require different measures
but using a multi-choice boot.ini should be your first step.
 
A

aa

www.bootdisk.com/popfiles.htm reads:
As you know it takes a lot of time and effort to maintain a website such as
this. I hope that you really appreciate my efforts and I hope that the
content of my site has been saving you both time and money.

I've worked hard to find, make available, and create some of the best fully
functional computer utilities so you can both find them and download them
very easily. As my site grows in popularity tho the demand for certain files
is becoming quite overwhelming. So in response I'd like to request that you
if you need these files that you help me out for my time and expenses for
just $4 to get instant access to EVERY file below.

After completing the transaction you will IMMEDIATELY be directed to a
download page that includes all the files below. Also, you will be sent an
email which also provides the link to the download page.


Click the button below to Checkout via PayPal to get

Immediate access to ALL the above files
 
A

aa

If an OS used to load OK and then stopped and David advised to look into
boot.ini I take it as something wrong happened to boot.ini - that is what I
call corrupted, though it might be called some other name
 
A

aa

I've managed to boot into w2k and accessed boot.ini:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000
Professional RUS" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition RU" /noexecute=optin /fastdetect


the first one boots OK, the second will not. What might be wrong with
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition RU" /noexecute=optin /fastdetect ?

There is the only physical disk and apart from primary partitions for WINNT
and for WINDOWS there is a logical partition as well as a hidden partition
with recovery for XP

Dave Patrick said:
It might depend on what you used PM for. You shouldn't have needed to use it
in order to install a second operating system. You might try creating a boot
disk.

For the floppy to successfully boot Windows XP the disk must contain the
"NT" boot sector. Format a diskette (on a Windows XP machine, not a
DOS/Win9x, so the NT boot sector gets written to the floppy), and copy
Windows XP versions of ntldr, ntdetect.com, and boot.ini to it. Edit the
boot.ini to give it a correct ARC path for the machine you wish to boot.
Below is an example of boot.ini. The default is to start the operating
system located on the first partition of the primary or first drive
(drive0). Then drive0 partition 2 and so on.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\Windows
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Windows XP 0,1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\Windows="Windows XP 0,2"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\Windows="Windows XP 1,1"
/noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(2)\Windows="Windows XP 1,2"
/noexecute=optin /fastdetect

(watch for line wrap)



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

aa said:
On ASUS notebook with Windows XP Home attempted to make it dual boot to
install W2K. Before dong any changes I copied original ntldr (245K) and
ntdetect.com(47K).
With Partition Magic created an NTFS primary partition and installed W2K
Pro
which went smoothly, and W2K was running OK
XP Home would not start at all because, as I seem to remember, ntldr(211K)
and ntdetect.com(34K) generated by W2K would not load XP, -so I replaced
them with the those of XP Home I copied earlier.

Now after selecting XPHome it produces the screen suggesting several modes
of loading XP Home, but whatever mode I select it just restarts the
computer.

I replaced ntldr and ntdetect.com with ntldr(230K) and ntdetect.com(47K)
from my working desktop. The first - booting into XP gave the same result,
i.e. list of loading optioons and restarting the computer.
But now W2K would not start. After shortly flashing that screen of
starting
W2K, it produced a blue_and_white screen of some gobbledegook among which
there are english patterns like
STOP: 0x000000A5 (0x00000002, 0x8907DE88,0x88FB23ó8,0x00000001)
ASPI BIOS
"readme.txt"
http://www.hardware-update.com
<F&>
(I guess the remaining gobbledegook represent Cyrilics as the computer is
localised for Russia)

I placed the screenshot here:
www.pifpaf.front.ru/blue_white_screen.jpg

What might be the problem and the remedy?
Click to expand...
Click to expand...
 
D

Dave Patrick

aa said:
Thanks, David.
I am aware that XP allows installing another OS withour Partition Magic
(PM), but with PM I made perhaps 15 dual boot computers and never had
problems with it. First thing I came across is the XP would not run w2k
installation disk on the grounds that it is an older version than itself.
Click to expand...
*** Don't run from XP Best to just boot the CD-Rom to start setup.


So
I opted they way I know - using PM. When PM suggested making boot disk I
skipped that for this notebook has no floppy drive

As to editing boot.ini - how do I access it if I cannot boot in?
Click to expand...
*** You'll need to use another computer to create the boot disk.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
A

aa

Thanks
There are quite a lot of options there. Which one would you recommend for
w2kPro and for XP Home ?
 
P

Pegasus \(MVP\)

To manufacture a Windows 2000 boot disk, follow David's
recipe. There is no need to download anything.

To manufacture a Bart PE boot CD, download the Bart PE
bood CD file. It is free but it requires the following:
- A WinXP Professional installation CD (but no product key)
- A CD burner
- A few hours of your time
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

remote boot gives blue screen? 3
Boot Windows 2000, the Blue screen of death and nVidia ? 2

Top