Anne Wilson wrote:
On Sunday 09 Mar 2003 1:18 pm, g wrote:
Anne Wilson wrote:
On Sunday 09 Mar 2003 11:59 am, Joerg Mertin wrote:
this is actually a BIOS remapping, telling the System to change the
Now I'm really confused.

just a new play on old term 'faking it'.

hthth.

but it did not. :P



g - I've been away a couple of days, so I'm just picking this up.

If windows is on hde1, and hde has been mapped to appear to be hdb, then windows will not boot. Correct?

incorrect.


}}-> understand a miss understanding, up to and including w98se,
}}-> ms os boots active drive and designates it as 'c:\'. es.

1st, go back and re read your lilo.conf.
2nd, re read my last.

lilo maps drives from ata100 controller to _bios_ position 0x81, 0x82.
this is not a 'physical', but a 'bios software' position.

at label 'other', bios positions are changed to move 'hde1', now '0x81',
to bios '0x80' and bios '0x80' becomes '0x81'.

this is all done in bios memory, where a byte of data can be a binary
'command', or, a binary 'switch', or, a 'pointer'. regardless of what
it is, it is located in an assigned place for a specific reason. if
you looked at these bytes as they 'may be' in bios they would look
on an order of;

 normal
 value assignment
 0x80  /dev/hda
 0x81  /dev/hdb
 0x82  /dev/hdc
 0x83  /dev/hdd

 0x88  /dev/hde  [ 0x88 - 0x8b are example ]
 0x89  /dev/hdf  [ have yet to see hw byte table ]
 0x8a  /dev/hdg
 0x8b  /dev/hdh

 1st re mapped
 0x80  /dev/hda
 0x88  /dev/hdb
 0x89  /dev/hdc
 0x83  /dev/hdd

 0x81  /dev/hde
 0x82  /dev/hdf
 0x8a  /dev/hdg
 0x8b  /dev/hdh

 2nd re mapped
 0x88  /dev/hda
 0x80  /dev/hdb
 0x89  /dev/hdc
 0x83  /dev/hdd

 0x81  /dev/hde
 0x82  /dev/hdf
 0x8a  /dev/hdg
 0x8b  /dev/hdh

now that you are more confused, grasp this;

in control of hardware, bytes are bits, and bits are switches.
a byte can turn on or off any single device, by bit position.

in assigning devices, 2 bytes used,
  msb is device type or group.
  lsb is device in type or group.

as i believe i mentioned else where,
  ata66 to ata66, ata100 to ata100.

you will need to change lilo.conf and fstab.

but it may end up less of a confusion. ;)

Does this mean that I should comment out the second mapping and try it?

no. try what i just suggested, again. <<bwg>>


that is, unless it works as it is and you are trying to understand
why your lilo has drive reassignment and how it is done.


peace out.


tc,hago.

g
.
=+=
think green...
  save a tree, save a life, save time, save bandwidth, save storage.
  send email:  text/plain - disable pgp/gpg/geek code attachments.
=+=
 if you are proud to be an american, then buy "made in america".
=+=



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to