Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[WolfWalker]

be appreciated

I am going to get 2 wd200 and formatthem 100 gigs each
c 100
d 100
e 100
f 100

Then I am going to by one dvd rom and one combo drive plus I am going to get to usb2 drives one 750 zip and on usb hd 120 or so that I can do back ups to.

Can some one give me suggestion on buying what dvd and what combo drive dvd=ram cd-r cd-rw.

[Griff]

Go here and read.

http://www.vcdhelp.com

On left side, select DVD writers/ recorders features/usercomments

Hope this helps

Griff

[RemyJ]

Well, here's my 2 cents:  

1:  Don't buy 200gb hard drives until you're sure your BIOS, IDE Controller and OS can handle drives over 137GB

2:  If you're using W2K or XP Professional, consider the following:
1) you can create spanned volumes
2) you can mount a partition as a directory in addition to, or instead of assigning it a driver letter.  

Here's what I'd do with 2 200gb drives and W2K or WXP Professional

Drive 1:  20gb OS partition "C:",  180gb data partition
Drive 2:  20gb temp/scratch/archive partition, 180gb data partition

Make the 2 180's a single 360gb spanned volume and mount it under c:\usr.  Place all your music and other data here.

Mount the 20gb temp partition under c:\data.  

Kiss drive letter foolishness goodbye.

There are plenty of other variations of this theme of course, but you get the idea.

[WolfWalker]

cool thanks for the info.  I know my machine can handle I just built it in July.  What is the reason for doing that way.  why not have 4 partions on the 2 hd

c: os this one could be split in half make half os and the other half page file.
d:applications
e;games
f: data

[RemyJ]

cool thanks for the info.  I know my machine can handle I just built it in July.  What is the reason for doing that way.  why not have 4 partions on the 2 hd

c: os this one could be split in half make half os and the other half page file.
d:applications
e;games
f: data

Managing free space is much easier.  If f: runs out of space but d: is only 10% full what will your plan be to use the space?  What will the effect be on the applications that use that data?  What happens when d: starts to fill up?

If you use spanned volumes and one starts to fill up, you can add another physical disk and extend the spanned volume onto it and no application will ever know or care.

The more physically based your space management scheme is, the harder it is to change.  

My disclaimer still stands:  there are lots of variations on this theme.  i'm just offering some things to think about.