A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » General Hardware & Peripherals » Homebuilt PC's
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Norton Ghost - Clone Won't Work



 
 
Thread Tools Display Modes
  #31  
Old October 16th 04, 03:17 PM
David Maynard
external usenet poster
 
Posts: n/a
Default

jimbo wrote:

David Maynard wrote:

jimbo wrote:

Ed Coolidge wrote:

jimbo wrote:

Still no go. I cloned again using the external USB2.0 case with the
new drive mounted. No error messages from Ghost, but when I try to
boot to WinXP using the newly cloned drive, it gives a message
saying the drive needs to be checked and it goes through three
chkdsk checks, all of which pass, then it reboots and the same
thing happens again.

And when I boot from the WinXP CD, it asks which Windows to use and
has "D:\" as the only option. "Repair" takes me to the "D:\" prompt
which doesn't provide much. "Install" doesn't give a repair option,
only a new installation and if I start that option, it gives a
warning message about another OS being there and that it is a bad
idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windo ws XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another post,
fails to boot.

jimbo





So far it looks like you did everything right, which would lead me
to suspect that there might be something wrong with the new drive,
or the BIOS has the disk configured incorrectly. It's been awhile,
but does Ghost have an option to verify the contents of the cloned
drive? If it does I would use it to see if it checks out. If you
have Partition Magic, you can use it to check the new drive. It
should be able to detect any partition or BIOS configuration errors.




Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any
partitions on it.

Suggestions?

jimbo




Well, Partition Magic not liking the partition is disturbing. But, for
now,

I see above you say you put the drive in a USB enclosure and cloned
it. I'm not concerned with that particular clone attempt but want to
know if you've had the new drive in the machine, regardless of the
interface, with your existing XP system running. And if you HAVE then
it's been 'installed' by XP, given a unique GUID, and assigned a drive
letter; which will be faithfully copied to the new drive when you do a
clone so it will not be a 'new' drive when booting from that clone but
will be whatever letter it was assigned, so it won't be assigned the
missing 'system drive' letter.

First, I'd like for you to boot the 'old' setup and record which
letter the two old drives are assigned. You are assuming the win98
boot drive is c? So XP is installed on D and SAYS itself that D is
it's system drive? I.E. the XP windows directory is on D:\Windows?

Anyway, on the chances that a 'virgin' drive will get detected in the
same order, you need to get the new drive back to 'virgin' status. And
the easiest way to do that is put the new drive as master on the
primary IDE port, boot a win98 rescue disk, and fdisk /mbr it.

Writing a win98 boot record will wipe out the GUID.

Then, do not boot XP with that new drive installed. Do the clone with
a Ghost FLOPPY.

Then remove your old XP drive, place the new one in as slave with the
win98 master, and see if it boots up right (while crossing fingers
that it detects the drives in the original order).





Yes, Win98 is on "C" and WinXP is on "D". And "C" partition is on the HD
jumpered as master and is at the end of the ribbon cable and "D"
partition is on the HD jumpered as slave and is on the middle of the
ribbon cable.


I'm apparently not being clear. "C" and "D" are letters that Windows
assigns and the two flavors of Windows don't so it the same way. So, when
you simply say "C" and "D" I am not sure which O.S. you're talking about.

It is specifically whether they both have them assigned the same, or
different, drive letters that I'm trying to get confirmed.

But I think the bigger issue right now is whether the new drive was
installed into XP before you did the clone, though, and get the GUID
cleaned off of it.

Btw, fixboot doesn't remove the GUID. fdisk /mbr does.


Thanks for all of the help and suggestions. I will be away for a day, so
I will reply again when I get back and have a chance to do some more
work on this problem.


Okedoke.


jimbo


  #32  
Old October 16th 04, 06:22 PM
jaster
external usenet poster
 
Posts: n/a
Default

On Sat, 16 Oct 2004 06:42:13 -0700, jimbo wrote:

