I'm gonna sound like a newbie....

[livilaNic]

Thanks. I may well run into problems when I do get it. I will let you know with a quickness if it gets the better of me...

Np. If you don't have a clue about this shit you will run into probs. Like I did. It took me a couple times to get the hang of wtf was goin' on. It feels great when you have a deicated audio drive though.

Its well worth the time and breakin shit phases.




L8er,
livilaNic

 

[Rokket]

Np. If you don't have a clue about this shit you will run into probs. Like I did. It took me a couple times to get the hang of wtf was goin' on. It feels great when you have a deicated audio drive though.

Its well worth the time and breakin shit phases.




L8er,
livilaNic

K.... so what happens if I install without putting XP on the harddrive?

Just wanna cover every angle. These damn computers are not cheap...

 

[Dogman]

K.... so what happens if I install without putting XP on the harddrive?

Just wanna cover every angle. These damn computers are not cheap...

Are you talking the second drive? It doesn't need an OS. You can format it, and then it just holds files, and junk. My second drive only has music on it. Lots and lots of music. The only reason you would put on a second OS, is if you needed to dual boot. If all your programs run in XP, there may not be a need for this.

You do have XP on the main harddrive, correct?

 

[xstatic]

You certainly do not want to put an OS on your audio drive. That would defeat the purpose of your audio drive. Even in a dual boot situation it would defeat the purpose. Also, two OS's can share the same drive without sharing system files, or you could add an additional partition to your first drive.

Installing your audio drive should be pretty easy. You should be able to just hook it up and boot up. Wnidows will detect it and you can even format it from inside windows instead of from a boot up disk and dos.

 

[livilaNic]

You certainly do not want to put an OS on your audio drive. That would defeat the purpose of your audio drive. Even in a dual boot situation it would defeat the purpose. Also, two OS's can share the same drive without sharing system files, or you could add an additional partition to your first drive.

Installing your audio drive should be pretty easy. You should be able to just hook it up and boot up. Wnidows will detect it and you can even format it from inside windows instead of from a boot up disk and dos.

"Do not"?

So your telling deicated DAWs "do not" have an operating system?


Rokket you can do it 2 ways.

1.The one I explained above or...


2.Install your new drive (slave).Start windows.

Right click start/properties/customize/Advanced/scroll down the list of options/System Administrative tools/Display on all programs menu

Now goto the Admin.tools in start. In the submenu goto Computer management.

Then find Disk management. Find the new drive which should be D:/.
right click it.

Make new partition.
It will take you through a wizard. Logical Drive. Now right-click again format to ntfs.

I don't know why you would want a deicated audio drive but thats just me.
To each his own.

L8er,
livilaNic

 

[Stephen C]

I have two hard drives set up in my system , the first ( 60gb ) has the O/S on it , with all my programs , the second drive ( 200gb ) is a slave to the first, and it only has two folders on the whole drive.
The fist folder holds " The Music Library " , the second folder is what I call " Additons Folder " . . . I place my songs there first, to make sure that the info is correct before moving them to the main folder.
Plus, I print of the info held in the " Additions " filder, so that I can keep a database of the songs contained in the second H/D...this way , I don't have to print a list of every song when I update 9 almost 2400 wave files so far ).
I would not recommend putting the O/S on the second drive.

 

[livilaNic]

I have two hard drives set up in my system , the first ( 60gb ) has the O/S on it , with all my programs , the second drive ( 200gb ) is a slave to the first, and it only has two folders on the whole drive.
The fist folder holds " The Music Library " , the second folder is what I call " Additons Folder " . . . I place my songs there first, to make sure that the info is correct before moving them to the main folder.
Plus, I print of the info held in the " Additions " filder, so that I can keep a database of the songs contained in the second H/D...this way , I don't have to print a list of every song when I update 9 almost 2400 wave files so far ).
I would not recommend putting the O/S on the second drive.

OMG.

Dude running songs from the other drive makes the computer go from drive (i'll say D) D:/ to (i'll say C) C:/ to run windows media or w/e programs you have on C:/. And say you install a program on D:/ then it places it in the same registry as C:/. So it has to run everything from C:/. Makes no sense not to have another OS on the other drive.

