Ghosting Issue

[Guest Parvardigar]

This is very uncomplicated. I have at work here only Dell Optiplex

GX1's running Windows 2000.

On all the machine I ghosted from former harddrive 9GB to new

harddrive 80GB.

No problems.

On this one machine I have ghosted in the usual fashion the 9GB to

the

80GB drive.

And I did this on two new fresh WD harddrives ending up with (after

installing the newly Ghosted drive) this Blue Screen

 

Stop 000000007B and so on ending with Inaccessible_Boot_Device.

 

 

I've ran the Ghost several times and ending with the blue screen

message.

In Bios I alter the device to auto, and it is found. Bios fine.

I can upon reboot launch safe, safe with networking, LKG, and so on.

However, the bluescreen appears in every instance with the Stop /

Device bluescreen message.

 

 

I've been successful on all the machines, all the same OS, ghosting;

and this computer is proving to be a problem. Is there a solution?

Let

me know. Thanks John M

[Guest John John (MVP)]

Re: Ghosting Issue

 

This is usually a controller issue, are all the machines identical? Is

the disk on an IDE controller? Is it on the same IDE controller

(Primary/Secondary)?

 

John

 

Parvardigar wrote:

> This is very uncomplicated. I have at work here only Dell Optiplex

> GX1's running Windows 2000.

> On all the machine I ghosted from former harddrive 9GB to new

> harddrive 80GB.

> No problems.

> On this one machine I have ghosted in the usual fashion the 9GB to

> the

> 80GB drive.

> And I did this on two new fresh WD harddrives ending up with (after

> installing the newly Ghosted drive) this Blue Screen

>

> Stop 000000007B and so on ending with Inaccessible_Boot_Device.

>

>

> I've ran the Ghost several times and ending with the blue screen

> message.

> In Bios I alter the device to auto, and it is found. Bios fine.

> I can upon reboot launch safe, safe with networking, LKG, and so on.

> However, the bluescreen appears in every instance with the Stop /

> Device bluescreen message.

>

>

> I've been successful on all the machines, all the same OS, ghosting;

> and this computer is proving to be a problem. Is there a solution?

> Let

> me know. Thanks John M

>

[Guest Parvardigar]

Re: Ghosting Issue

 

On Oct 22, 7:58 am, "John John (MVP)" <audetw...@nbnet.nb.ca> wrote:

> This is usually a controller issue, are all the machines identical?  Is

> the disk on an IDE controller?  Is it on the same IDE controller

> (Primary/Secondary)?

>

> John

>

>

>

> Parvardigar wrote:

> > This is very uncomplicated. I have at work here only Dell Optiplex

> > GX1's running Windows 2000.

> > On all the machine I ghosted from former harddrive 9GB to new

> > harddrive 80GB.

> > No problems.

> > On this one machine I have ghosted in the usual fashion the 9GB to

> > the

> > 80GB drive.

> > And I did this on two new fresh WD harddrives ending up with (after

> > installing the newly Ghosted drive) this Blue Screen

>

> > Stop 000000007B and so on ending with Inaccessible_Boot_Device.

>

> > I've ran the Ghost several times and ending with the blue screen

> > message.

> > In Bios I alter the device to auto, and it is found. Bios fine.

> > I can upon reboot launch safe, safe with networking, LKG, and so on.

> > However, the bluescreen appears in every instance with the Stop /

> > Device bluescreen message.

>

> > I've been successful on all the machines, all the same OS, ghosting;

> > and this computer is proving to be a problem. Is there a solution?

> > Let

> > me know. Thanks John M- Hide quoted text -

>

> - Show quoted text -

 

 

All the machines are identitcal. I even used three identical computers

using the same cable ; primary ; auto detect. If I return the old hard

drive, no issue ; and insert the ghosted hard drive ; problem. I've

followed on all the computers (all the same model) this exact

procedure ...WD format on the new hard drive - checking cmos for hard

drive (old) master ; hard drive new (slave) and then Ghosting.

 

Returning cmos to the original setting hard drive primary ; no slave.

And getting a blue screen on reboot boot. Than I replace the new hard

drive with the old hard drive and no issues.

 

Now I could see problems if a few of the computers were to give me

ghosting troubles ....but 11 computer ; all exact model ; the exact

ghosting procedure - and everything without a hitch until this current

situation with Joe's computer.

 

Thanks

[Guest Pegasus \(MVP\)]

Re: Ghosting Issue

 

 

"Parvardigar" <parvardigar@yahoo.com> wrote in message

news:dcc85f8e-c977-484c-a802-2839444ba947@p10g2000prf.googlegroups.com...