jaster wrote:
On Thu, 14 Oct 2004 11:55:05 -0700, jimbo wrote:


I have physical hard drive "C" with Win98 and physical hard drive "D"
with WinXP in a dual boot setup. I want to injstall a new, larger
physical hard drive "D". I have tried to follow the procedure for
cloning a drive using Norton Ghost. I disconnected the cables from "C"
and connected the new hard drive. (I set the new drive's jumper to
"master" the same as the "C" drive.) Then Norton Ghost was booted from
floppies and I cloned drive 2 to drive 1. This all seemed to OK. Then I
disconnected the new drive and changed the jumper to "slave". Then I
reconnected the "C" drive. Then I disconnected the "D" drive and
connected the new drive in it's place. Now when I boot to WinXP it
fails just after the WinXP splash screen. A blue screen with an error
message appears and the system reboots.

Any insight will be appreciated.

jimbo



I think XP looks for boot image on the C drive and that is looking for
the old D drive not the new drive. With the new D drive installed try
booting from your WinXP CD go into repair XP and run fixboot. If that
doesn't fix the problem then you'll need to boot the XP CD go into
install mode and then repair the installed XP.

When I clone a drive I use the drive vendor's utility to make a clone
of the drive.


Did that. Fixboot does not fix the proglem. And Install does not give an
option to repair, only to do a new install. So, for some reason, the
Ghost clone is not being recognized as a WinXP installation, although it
is being recognized as a Windows installation of some kind.

jimbo



Maybe when you restored the Ghost image to the new drive you set as a
primary partition and not as a logical partition?

When you go through the installation menu you should select install and
you should be presented with another menu asking if you want to install or
repair the existing XP installation.

At this point in your exercise does it make sense to continue the
frustration or is it the learning process? If not learning and you know
the other software and data has been cloned to the new drive, just install
XP on the new drive. The install process "repair installation" is pretty
much the same as a new install of XP anyway except it saves
re-installation of most programs.

  #33  
Old October 16th 04, 08:38 PM
jimbo
external usenet poster
 
Posts: n/a
Default

jaster wrote:
On Sat, 16 Oct 2004 06:42:13 -0700, jimbo wrote:


jaster wrote:

On Thu, 14 Oct 2004 11:55:05 -0700, jimbo wrote:



I have physical hard drive "C" with Win98 and physical hard drive "D"
with WinXP in a dual boot setup. I want to injstall a new, larger
physical hard drive "D". I have tried to follow the procedure for
cloning a drive using Norton Ghost. I disconnected the cables from "C"
and connected the new hard drive. (I set the new drive's jumper to
"master" the same as the "C" drive.) Then Norton Ghost was booted from
floppies and I cloned drive 2 to drive 1. This all seemed to OK. Then I
disconnected the new drive and changed the jumper to "slave". Then I
reconnected the "C" drive. Then I disconnected the "D" drive and
connected the new drive in it's place. Now when I boot to WinXP it
fails just after the WinXP splash screen. A blue screen with an error
message appears and the system reboots.

Any insight will be appreciated.

jimbo


I think XP looks for boot image on the C drive and that is looking for
the old D drive not the new drive. With the new D drive installed try
booting from your WinXP CD go into repair XP and run fixboot. If that
doesn't fix the problem then you'll need to boot the XP CD go into
install mode and then repair the installed XP.

When I clone a drive I use the drive vendor's utility to make a clone
of the drive.


Did that. Fixboot does not fix the proglem. And Install does not give an
option to repair, only to do a new install. So, for some reason, the
Ghost clone is not being recognized as a WinXP installation, although it
is being recognized as a Windows installation of some kind.

jimbo




Maybe when you restored the Ghost image to the new drive you set as a
primary partition and not as a logical partition?

When you go through the installation menu you should select install and
you should be presented with another menu asking if you want to install or
repair the existing XP installation.

