Re: SATA drive compatibility problem

Hello,

I have a dual boot system (eCS 1.2R/Windows 2000 SP4) with three
hard drives: 2 IDE and one SATA. The problem is that eCS is not
playing well with others. :(

Specifically, the 200GB SATA drive is being reported to the BIOS
and Windows 2000 as a ~65GB drive after I boot to eCS (using DANSI606)
and then reboot the system, either to the BIOS or to Windows. The
drive is correctly reported in both BIOS and Windows 2000 only after
a power on start up and prior to booting eCS. The motherboard is a
Gigabyte model and it has the NForce 3 chipset and SATA controller.

Any help resolving this will be greatly appreciated.

Thanks in advance,

Peter Brown wrote:
> Hi Bennie
> 
> Bennie Nelson wrote:
>> Hello,
>>
>> I have a dual boot system (eCS 1.2R/Windows 2000 SP4) with three
>> hard drives: 2 IDE and one SATA. The problem is that eCS is not
>> playing well with others. :(
>>
>> Specifically, the 200GB SATA drive is being reported to the BIOS
>> and Windows 2000 as a ~65GB drive after I boot to eCS (using DANSI606)
>> and then reboot the system, either to the BIOS or to Windows. The
>> drive is correctly reported in both BIOS and Windows 2000 only after
>> a power on start up and prior to booting eCS. The motherboard is a
>> Gigabyte model and it has the NForce 3 chipset and SATA controller.
>>
>> Any help resolving this will be greatly appreciated.
>>
>> Thanks in advance,
>> Bennie Nelson
> 
> 
> 
> Is the danis506.add current? - I think 182 is the current release.
> 
> Are there any BIOS updates available for the mainboard?
> 
> 
> Both of the above may have a bearing on the problem but if they do not 
> then I think you may need to ask someone with a bit more technical 
> knowledge - maybe Daniela herself.
> 
> Regards
> 
> Pete

I have not updated the DANIS506 driver in some time, so I
know it is not current. I'll give that a whirl.

Thanks for the response,

Hi Bennie

Bennie Nelson wrote:
> Hello,
> 
> I have a dual boot system (eCS 1.2R/Windows 2000 SP4) with three
> hard drives: 2 IDE and one SATA. The problem is that eCS is not
> playing well with others. :(
> 
> Specifically, the 200GB SATA drive is being reported to the BIOS
> and Windows 2000 as a ~65GB drive after I boot to eCS (using DANSI606)
> and then reboot the system, either to the BIOS or to Windows. The
> drive is correctly reported in both BIOS and Windows 2000 only after
> a power on start up and prior to booting eCS. The motherboard is a
> Gigabyte model and it has the NForce 3 chipset and SATA controller.
> 
> Any help resolving this will be greatly appreciated.
> 
> Thanks in advance,
> Bennie Nelson



Is the danis506.add current? - I think 182 is the current release.

Are there any BIOS updates available for the mainboard?


Both of the above may have a bearing on the problem but if they do not 
then I think you may need to ask someone with a bit more technical 
knowledge - maybe Daniela herself.

Regards

Hi Bennie,

> I have not updated the DANIS506 driver in some time, so I
> know it is not current. I'll give that a whirl.

That would be a good first move (IMHO)...

Also be aware that most motherboards will not check all H/W on a 
re-boot and so "inherit" issues on the restart, hence why a full
power
off/on is always a "safe" move. Some manufacturers have a "Cold 
Restart" option, that does a full H/W check and resets to BIOS startup
values so is probably the best way to go if the above does not work.

Good luck...................pk.


-- 

Peter wrote:
> Hi Bennie,
> 
>> I have not updated the DANIS506 driver in some time, so I
>> know it is not current. I'll give that a whirl.
> 
> That would be a good first move (IMHO)...
> 
> Also be aware that most motherboards will not check all H/W on a 
> re-boot and so "inherit" issues on the restart, hence why a full
power
> off/on is always a "safe" move. Some manufacturers have a
"Cold 
> Restart" option, that does a full H/W check and resets to BIOS
startup
> values so is probably the best way to go if the above does not work.
> 
> Good luck...................pk.
> 
> 

I was not aware of the "cold restart option." I'll
check into that, as well.

Thanks, again!