On Thu, 6 Jun 2013, Bob Proulx wrote:
BIOS bugs.
A BIOS bug is surely involved, but that's not enough to explain the facts:
After 4 years without any problem, a BIOS setting suddently changes, the
BIOS being the same since the beginning (no BIOS update)
For any software, a bug needs a
Pierre Frenkiel wrote:
> Bob Proulx wrote:
> >You are correct. The BIOS has an ordering. The OS has an ordering.
> >They are separate software and will each do their own thing. I have
> >often had problems with the BIOS disk ordering being different form
> >the OS disk ordering.
>
> my concer
On Wed, 5 Jun 2013, Bob Proulx wrote:
You are correct. The BIOS has an ordering. The OS has an ordering.
They are separate software and will each do their own thing. I have
often had problems with the BIOS disk ordering being different form
the OS disk ordering.
my concern is not disk ord
Pierre Frenkiel wrote:
> the problem was with the BIOS boot sequence, and as far as I know,
> this is totally independant of any OS.
You are correct. The BIOS has an ordering. The OS has an ordering.
They are separate software and will each do their own thing. I have
often had problems with
On Ma, 04 iun 13, 16:39:05, Pierre Frenkiel wrote:
>
> sorry, but I think that you didn't understand: my BIOS perfectly detects all
> existing drives, as
> 1/ they are all listed in the BIOS "general" and "hard disc" menus
> 2/ I was able to put the good one in the boot sequence.
The BIO
hi Dan,
On Tue, 4 Jun 2013, Dan Ritter wrote:
BIOS settings are all too often corrupted. I have two Intel
motherboards that need BIOS re-checked any time they have an
unexpected power outage.
that can't be my case, as I have an UPS, and no power failure long
enough to exhaust the UPS batter
On Tue, 04 Jun 2013 22:39:05 +0800, Pierre Frenkiel
wrote:
On Tue, 4 Jun 2013, Goh Lip wrote:
Okay, understood what you mean.
Your bios did not detect both drives and the first drive it detected
was put into the boot sequence.
sorry, but I think that you didn't understand: my BIOS p
On Tue, 4 Jun 2013, Goh Lip wrote:
Okay, understood what you mean.
Your bios did not detect both drives and the first drive it detected was put
into the boot sequence.
sorry, but I think that you didn't understand: my BIOS perfectly detects all
existing drives, as
1/ they are all list
On Tue, 04 Jun 2013 17:09:15 +0800, Pierre Frenkiel
wrote:
On Tue, 4 Jun 2013, Goh Lip wrote:
The allocation of disk numbering (sda, sdb...or (hd0, hd1...) is done
by bios and the OS will use whatever the bios determine.
Also this numbering is not consistent with each reboot.
We should
On Tue, 4 Jun 2013, Goh Lip wrote:
The allocation of disk numbering (sda, sdb...or (hd0, hd1...) is done by bios
and the OS will use whatever the bios determine.
Also this numbering is not consistent with each reboot.
We should always set "master" and "slave" for jumper wires or use correct
On 06/04/2013 02:29 PM, Pierre Frenkiel wrote:
On Mon, 4 Jun 2013, Pierre Frenkiel wrote:
After a problem with a ligthscribe dvd, I had to reboot my PC,
. . .
At last I found the explanation, which seems rather incredible:
In my BIOS settings, the boot sequence has been modified,
the 1
On Mon, 4 Jun 2013, Pierre Frenkiel wrote:
After a problem with a ligthscribe dvd, I had to reboot my PC,
. . .
At last I found the explanation, which seems rather incredible:
In my BIOS settings, the boot sequence has been modified,
the 1st internal disc (ST3250410AS) being replaced by th
12 matches
Mail list logo