At this point in your exercise does it make sense to continue the
frustration or is it the learning process? If not learning and you know
the other software and data has been cloned to the new drive, just install
XP on the new drive. The install process "repair installation" is pretty
much the same as a new install of XP anyway except it saves
re-installation of most programs.


Well, as I just said, that option is not given to me when I select the
WinXP install option from the first menu. For some reason, the program
is not seeing the WinXP installation. It is seeing something because
if I select istall, it gives a message about it being a bad idea to
install two OSs on the same partition.

jimbo
  #34  
Old October 17th 04, 12:41 AM
jimbo
external usenet poster
 
Posts: n/a
Default

David Maynard wrote:
jimbo wrote:

David Maynard wrote:

jimbo wrote:

Ed Coolidge wrote:

jimbo wrote:

Still no go. I cloned again using the external USB2.0 case with
the new drive mounted. No error messages from Ghost, but when I
try to boot to WinXP using the newly cloned drive, it gives a
message saying the drive needs to be checked and it goes through
three chkdsk checks, all of which pass, then it reboots and the
same thing happens again.

And when I boot from the WinXP CD, it asks which Windows to use
and has "D:\" as the only option. "Repair" takes me to the "D:\"
prompt which doesn't provide much. "Install" doesn't give a repair
option, only a new installation and if I start that option, it
gives a warning message about another OS being there and that it
is a bad idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windo ws XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another
post, fails to boot.

jimbo






So far it looks like you did everything right, which would lead me
to suspect that there might be something wrong with the new drive,
or the BIOS has the disk configured incorrectly. It's been awhile,
but does Ghost have an option to verify the contents of the cloned
drive? If it does I would use it to see if it checks out. If you
have Partition Magic, you can use it to check the new drive. It
should be able to detect any partition or BIOS configuration errors.





Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any
partitions on it.

Suggestions?

jimbo




Well, Partition Magic not liking the partition is disturbing. But,
for now,

I see above you say you put the drive in a USB enclosure and cloned
it. I'm not concerned with that particular clone attempt but want to
know if you've had the new drive in the machine, regardless of the
interface, with your existing XP system running. And if you HAVE then
it's been 'installed' by XP, given a unique GUID, and assigned a
drive letter; which will be faithfully copied to the new drive when
you do a clone so it will not be a 'new' drive when booting from that
clone but will be whatever letter it was assigned, so it won't be
assigned the missing 'system drive' letter.

First, I'd like for you to boot the 'old' setup and record which
letter the two old drives are assigned. You are assuming the win98
boot drive is c? So XP is installed on D and SAYS itself that D is
it's system drive? I.E. the XP windows directory is on D:\Windows?

Anyway, on the chances that a 'virgin' drive will get detected in the
same order, you need to get the new drive back to 'virgin' status.
And the easiest way to do that is put the new drive as master on the
primary IDE port, boot a win98 rescue disk, and fdisk /mbr it.

Writing a win98 boot record will wipe out the GUID.

Then, do not boot XP with that new drive installed. Do the clone with
a Ghost FLOPPY.

Then remove your old XP drive, place the new one in as slave with the
win98 master, and see if it boots up right (while crossing fingers
that it detects the drives in the original order).





Yes, Win98 is on "C" and WinXP is on "D". And "C" partition is on the
HD jumpered as master and is at the end of the ribbon cable and "D"
partition is on the HD jumpered as slave and is on the middle of the
ribbon cable.



I'm apparently not being clear. "C" and "D" are letters that Windows
assigns and the two flavors of Windows don't so it the same way. So,
when you simply say "C" and "D" I am not sure which O.S. you're talking
about.

It is specifically whether they both have them assigned the same, or
different, drive letters that I'm trying to get confirmed.

But I think the bigger issue right now is whether the new drive was
installed into XP before you did the clone, though, and get the GUID
cleaned off of it.

Btw, fixboot doesn't remove the GUID. fdisk /mbr does.


Thanks for all of the help and suggestions. I will be away for a day,
so I will reply again when I get back and have a chance to do some
more work on this problem.