On Oct 22, 7:58 am, "John John (MVP)" <audetw...@nbnet.nb.ca> wrote:

> This is usually a controller issue, are all the machines identical? Is

> the disk on an IDE controller? Is it on the same IDE controller

> (Primary/Secondary)?

>

> John

>

>

>

> Parvardigar wrote:

> > This is very uncomplicated. I have at work here only Dell Optiplex

> > GX1's running Windows 2000.

> > On all the machine I ghosted from former harddrive 9GB to new

> > harddrive 80GB.

> > No problems.

> > On this one machine I have ghosted in the usual fashion the 9GB to

> > the

> > 80GB drive.

> > And I did this on two new fresh WD harddrives ending up with (after

> > installing the newly Ghosted drive) this Blue Screen

>

> > Stop 000000007B and so on ending with Inaccessible_Boot_Device.

>

> > I've ran the Ghost several times and ending with the blue screen

> > message.

> > In Bios I alter the device to auto, and it is found. Bios fine.

> > I can upon reboot launch safe, safe with networking, LKG, and so on.

> > However, the bluescreen appears in every instance with the Stop /

> > Device bluescreen message.

>

> > I've been successful on all the machines, all the same OS, ghosting;

> > and this computer is proving to be a problem. Is there a solution?

> > Let

> > me know. Thanks John M- Hide quoted text -

>

> - Show quoted text -

 

 

All the machines are identitcal. I even used three identical computers

using the same cable ; primary ; auto detect. If I return the old hard

drive, no issue ; and insert the ghosted hard drive ; problem. I've

followed on all the computers (all the same model) this exact

procedure ...WD format on the new hard drive - checking cmos for hard

drive (old) master ; hard drive new (slave) and then Ghosting.

 

Returning cmos to the original setting hard drive primary ; no slave.

And getting a blue screen on reboot boot. Than I replace the new hard

drive with the old hard drive and no issues.

 

Now I could see problems if a few of the computers were to give me

ghosting troubles ....but 11 computer ; all exact model ; the exact

ghosting procedure - and everything without a hitch until this current

situation with Joe's computer.

 

Thanks

==============

The machines are obviously not identical. If they were then you would not

have the problem. I have come across similar issues - they were caused by

one machine having a slightly different chip set. A repair installation

might fix the problem.

[Guest Parvardigar]

Re: Ghosting Issue

 

On Oct 22, 9:11 am, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:

> "Parvardigar" <parvardi...@yahoo.com> wrote in message

>

> news:dcc85f8e-c977-484c-a802-2839444ba947@p10g2000prf.googlegroups.com...

> On Oct 22, 7:58 am, "John John (MVP)" <audetw...@nbnet.nb.ca> wrote:

>

>

>

>

>

> > This is usually a controller issue, are all the machines identical? Is

> > the disk on an IDE controller? Is it on the same IDE controller

> > (Primary/Secondary)?

>

> > John

>

> > Parvardigar wrote:

> > > This is very uncomplicated. I have at work here only Dell Optiplex

> > > GX1's running Windows 2000.

> > > On all the machine I ghosted from former harddrive 9GB to new

> > > harddrive 80GB.

> > > No problems.

> > > On this one machine I have ghosted in the usual fashion the 9GB to

> > > the

> > > 80GB drive.

> > > And I did this on two new fresh WD harddrives ending up with (after

> > > installing the newly Ghosted drive) this Blue Screen

>

> > > Stop 000000007B and so on ending with Inaccessible_Boot_Device.

>

> > > I've ran the Ghost several times and ending with the blue screen

> > > message.

> > > In Bios I alter the device to auto, and it is found. Bios fine.

> > > I can upon reboot launch safe, safe with networking, LKG, and so on.

> > > However, the bluescreen appears in every instance with the Stop /

> > > Device bluescreen message.

>

> > > I've been successful on all the machines, all the same OS, ghosting;

> > > and this computer is proving to be a problem. Is there a solution?

> > > Let

> > > me know. Thanks John M- Hide quoted text -

>

> > - Show quoted text -

>

> All the machines are identitcal. I even used three identical computers

> using the same cable ; primary ; auto detect. If I return the old hard

> drive, no issue ; and insert the ghosted hard drive ; problem. I've

> followed on all the computers (all the same model) this exact

> procedure ...WD format on the new hard drive - checking cmos for hard

> drive (old) master ; hard drive new (slave) and then Ghosting.

>

> Returning cmos to the original setting hard drive primary ; no slave.

> And getting a blue screen on reboot boot. Than I replace the new hard

> drive with the old hard drive and no issues.

>

> Now I could see problems if a few of the computers were to give me

> ghosting troubles ....but 11 computer ; all exact model ; the exact

