Not SATA Bias Issue - SOLVED
Not SATA Bias Issue - SOLVED
On the same computer, version 1.59 recognizes properly 4 SATA and 1 USB drive. However, versions 1.60 & 1.61 stop displaying a message about finding 5 SATA drives for SATA bias.
I've learnt later that it is not a SATA Bias issue. See my later posts.
EDIT:
Finally, I've found the root cause.
If you boot your system from a BootIT BM bootable CD including scripting, HD emulation will be used and the boot might be halted - if BootIT BM has been already installed. However, if you uninstall BootIT BM previously, you can boot from the BootIT BM setup CD without any problems.
I've learnt later that it is not a SATA Bias issue. See my later posts.
EDIT:
Finally, I've found the root cause.
If you boot your system from a BootIT BM bootable CD including scripting, HD emulation will be used and the boot might be halted - if BootIT BM has been already installed. However, if you uninstall BootIT BM previously, you can boot from the BootIT BM setup CD without any problems.
Last edited by SATA Bias on Sat Oct 10, 2020 2:30 pm, edited 5 times in total.
-
- Posts: 3654
- Joined: Thu May 05, 2011 10:37 pm
Re: SATA Bias Issue
Hello,
It's just reading a sector (maybe a few) on each drive during that. Try
a cold boot (unplug power). Ensure no card readers without media
causing delay.
On 12/4/2019 2:31 PM, SATA Bias wrote:
> On the same computer, version 1.59 recognizes properly 4 SATA and 1 USB drive. However, versions 1.60 & 1.61 stop displaying a message about finding 5 SATA drives for SATA bias.
>
>
It's just reading a sector (maybe a few) on each drive during that. Try
a cold boot (unplug power). Ensure no card readers without media
causing delay.
On 12/4/2019 2:31 PM, SATA Bias wrote:
> On the same computer, version 1.59 recognizes properly 4 SATA and 1 USB drive. However, versions 1.60 & 1.61 stop displaying a message about finding 5 SATA drives for SATA bias.
>
>
Re: SATA Bias Issue
Cold boot does not make difference and there is no card reader.
"Reading 5 BIOS hard drive(s) to gather data for SATA Bias option... Done"
The same happens with option BIOSMBRM=0, so the installer ignores it.
Please consider to check the difference in the source code between versions 1.59 and 1.60/1.61. There must be something, not intentionally, changed.
"Reading 5 BIOS hard drive(s) to gather data for SATA Bias option... Done"
The same happens with option BIOSMBRM=0, so the installer ignores it.
Please consider to check the difference in the source code between versions 1.59 and 1.60/1.61. There must be something, not intentionally, changed.
-
- Posts: 3654
- Joined: Thu May 05, 2011 10:37 pm
Re: SATA Bias Issue
Maybe it's your video settings since that is done prior to moving to the
GUI.
On 12/5/2019 4:14 AM, SATA Bias wrote:
> Cold boot does not make difference and there is no card reader.
> "Reading 5 BIOS hard drive(s) to gather data for SATA Bias option... Done"
> The same happens with option BIOSMBRM=0, so the installer ignores it.
> Please consider to check the difference in the source code between versions 1.59 and 1.60/1.61. There must be something, not intentionally, changed.
>
>
GUI.
On 12/5/2019 4:14 AM, SATA Bias wrote:
> Cold boot does not make difference and there is no card reader.
> "Reading 5 BIOS hard drive(s) to gather data for SATA Bias option... Done"
> The same happens with option BIOSMBRM=0, so the installer ignores it.
> Please consider to check the difference in the source code between versions 1.59 and 1.60/1.61. There must be something, not intentionally, changed.
>
>
Re: SATA Bias Issue
Maybe. BUT: How do you explain the different behavior of versions 1.59 and the newer ones - with the same video settings? Are you sure that the relevant source code has not changed? And why the BIOSMBRM=0 setting is ignored? Did you check it?
I could test these versions also on a PC with 3 SATA HDDs and no USB drive. Version 1.59 has been installed successfully, but the BIOSMBRM=0 setting was ignored. Version 1.61 went through the SATA Bias phase, but has stopped later with an error message: Causeway Error 09 , Unrecoverable internal exception, etc.
I hope this helps.
I could test these versions also on a PC with 3 SATA HDDs and no USB drive. Version 1.59 has been installed successfully, but the BIOSMBRM=0 setting was ignored. Version 1.61 went through the SATA Bias phase, but has stopped later with an error message: Causeway Error 09 , Unrecoverable internal exception, etc.
I hope this helps.
-
- Posts: 3654
- Joined: Thu May 05, 2011 10:37 pm
Re: SATA Bias Issue
Did you put it under the [OPTIONS] section
[OPTIONS]
BIOSMBRM=0
in BOOTITBM.INI in the same directory with the rest of the files?
Nothing changed in the startup area. Maybe download again clearing
cache and build to new media to ensure not corruption in the files.
On 12/5/2019 12:11 PM, SATA Bias wrote:
> Maybe. BUT: How do you explain the different behavior of versions 1.59 and the newer ones - with the same video settings? Are you sure that the relevant source code has not changed? And why the BIOSMBRM=0 setting is ignored? Did you check it?
>
> I could test these versions also on a PC with 3 SATA HDDs and no USB drive. Version 1.59 has been installed successfully, but the BIOSMBRM=0 setting was ignored. Version 1.61 went through the SATA Bias phase, but has stopped later with an error message: Causeway Error 09 , Unrecoverable internal exception, etc.
>
> I hope this helps.
>
>
[OPTIONS]
BIOSMBRM=0
in BOOTITBM.INI in the same directory with the rest of the files?
Nothing changed in the startup area. Maybe download again clearing
cache and build to new media to ensure not corruption in the files.
On 12/5/2019 12:11 PM, SATA Bias wrote:
> Maybe. BUT: How do you explain the different behavior of versions 1.59 and the newer ones - with the same video settings? Are you sure that the relevant source code has not changed? And why the BIOSMBRM=0 setting is ignored? Did you check it?
>
> I could test these versions also on a PC with 3 SATA HDDs and no USB drive. Version 1.59 has been installed successfully, but the BIOSMBRM=0 setting was ignored. Version 1.61 went through the SATA Bias phase, but has stopped later with an error message: Causeway Error 09 , Unrecoverable internal exception, etc.
>
> I hope this helps.
>
>
Re: Not SATA Bias Issue
I can share with you my (final) findings.
BootIt BM v1.61 setup CDs, prepared with makedisk.exe v1.6.8.2 and BOOTITBM.INI in the same folder, including:
- BootIt BM only OK
- BootIt BM + Image for DOS OK
- BootIt BM + Scripting OK
- BootIt BM + Image for DOS + Scripting It finds during SATA Bias one more SATA drives than there are in the reality and halts with a DOS Extender Causeway Error.
I could reproduce these results on two different PCs.
BootIt BM v1.61 setup CDs, prepared with makedisk.exe v1.6.8.2 and BOOTITBM.INI in the same folder, including:
- BootIt BM only OK
- BootIt BM + Image for DOS OK
- BootIt BM + Scripting OK
- BootIt BM + Image for DOS + Scripting It finds during SATA Bias one more SATA drives than there are in the reality and halts with a DOS Extender Causeway Error.
I could reproduce these results on two different PCs.
Re: Not SATA Bias Issue
Thanks for the information.
-
- Posts: 3654
- Joined: Thu May 05, 2011 10:37 pm
Re: Not SATA Bias Issue
It would have to do with the HD emulation, we'll check if issue with
overrun but pretty sure it uses device sector size for buffers (although
if it reports 512 but BIOS reads 2048, that could be an issue).
On 12/6/2019 2:32 PM, SATA Bias wrote:
> I can share with you my (final) findings.
> BootIt BM v1.61 setup CDs, prepared with makedisk.exe v1.6.8.2 and BOOTITBM.INI in the same folder, including:
> - BootIt BM only OK
> - BootIt BM + Image for DOS OK
> - BootIt BM + Scripting OK
> - BootIt BM + Image for DOS + Scripting It finds during SATA Bias one more SATA drives than there are in the reality and halts with a DOS Extender Causeway Error.
> I could reproduce these results on two different PCs.
>
>
overrun but pretty sure it uses device sector size for buffers (although
if it reports 512 but BIOS reads 2048, that could be an issue).
On 12/6/2019 2:32 PM, SATA Bias wrote:
> I can share with you my (final) findings.
> BootIt BM v1.61 setup CDs, prepared with makedisk.exe v1.6.8.2 and BOOTITBM.INI in the same folder, including:
> - BootIt BM only OK
> - BootIt BM + Image for DOS OK
> - BootIt BM + Scripting OK
> - BootIt BM + Image for DOS + Scripting It finds during SATA Bias one more SATA drives than there are in the reality and halts with a DOS Extender Causeway Error.
> I could reproduce these results on two different PCs.
>
>
Re: Not SATA Bias Issue
TeraByte Support wrote:
> It would have to do with the HD emulation, we'll check if issue with
> overrun but pretty sure it uses device sector size for buffers (although
> if it reports 512 but BIOS reads 2048, that could be an issue).
>
> On 12/6/2019 2:32 PM, SATA Bias wrote:
> > I can share with you my (final) findings.
> > BootIt BM v1.61 setup CDs, prepared with makedisk.exe v1.6.8.2 and
> BOOTITBM.INI in the same folder, including:
> > - BootIt BM only OK
> > - BootIt BM + Image for DOS OK
> > - BootIt BM + Scripting OK
> > - BootIt BM + Image for DOS + Scripting It finds during SATA Bias one
> more SATA drives than there are in the reality and halts with a DOS
> Extender Causeway Error.
> > I could reproduce these results on two different PCs.
> >
> >
Version 1.62 did not solve this issue.
> It would have to do with the HD emulation, we'll check if issue with
> overrun but pretty sure it uses device sector size for buffers (although
> if it reports 512 but BIOS reads 2048, that could be an issue).
>
> On 12/6/2019 2:32 PM, SATA Bias wrote:
> > I can share with you my (final) findings.
> > BootIt BM v1.61 setup CDs, prepared with makedisk.exe v1.6.8.2 and
> BOOTITBM.INI in the same folder, including:
> > - BootIt BM only OK
> > - BootIt BM + Image for DOS OK
> > - BootIt BM + Scripting OK
> > - BootIt BM + Image for DOS + Scripting It finds during SATA Bias one
> more SATA drives than there are in the reality and halts with a DOS
> Extender Causeway Error.
> > I could reproduce these results on two different PCs.
> >
> >
Version 1.62 did not solve this issue.