Okedoke.


jimbo




Well, on XP, "C" partition is Win98 and "D" partition is WinXP. On
Win98, Win98 is on "C" and Win98 can't see the "D" NTFS partition.

jimbo
  #35  
Old October 17th 04, 01:15 AM
jimbo
external usenet poster
 
Posts: n/a
Default

jimbo wrote:
I have physical hard drive "C" with Win98 and physical hard drive "D"
with WinXP in a dual boot setup. I want to injstall a new, larger
physical hard drive "D". I have tried to follow the procedure for
cloning a drive using Norton Ghost. I disconnected the cables from "C"
and connected the new hard drive. (I set the new drive's jumper to
"master" the same as the "C" drive.) Then Norton Ghost was booted from
floppies and I cloned drive 2 to drive 1. This all seemed to OK. Then I
disconnected the new drive and changed the jumper to "slave". Then I
reconnected the "C" drive. Then I disconnected the "D" drive and
connected the new drive in it's place. Now when I boot to WinXP it fails
just after the WinXP splash screen. A blue screen with an error message
appears and the system reboots.

Any insight will be appreciated.

jimbo


Well, the next thing I will try when I get back to my desktop is to do
the fdisk /mbr from Win98. But I am very concerned about Partition Magic
not seeing any partitions on my WinXP hard drive. And the WinXP
installation CD doesn't see the WinXP installation, so it doesn't offer
an option for a "repair" installation. And another wrinkle, Windows
Explorer sees a third hard drive "G" with 0 byte size and no file
system. I have physical drives "C" 40 GB HD, "D" 40 GB HD, "E" DVD
reader and "F", DVD burner. And then this fanthom "G" drive that doesn't
show up anyplace except in Windows Explorer.

jimbo
  #36  
Old October 17th 04, 01:26 AM
Ed Coolidge
external usenet poster
 
Posts: n/a
Default

I was just curious. What error did Partition Magic give?
Also, have you tried installing the new drive XP with the other two? If so was
the new drive accessible?

jimbo wrote:

Well, I did a WinXP installation on the new drive with no problems. But
interesting, when I checked everything out with Partition Magic, it
reports "Bad Disk" for the old "D" drive! Even though it works perfectly
with my system, now and in the past. It shows up in Device Manager as
working, etc. No errors of any kind, boots the WinXP installation, etc,
etc. But for some reason Partition Magic thinks there is something wrong
with it and does not even show any partitions on it.

Suggestions?

jimbo

  #37  
Old October 17th 04, 02:46 AM
David Maynard
external usenet poster
 
Posts: n/a
Default

jimbo wrote:

jimbo wrote:

I have physical hard drive "C" with Win98 and physical hard drive "D"
with WinXP in a dual boot setup. I want to injstall a new, larger
physical hard drive "D". I have tried to follow the procedure for
cloning a drive using Norton Ghost. I disconnected the cables from "C"
and connected the new hard drive. (I set the new drive's jumper to
"master" the same as the "C" drive.) Then Norton Ghost was booted from
floppies and I cloned drive 2 to drive 1. This all seemed to OK. Then
I disconnected the new drive and changed the jumper to "slave". Then I
reconnected the "C" drive. Then I disconnected the "D" drive and
connected the new drive in it's place. Now when I boot to WinXP it
fails just after the WinXP splash screen. A blue screen with an error
message appears and the system reboots.

Any insight will be appreciated.

jimbo



Well, the next thing I will try when I get back to my desktop is to do
the fdisk /mbr from Win98. But I am very concerned about Partition Magic
not seeing any partitions on my WinXP hard drive. And the WinXP
installation CD doesn't see the WinXP installation, so it doesn't offer
an option for a "repair" installation.


I'm not entirely sure how XP determines whether there's a 'valid'
installation on a disk but since you have the boot files on C, then the
rest of the system on D, perhaps it doesn't think it's all there.

