LinuxSA Mailing list archives
Index:
[thread]
[date]
[subject]
[author]
From: Handy <handy@techie.com>
To : linuxsa@linuxsa.org.au
Date: Thu, 10 Feb 2000 23:31:44 -0800
BIOS Upgrade?
This is a multi-part message in MIME format.
------=_NextPart_000_0079_01BF741E.FDB37260
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all,
This is my first post, but have been reading for ages.
Names Andrew and could probably be classified as an 'experienced =
newbie'.
Im sorry my first post has to be relatively non-linux, but Im totally =
stumped 'ere.
Anyhoo, heres the question:
Scenario:
- for the first time ive built a box from scratch and intend for it to =
be a linux/windoze box
Problem
- when the HD (A 6.5 Gb samsung SV0682D) is paritioned from cylendar 0 =
to 1024 as a fat32 DOS/WIN partition, made bootable (sys a:\ c: or =
format c: /s), the drive does not boot from the BIOS system summary =
screen ... nor does it give *any* indication of the drive having an =
un-bootable volume/MBR etc
- BIOS detects the drive *perfectly* on auto, all wires are connected =
and it responds perfectly to commands, since i can boot a linux/windoze =
floppy and format it and write files to it etc
- The partition is active
What Ive Tried
- Jumpers in all positions on the HD (as usual that diagramatic sticker =
is orientationally non-descript)
- Formatting below the 1024 cylendar boundary
- Manually setting the drive specs in BIOS
- Making the drive 'bootable' using sys/format (which writes some form =
of MBR right?)
My Diagnosis
- BIOS Upgrade required
- Possibly the FAT32 as opposed to FAT16 ... although Im positive the =
BIOS doesnt care for things at such a high level
I was wondering if people would care to critique my diagnosis?
Ohh and how much would it cost for an upgrade? (Im prettey sure its not =
flashable) Im hoping not much since I cant afford to spend ANY more $$ =
on this box!
(BTW its a 02/06/96-i430FX-2A59CF3CC-00 motherboard (manufactured by =
Full-Yes Industries at www.fyi.com.tw which is down at the time of =
writing))
Thanx for tolerating me :)
AndrewH
------=_NextPart_000_0079_01BF741E.FDB37260
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This is my first post, but have been =
reading for=20
ages.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Names Andrew and could probably be =
classified as an=20
'experienced newbie'.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Im sorry my first post has to be =
relatively=20
non-linux, but Im totally stumped 'ere.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Anyhoo, heres the =
question:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Scenario:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- for the first time ive built a box =
from scratch=20
and intend for it to be a linux/windoze </FONT><FONT face=3DArial=20
size=3D2>box</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Problem</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- when the HD (A 6.5 Gb samsung =
SV0682D) is=20
paritioned from cylendar 0 to 1024 as </FONT><FONT face=3DArial =
size=3D2>a fat32=20
DOS/WIN partition, made bootable (sys a:\ c: or format c: /s), the drive =
does=20
not </FONT><FONT face=3DArial size=3D2>boot from the BIOS system summary =
screen ...=20
nor does it give *any* indication of the drive having an un-bootable =
volume/MBR=20
etc</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- BIOS detects the drive *perfectly* on =
auto, all=20
wires are connected and it responds perfectly to commands, since i can =
boot a=20
linux/windoze floppy and format it and write files to it =
etc</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- The partition is active</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>What Ive Tried</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- Jumpers in all positions on the HD =
(as usual that=20
diagramatic sticker is orientationally<FONT face=3DArial =
size=3D2></FONT>=20
non-descript)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- Formatting below the 1024 cylendar=20
boundary</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- Manually setting the drive specs in=20
BIOS</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- Making the drive 'bootable' using =
sys/format=20
(which writes some form of MBR right?)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>My Diagnosis</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- BIOS Upgrade required</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- Possibly the FAT32 as opposed to =
FAT16 ...=20
although Im positive the BIOS doesnt care for things at such a high =
level</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I was wondering if people would care to =
critique my=20
diagnosis?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Ohh and how much would it cost for an =
upgrade? (Im=20
prettey sure its not flashable) <FONT face=3DArial size=3D2>Im =
hoping not much=20
since I cant afford to spend ANY more $$ on this =
box!</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>(BTW its a 02/06/96-i430FX-2A59CF3CC-00 =
motherboard=20
(manufactured by Full-Yes Industries at <A=20
href=3D"http://www.fyi.com.tw">www.fyi.com.tw</A> which is down at the =
time of=20
writing))</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanx for tolerating me :)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>AndrewH</FONT></DIV>
<DIV> </DIV></FONT></DIV></BODY></HTML>
------=_NextPart_000_0079_01BF741E.FDB37260--
--
LinuxSA WWW: http://www.linuxsa.org.au/ IRC: #linuxsa on irc.linux.org.au
To unsubscribe from the LinuxSA list:
mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject
Index:
[thread]
[date]
[subject]
[author]
Return to the LinuxSA Mailing List Information Page