> ghosting procedure - and everything without a hitch until this current

> situation with Joe's computer.

>

> Thanks

> ==============

> The machines are obviously not identical. If they were then you would not

> have the problem. I have come across similar issues - they were caused by

> one machine having a slightly different chip set. A repair installation

> might fix the problem.- Hide quoted text -

>

> - Show quoted text -

 

Yes...I can agree...even though these are all Dell Optiplex 110. The

'only' difference is the Mhz.

I don't understand a repair installation. Just a short comment on that

and I'll be willing to do a repair.

 

charlie

[Guest John John (MVP)]

Re: Ghosting Issue

 

Parvardigar wrote:

> Yes...I can agree...even though these are all Dell Optiplex 110. The

> 'only' difference is the Mhz.

> I don't understand a repair installation. Just a short comment on that

> and I'll be willing to do a repair.

 

How to perform an in-place upgrade of Windows 2000

http://support.microsoft.com/kb/292175

 

John

[Guest Sid Elbow]

Re: Ghosting Issue

 

Parvardigar wrote:

> On all the machine I ghosted from former harddrive 9GB to new

> harddrive 80GB.

> No problems.

> On this one machine I have ghosted in the usual fashion the 9GB to

> the

> 80GB drive.

> And I did this on two new fresh WD harddrives ending up with (after

> installing the newly Ghosted drive) this Blue Screen

>

> Stop 000000007B and so on ending with Inaccessible_Boot_Device.

 

I'm a bit vague on this because I'm going from memory and my memory

these days, well ....

 

It seems to me I ran into this myself when trying to restore a ghost

image to a fresh, unpartitioned drive. Never found out the cause but I

believe I got round it by manually creating (and perhaps formatting) an

empty partition on the drive first and then restoring to (overwriting)

that. At any rate it can't hurt to try before you take more drastic

measures.

[Guest Parvardigar]

Re: Ghosting Issue

 

On Oct 22, 10:44 am, "John John (MVP)" <audetw...@nbnet.nb.ca> wrote:

> Parvardigar wrote:

>

>   > Yes...I can agree...even though these are all Dell Optiplex 110. The

>

> > 'only' difference is the Mhz.

> > I don't understand a repair installation. Just a short comment on that

> > and I'll be willing to do a repair.

>

> How to perform an in-place upgrade of Windows 2000http://support.microsoft.com/kb/292175

>

> John

 

There are two issues. If I alter cmos to boot first, to cd, for some

reason it boots to the hard drive. I can boot off the win98 setup

disks to get access to the Cd rom; but, because the drive is NTFS, the

Windows 2000 setup is unable to run an install because it is unable to

recognize the c:/ drive NTFS partition.

 

Even if I could overwrite C:\windows with \i386 I would loose the

registry so that would defeat the whole Ghosting operation.

I'm am Ghosting with accounting software on this drive and I need a

prestine Ghost.

 

Thanks

 

 

Thanks

[Guest Pegasus \(MVP\)]

Re: Ghosting Issue

 

 

"Parvardigar" <parvardigar@yahoo.com> wrote in message

news:a45a6472-b6ca-44bc-ab0f-de5a669d0e98@u29g2000pro.googlegroups.com...

On Oct 22, 10:44 am, "John John (MVP)" <audetw...@nbnet.nb.ca> wrote:

> Parvardigar wrote:

>

> > Yes...I can agree...even though these are all Dell Optiplex 110. The

>

> > 'only' difference is the Mhz.

> > I don't understand a repair installation. Just a short comment on that

> > and I'll be willing to do a repair.

>

> How to perform an in-place upgrade of Windows

> 2000http://support.microsoft.com/kb/292175

>

> John

 

There are two issues. If I alter cmos to boot first, to cd, for some

reason it boots to the hard drive. I can boot off the win98 setup

disks to get access to the Cd rom; but, because the drive is NTFS, the

Windows 2000 setup is unable to run an install because it is unable to

recognize the c:/ drive NTFS partition.

 

Even if I could overwrite C:\windows with \i386 I would loose the

registry so that would defeat the whole Ghosting operation.

I'm am Ghosting with accounting software on this drive and I need a

prestine Ghost.

 

Thanks

=============

I can think of two reasons why you cannot boot the machine with your Win2000

installation CD.

a) The CD is damaged. Have you tried it on a different PC?

b) You have not configured your BIOS to boot from the CD. Have you tried

booting the machine with a WinXP CD?

 

Regardless of the above, AFAIR a Repair Installation will leave your

software settings (e.g. your accounting program) intact. Even if it does not

you have nothing to lose - you can always re-image the machine.

 

Thanks