Re: *** STOP: (0x0000007B,0XF85438D0,0XC000009C,0X00000000,0x00000

I'll try that tonight when I get home. I can press F8 and go to the command
prompt, but if I do a format A:, is that going to format the diskette with
the NT boot sector, as you stated? If so, then all I have to do is locate
the other three files you mentioned (ntldr, ntdetect, and boot.ini) and copy
them to the diskette. I would assume during the boot of the W2K machine, I
should also see if it is a SCSI or other type of controller during the boot
up process.

If this is successful, and I don't get the blue screen of death with the
"STOP" msg, then am I going to boot up in W2K, or just the "A:" or "C:"
prompt, with this boot disk?

Also, if I create a full set of Boot Disks, then I will need four diskettes,
and will use the CD drive to make all four boot disks. This is not want you
are talking about, when you wanted me to create a "BOOT" disk is it? You
only want me to create one W2K Boot Disk with the W2K Boot sector and all of
the files, is that correct? Sorry for all the confusion, but I am not that
well versed with W2K, I run XP on my PC and the wife uses W2K on hers. So I
am still going through a learning curve with W2K. Thanks again Dave, for
your assistance.

"Dave Patrick" wrote:

> Be aware that Microsoft use the term boot partition for the partition where
> the operating system is installed, while the system partition is the first
> primary active partition (where the boot sector and files required to start
> the operating system reside) The system and boot partition can be
> one-and-the-same but this isn't always the case.
>
> I'll assume that C:\ is the system and boot partition. It might be the
> active partition has changed and or that boot.ini no longer points to the
> correct location.
>
> First lets try a boot floppy.
>
> Try creating a boot disk. For the floppy to successfully boot Windows 2000
> the disk must contain the "NT" boot sector. Format a diskette (on a Windows
> 2000 machine, not a DOS/Win9x, so the NT boot sector gets written to the
> floppy), and copy Windows 2000 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)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
> multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
> multi(0)disk(0)rdisk(1)partition(1)\WINNT="Windows 2000 1,1"
> multi(0)disk(0)rdisk(1)partition(2)\WINNT="Windows 2000 1,2"
>
> Another possibility is to try loading the controller driver also from
> floppy. For the floppy to successfully boot Windows 2000 the disk must
> contain the "NT" boot sector. Format a diskette (on a Windows 2000 machine,
> not a DOS/Win9x, so the "NT" boot sector gets written to the floppy), then
> copy 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.
>
> In order for this to work you'll want to change the arc path in boot.ini
> from multi syntax to scsi syntax to indicate that Windows 2000 will load a
> boot device driver and use that driver to access the boot partition. Then
> also copy the correct manufacturer SCSI, or ultra DMA, or ATA100, or raid,
> or serial ATA driver to the floppy but renamed to ntbootdd.sys
>
> Something like this below;
>
> [boot loader]
> timeout=10
> default=scsi(0)disk(0)rdisk(0)partition(1)\winnt
> [operating systems]
> scsi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 0,1"
> scsi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000 0,2"
> scsi(0)disk(1)rdisk(0)partition(1)\WINNT="Windows 2000 1,1"
> scsi(0)disk(1)rdisk(0)partition(2)\WINNT="Windows 2000 1,2"
>
> --
> Regards,
> Dave
>
> -------------
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Bob Brighton" wrote:
> | She has two Partitions: "C" is the boot drive and "D" has all of her
> | miscellaneous applications and files are on this drive. "D" is the bigger
> | drive of the two. All of her regular applications (Microsoft Office, WEB
> | Development Applications, and most of her regular standard installs), are
> all
> | on the "C" drive under Programs. I don't know what type of controller she
> | has, if needed, I can open up the box and try and get that information or
> try
> | and figure it out, if it will help.
>
>
>
.

Relevant Pages

  • Re: Vista, Xin ho?i xi?n :)
    ... a powerful, reliable, and easy-to-use boot manager. ... disk or have several multiboot systems on the same partition. ... OS Selector allows you to install different multi-boot ... Hide any partitions independently of any given operating system. ...
    (soc.culture.vietnamese)
  • Re: Vista, Xin ho?i xi?n :)
    ... a powerful, reliable, and easy-to-use boot manager. ... disk or have several multiboot systems on the same partition. ... OS Selector allows you to install different multi-boot ... Hide any partitions independently of any given operating system. ...
    (soc.culture.vietnamese)
  • Re: BootIt NG high level steps - best approach??
    ... backup boot strategy. ... As far as BING, I should tell you I've been using this software ... make managing your bootable options and partition management so much easier. ... drives) and the DATA partition on a mirrored array. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Dual booting
    ... of Microsoft's dual boot scenario. ... The extended partition is not assigned a drive letter, ... BIOS reserves letters A and B for floppy drives, ... If WinXP Setup ...
    (microsoft.public.windowsxp.general)
  • Re: Dual Boot Instructions
    ... I ended up reinstalling Vista, ... The boot SECTOR is not the bootLOADER. ... finds the partition table for that HDD and sees that the first partition is ... violated, we no longer can simply install WinXP, install Vista and ...
    (microsoft.public.windows.vista.hardware_devices)