Perhaps caused by this mystery partition of yours.

And another wrinkle, Windows
Explorer sees a third hard drive "G" with 0 byte size and no file
system. I have physical drives "C" 40 GB HD, "D" 40 GB HD, "E" DVD
reader and "F", DVD burner. And then this fanthom "G" drive that doesn't
show up anyplace except in Windows Explorer.

jimbo


That could be the problem. If the existing D drive has some sort of
'mystery' partition on it then XP could be assigning the drive letters
differently than you expect when the new drive comes up.

Try doing a partition to partition copy, not the 'whole (old) drive'. You
can still tell it to make the new partition fill the new drive so it's one
big partition.

Or do you have one of those CD emulator software packages installed?

  #38  
Old October 17th 04, 02:46 AM
Peter
external usenet poster
 
Posts: n/a
Default

In article ,
says...
Peter wrote:

In article ,

says...

On Thu, 14 Oct 2004 11:55:05 -0700, jimbo wrote:


I have physical hard drive "C" with Win98 and physical hard drive "D" with
WinXP in a dual boot setup. I want to injstall a new, larger physical hard
drive "D". I have tried to follow the procedure for cloning a drive using
Norton Ghost. I disconnected the cables from "C" and connected the new
hard drive. (I set the new drive's jumper to "master" the same as the "C"
drive.) Then Norton Ghost was booted from floppies and I cloned drive 2 to
drive 1. This all seemed to OK. Then I disconnected the new drive and
changed the jumper to "slave". Then I reconnected the "C" drive. Then I
disconnected the "D" drive and connected the new drive in it's place. Now
when I boot to WinXP it fails just after the WinXP splash screen. A blue
screen with an error message appears and the system reboots.

Any insight will be appreciated.

jimbo

I think XP looks for boot image on the C drive and that is looking for
the old D drive not the new drive.


Why wouldn't that 'boot image' not be looking for the new D drive.


What makes you think the new drive is 'D'?

Because it's the only other HD on the system. At least that's how it
works with my setup. I have 2 HD's on the primary IDE and set to cable
select, allowing me to boot from either IDE. When I boot from one the
other becomes drive D and vice versa. Now, perhaps XP can mess things
up when assigning drive letters, but seeing as the original cloning
process was done from boot floppies then I can't see how this could
possibly happen.

Surely there should be no difference between the old and new drive,
unless, that is, Norton Ghost doesn't create an 'exact' copy (sector for
sector) of the original D drive. Haven't used NG so don't know how it
works exactly.






--
Pete Ives
Remove All_stRESS before sending me an email
  #39  
Old October 17th 04, 02:56 AM
Peter
external usenet poster
 
Posts: n/a
Default

In article ,
says...
David Maynard wrote:

jimbo wrote:

Ed Coolidge wrote:

jimbo wrote:

Still no go. I cloned again using the external USB2.0 case with the
new drive mounted. No error messages from Ghost, but when I try to
boot to WinXP using the newly cloned drive, it gives a message
saying the drive needs to be checked and it goes through three
chkdsk checks, all of which pass, then it reboots and the same thing
happens again.

And when I boot from the WinXP CD, it asks which Windows to use and
has "D:\" as the only option. "Repair" takes me to the "D:\" prompt
which doesn't provide much. "Install" doesn't give a repair option,
only a new installation and if I start that option, it gives a
warning message about another OS being there and that it is a bad
idea to install two OSs on the same partition.

It appears that Ghost is not performing a proper clone.

Here is the boot.ini file from "C" root.

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windo ws XP" /fastdetect
C:\="Windows 98"

And the attempt to use the second IDE as described in another post,
fails to boot.

jimbo




So far it looks like you did everything right, which would lead me to
suspect that there might be something wrong with the new drive, or
the BIOS has the disk configured incorrectly. It's been awhile, but
does Ghost have an option to verify the contents of the cloned
drive? If it does I would use it to see if it checks out. If you
have Partition Magic, you can use it to check the new drive. It
should be able to detect any partition or BIOS configuration errors.



Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any partitions
on it.

