On Thu, 26 Apr 2007 00:42:32 -0700, GHalleck
<(E-Mail Removed)> wrote:
>
>Stan Hilliard wrote:
>
>> With XP-Pro: Whenever I perform an operation that requires Partition
>> Magic or True Image to reboot to run in DOS, the boot fails and I have
>> to go into BIOS and restore the proper hard disk boot priority before
>> the program can run.
>>
>> I have three volumes. The (incorrect,changed) boot order that I have
>> to fix in BIOS is:
>> 1 SCSI-1: ST3250823AS
>> 2 SCSI-0: ST3250823AS
>> 3 SCSI-2: 7Li_RAID
>> 4 Bootable add-in cards
>>
>> The volume with priority 3 is the only one with an active partition,
>> so I don't know why it is not first. What could be happening here?
>>
>> To make XP boot correctly, I have to change the order back to:
>> 1 SCSI-2: 7Li_RAID
>> 2 SCSI-1: ST3250823AS
>> 3 SCSI-0: ST3250823AS
>> 4 Bootable add-in cards
>>
>> The next time PM or TI tries to boot to DOS the order will revert back
>> again. When I boot with the Partition Magic recovery floppies while
>> the boot orders are wrong, the disk with (incorrect) boot priority 1
>> is called drive 1. PM must assign its disk numbers from the boot
>> order.
>>
>> Here are some more facts: Referring to the correct (second) boot order
>> list:
>>
>> Priority 1: both drives in the RAID 0 array are cabled to the
>> motherboard.
>>
>> Priority 2 & 3: both are cabled to a PPA 1301 2-port SATA card.
>> Neither drive contains a primary partition, so I don't know why they
>> are on the list. I will later add another disk drive to (2), making it
>> a second RAID 0.
>>
>> Priority 4: I don't know what the bootable card is but I would assume
>> it is the SATA card.
>
>
>When referring to DOS, is it being made to a specific version of
>DOS, e.g., MS-DOS, PC-DOS, Culebra DOS, etc.? Second, are SCSI
>drivers, RAID drivers, etc., native to the version of DOS that is
>being called up or do they have to be loaded separately, like in
>the days of old via an autoexec.bat file and a config.sys file?
>The re-ordering of the boot sequence just might be a consequence
>of how the DOS app interprets of the system bios and re-assigns
>priorities accordingly. It should be possible to get this sorted
>with more pertinent information.
The Command.com in the Partition Magic folder and on the recovery disk
contains Caldera DR-DOS 7.02. Here is the autoexec.bat of the recovery
disk.
AUTOEXEC.BAT =================================
@ECHO Off
PROMPT $P$G
REM -------------------------------------------------------
REM -- DO NOT EDIT THIS FILE! IF YOU WISH TO ADD NETWORK --
REM -- OR CD-ROM DRIVERS, CUSTOM KEYBOARDS, ETC., PLEASE --
REM -- EDIT AUTOEXE2.BAT INSTEAD. --
REM -------------------------------------------------------
IF EXIST AUTOEXE2.BAT CALL AUTOEXE2.BAT
ECHO.
ECHO Please Insert PartitionMagic Disk 2
ECHO.
ECHO.
ECHO *** Press Any Key to Continue ***
ECHO.
PAUSE >NUL
ECHO Norton PartitionMagic 8.0
ECHO Copyright 1994-2004, Symantec Corporation
ECHO All rights reserved.
ECHO.
ECHO Loading. Please wait...
ECHO.
PQMAGIC
AUTOEXE2.BAT =================================
REM -------------------------------------------------------
REM -- Put keyboard codes (xx) and --
REM -- code page variables (yyy) here. --
REM -------------------------------------------------------
REM MODE CON CP PREP=((yyy) EGA.CPI)
REM MODE CON CP SEL=yyy
REM KEYB xx,yyy
REM -------------------------------------------------------
REM -- Put network or CD-ROM drivers here. --
REM -------------------------------------------------------
REM Windows DOS:
REM MSCDEX.EXE /D:driver_name [/L:drive_letter] [/M:buffers]
REM Caldera DOS:
REM NWCDEX.EXE /D:driver_name [/L:drive_letter] [/M:buffers]
============================================= end
When I first setup the hardware I installed from CD a ULi M5289 SATA
controller driver.
I would have thought that the BIOS settings would not be messed with
by the particular software operating system.
Any advice?
Stan Hilliard
|
Similar Threads
