Hello Do you Know the diffrences between these two drives? oh and just
to make my post useful :-

1, Make sure all ide drives are connected with boot Hard drive as
primary master (set with jumper on back of hard drive (use anti-static
strap))

2, when using linux make sure you have a low-level hard disk formater
(floppy) so that if the install need changing to put windows back on
you can (with out using web on a mates comp paniking)

3, Save all important docs on several floppies as they are not built
like they used to be)

4, If you add/remove a cd/dvd drive windows will not autmatically find
it's files when requested (looks on old drive letter) so use browse or
treat as good time to re-format and reinstall (speed)

5, install cd/dvd drive on different ide channel (speed)

6, Use google a lot to find out stuff

6, Always install driver disk first for USB devices THEN the hardware
itself

7, Two sugars please

Thanks for your help guys sorry if i told you what you already know
(just wanted to give as well as ask for advice)or indeed if you
disagree.

[ Post a follow-up to this message ]

mcmahoncrstp@btopenworld.com (dave) wrote in
news:9618ffec.0409251135.6f5de3ee@posting.google.com:

> Hello Do you Know the diffrences between these two drives? oh and just
> to make my post useful :-

No need, but babbling off archaic design doctrines is hardly useful.

> 1, Make sure all ide drives are connected with boot Hard drive as
> primary master (set with jumper on back of hard drive (use anti-static
> strap))

It'll work fine without doing that.

> 2, when using linux make sure you have a low-level hard disk formater
> (floppy) so that if the install need changing to put windows back on
> you can (with out using web on a mates comp paniking)

Windows will replace the partitioning and master boot record without a
hitch (at least if it's w2k and newer - i don't remember problems with
older windows version, but can't rule it out).

> 3, Save all important docs on several floppies as they are not built
> like they used to be)

Or use something that's not a dead technology. CD's or online copies is a
good way to go. However you do it, make sure you have more than one copy of
anything important and CHECK the copies regularly in case they break.

> 4, If you add/remove a cd/dvd drive windows will not autmatically find
> it's files when requested (looks on old drive letter) so use browse or
> treat as good time to re-format and reinstall (speed)

Change the drive letter if you replaced an old drive.

> 5, install cd/dvd drive on different ide channel (speed)

Not too big of a deal on UDMA channels. The main point is to avoid having
the source and target of copy operations (like cd burning) on different
channels.



--
/Jesper Monsted

[ Post a follow-up to this message ]

Jesper Monsted wrote:
> mcmahoncrstp@btopenworld.com (dave) wrote in
> news:9618ffec.0409251135.6f5de3ee@posting.google.com:
>
<snip> 
>
>
> Not too big of a deal on UDMA channels. The main point is to avoid having
> the source and target of copy operations (like cd burning) on different
> channels.
>
Perhaps a good time to double check my knowledge - I was under the
impression that the ide channel will noly run at the speed of the
slowest devide, so putting a UDMA133 Hard disk on the same channel as a
UDMA66 cd-rom drive will significantly impact the speed of the hard disk.

I agree with and understand avoiding transfers between drives on the
same channel though.

--
Meurig
(http://xboxmods.meurig.com - modded xbox for sale)

[ Post a follow-up to this message ]

"Meurig Freeman" <me@*NnoSpam*meurig.com> wrote in message
news:4155e0a7$0$22760$db0fefd9@news.zen.co.uk...
> Jesper Monsted wrote: 
> <snip> 
having[vbcol=seagreen] 
> Perhaps a good time to double check my knowledge - I was under the
> impression that the ide channel will noly run at the speed of the
> slowest devide,

NO,  each device runs at its own speed.

> so putting a UDMA133 Hard disk on the same channel as a
> UDMA66 cd-rom drive will significantly impact the speed of the hard disk.

NO,  for two reasons.  First the UDMA133 HD will burst at UDMA133 speeds
even when a UDMA66 gadget on the same cable.  Second UDMA66 will run most
current HDs at full speed.

> I agree with and understand avoiding transfers between drives on the
> same channel though.

That's a different issue.  That's where UDMA133 helps.  Put two recent
UDMA133 HDs on a single cable and UDMA133 mode will allow both to run at
near full speed doing big file transfers.  Make them both run in UDMA66 mode
then there will be impaired performance in simultaneous big file operations.

[ Post a follow-up to this message ]

Ron Reaugh wrote:
> "Meurig Freeman" <me@*NnoSpam*meurig.com> wrote in message
> news:4155e0a7$0$22760$db0fefd9@news.zen.co.uk...
> 
>
> having
> 
>
>
> NO,  each device runs at its own speed.
>
> 
>
>
> NO,  for two reasons.  First the UDMA133 HD will burst at UDMA133 speeds
> even when a UDMA66 gadget on the same cable.  Second UDMA66 will run most
> current HDs at full speed.
>
> 
>
>
> That's a different issue.  That's where UDMA133 helps.  Put two recent
> UDMA133 HDs on a single cable and UDMA133 mode will allow both to run at
> near full speed doing big file transfers.  Make them both run in UDMA66 mo
de
> then there will be impaired performance in simultaneous big file operation
s.
>
>

Good job I checked then, guess I might take another look at my IDE
cables at some point!

--
Meurig
(http://xboxmods.meurig.com - modded xbox for sale)

[ Post a follow-up to this message ]

I was told it made speed faster as virtual memory is faster if using a HDD
on another channel so that that the primary channel is 'overload loading a
prog (for example) AND accessing Virtual memory,

I posted the advice so my question was'n just selfish BTW what is the
difference between the two drives?????

[ Post a follow-up to this message ]

"McMahon" <@nospam.net> wrote in message
news:D-CdnYz5oImJWcvcRVnyjQ@fireflyuk.net...
> I was told it made speed faster as virtual memory is faster if using a HDD
> on another channel so that that the primary channel is 'overload loading a
> prog (for example) AND accessing Virtual memory,


There 's basically only one thing that speeds virtual memory and that's more
RAM.

[ Post a follow-up to this message ]