FIXMBR redux

Thanks, Michael. I'm happy that I saw the same possible source
of the hang up as I saw. As for starting from scratch, of course
I can put my present system away for a backup, and start from scratch,
with a new install of XP and try to find source software for every
program that's in my Program Files. I have the opinion that there
would be some I'd never find, and that it would be a herculean
effort. I'm going to try a no-Norton and disconnected from the line
approach, to see what happens. The two articles......interesting
information, but I don't see that they give me anything I can
actually do.
WBL

Michael Solomon (MS-MVP Windows Shell/User) wrote:

"BTW, Michael, I understand your "have both drives alive when you
install XP" suggestion, but that is probably two orders of magnitude
more impractical than the NSW uninstall."

LOL, yes, I know you've been trying to avoid the start from scratch
scenario. On the other hand, if you consider the time you've invested here,
you just about could have started from scratch.

Yes, I'd have to agree about Norton and there is a possibility the whole
thing is choking on that.

Okay, here's an KB article about afd.sys:
http://support.microsoft.com/default...b;EN-US;174465

Take it with a grain of salt. The fact is the system stops in the midst of
loading hardware drivers and that puts me back at the anti-piracy scenario.
That article makes reference to bad SAP packets being sent over the network.

Here's the KB on the other item:
http://support.microsoft.com/default.aspx?kbid=329175

Problem is, I seem to recall these failures in both bootlogs so they may not
be relevant.



--
William B. Lurie

If I do msconfigdiagnostic startup (load basic stuff
only).....and boot that way, then make a Copy of the
drive (or Drive Image of the drive).......and then try
loading that copy......will it boot up with only the
basic services, or will it try to do a full load of
my start-up list?
--
Bill Lurie

