1590 Tyan partition large HD FAT32X VIA MVP3
Phil Lee
using MBs having VIA MVP3 chipsets, such as Tyan S1590 Trinity, FIC VA-503+,
PA-2013, EPoX 58MVP3C-M, AOpen AX59-Pro, and Shuttle HOT-591P? The VIA
chipset was released in Jan 98.
I have a Tyan S1590S Trinity Super7 MB and Award (Phoenix) BIOS 4.51PG. Was
not able to install a partition utility (Partition Cmdr v4.02) on a new HD
until BIOS was upgraded. I was able to solve conflict by updating flash BIOS
from OEM release v0.09 (5/28/98) to current v1.14 (10/20/98). My Tyan MB was
brought in Oct 98.
HD is a IBM Deskstar GP 8.4GB, DTTA-350840, with 1027 cyl, where the FAT32
limit is 1024. Thus IBM drive should show as a FAT32X.
Suspect that Tyan's old BIOS had issues in the Southbridge EIDE controller
in the VIA 586B rev CD chip, such as Int13 or EBIOS. A EIDE fix was not
mentioned in the release notes.
I think that reviews of motherboards need to include MB rev, chipset rev,
and BIOS rel rev and date. I have faced numerous situations which was solved
by exchanging of MB versions and updating BIOS.
Microsoft has PC97 Certified the following VIA MVP3 MBs as Hardware
Compatible for Win95/8/NT, a Shuttle HOT-591P with BIOS dated 6/18/98
(current 11/10/98).
------
What is your experience using Win95B/98 OS FDISK? How about using the very
new versions of 3rd party utilities, such as PQ Partition Magic v4.0 (9/98),
V-Comm System (Partition) Commander Deluxe v4.02 (9/29/98)? Shareware
partitioning Bootit Lite?
I found that Partition Cmdr v4.02 cannot chg a FAT32 back to a FAT16.
Any particular issues when having multiple boot with Win 3.11, 95, 95B, 98,
NT4, Novell, Linux in a partition?
Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
Tom Pfeifer
supporting the Int13 extensions is required in order to have FAT32X to
begin with. A FAT32X partition is the same as FAT32 except that some or
all of it exists beyond the 1024th cylinder. The Int 13 extensions are
needed to access or partition any portion of the disk beyond that 1024th
cylinder. With LBA translation enabled in the BIOS, 1024 cylinders =
about 8.4GB (7.8GB binary)
I have been using PM 4.0 for a few months. There are a few minor
problems, but generally it works fine, including on large drives. I
haven't tried the others you mention.
> Any particular issues when having multiple boot with Win 3.11, 95, 95B, 98,
> NT4, Novell, Linux in a partition?
I would never even try to get all of those in one partition, but aside
from original 95 and Novell, I have all of them installed and running on
my machine right now. Each is installed on it's own partition.
Tom
Phil Lee
=====
Tom Pfeifer wrote in message <3698F921...@snet.net>...
Charles Kaucher
http://www.storage.ibm.com/hardsoft/diskdrdl/prod/14gx16gppr.htm
The Trinity Bios is the latest available 10/28/98. The HD is recognized
as
1229 cylinders 255 heads and 63 sectors for 10110M of space in LBA
mode.
When I boot to win95b or win98 and try to Fdisk I get an error "reading
disk." I have been able to install LINUX on this system several times
and have had IBM on the phone running several diagnostics. The
conclusion is it is not the hard drive.
I am told that Fdisk in LINUX doesnot use the bios but Windows fdisk
does.
Since LINUX works must be the board?
Need help. Don't know anything about fat32x.
Charles Kaucher
"W. Dean Milner" wrote:
>
> x-no-archive: yes
>
> "Phil Lee" <pl...@orbis.net> wrote:
> >Hi, has anyone else experienced FAT32X issues when partitioning large HDs
> >using MBs having VIA MVP3 chipsets, such as Tyan S1590 Trinity, FIC VA-503+,
> >PA-2013, EPoX 58MVP3C-M, AOpen AX59-Pro, and Shuttle HOT-591P? The VIA
> >chipset was released in Jan 98.
>
> It would appear to be either a chipset or BIOS issue (or possibly
> both). My cousin had trouble moving a large drive with a large
> extended partition to a Via based A-Trend MB. Not sure if he has
> solved it yet though.
>
> Dean
>
> Note: remove the (.ns) from the user id before emailing.
Phil Lee
Win95B compatibility with a legacy FIC PA-2006 which has a VIA VP1 chip set.
The VP1 Southbridge/EIDE controller is the 586 chip. The Tyan S1590S Trinity
uses the newer MVP3 chipset, the 586B ver CD chip. Since the VP chipset is
Int13 / EBIOS compatible, then the fault lies with Tyan R&D.
Tyan needs to fix the "Core" BIOS so that the Trinity can fully utilize
large drives, including 3rd party and Win95B partitioning.
So Gilb...@tyan.com , is this issue being worked on and when can we expect
a fix?
Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
======
Charles Kaucher wrote in message <369A1C6F...@mediaone.net>...
Howard W Wortley
I have a Tyan Titan Turbo S1573S and recently - last weekend - wanted to
install a 10.1 Gbyte IBM Deskstar. As I expected the BIOS only detected it
as 8.4 Gbyte. Downloaded EZDRIVE (free) from www.ibm.com\harddrive and
installed it. Works like a charm with WIn98. NAV and scandisk all work fine.
They also have NT and OS2 support. Not keen on upgrading the BIOS sorta
risky in my experience.
Hope this helps
Howard
Phil Lee <pl...@orbis.net> wrote in message news:77ag4t$o2s$1...@remarQ.com...
>Hi, has anyone else experienced FAT32X issues when partitioning large HDs
>using MBs having VIA MVP3 chipsets, such as Tyan S1590 Trinity, FIC
VA-503+,
>PA-2013, EPoX 58MVP3C-M, AOpen AX59-Pro, and Shuttle HOT-591P? The VIA
>chipset was released in Jan 98.
>
Phil Lee
I am assuming that the BIOS config did not show the correct cyl,hd,sec in
LBA mode. This is surprising as MS, Intel, and IBM work together closely.
Have a heart, flashing the BIOS chip is not hard, and the warnings seem too
threatening. I have not blown the process in over 10 trials on different
BIOS and MB mkrs. Just follow the straight-forward directions closely. Do
one once, it is all the same.
Did you partition the HD as one or two FAT32s or are they multiple 2GB FAT16
partitions? I am surprised that you would have FAT32X issues with Win98 on
it. I am well aware with the IBM (On Track) EZdrive utility which adds a
XBIOS overlay file. This corrects deficient EBIOS issues. I have used it on
legacy 386/486 BIOSs or EIDE controllers with XBIOS built-in!
I have found that this solution is problematic in backup/restore and
multi-boot, multi-OS bootdrives. Hard to use PQ DriveCopy and DriveImage
utilities.
Thanks for your workaround though. I just wish Tyan and/or VIA would find a
big stick and solve this problem the right way.
Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
======
Howard W Wortley wrote in message
<#EN2orYP#GA....@uppssnewspub05.moswest.msn.net>...
Tom
Maxtor 11.5gb.
Regards.
Phil Lee
have?
Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
======
Tom wrote in message <369A62...@erols.com>...
Tom
Currently my 11.5GB Maxtor (primary master) has OS/2 Warp 4 (HPFS),
Windows NT 4.0 (NTFS), and Windows98 (FAT32) as primary partitions, plus
an extended partion containing two logical partions (both FAT32). My
primary slave is a Creative Encore DVD drive. My secondary master (a WD
2.0GB) has one primary and one extended partition (with one logical
partition inside.) My secondary slave (Maxtor 5.0GB) has a Linux swap
(primary), a primary Linux ext2 partition (RedHat 5.2), and a primary
FAT32 partition. I use BootMagic to boot OS/2, WinNT, Win98, or Linux
RedHat 5.2. Everything is very stable.
Carsten Geutebrück
>
> I have a Trinity 1590s with a IBM 14GXP DTTA 371010 had drive.
> recognized as 1229 cylinders 255 heads and 63 sectors for 10110M
> of space in LBA mode.
> When I boot to win95b or win98 and try to Fdisk I get an error
> "reading disk."
I have the same (1590S & DTTA 371010) configuration and had
no problems. After selfdetection harddrive it appears like yours
and then I used fdisk with FAT32 enabled !!! from a Win98 boot
disk and made 2 partitions,
one 2GB for windows and system and 8GB for progs and data.
My BIOS settings are: autodetect UDMA, IDE prefetch enabled etc.
Did you used fdisk with enabled FAT32 ??? It's recommended
for bigger harddrives than 2GB and for smaller clustersizes.
Bye,
Carsten
--
All about 3D compatibility
http://home.t-online.de/home/ce-ge
Phil Lee
BIOS and rev, date?
Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
======
Tom wrote in message <369A9D...@erols.com>...
Charles Kaucher
My experience has confirmed your response. I was able to get win95 to
install except when it came to rebooting. The drive failed to be
recognized or rather the board failed to recognize the hard drive. I
went into the BIOS and "user defined" the HD and that seem to work for
awhile. This morning, it didn't seem to matter what I used ---auto or
user --- it still was quite a trick to get it recognized. The most
reliable method seemed to be turn the machine off entirely.
Does this issue also exist with the 1592s?
To others, There should be no need to use disk manager software with
this board. IT also prohibits a dual boot system to LINUX.
Chuck Kaucher
Phil Lee wrote:
>
> Hi Charles, IBM's HD Compatibility KB shows that the Deskstar GP 10GB has
> Win95B compatibility with a legacy FIC PA-2006 which has a VIA VP1 chip set.
> The VP1 Southbridge/EIDE controller is the 586 chip. The Tyan S1590S Trinity
> uses the newer MVP3 chipset, the 586B ver CD chip. Since the VP chipset is
> Int13 / EBIOS compatible, then the fault lies with Tyan R&D.
>
> Tyan needs to fix the "Core" BIOS so that the Trinity can fully utilize
> large drives, including 3rd party and Win95B partitioning.
>
> So Gilb...@tyan.com , is this issue being worked on and when can we expect
> a fix?
>
> Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
>
> ======
> Charles Kaucher wrote in message <369A1C6F...@mediaone.net>...
> >I have a Trinity 1590s with a IBM 14GXP DTTA 371010 had drive.
> >
> >http://www.storage.ibm.com/hardsoft/diskdrdl/prod/14gx16gppr.htm
> >
> >The Trinity Bios is the latest available 10/28/98. The HD is recognized
> >as
> >1229 cylinders 255 heads and 63 sectors for 10110M of space in LBA
> >mode.
> >When I boot to win95b or win98 and try to Fdisk I get an error "reading
> >disk." I have been able to install LINUX on this system several times
> >and have had IBM on the phone running several diagnostics. The
> >conclusion is it is not the hard drive.
> >
> >I am told that Fdisk in LINUX doesnot use the bios but Windows fdisk
> >does.
> >Since LINUX works must be the board?
> >
> >Need help. Don't know anything about fat32x.
> >
> >Charles Kaucher
> >
> >
> >"W. Dean Milner" wrote:
> >>
> >> x-no-archive: yes
> >>
> >> "Phil Lee" <pl...@orbis.net> wrote:
> >> >Hi, has anyone else experienced FAT32X issues when partitioning large
> HDs
> >> >using MBs having VIA MVP3 chipsets, such as Tyan S1590 Trinity, FIC
> VA-503+,
> >> >PA-2013, EPoX 58MVP3C-M, AOpen AX59-Pro, and Shuttle HOT-591P? The VIA
> >> >chipset was released in Jan 98.
> >>
Phil Lee
You are finding that you can't reboot a large IBM HD on a Tyan 1590 (1592
VP3, v1.10) with the latest BIOS rev v1.14, once it has been Win95B/8
Fdisked as a single 10GB FAT32X partition?
If this is so, this confirms my HD hanging when attempting to single
partition an IBM into a FAT32X. Only I used a partitioning utility, V-Comm
System (Partition) Commander v4.02
Conclusion: Tyan's 1590 BIOS v1.14 has issues with FAT32X partitions on
large HDs.
This opinion has been echoed by Bryan Smith b.j....@ieee.org in a private
email, using Win95B/8/Linux Fdisk and PQ PM4 (best results), VComm, QD. He
says that "... most BIOSes were created before a 'standard' was finally set
[by whom, MS?] on how to use LBA to break the 1024 cylinder barrier." He
uses ABit BH6 P2 boards which have the Intel BX chipset. He gets
"disappearing" FAT32X drives too. Sounds like FAT32X is a fundamental OS vs
BIOS issue.
Workaround: Use Win95B/8/NT4/Linux Fdisk, or Partition Magic 4, to partition
a large HD into FAT32s less than 8GB. Gulp...
Fix: Gilb...@tyan.com this issue has been replicated by others. Can we
expect a fix ASAP? Hey, I've been also hit by defective SRAM, a widespread
return issue, on Tomcat IV S1564S about 1 1/2 years ago. Are we playing
baseball?
Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
======
Charles Kaucher wrote in message <369B6CBA...@mediaone.net>...
Phil Lee
11GB HD with no problems, you are failing to grasp the most important
factor. It appears that you are partitioning your HDs into FAT32 partitions,
not FAT32X (greater than 8GB EACH). Your successful use of PQ Partition
Magic 4 and Boot Magic is incidental.
I am well aware of the workaround, use FAT32 partitions less than 8GB. The
real issue is how to efficiently use the 16GB and larger HDs. A Tyan BIOS
fix is still required ASAP.
Lets not continue to spread dis-information.
Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
======
Phil Lee wrote in message <77fpgb$oeb$1...@remarQ.com>...
Tom
saw it ok. I just prefer partitioning as its easier to do backups.
Charles Kaucher
Phil Lee wrote:
>
> Hi Charles, let me confirm, as there are many posts to this thread.
>
> You are finding that you can't reboot a large IBM HD on a Tyan 1590 (1592
> VP3, v1.10) with the latest BIOS rev v1.14, once it has been Win95B/8
> Fdisked as a single 10GB FAT32X partition?
Actually I have only 3 gig of formatted with win95b fdisk although I
have tried to fully partition it as one of my many attempts to load
win95 and win98. I am planning to use the remainder for LINUX. Other
than that I can confirm the above. Im addition, I can say that I must
turn off the machine and not just soft boot to get it to recognize. It
takes three or four boots sometimes. So far the best method is to wait
a few minutes, get some coffee and then turn it on. Make sure you cream
in the coffee. :<)
> If this is so, this confirms my HD hanging when attempting to single
> partition an IBM into a FAT32X. Only I used a partitioning utility, V-Comm
> System (Partition) Commander v4.02
> Conclusion: Tyan's 1590 BIOS v1.14 has issues with FAT32X partitions on
> large HDs.
This is where I am headed.
So why did this machine run flawlessly with LINUX Redhat 5.2 for months?
I am told why this doesnot affect LINUX is because LINUX is very
efficient in managing the hardware and doesn't use the Bios on Boot to
grab the HD info.
<snip>
> Workaround: Use Win95B/8/NT4/Linux Fdisk, or Partition Magic 4, to partition
> a large HD into FAT32s less than 8GB. Gulp...
This really isn't a solution. THe problem is detecting the HD not
reading it. Obviously, if you can't see it you can't read it.
> Fix: Gilb...@tyan.com this issue has been replicated by others. Can we
> expect a fix ASAP? Hey, I've been also hit by defective SRAM, a widespread
> return issue, on Tomcat IV S1564S about 1 1/2 years ago. Are we playing
> baseball?
>
> Phil, Sys Engr, Minneapolis, Silicon Tundra, pl...@orbis.net
See cc above to Gilbert
Chuck Kaucher
spelling and grammar exta