Suggestions?

jimbo



Well, Partition Magic not liking the partition is disturbing. But, for now,

I see above you say you put the drive in a USB enclosure and cloned it.
I'm not concerned with that particular clone attempt but want to know if
you've had the new drive in the machine, regardless of the interface,
with your existing XP system running. And if you HAVE then it's been
'installed' by XP, given a unique GUID, and assigned a drive letter;
which will be faithfully copied to the new drive when you do a clone so
it will not be a 'new' drive when booting from that clone but will be
whatever letter it was assigned, so it won't be assigned the missing
'system drive' letter.

First, I'd like for you to boot the 'old' setup and record which letter
the two old drives are assigned. You are assuming the win98 boot drive
is c? So XP is installed on D and SAYS itself that D is it's system
drive? I.E. the XP windows directory is on D:\Windows?

Anyway, on the chances that a 'virgin' drive will get detected in the
same order, you need to get the new drive back to 'virgin' status. And
the easiest way to do that is put the new drive as master on the primary
IDE port, boot a win98 rescue disk, and fdisk /mbr it.

Writing a win98 boot record will wipe out the GUID.

Then, do not boot XP with that new drive installed. Do the clone with a
Ghost FLOPPY.

Then remove your old XP drive, place the new one in as slave with the
win98 master, and see if it boots up right (while crossing fingers that
it detects the drives in the original order).





Yes, Win98 is on "C" and WinXP is on "D". And "C" partition is on the
HD jumpered as master and is at the end of the ribbon cable and "D"
partition is on the HD jumpered as slave and is on the middle of the
ribbon cable.

Thanks for all of the help and suggestions. I will be away for a day,
so I will reply again when I get back and have a chance to do some
more work on this problem.

jimbo

So, how was the new, replacement HD originally partitioned again? I'm
not too familiar with Ghost, but does it also do the partitioning and
create the file system that is to be used?

If I were to clone an NTFS partition to another drive I'd want to make
sure that that drive was already formatted using the NTFS file system.
As a hypothetical question, what would happen if you tried to clone an
NTFS partitioned HD to a FAT32 formatted HD?
--
Pete Ives
Remove All_stRESS before sending me an email
  #40  
Old October 17th 04, 04:57 AM
jimbo
external usenet poster
 
Posts: n/a
Default

Ed Coolidge wrote:
I was just curious. What error did Partition Magic give?
Also, have you tried installing the new drive XP with the other two? If
so was the new drive accessible?

jimbo wrote:

Well, I did a WinXP installation on the new drive with no problems.
But interesting, when I checked everything out with Partition Magic,
it reports "Bad Disk" for the old "D" drive! Even though it works
perfectly with my system, now and in the past. It shows up in Device
Manager as working, etc. No errors of any kind, boots the WinXP
installation, etc, etc. But for some reason Partition Magic thinks
there is something wrong with it and does not even show any partitions
on it.

Suggestions?

jimbo


Just the word "bad" after the drive 2 header and no partition
information. And yes, Partition Magic can and was used to create an NTFS
partition. When the new drive is placed in the external USB enclosure,
Windows Explorer could see it OK. It just wouldn't boot to WinXP when it
was placed in the old WinXP HD.

jimbo
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Clone IDE to SATA hard drive TOM B WILSON Homebuilt PC's 3 October 2nd 04 09:46 PM
isolating new clone drive for 1st bootup Timothy Daniels General 86 February 29th 04 04:37 PM
DELL upgrade with Kingston Value RAM - will it work properly stromer General 0 January 31st 04 09:29 AM
Can't get two CD drives to work on XP machine Bruce General 2 September 5th 03 01:01 AM
clone harddisk Ralph Mowery General 1 August 24th 03 12:40 AM


All times are GMT +1. The time now is 06:04 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.