Dixonian69 Wrote:
> restore you boot.ini file to original.
>
> it won't boot into Win 2k now?
>
> are you worried about data in win 2k or win xp?
>
>
> "ObsidianRazor" wrote:
>
>
> Dixonian69 Wrote:
> It worked for almost a year?
> so what has changed anything?
>
> change first boot.ini file to this:
> Note: I changed the rdisk ( ) value from "0" to "1", in the
> default
> and
> operating sysfor th win xp entries.
> [boot loader]
> timeout=30
> default=signature(292a91c)disk(0)rdisk(1)partition (1)\WINDOWS
> [operating systems]
> signature(292a91c)disk(0)rdisk(1)partition(1)\WIND OWS="Microsoft
> Windows XP Professional" /fastdetect
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> Professional" /fastdetect /NoExecute=OptIn
>
> If this doesn't work, there must be something wrong with the slave
> HDD.
>
> run hardware diagnostics on the drive.
>
> "ObsidianRazor" wrote:
>
>
> Dixonian69 Wrote:
> is there only one partition on primary slave?
> what kind of a drive is it?
>
> this is unusaul description and doesn't match the second boot.ini
> file!!
> signature(292a91c)
>
> if you change boot order, so that primary slave is set as first
> boot,
> Can
> you boot to Win XP?
>
>
> "ObsidianRazor" wrote:
>
>
> Dixonian69 Wrote:
> Physically in you computer which HDD contains win 2k?
> Is the win 2k HDD set as primary master?
>
> Is win 2k HDD set as HD(0) is computer bios?
> is win 2k ((HD(0)) set as first boot device in boot order?
>
> This is not normal boot.ini enrty!!
> signature(292a91c)
>
> on your first boot.ini, change from:
> [boot loader]
> timeout=30
> default=signature(292a91c)disk(0)rdisk(0)partition (1)\WINDOWS
> [operating systems]
> signature(292a91c)disk(0)rdisk(0)partition(1)\WIND OWS="Microsoft
> Windows XP Professional" /fastdetect
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> Professional" /fastdetect /NoExecute=OptIn
>
> change to:
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(1)partition(1)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Micro soft Windows XP
> Professional" /fastdetect /NoExecute=OptIn
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> Professional" /fastdetect /NoExecute=OptIn
>
> Leave boot order alone for now!!
>
> "ObsidianRazor" wrote:
>
>
> Dixonian69 Wrote:
> does it boot into either OS?
>
> "ObsidianRazor" wrote:
>
>
> I run a dual OS boot from separate HD's. I installed W2K on first
> disk
> and installed WXP on the 2nd disk while running the W2K OS. The
> following boot.ini are respective (W2K/WXP)
>
> [boot loader]
> timeout=30
> default=signature(292a91c)disk(0)rdisk(0)partition (1)\WINDOWS
> [operating systems]
> signature(292a91c)disk(0)rdisk(0)partition(1)\WIND OWS="Microsoft
> Windows XP Professional" /fastdetect
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> Professional" /fastdetect /NoExecute=OptIn
>
> [boot loader]
> timeout=30
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP
> Professional" /fastdetect /NoExecute=OptIn
>
> After a hard power cycle I am now getting the hal.dll corrupt or
> missing and I have replaced the file on my XP disk. Same problem.
>
> Any ideas? TIA for all that respond.
>
> OR
>
>
> --
> ObsidianRazor
>
> I guess it would have made a little more sense to have provided that
> tidbit of info. I can boot the W2K and am able to read & open files
> on
> the WXP disk. I used my WXP disk and booted from the CD ROM and
> tried
> the repair option, but it only brings up the c:/WINNT from the W2K
> disk. I used the expand command to replace the WXP hal.dll and I
> also
> tried copying a duplicate of the file from the i386 directory,
> neither
> of which worked. I'm assuming it has something to do with the
> boot.ini
> but I'm not sure what it is since they look normal.
>
>
> --
> ObsidianRazor
>
>
> I tried the replacement of the boot.ini you provided and when I
> select
> the XP option it just sits there with a blank screen. The W2K
> portion
> still works, so I reinstalled the origianl boot.ini and I'm back at
> sqaure 1.
>
> W2K disk is primary master; WXp is primary slave.
> W2K is first boot order
>
>
> --
> ObsidianRazor
>
>
> I was never able to boot from the WXP disk when I set it as the
> primary
> boot device. I tried figuring that out originally but never did, so
> I
> simply made the W2K disk the primary boot device and I received the
> boot.ini option to boot either OS and it's worked that way for
> almost
> a
> year. W2K disk is a WD400JB and the WXP is a WD1600JB. Each HD has
> a
> sinlge partition.
>
>
> --
> ObsidianRazor
>
>
> Progressing downhill. Latest attempts have resulted in the following
> message;
> Windows could not start because of an error in the software
> Please report this problem as :
> load needed DLLs for kernel.
>
> It looks as though I need to reload WXP and is there a way to do that
> without losing the disk data and having to reinstall all
> applications?
>
>
> --
> ObsidianRazor
>


I can boot W2K still, just getting a different error message when i
attempt to start the WXP. I ran the Western Digital diag on the HDD
and the quick test comes back clean. I'm at about the point where I'm
going to attempt a reload of XP on top of the existing file structure,
but normally I just reformat and load a clean version. This time
around I've got a lot of data (50G) and no place to easily transfer it
to. If I reload XP, will it preseve the 'my documents' directory?


--
ObsidianRazor

I can boot the W2K and am able to read & open files on
the WXP disk.

This time around I've got a lot of data (50G) and no place to easily
transfer it to.

you don't have that much space on W2K HDD?


Have you ever tried to change BIOS boot order and boot to Win XP HDD as
first boot device and see if that HDD boot.ini file works?


"ObsidianRazor" wrote:

>
> Dixonian69 Wrote:
> > restore you boot.ini file to original.
> >
> > it won't boot into Win 2k now?
> >
> > are you worried about data in win 2k or win xp?
> >
> >
> > "ObsidianRazor" wrote:
> >
> >
> > Dixonian69 Wrote:
> > It worked for almost a year?
> > so what has changed anything?
> >
> > change first boot.ini file to this:
> > Note: I changed the rdisk ( ) value from "0" to "1", in the
> > default
> > and
> > operating sysfor th win xp entries.
> > [boot loader]
> > timeout=30
> > default=signature(292a91c)disk(0)rdisk(1)partition (1)\WINDOWS
> > [operating systems]
> > signature(292a91c)disk(0)rdisk(1)partition(1)\WIND OWS="Microsoft
> > Windows XP Professional" /fastdetect
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> > Professional" /fastdetect /NoExecute=OptIn
> >
> > If this doesn't work, there must be something wrong with the slave
> > HDD.
> >
> > run hardware diagnostics on the drive.
> >
> > "ObsidianRazor" wrote:
> >
> >
> > Dixonian69 Wrote:
> > is there only one partition on primary slave?
> > what kind of a drive is it?
> >
> > this is unusaul description and doesn't match the second boot.ini
> > file!!
> > signature(292a91c)
> >
> > if you change boot order, so that primary slave is set as first
> > boot,
> > Can
> > you boot to Win XP?
> >
> >
> > "ObsidianRazor" wrote:
> >
> >
> > Dixonian69 Wrote:
> > Physically in you computer which HDD contains win 2k?
> > Is the win 2k HDD set as primary master?
> >
> > Is win 2k HDD set as HD(0) is computer bios?
> > is win 2k ((HD(0)) set as first boot device in boot order?
> >
> > This is not normal boot.ini enrty!!
> > signature(292a91c)
> >
> > on your first boot.ini, change from:
> > [boot loader]
> > timeout=30
> > default=signature(292a91c)disk(0)rdisk(0)partition (1)\WINDOWS
> > [operating systems]
> > signature(292a91c)disk(0)rdisk(0)partition(1)\WIND OWS="Microsoft
> > Windows XP Professional" /fastdetect
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> > Professional" /fastdetect /NoExecute=OptIn
> >
> > change to:
> > [boot loader]
> > timeout=30
> > default=multi(0)disk(0)rdisk(1)partition(1)\WINDOW S
> > [operating systems]
> > multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Micro soft Windows XP
> > Professional" /fastdetect /NoExecute=OptIn
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> > Professional" /fastdetect /NoExecute=OptIn
> >
> > Leave boot order alone for now!!
> >
> > "ObsidianRazor" wrote:
> >
> >
> > Dixonian69 Wrote:
> > does it boot into either OS?
> >
> > "ObsidianRazor" wrote:
> >
> >
> > I run a dual OS boot from separate HD's. I installed W2K on first
> > disk
> > and installed WXP on the 2nd disk while running the W2K OS. The
> > following boot.ini are respective (W2K/WXP)
> >
> > [boot loader]
> > timeout=30
> > default=signature(292a91c)disk(0)rdisk(0)partition (1)\WINDOWS
> > [operating systems]
> > signature(292a91c)disk(0)rdisk(0)partition(1)\WIND OWS="Microsoft
> > Windows XP Professional" /fastdetect
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000
> > Professional" /fastdetect /NoExecute=OptIn
> >
> > [boot loader]
> > timeout=30
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP
> > Professional" /fastdetect /NoExecute=OptIn
> >
> > After a hard power cycle I am now getting the hal.dll corrupt or
> > missing and I have replaced the file on my XP disk. Same problem.
> >
> > Any ideas? TIA for all that respond.
> >
> > OR
> >
> >
> > --
> > ObsidianRazor
> >
> > I guess it would have made a little more sense to have provided that
> > tidbit of info. I can boot the W2K and am able to read & open files
> > on
> > the WXP disk. I used my WXP disk and booted from the CD ROM and
> > tried
> > the repair option, but it only brings up the c:/WINNT from the W2K
> > disk. I used the expand command to replace the WXP hal.dll and I
> > also
> > tried copying a duplicate of the file from the i386 directory,
> > neither
> > of which worked. I'm assuming it has something to do with the
> > boot.ini
> > but I'm not sure what it is since they look normal.
> >
> >
> > --
> > ObsidianRazor
> >
> >
> > I tried the replacement of the boot.ini you provided and when I
> > select
> > the XP option it just sits there with a blank screen. The W2K
> > portion
> > still works, so I reinstalled the origianl boot.ini and I'm back at
> > sqaure 1.
> >
> > W2K disk is primary master; WXp is primary slave.
> > W2K is first boot order
> >
> >
> > --
> > ObsidianRazor
> >
> >
> > I was never able to boot from the WXP disk when I set it as the
> > primary
> > boot device. I tried figuring that out originally but never did, so
> > I
> > simply made the W2K disk the primary boot device and I received the
> > boot.ini option to boot either OS and it's worked that way for
> > almost
> > a
> > year. W2K disk is a WD400JB and the WXP is a WD1600JB. Each HD has
> > a
> > sinlge partition.
> >
> >
> > --
> > ObsidianRazor
> >
> >
> > Progressing downhill. Latest attempts have resulted in the following
> > message;
> > Windows could not start because of an error in the software
> > Please report this problem as :
> > load needed DLLs for kernel.
> >
> > It looks as though I need to reload WXP and is there a way to do that
> > without losing the disk data and having to reinstall all
> > applications?
> >
> >
> > --
> > ObsidianRazor
> >
>
>
> I can boot W2K still, just getting a different error message when i
> attempt to start the WXP. I ran the Western Digital diag on the HDD
> and the quick test comes back clean. I'm at about the point where I'm
> going to attempt a reload of XP on top of the existing file structure,
> but normally I just reformat and load a clean version. This time
> around I've got a lot of data (50G) and no place to easily transfer it
> to. If I reload XP, will it preseve the 'my documents' directory?
>
>
> --
> ObsidianRazor
>