If you want more space or w/e for audio. Partition your C:/ and make that audio storage. Serves the same purpose.

 

[Rokket]

OMG.

Dude running songs from the other drive makes the computer go from drive (i'll say D) D:/ to (i'll say C) C:/ to run windows media or w/e programs you have on C:/. And say you install a program on D:/ then it places it in the same registry as C:/. So it has to run everything from C:/. Makes no sense not to have another OS on the other drive.

If you want more space or w/e for audio. Partition your C:/ and make that audio storage. Serves the same purpose.

I may just get an external harddrive then. My harddrive is only 60GB. I want to save all my wave files because everytime I turn around, I delete them when I am done, and I always find something about my songs that I want to change later and can't. One song can be as much as 140MB or more worth of tracks, so I will fill up my drive fast that way. I was looking for mass storage. I will figure it out.
Thanks for the help, all of you.
I am going to research this a bit and talk to some IT folks that I know and see which solution will best fit my needs.

 

[livilaNic]

*sigh* GL,HF

 

[fraserhutch]

OMG.

Dude running songs from the other drive makes the computer go from drive (i'll say D) D:/ to (i'll say C) C:/ to run windows media or w/e programs you have on C:/. And say you install a program on D:/ then it places it in the same registry as C:/. So it has to run everything from C:/. Makes no sense not to have another OS on the other drive.

If you want more space or w/e for audio. Partition your C:/ and make that audio storage. Serves the same purpose.

No, it does not. The theory is, what you gain by having your audio on a seperate drive is gained by installing it on a seperate IDE controller. That way, say, system file access goes through IDE1 and audio file access goes thorugh IDE2.

*If* you install the 2nd drive on the the same IDE controller the improvement is negligable.

Now, if you want a seperate OS install for your DAW, that is a different question here. Is that what you want to do Rokket? If so, then you would want to partition your system drive. I would still suggest keeping the audio drive seperate on another controller.

As for your example above, it does not work that way. Your music application gets loaded first, and then *it* loads you audio files. Contention arises when application or standard OS services and background tasks need disk access behind the scenes (and trust me, they do a lot), in which case that IO contends with you audio data IO. You can alleviate a lot of that IO contention by keeping the access on seperate IDE controllers.

My $0.02, for the very little it's worth

 

[bigwillz24]

How did a simple question like can I install another hard drive in my computer without installing another OS turn into a pissing match about who has a better method of installing a got damned Hard Drive!

 

[Rokket]

No, it does not. The theory is, what you gain by having your audio on a seperate drive is gained by installing it on a seperate IDE controller. That way, say, system file access goes through IDE1 and audio file access goes thorugh IDE2.

*If* you install the 2nd drive on the the same IDE controller the improvement is negligable.

Now, if you want a seperate OS install for your DAW, that is a different question here. Is that what you want to do Rokket? If so, then you would want to partition your system drive. I would still suggest keeping the audio drive seperate on another controller.

As for your example above, it does not work that way. Your music application gets loaded first, and then *it* loads you audio files. Contention arises when application or standard OS services and background tasks need disk access behind the scenes (and trust me, they do a lot), in which case that IO contends with you audio data IO. You can alleviate a lot of that IO contention by keeping the access on seperate IDE controllers.

My $0.02, for the very little it's worth

What I am looking for is probably just mass storage. But I got to thinking that I may want to move my software (Vegas) to that drive as well, and just have all my audio on the same drive. In effect, it would all be separate from the main pc.
I don't know exactly what my aim is, I guess. Just that I know that I am tired of deleting my tracks when I am "done", only to find out later on that I wanted to change something and can't.

I just noticed you guys have the same avatar. The little guy looks like he's doing a pee pee dance. Makes me have to go! LOL!

 

[Rokket]

How did a simple question like can I install another hard drive in my computer without installing another OS turn into a pissing match about who has a better method of installing a got damned Hard Drive!