Dear Michael and Sharon:
You'll be pleased to learn that your efforts and my
persistence seem to have just about solved the problem.
What I did to create a bootable clone of my Master Drive
was essentially this:
Booted Master Drive.
Did msconfig and did Selective Startup.
UNchecked the one startup entry which had Symantec
in its description. (ccApp, whatever that is)
Rebooted.
Cleared ntbtlog.
Used Drive Image 7 to`Copy Master Drive C: partition to
Slave Drive, J: partition, first partition on
the drive, primary, active partition. With MBR.
I selected the option "Make bootable".
Then I shut down, jumpered Clone as Master, put it in
"only drive" on the cable, and booted normally,
but with bootlog, because I expected it to fail.
It fooled me. It booted right up, and I saved its bootlog,
and the Master's bootlog and Clone bootlog are at

http://bellsouthpwp.net/b/i/billurie/ntbtlog6.txt
and
http://bellsouthpwp.net/b/i/billurie/ntbtlog7.txt

I suppose I could carry the test further by actually deactivating
Norton System Works in its own application program, and
making new bootlogs, because both the above still show some Symantec
loading. But there is no need to gild the lily, nor to bother you
nice people interminably. I hope that my efforts might some day
help you to help other poor unfortunates such as I was and am.
And if you want to study the above bootlogs and tell me anything
worthwhile that they tell you, I'd be most happy to learn even
more.

G'night, and thank you again.



--
William B. Lurie

Michael & Sharon:
I studied the two bootlogs which I posted in my message
an hour or so ago......and I found them quite
interesting and informative. The contents of the two
bootlogs are, I believe, identical, but the entries,
which are presumably in order time-wise, are in
different order in the two logs. Now I know the old
proverb about looking a gift horse in the mouth...
(I remember my grandmother reciting it in German
around 1935). But I found it interesting nonetheless.

Perhaps you can tell me what "ccapp" is, that I deselected
from my Startup list....and why, if there's no Symantec
in my Startup list, I still find it loading in bootlogs.

I have not tried to energize the Norton software on the
clone, because I've found in the past that they are
inclined to sniff and find reasons not to "activate"
a second hard drive, no matter what its ancestry is.
I have no need to go online with the clone. Its purpose
is to be a guaranteed substitute if and when the Master
fails. I'm satisfied that I now have that.
--
William B. Lurie

And another semi-final note:
My cloned Master is on its own hard drive.
I can boot to it if I jumper it as Master,
just like the real Master.
Or if I jumper it as Slave and mount
it with the Master, I can make a minor change in
my BIOS and boot to either hard drive at will.

I have left the "Go to XP or to Recovery Console"
option in boot-up, because it isn't hurting
anything, and only wastes a few seconds in booting.
Not that the RC option would work, if I needed it;
it stops with a message like "file hal.dll is
missing and needs to be reloaded". *That* surely
isn't broke enough to fix, after all we've been
through!

And again, thanks to all the people who have
patiently helped on this cloning problem.
William B. Lurie

On Fri, 4 Jun 2004 16:48:45 -0500, "*Vanguard*"
wrote:

William B. Lurie said in :
Sharon F wrote:
On Wed, 02 Jun 2004 07:40:05 -0400, William B. Lurie wrote:

snip]

So I went back to where I was a month ago, when I tried making
what PowerQuest describes as a "copy". I installed my Slave
drive as Master and formatted it anew, as Active and Primary,
and empty. I then jumpered it as Slave, put it in Slave
position, put my Master on as Master, and used Drive Image 7.0
to "Copy One Drive to Another This copes the contents of
your Drive directly to another drive". Actually, I copied only
the first (Master) partition of my Master Drive to the Slave.

I've not used it, but presumably your doing ALL OF THIS using Drive
Image's PQRE ?.


I used Partition Magic to verify that the Slave Drive contained
very close to the same number of bytes as the Master OS. I then
shut down, jumpered the Slave Drive as a Single Drive, put it in
Master position on the cable, no other drive present, and booted
up. It got to where I was when I did this same thing a month
ago, so at least it's reproducible. It booted through BIOS, to
the place where I could select XP Pro or Recovery Console, I
picked XP, and got the black Windows logo screen, and then after
the usual wait, the light blue Windows logo screen, which should
say "loading your personal settings"........and there it hangs.

[snip]

Boy, sure sounds like what you did should have worked. The only thing
that comes to mind at the moment is disk signatures. Each disk has an
area where a unique signature of hex bytes get written to it. Windows
NT/2000/XP will use the signatures to identify the device. That is why
you can configure a partition on a disk as C:, insert a new hard drive
in the physical scan chain that positions it before your old drive, and
C: will still be seen as the partition on your now second hard drive.

And this, I think, is the key !

I just reproduced this behaviour on a testbed system, by changing the
logical drive letter assigned to a System/Boot Volume from C: to G:...


In your case, however, I will bet that it is the exact opposite of my
test. ie Your System/Boot Volume is G: (or perhaps another drive
letter).

Window Setup will do this sometimes, when there is an existing primary
partition, setting it up the new Windows installation to boot from a
Logical partition, which is usually mounted as G:. Some Brand-name
systems will, consequently, be shipped this way.

Basically, when the 'cloned' copy is booted, it's Disk signature, if it
has one, is NOT the same as the original, and thus when Windows looks in
the registry at boot-up (HKLM\SYSTEM\MountedDevices), there isn't an
entry for it, and it will then assign this 'new' volume a drive letter
based upon the 'order' it enumerates partitions/volumes. In this case,
first Active Primary Partition on the first Hard disk, it will be C:.

In other words, at the Welcome screen, Windows tries to initate various
logon and setup tasks, which are stored within the registry (likely the
user-related stuff), but it is failing or try to look in the wrong
place.

Specifically what it's trying to load, I don't know (yet). But it is
probably the whole of the 'user' Registry Hive. Why it doesn't produce
an error message, I think, is just an oversight (bug).

So what to do ?

Looking through the Drive Image 7.0 Help file ("Restoring a Single Drive
Using the PQRE"), there is an option to "Restore the original disk
signature". Try enabling that.

If that doesn't work, then things are likely to get ugly (technical). If
you really want to resolve this, I'll (we'll) need more details about
the system setup. First and foremost, is the wether the System/Boot
Volume is C: or not. Other low-level details, such as those presented by
PowerQuest's PTEDIT32.EXE utility, may be needed. It should be installed
already, in the "Program Files\PowerQuest\Drive Image 7.0\UTILITY"
folder.

I don't have a copy of Drive Image 7.0 here, either.

[snip]


PS: I stumbled across this thread from a link on the Windows XP expert
forums. I don't normally subscribe to this newsgroup, and had to
subscribe to answer this message. I have NOT read all of the other
messages, yet either, so be aware [Insert usually warnings, going of
half-cocked, etc] .

PPS: like others on this forum (I'm sure), I'm quite busy, so don't
expect too much from me. But I hope I was able to contribute. I'll
likely unsubscribe from this group, as it's generally not one that I am
interested in. But time permitting, I'll try to monitor this thread for
a few days.

William B. Lurie said in :
*Vanguard* wrote:
William B. Lurie said in :
snip

It would be awfully nice
to repeat this bootlog experiment with all Norton software
deactivated, as a first step. As a second step, I could repeat it
with NSW out, uninstalled, but that, unfortunately, is an
unfortunate thought, because it is virtually impossible to
uninstall. But taking it out
of the startup menu might make it harmless, and not load, and maybe
not stand in the way.


Disabling the services that startup was one of my earlier suggestions
but you'll need to install the Recovery Console to do so. See my
message at . Just do
that when you have the clone drive as the master and only drive in
the host (so you are modifying the configuration of its NT services
and not of your master drive). That way you can see if configuring
the Norton service to be disabled so they don't startup fixes your
hang problem.

But I am not able to get the clone to load fully as Master. And I
don't think I can make RC load with Clone as Master (I get a DOS
message like xxxxx.dll not found or something like that. I
think I can take NSW out of the start-up menu, and pull
my ISP connection, make a new bootlog and then a new clone and see
if maybe the new clone will load. I can try that later today. And
thanks again for stepping in.

Sorry to get back so late. Been recovering my system (I shot myself in
my foot by monkeying around with the MBR and screwed up the partition
table).

You can also load the Recovery Console without installing it. Boot
using the Windows XP install CD. The first Repair option will load the
Recovery Console (I think it uses a ramdrive). It is the second Repair
option that will exercise a Repair on an install of Windows XP on the
hard drive.

So I was wrong that you need to install the Recovery Console in order to
use it. I just loaded it myself using the install CD so I could run
FIXMBR to restore the bootstrap program in the MBR. When you load the
Recovery Console from the install CD, your drive letters might change so
be careful as to which one you use. However, you get to select which OS
to log into and so any disable commands entered while logged in under
that instance would disable the service only in that instance of
Windows.

--
__________________________________________________ __________
*** Post replies to newsgroup. Share with others.
*** Email domain = ".com" *AND* append "=NEWS=" to Subject.
__________________________________________________ __________

William B. Lurie said in :
Michael & Sharon:
I studied the two bootlogs which I posted in my message
an hour or so ago......and I found them quite
interesting and informative. The contents of the two
bootlogs are, I believe, identical, but the entries,
which are presumably in order time-wise, are in
different order in the two logs. Now I know the old
proverb about looking a gift horse in the mouth...
(I remember my grandmother reciting it in German
around 1935). But I found it interesting nonetheless.

Perhaps you can tell me what "ccapp" is, that I deselected
from my Startup list....and why, if there's no Symantec
in my Startup list, I still find it loading in bootlogs.

I have not tried to energize the Norton software on the
clone, because I've found in the past that they are
inclined to sniff and find reasons not to "activate"
a second hard drive, no matter what its ancestry is.
I have no need to go online with the clone. Its purpose
is to be a guaranteed substitute if and when the Master
fails. I'm satisfied that I now have that.

ccapp.exe = Common Client Application
Used and shared by several Symantec products, like Norton AntiVirus and
Norton Internet Security (firewall).

Besides the Norton programs listed in the Startup panel in msconfig.exe,
you also have to disable the Norton services under the Services panel
(or use services.msc).

--
__________________________________________________ __________
*** Post replies to newsgroup. Share with others.
*** Email domain = ".com" *AND* append "=NEWS=" to Subject.
__________________________________________________ __________

Van, you said:

ccapp.exe = Common Client Application
Used and shared by several Symantec products, like Norton AntiVirus and
Norton Internet Security (firewall).

Besides the Norton programs listed in the Startup panel in msconfig.exe,
you also have to disable the Norton services under the Services panel
(or use services.msc).

Services panel? I should search and find services.msc ?? Or what?

Note my story about Recovery Console... I installed it long ago...
But as one of my messages says, there's a file missing and it
won't go there even when I choose that option rather than XP.
--
William B. Lurie

William B. Lurie said in :
Van, you said:

ccapp.exe = Common Client Application
Used and shared by several Symantec products, like Norton AntiVirus
and Norton Internet Security (firewall).

Besides the Norton programs listed in the Startup panel in
msconfig.exe, you also have to disable the Norton services under the
Services panel (or use services.msc).

Services panel? I should search and find services.msc ?? Or what?

Just run it in the Run dialog (Start - Run or hitting Windows+R to get
the command input dialog); the "services.msc" file should already be in
your PATH environment variable to find it for execution (otherwise, it
is under %systemroot%\system32, or under Start - Programs -
Administrative Tools). It is an MMC applet (you can run mmc.exe to roll
your own by adding snap-ins to your custom MMC applet, which I did for
certificate management). Or look under the Services panel in
msconfig.exe (although I don't think that is as helpful at identifying
the Norton services since several are listed as "unknown" for their
author).

Note my story about Recovery Console... I installed it long ago...
But as one of my messages says, there's a file missing and it
won't go there even when I choose that option rather than XP.

There is no such xxxxx.dll file so I don't know what file you really
meant to indicate was noted as missing. If it is not part of Windows
(i.e., the Recovery Console needs some file from the Windows install and
doesn't provide it itself) then an install of the Recovery Console
should include that file. There are 65 .dl? files under the C:\cmdcons
subdirectory and if it is one of them that you see a message complaining
that it is missing then a reinstall of the Recovery Console should bring
it back.

You could simply run "d:\i386\winnt32.exe /cmdcons" from the install
CD to install it atop of itself. Or just pick the first "Repair" option
when booting from the install CD to have it create a ramdisk into which
the recovery files are stored (so you don't have to install it but just
instead run it from memory off the ramdisk). See
http://support.microsoft.com/?id=310602 (I don't remember having to hit
"C" after hitting "R" for the first Repair option presented during the
boot from the install CD).

Below is the folder and file list using PC Mag's TreePrint utility for
the C:\cmdcons subdirectory on my host:

TreePrint listing of: C:\cmdcons

C:\cmdcons
| 1394bus.sy_
| abp480n5.sy_
| acpi.sy_
| acpiec.sy_
| adpu160m.sy_
| aha154x.sy_
| aic78u2.sy_
| aic78xx.sy_
| aliide.sy_
| amsint.sy_
| asc.sy_
| asc3350p.sy_
| asc3550.sy_
| atapi.sy_
| autochk.exe
| autofmt.exe
| biosinfo.inf
| BOOTSECT.DAT
| bootvid.dl_
| c_1252.nl_
| c_437.nl_
| cbidf2k.sy_
| cd20xrnt.sy_
| cdfs.sy_
| cdrom.sy_
| classpnp.sy_
| cmdide.sy_
| cpqarray.sy_
| dac2w2k.sy_
| dac960nt.sy_
| disk.sy_
| disk101
| disk102
| disk103
| disk104
| dmboot.sy_
| dmio.sy_
| dmload.sy_
| dpti2o.sy_
| drvmain.sdb
| fastfat.sy_
| fdc.sy_
| flpydisk.sy_
| ftdisk.sy_
| hal.dl_
| halaacpi.dl_
| halacpi.dl_
| halapic.dl_
| hidclass.sy_
| hidparse.sy_
| hidusb.sy_
| hpn.sy_
| i2omgmt.sy_
| i2omp.sy_
| i8042prt.sy_
| ini910u.sy_
| intelide.sy_
| isapnp.sy_
| KBDAL.DLL
| KBDBE.DLL
| KBDBLR.DLL
| KBDBR.DLL
| KBDBU.DLL
| KBDCA.DLL
| kbdclass.sy_
| KBDCR.DLL
| KBDCZ.DLL
| KBDCZ1.DLL
| KBDDA.DLL
| KBDDV.DLL
| KBDES.DLL
| KBDEST.DLL
| KBDFC.DLL
| KBDFI.DLL
| KBDFR.DLL
| KBDGKL.DLL
| KBDGR.DLL
| KBDGR1.DLL
| KBDHE.DLL
| KBDHE220.DLL
| KBDHE319.DLL
| KBDHELA2.DLL
| KBDHELA3.DLL
| kbdhid.sy_
| KBDHU.DLL
| KBDHU1.DLL
| KBDIC.DLL
| KBDIR.DLL
| KBDIT.DLL
| KBDIT142.DLL
| KBDLA.DLL
| KBDLT.DLL
| KBDLV.DLL
| KBDLV1.DLL
| KBDNE.DLL
| KBDNO.DLL
| KBDPL.DLL
| KBDPL1.DLL
| KBDPO.DLL
| KBDRO.DLL
| KBDRU.DLL
| KBDRU1.DLL
| KBDSF.DLL
| KBDSG.DLL
| KBDSL.DLL
| KBDSL1.DLL
| KBDSP.DLL
| KBDSW.DLL
| KBDTUF.DLL
| KBDTUQ.DLL
| KBDUK.DLL
| KBDUR.DLL
| kbdus.dll
| KBDUSL.DLL
| KBDUSR.DLL
| KBDUSX.DLL
| KBDYCC.DLL
| KBDYCL.DLL
| kd1394.dl_
| kdcom.dl_
| ksecdd.sys
| l_intl.nl_
| lbrtfdc.sy_
| migrate.inf
| mountmgr.sy_
| mraid35x.sy_
| ntdetect.com
| ntfs.sys
| ntkrnlmp.ex_
| ohci1394.sy_
| oprghdlr.sy_
| partmgr.sy_
| pci.sy_
| pciide.sy_
| pciidex.sy_
| pcmcia.sy_
| perc2.sy_
| perc2hib.sy_
| ql1080.sy_
| ql10wnt.sy_
| ql12160.sy_
| ql1240.sy_
| ql1280.sy_
| ramdisk.sy_
| sbp2port.sy_
| scsiport.sy_
| serenum.sy_
| serial.sy_
| setupdd.sy_
| setupldr.bin
| setupreg.hiv
| sfloppy.sy_
| sparrow.sy_
| spcmdcon.sys
| spddlang.sy_
| sym_hi.sy_
| sym_u3.sy_
| symc810.sy_
| symc8xx.sy_
| tffsport.sy_
| toside.sy_
| txtsetup.sif
| ultra.sy_
| usbccgp.sy_
| usbd.sy_
| usbehci.sy_
| usbhub.sy_
| usbohci.sy_
| usbport.sy_
| usbstor.sy_
| usbuhci.sy_
| vga.sy_
| vgaoem.fo_
| viaide.sy_
| videoprt.sy_
| winnt.sif
| wmilib.sy_
|
\---system32
ntdll.dll
smss.exe

Although the C:\cmdcons folder has the system, hidden, and read-only
attributes set for it, the files and folders underneath are not hidden,
so this treelist should be complete.

--
__________________________________________________ __________
*** Post replies to newsgroup. Share with others.
*** Email domain = ".com" *AND* append "=NEWS=" to Subject.
__________________________________________________ __________

Again, thanks, Vang, for the detailed and informative
posting. I have saved it in my separate large file
on this subject, and I may have the courage to follow
where it leads, but not right now. It is too big an
undertaking, I fear. It's almost a case of the cure
being worse than living with the disease.

Just one point: the error message which appears when
I select RC at boot-up, I quoted exactly and completely.
I noted that the last component of the sequence which
should have defined the extension of the reportedly
'missing' file didn't really identify it, but that's
what was on my screen.
Bill L.

*Vanguard* wrote:
William B. Lurie said in :

Van, you said:

ccapp.exe = Common Client Application
Used and shared by several Symantec products, like Norton AntiVirus
and Norton Internet Security (firewall).

Besides the Norton programs listed in the Startup panel in
msconfig.exe, you also have to disable the Norton services under the
Services panel (or use services.msc).

Services panel? I should search and find services.msc ?? Or what?


Just run it in the Run dialog (Start - Run or hitting Windows+R to get
the command input dialog); the "services.msc" file should already be in
your PATH environment variable to find it for execution (otherwise, it
is under %systemroot%\system32, or under Start - Programs -
Administrative Tools). It is an MMC applet (you can run mmc.exe to roll
your own by adding snap-ins to your custom MMC applet, which I did for
certificate management). Or look under the Services panel in
msconfig.exe (although I don't think that is as helpful at identifying
the Norton services since several are listed as "unknown" for their
author).


Note my story about Recovery Console... I installed it long ago...
But as one of my messages says, there's a file missing and it
won't go there even when I choose that option rather than XP.


There is no such xxxxx.dll file so I don't know what file you really
meant to indicate was noted as missing. If it is not part of Windows
(i.e., the Recovery Console needs some file from the Windows install and
doesn't provide it itself) then an install of the Recovery Console
should include that file. There are 65 .dl? files under the C:\cmdcons
subdirectory and if it is one of them that you see a message complaining
that it is missing then a reinstall of the Recovery Console should bring
it back.

You could simply run "d:\i386\winnt32.exe /cmdcons" from the install
CD to install it atop of itself. Or just pick the first "Repair" option
when booting from the install CD to have it create a ramdisk into which
the recovery files are stored (so you don't have to install it but just
instead run it from memory off the ramdisk). See
http://support.microsoft.com/?id=310602 (I don't remember having to hit
"C" after hitting "R" for the first Repair option presented during the
boot from the install CD).

Below is the folder and file list using PC Mag's TreePrint utility for
the C:\cmdcons subdirectory on my host:

TreePrint listing of: C:\cmdcons

C:\cmdcons
| 1394bus.sy_
| abp480n5.sy_
| acpi.sy_
| acpiec.sy_
| adpu160m.sy_
| aha154x.sy_
| aic78u2.sy_
| aic78xx.sy_
| aliide.sy_
| amsint.sy_
| asc.sy_
| asc3350p.sy_
| asc3550.sy_
| atapi.sy_
| autochk.exe
| autofmt.exe
| biosinfo.inf
| BOOTSECT.DAT
| bootvid.dl_
| c_1252.nl_
| c_437.nl_
| cbidf2k.sy_
| cd20xrnt.sy_
| cdfs.sy_
| cdrom.sy_
| classpnp.sy_
| cmdide.sy_
| cpqarray.sy_
| dac2w2k.sy_
| dac960nt.sy_
| disk.sy_
| disk101
| disk102
| disk103
| disk104
| dmboot.sy_
| dmio.sy_
| dmload.sy_
| dpti2o.sy_
| drvmain.sdb
| fastfat.sy_
| fdc.sy_
| flpydisk.sy_
| ftdisk.sy_
| hal.dl_
| halaacpi.dl_
| halacpi.dl_
| halapic.dl_
| hidclass.sy_
| hidparse.sy_
| hidusb.sy_
| hpn.sy_
| i2omgmt.sy_
| i2omp.sy_
| i8042prt.sy_
| ini910u.sy_
| intelide.sy_
| isapnp.sy_
| KBDAL.DLL
| KBDBE.DLL
| KBDBLR.DLL
| KBDBR.DLL
| KBDBU.DLL
| KBDCA.DLL
| kbdclass.sy_
| KBDCR.DLL
| KBDCZ.DLL
| KBDCZ1.DLL
| KBDDA.DLL
| KBDDV.DLL
| KBDES.DLL
| KBDEST.DLL
| KBDFC.DLL
| KBDFI.DLL
| KBDFR.DLL
| KBDGKL.DLL
| KBDGR.DLL
| KBDGR1.DLL
| KBDHE.DLL
| KBDHE220.DLL
| KBDHE319.DLL
| KBDHELA2.DLL
| KBDHELA3.DLL
| kbdhid.sy_
| KBDHU.DLL
| KBDHU1.DLL
| KBDIC.DLL
| KBDIR.DLL
| KBDIT.DLL
| KBDIT142.DLL
| KBDLA.DLL
| KBDLT.DLL
| KBDLV.DLL
| KBDLV1.DLL
| KBDNE.DLL
| KBDNO.DLL
| KBDPL.DLL
| KBDPL1.DLL
| KBDPO.DLL
| KBDRO.DLL
| KBDRU.DLL
| KBDRU1.DLL
| KBDSF.DLL
| KBDSG.DLL
| KBDSL.DLL
| KBDSL1.DLL
| KBDSP.DLL
| KBDSW.DLL
| KBDTUF.DLL
| KBDTUQ.DLL
| KBDUK.DLL
| KBDUR.DLL
| kbdus.dll
| KBDUSL.DLL
| KBDUSR.DLL
| KBDUSX.DLL
| KBDYCC.DLL
| KBDYCL.DLL
| kd1394.dl_
| kdcom.dl_
| ksecdd.sys
| l_intl.nl_
| lbrtfdc.sy_
| migrate.inf
| mountmgr.sy_
| mraid35x.sy_
| ntdetect.com
| ntfs.sys
| ntkrnlmp.ex_
| ohci1394.sy_
| oprghdlr.sy_
| partmgr.sy_
| pci.sy_
| pciide.sy_
| pciidex.sy_
| pcmcia.sy_
| perc2.sy_
| perc2hib.sy_
| ql1080.sy_
| ql10wnt.sy_
| ql12160.sy_
| ql1240.sy_
| ql1280.sy_
| ramdisk.sy_
| sbp2port.sy_
| scsiport.sy_
| serenum.sy_
| serial.sy_
| setupdd.sy_
| setupldr.bin
| setupreg.hiv
| sfloppy.sy_
| sparrow.sy_
| spcmdcon.sys
| spddlang.sy_
| sym_hi.sy_
| sym_u3.sy_
| symc810.sy_
| symc8xx.sy_
| tffsport.sy_
| toside.sy_
| txtsetup.sif
| ultra.sy_
| usbccgp.sy_
| usbd.sy_
| usbehci.sy_
| usbhub.sy_
| usbohci.sy_
| usbport.sy_
| usbstor.sy_
| usbuhci.sy_
| vga.sy_
| vgaoem.fo_
| viaide.sy_
| videoprt.sy_
| winnt.sif
| wmilib.sy_
|
\---system32
ntdll.dll
smss.exe

Although the C:\cmdcons folder has the system, hidden, and read-only
attributes set for it, the files and folders underneath are not hidden,
so this treelist should be complete.



--
William B. Lurie

try this... get an old windows 9x start-up floppy and use the dos FDISK command firstly to list the partitions on your cloned drive, and then to set the appropriate one as the boot-up partition (I forget whether it's called boot or system or whatever). I r
ecently found that unless the boot-up partition is marked as such, then XP will simply not boot from it. If no partition is marked as bootable then XP refuses to boot from any partition.

MS has not given the XP user any tools to set the boot partition before XP has already booted up (by which time the tools are not needed). Naturally I think this situation is a pathetic oversight on the part of MS, but I'm sure they'll be really worried by
that :-)

Oh, nearly forgot... I had used FIXMBR and some of the other stuff from the XP recovery console but nothing in RC does what the old FDISK does. There's nothing else on the XP installation CD to help.

One more thing... don't worry if FDISK thinks the partition is much smaller than it really is. All we're doing here is setting the flag in the MBR to let XP know which partition it is possible to boot from. Once you have done that, get out of fdisk and boo
t from your hard disk.

cheers.



"William B. Lurie" wrote:

I think this leads back to my discussions with, and
advice from, Michael Solomon a while back.......

Since 'solving' the problems of creating a drive image
of my master hard drive with Drive Image 7, and creating
a clone of that drive with its PowerQuest Recovery
Environment software, I've been living is a fool's
paradise. I discovered this when I went to create the
monthly Drive Image yesterday, and create the clone on
a newly purchased hard drive.

I've been living with my Master drive booting to a
choice between normal start-up and Recovery Console,
a minor annoyance because after a ten-second countdown
it goes to normal boot, automatically. No problem there.

I believe that the main part of the problem is now that
the new exact clone does not have Master Boot Record
correct, because the 'Normal Boot' path leads to the
choices of Safe Mode or Normal etcetera, and no choice
gets to anything other than a repeat of that set of
choices. If I select Recovery Console, I get a short
DOS-type message saying that file 'xxxxx.dll' is missing,
and to reload it somehow from somewhere. I suspect that
more than one '.dll' file will be in the list of what it
needs. I tried selecting Recovery Console, hoping that I
could somehow do a FIXMBR there, but I can't get to RC.

Incidentally, in running Drive Image, I've repeated the
whole image-and-recreate process, with and without the
'keep the MBR' option, with no apparent difference in
results. I've tried to solve the problem without going to
you experts, but what I've considered all logical paths
haven't solved it.

William B. Lurie

"Alan F." Alan wrote in message
...
try this... get an old windows 9x start-up floppy and use the dos FDISK
command firstly to list the partitions on your cloned drive, and then to
set the appropriate one as the boot-up partition (I forget whether it's
called boot or system or whatever). I recently found that unless the
boot-up partition is marked as such, then XP will simply not boot from it.
If no partition is marked as bootable then XP refuses to boot from any
partition.

MS has not given the XP user any tools to set the boot partition before XP
has already booted up (by which time the tools are not needed). Naturally
I think this situation is a pathetic oversight on the part of MS, but I'm
sure they'll be really worried by that :-)

Oh, nearly forgot... I had used FIXMBR and some of the other stuff from
the XP recovery console but nothing in RC does what the old FDISK does.
There's nothing else on the XP installation CD to help.

One more thing... don't worry if FDISK thinks the partition is much
smaller than it really is. All we're doing here is setting the flag in the
MBR to let XP know which partition it is possible to boot from. Once you
have done that, get out of fdisk and boot from your hard disk.

cheers.

LOL!

Michael Solomon (MS-MVP Windows Shell/User) wrote:

If PartitionMagic or DriveImage really don't include the MBR in whatever

version you have, and if you were looking to copy the MBR from the
source drive to the cloned drive, use mbrutil from Powerquest. Go to:

ftp://ftp.symantec.com/public/englis.../pq/utilities/

and download head.zip.


Michael, I am back on the cloning matter, and followed your advice
as mentioned above. I found 'head' and 'mbrutil', and unzipped
and created a folder for those files. But from their shorthand,
I can't seem to find a syntax for MBRUTIL which will recover the MBR
and save it to a file (named, say 'savedmbr.xxx' where I don't
know what extension to use), and then, if I can save that file,
just how do I apply it to my cloned hard drive, running as
D:, my Slave Drive?

And, while I'm about it, you'll recall that booting asks for choice
of XP or RC, with a 10-second default at the moment. Since mine
won't go to RC anyway if I were to select that option, claiming
that some .dll file is missing, can you tell me how to eliminate that
option altogether (not just set it to zero time, but delete the option)?
I wouldn't do it on my Master Drive, because I'd be afraid of breaking
it, but it's something I can do on the Slave while running the Master.
It might even help it to become bootable.

Thank you.

William B. Lurie

You should have used XCOPY in xp for cloneing the hd,it works...
If the drive happens to be missing files/folders you should run as
master,boot to xp cd,select,install xp,repair xp.Or you can run youre 3rd
party noncense and figure out all the problems like you have...

"William B. Lurie" wrote:

Michael Solomon (MS-MVP Windows Shell/User) wrote:

If PartitionMagic or DriveImage really don't include the MBR in whatever

version you have, and if you were looking to copy the MBR from the
source drive to the cloned drive, use mbrutil from Powerquest. Go to:

ftp://ftp.symantec.com/public/englis.../pq/utilities/

and download head.zip.


Michael, I am back on the cloning matter, and followed your advice
as mentioned above. I found 'head' and 'mbrutil', and unzipped
and created a folder for those files. But from their shorthand,
I can't seem to find a syntax for MBRUTIL which will recover the MBR
and save it to a file (named, say 'savedmbr.xxx' where I don't
know what extension to use), and then, if I can save that file,
just how do I apply it to my cloned hard drive, running as
D:, my Slave Drive?

And, while I'm about it, you'll recall that booting asks for choice
of XP or RC, with a 10-second default at the moment. Since mine
won't go to RC anyway if I were to select that option, claiming
that some .dll file is missing, can you tell me how to eliminate that
option altogether (not just set it to zero time, but delete the option)?
I wouldn't do it on my Master Drive, because I'd be afraid of breaking
it, but it's something I can do on the Slave while running the Master.
It might even help it to become bootable.

Thank you.

William B. Lurie