Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: Eagler on March 25, 2002, 03:38:44 PM
-
I have one of these MB's on order with an AMD XP 2000 cpu & two sticks of Crucial PC2100 256MB ram. This will go with a geforce4 ti4400 I bought local last week.
The board is raid ready.
Question is:
Would I get better performance with a single western digital 100 gig 7200 ATA100 drive or strip raid two 80 gig Maxtors. These are ATA100 also but are only 5400 speed. Can I dual boot win98 and XP off raid drives?
Never setup a raid before.
tia for any tips or suggestions
-
Good question there Eagler. I have a 7200rpm 80gig Maxtor ATA-133 running along side an older IBM 13.3gig 7200rpm drive. I have the Maxtor on an ATA-133 card running as my back up drive at the moment. Soon it will be primary and this 13.3 will go into my little boy's computer.
-
I have the same motherboard, and use two Maxtor 40-Gig, 7200 RPM drives in a RAID-0 configuration. I also set it up as a dual-boot system with WinXP and Win98 SE. Setting up the RAID array is simple, just read the MB's user's guide and activate the appropriate set-up menu (using control-f, I think) during the boot sequence. Setting up the dual-boot configuration is also painless; just use Fdisk (or a comparable program) to set up multiple partitions on your disk (or disks, in the case of a RAID array), and install Win98SE first. I set up my WinXP partition as an NTFS file system, which has some advantages (e.g., encryption) over a FAT-32 system. If I had to do it over again, however, I think I would make both partitions FAT-32 so that I could freely transfer files back and forth. As it is, my WinXP installation can access files in my Win98SE directory structure, but not vice-versa.
Using the RAID chipset on your motherboard, you can configure two identical drives as a RAID-0 array or as a RAID-1 array. A RAID-0 array offers a performance advantage (over either of the drives configured as a stand-alone drive) because of the way that it stores data in alternating "stripes" on the two drives. I canont quantify the advantage a RAID-0 array of two 5400 rpm drives would have over a single 7200 rpm drive, but I don't expect that it would be extreme. Moreover, a RAID-0 connection of two n-byte drives yields an array of size 2n bytes (e.g., your two 80 GB drives would form a 160 GB RAID-0 array). A RAID-1 array offers no performance advantage, and a RAID-1 array of two n-byte drives yields an array of size n bytes (e.g., your two 80 GB drives would form an 80 GB RAID-0 array). The advantage of a RAID-1 array is that it uses data redundancy so that the failure of either of the two drives should be (I have not used a RAID-1 array) recoverable.
From my experience with RAID-0 arrays on two different motherboards, there are (at least) three problems or potential problems of which you should be aware before going down this road. You'll have to decide whether those problems are worth the modest performance gain.
First (and this applies to either RAID configuration), you will not be able to unplug your two RAID drives and connect them to another motherboard (unless it uses the same or a compatible RAID controller) if you decide to build a new PC, upgrade, tranesfer data, etc. If you use a single, EIDE drive, you will have much greater flexibility in that regard.
Second, RAID-0--the only configuration that gives you increased performance--offers no increased protection against drive failure. To the contrary, if you use RAID-0, if either of the two drives fails, you are likely in an unrecoverable situation (i.e., the probability of an unrecoverable failure is GREATER for a RAID-0 configuration than it is for a single drive). A RAID-1 configuration uses data redundancy, so that if one drive fails, you should be able to recover. I've never tried this on a PC with two drives, so I don't know how well it works. RAID-1, however, provides no performance advantage and your two 80 GB drives would yeild only 80 GB of storage.
Third, it is a bit of a hassle getting the operating system installation programs to recognize the RAID array, which you set up (define the array, its partitions, and format) prior to installing the operating system. If I recall correctly, use must use a utility on the ASUS driver CD-ROM to create a floppy disk containing the RAID drivers. The WinXP set-up routine will prompt you for this disk during installation. It is no big deal, really, but if you don't have a working PC on hand on with which to make the required floppy, it can be frustrating.
If I were in your situation, I would create a dual-boot system, placing the Win98SE installation on one of the 80-GB drives and placing the WinXP installation on the 100-GB drive. Even though I have a dual-boot system, I almost never use Win98SE, so placing it on the 5400 RPM drive would be no big deal. In particular, I play AH under WinXP, and find the performance to be as good, if not better, as under Win98SE.
(If, by chance, your reason for installing Win98SE is to use a Saitek X-36 or X-45 rig, you can use it under WinXP with drivers available from http://saitekhelp.simhq.com. Those drivers are, in my opinion, superior to Saitek's SGE solution under Win98SE.)
Hope that helps.
- JNOV
-
LoneStarBuckeye
thanks for the info
gonna stay away from raid at this point and go with separate drives on separate ide controllers, as you stated above.
with the XP drivers for your Saitek, can you get the rotors to band?
thanks again
-
No, unfortunately, the rotors are not supported at all.
- JNOV
-
Although it looks like the question's already been answered, I'd go with the single 7200 rpm drive. Performance ought to be about the same as the raid array, but reliability would be far better with just one drive.
I'm not completely familiar with your situation, but if I had those drives I'd do the following: Split the 7200 rpm drive into 2 partitions. If you are doing a dual boot, install WinXP on the first partition, put win98se on the second partition. Format the 5400 rpm drives as FAT32 and use them as storage for things like MP3s and downloads etc. Keep the 7200 rpm drive for programs and system files only. That is what I would do, given your situation as I understand it.
-
thanks bloom for your input
I was thinking along those lines. I need to format the WinXP partitation as ntsf to get around the 4gig limit for my digital video experiments. If the storage drive(s) are fat32, wouldn't that limit back to 4gig on file size? Can I partitation the 80gig into two drives for storage, one being fat32 and the other being ntsf?
Would I gain anyhting by putting each IDE device on its own IDE controller? Going ATA100 on the raid ports, the board gives me up to eight ide devices - two per port. I was thinking to put the 100gig 7200 WD on the ide0, a 80gig on ide1, the plextor burner on ide3 and the cd rom player on ide4. All with their own cable and without having to share the ide port. Or would the two 80's on ide1, one formatted for fat32 and the other for ntsf be the way to go?
-
Personally, I would not use the NTFS filesystem. While it has some advantages over FAT32, it also comes with the possibility of a hard crash.
It is possible for the NTFS filesystem to get damaged in a system crash to the point it cannot recover. With a FAT32 filesystem in the same scenario, you end up losing a file or two.
FAT32 does not suffer from the 4GB limitation. I have 2 partitions of 20GB each with FAT32 on both. One is 98SE and the other is W2K.
In this configuration you can copy files back and forth without regard to which OS is booted.
blooms configuration suggestion is a good one when you have 2 drives to dink with.
-
Skuzzy thanks for your input
what I ran into with the fat32 was a digital video file would not capture past 4gig worth of stuff (avi) in one file. It'd breeak it off, in 4gig chunks which required assembling them back together before I could make them into a svcd. With ntsf, I would not have that limitation - I think.
-
Ahhh,..ok...and WOW! Uh, Eagler I think you may have hit the wall on the maximum file size of a single file in the operating system.
I do not believe this is a file system issue, but an OS issue. Could be wrong,..it has been a while since I dug into that stuff.
-
Eagler,
How did you get AH to work with a GeForce Card.... mine keeps locking up when I go into the game.
Bodhi
-
eagler about video , got crap load of problems with 266a2 chipsed based boards
in my old kt 133a just worked fine the DVB-s and WinTV PWR
both have hardware MPG2 and MPG 1 , after many reinstal finaly PWR work but XP display the videos distorsed and crah if trying play MPG2 clip with media player < strange on Kt 133 board and Win ME it never crashed even if runed 5 divx proces in backround> with XP i can play MPG2 clips only with SOFT DVD player or my MPG2 card
now smashin the MB266a out of windows and will try next week the KT333, hope will be beter
ups just forget , with latest update and on Win XPi have no limit on file size , can go over 4 go , wery useful for burning DVD vobs
-
thanks minus
Got the board this morning, haven't put it in et. Still on the IWILL KK266 with 1.33 T-Bird.
Bodhi
Mine's the PNY model.
I just set the adapter back to pci vga then switched out the geforce2 ultra for the geforce4 ti 4400 and loaded the default settings using the driver on the cd rom. I was switching around btwn the ti4400, an ati 8500 128MB and the old ge2 ultra. I do not think i have a clean install as I do not get fps hardly any if at all and sometimes below what got on the geforce2. But then again the ge4 has AA set to "use if software wants" which I think sets it up to run 2X in AH. Good looking scenes in the game but the new map in CT (Stalingrad) put a hurtin on the ti4400, running slightly slower than the ultra.
Check out the Geforce4 ti4400 thread. I have the settings for the stereo glasses posted. With this setting the mouse works. It's pretty neat looking, though harder to hit anything.
Let you know when I have the new stuff in and running.
Bodhi
Are you associated with Warbird Adventures in Kissimmee? Any of your buddies? I have a date 4/1 at 1100 for an hour ride in their T-6. Xmas present from the wife. Looking forward to it.
-
Eagler,
Head into the museum after and ask for Bodhi, they will find me.
:)
-
Eagler if you're going to do videoediting, I'd consider getting another 7200rpm drive and use it in raid-0 configuration. It speeds your IO up considerably and that's exactly what you need when dealing with 4gig+ files.
What you said about different IDE ports on the drives - yes, it will help your performance if the drives do work simultaneously.
One trick to speed up action is to place your vcache (swap) to the drive which does _not_ contain system files and make sure that drive uses a different IDE port than the hd that has your OS in.
That way when the system accesses the system files and writes stuff to the cache simultaneously, they use different IO channels which works a bit faster.
Uh, and Skuzzy: Fat32 in a corporate enviroment is a security risk since it contains no user restrictions. Fat32 workstations are an open invitation to anyone who gets their hands on one, directly or via the network.
I've worked for 4 years administering NT servers and workstations with full NTFS fileformats (totaling of 80 workstations and 4 servers) and I have never seen the described 'hard crash' even at the post which had severe quality-of-service problems electricitywise which effectively cut the mains from the workstations for a couple milliseconds each time large milling machines were started next door.
The OS's were a true mess, yes, but NTFS survived the ordeal. Naturally I upgraded the UPS systems to that office when I got to the job and realized the reason for the constant software errors.
I wouldn't worry about using NTFS, I really don't see it as a risk. A bigger risk is to go to raid-0 and this is what you should seriously consider eagler.. Raid-0 brings IO speed, but doubles your chances of losing data. Nevertheless unless you can afford to get more hd's to build raid-5, I'd build a raid-0 for videoediting purposes.
Just back up your data often enough.
-
Minus: Judging from the reviews I've read of the 333 boards, they're not any faster than 266a and will have the same set of problems.
I use kt266a myself and it does have some issues with pci latency related operations. Fortunately my motherboard contained bios support for adjusting it so I no longer suffer from problems.
Still, the more I play with AMD based systems, the more I start to agree with Skuzzy. If you want cheap speed and hours spent getting to know why your system is not working properly - buy AMD. I don't mind this since this also relates to my work and goes from practise.
If you want stinky pricey bloated system which works like a charm when you slap the things on the board - buy Intel. You lose something in both ways.
-
Actually mrsid2, FAT32 is not inherently any more of a security risk than NTFS, as long as the only things loaded in the network are the Ethernet drivers and the TCP/IP stack.
Yes, if you load anything else, such as NetBUIE, or MS Client, or have File and Printer sharing enabled, or install as part of a workgroup you do open yourself for some security problems.
I can hard crash a NTFS system in about 5 minutes, but then my environment is a pretty stressful one from a networking standpoint. My only hard crashes occurred using Exchange or IIS in stress testing. Sometimes the filesystem would recover, other times it required a full OS reinstallation. Reverting to FAT32, I would see lost files and such but always managed to get the system back up without an OS reinstall.
Both filesystems have plus and minuses. Just depends on your environment.
It's good to know XP gets around the file size limitation. Heck, for video work, I would go with a SCSI adapter and a Seagate Cheetah HD is you want really good video streaming performance. Expensive, but very fast.
-
Skuzzy what about user restrictions INSIDE your network?
How do you manage confidential filefolders with fat32 in order to keep them out of reach of the general users?
-
Inside the network is not an issue. First, we never enable file and printer sharing. Even is someone did, they would be all alone unless it was a conspiracy.
My standing policy is; if you alter your computer system without authorization (including the installation of any software), you will no longer be employed here. We run network monitors to see if that happens and do a periodical random check of the computers as well.
We do not have any workgroups enabled, save one, and it is on its own network subnet, and binds to tcp/ip for broadcasts which keeps the broadcasts from reaching any other part of the network. Putting that network behind a firewall makes it very hard to get to from the outside as well.
If you cannot see the drive, you cannot get to the files irregardless of permissions. We download and test various hack programs to make sure all is secure as well.
I periodically have to notify clients to turn off NetBUIE on thier networks so they can remain invisible. Most people seem unaware you can bind a client to TCP/IP on a subnet and the broadcasts do not cross outside the subnet.
That answer your question?
-
Well, kinda, thanks..
I guess you have no need for a shared network.
-
MrSid, I'm sure I've mentioned this before, but "pci latency" issues are not an "AMD" specific problem. Intel i850 and i845 boards also suffer from this problem. Your problem is actually a VIA issue, not an AMD issue. (P4X266 suffers from it as well.)
I think there is a lot of confusion on this issue:
The problem is due to the 133 MB/sec bandwidth limitations of the PCI bus itself and how it behaves when that limit is exceeded. Intel's workaround was simply to limit bandwidth usage to 80 or 90 MB/s. (I can't remember the exact figure at the moment.) VIA's fix was to change the interupt timings to reduce the bandwidth used at any given point. Both solutions (of course) reduce performance. I850 and i845 hard disk benchmarks are, as a result, pretty poor compared to other chipsets.
Some AMD supporting chipsets, nVidia's nForce for example, has no reported "pci latency" issues. I don't know if the Ali and Sis chipsets suffer from this.
The SB Live series of soundcards had driver issues that could cause some serious problems. Even though 133 MB/s sounds like plenty, remember that on all but a very few examples, IDE disk traffic was transfered across the PCI bus. Burst transfer speeds for some drives may require all available bandwidth. (ATA133 can support a transfer rate of 133 MB/s remember.) Add a SB Live playing an audio stream while transfering large files back and forth between the primary and secondary IDE channels and disaster resulted. I'd imagine a raid array would be even worse. (Nvidia got around the problem by moving IDE traffic to a "Hyper Transport" 800 MB/s capable bus.) I personally think that Serial ATA should help with this problem when it becomes available later this year. (If it's not delayed again... )
In no way does the processor itself directly cause this problem.
_____________________________ ______________________
I personally generally go with NTFS on my own system for security reasons, but I will say that in a dual boot configuration with Win9x, FAT32 is more convienient as Win9x cannot read NTFS formatted disks.
If you turn off some of the silly Windows 2000/XP disk indexing services, NTFS also improves disk performance compared to FAT32 on large partitions.
I'm not sure if the 4 GB limit is a FAT32 issue or an OS issue. I personally think it's probably an OS issue.
In Eagler's case, I'd probably suggest FAT32 IF he planned on a dual boot configuration where Win9x was heavily used. You *could* set aside a small special partition for Win2k/XP OS itself and format it NTFS. I think I'd probably go with FAT32 though. I've actually had a power failure wipe out an NTFS formatted disk to the point where I had to reformat it. :(
-
Bloom25: I know about the pci latency issues with Intel boards also. What I meant really was that I haven't seen an amd based system yet that would have worked 'out of the box.'
They need more or less tweaking to have optimum performance, or sometimes _any_ kind of performance, something I usually can skip if I use an Intel board.
I bought my first amd with abit amd760+686b board and tried to get it stable for 3 months, losing a hefty amount of valuable data in the process even though it was due to a broken harddrive. The 686B systems had the nice 'feature' of corrupting large data transfers so it was a pleasure making a backup from the 30 gigabytes of data I had stored. Read impossible. I also suspect the 761 board was faulty even though the reseller never admitted it.
Anyway, after 3 months I changed the board to a 266a one and even this one hasn't worked as expected from the reviews. I've had to toy with the settings to get IO to work fluidly with multitasking.
Not even you can convince me that this system would have been even a fraction as stable like my old BH6 was.
Now with my IBM 60GXP giving me noises similar to the 'click of death' I'm really starting to get frustrated with this box.
Judging from my experience I can reckommend AMD to people who want high performance and low cost - if they're willing to tweak the system. If they're n00bs.. The choice does get harder.
-
Originally posted by bloom25
I personally generally go with NTFS on my own system for security reasons, but I will say that in a dual boot configuration with Win9x, FAT32 is more convienient as Win9x cannot read NTFS formatted disks.
If you turn off some of the silly Windows 2000/XP disk indexing services, NTFS also improves disk performance compared to FAT32 on large partitions.
I'm not sure if the 4 GB limit is a FAT32 issue or an OS issue. I personally think it's probably an OS issue.
I can tell you absolutely for certain that the 4GB file size limitation is a FAT32 file system limitation. If you look at how the file system is organized, the math says you can't have any larger than 4GB in a single file.
http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/windows2000/en/server/help/choosing_between_NTFS_FAT_and_FAT32.htm
NTFS can have a partition up to 16 Exabytes, and theoretically you can have a single file as big as the entire file system. Practically, I'd say a single file of a Terrabyte or 2 would be the most I'd want to try.
I work doing performance testing on NT/Win2k for my company. I have not had a single problem with NTFS. I don't know what the heck Skuzzy is doing with it, but I believe for your average user NTFS is far more stable and secure. I can't remember the last time I actually had to reformat a drive in NTFS due to errors... it's just never happened to me. I generally migrate 50 GB file structures and up to 100,000 users using our products, and I've never had NTFS fail. Ever. Obviously I don't do the kind of file I/O that Skuzzy tests with, but then again I doubt any of you guys would either. FAT 32 is a hack to make FAT better, but it's not nearly as stable, efficient, scalable, or secure as NTFS in my experience. NTFS's file level security just makes it a must-have in my book, but I think I'd use it anyway.
BTW, this is a great article comparing the two file systems: http://www.anandtech.com/guides/viewfaq.html?i=63
-
I should have just done the math. Fat 32 uses 32 bit addressing, meaning 4294967296 Bytes is the limit. Since Windows considers 1024 KB as a MB, that would come out to around 4.1 Gigabytes. :o
I guess if you do need to have files larger than 4 Gigs, than NTFS is the only way to go.