I don't know... they are just trying to help. If I was stateside, this would be a no-brainer for me. I'd take it to someone who gets paid to do it and let them install it. Then I'd have them set it up for me the way I wanted it.
Part of the problem is that I don't know where to go here to get that done.

The other part is I'm not sure what I want...

 

[fraserhutch]

How did a simple question like can I install another hard drive in my computer without installing another OS turn into a pissing match about who has a better method of installing a got damned Hard Drive!

No pissing match here. Just advice being given that was requested. But if it's a problem, I'll refrain from giving my advice

No harm, no foul.

 

[cellardweller]

I haven't read this whole thread because it makes my no-no's shrivel...but I got $.02.

Primary OS Drive (C) ribbon cable #1
Secondary audio drive (E) ribbon cable #2
CDR (D) also on ribbon cable #2

Mines pretty barebones, but that "keeps it simple, stupid" (K.I.S.S., words to live by...)

 

[livilaNic]

No, it does not. The theory is, what you gain by having your audio on a seperate drive is gained by installing it on a seperate IDE controller. That way, say, system file access goes through IDE1 and audio file access goes thorugh IDE2.

What is your point here? I'm not grasping the idea. So if you had 2 IDE controllers from your mobo. You would say on C:/WINDOWS and say D:/Audio. It wouldn't have to access drive C:/? How would you install anything on the D:/Audio without an operating system?

I'm still in the learning process. So try to leave it in lymens terms.


L8er,
livilaNic

 

[livilaNic]

(K.I.S.S., words to live by...)

Been to A.A. or N.A. much?

 

[cellardweller]

What is your point here? I'm not grasping the idea. So if you had 2 IDE controllers from your mobo. You would say on C:/WINDOWS and say D:/Audio. It wouldn't have to access drive C:/? How would you install anything on the D:/Audio without an operating system?

I'm still in the learning process. So try to leave it in lymens terms.


L8er,
livilaNic

A man after my own heart, so I will explain it in terms that even I understand...

It is through a process called F.M. (fu**ing magic) that this occurs....

I have no idea, but it works... One OS on C, nothing but data on D (E,F,G,Z what ever, use japanese characters if it congests your member )

 

[cellardweller]

Been to A.A. or N.A. much?

nah, cuts too hard into my drinking time...

 

[fraserhutch]

What is your point here? I'm not grasping the idea. So if you had 2 IDE controllers from your mobo. You would say on C:/WINDOWS and say D:/Audio. It wouldn't have to access drive C:/? How would you install anything on the D:/Audio without an operating system?

I'm still in the learning process. So try to leave it in lymens terms.


L8er,
livilaNic

OK, I'll try to be clear - something I have to work on at times So if I say something that doesn't make sense, yell at me and I'll clear it up.

Most, if not all, PC motherboards have two IDE controllers (newer ones also have SATA controllers, but that is besides the point for now). Each IDE controller can accept two devices; a master and a slave.

So, in theory, you could install up to 4 hard disks on your system. If you did that, and created a single partition on each, then you would, in Windows, have C, D, E, and F drives. You can install install your OS on any of these you like; Windows installation defaults to the first drive, in our case, C. You would be able to access any of the drives as storage. You do not have to have an OS installation on each disk (which is what I think you were wondering about). In fact, on my system, I have disk drives C, D, H, and I. I have E and F DVD drives.

C and D are my first hard disk partitioned into 2 drives.
G and I are my second disk partitioned into 2 drives. I keep my audio and G, and my programs installed on C.

I only have the one OS installed on this box.

My first disk and my first DBV are installed on IDE1, My second disk and my second DVD are installed on the second controlller. So, when my audio app loads, it loads from C, as does all my system software and background tasks. These accesses all go through the IDE 1 controller. When my audio app loads audio and sequence data, because that data resides on a seperate disk on a seperate IDE controller (IDE2), it can be loaded into memory at the same time system and background data is loaded from IDE1 due to the use of DMA.

Now, if my system and program applications all resided on the same disk (or in fact, different disks on the same IDE controller), then the loads could not be concurrent, they would be loaded sequentially.

Hope this helps a bit.