hawksbill666 said:
I did notice the Acronis tech support guy popping in- like for
the Solaris
image that doubled hard drives and partitions- but most
fundamental problems
seem to based on following (hidden?) directions as a last
resort. I trusted
my 27 yrs. of network pre-to-post MS-DOS hardware experience
on an
exasperating XP Pro_W2K dual boot licking via PM by not
reading ~everything~
beforehand. But it did lead me to a very helpful site I may
not have
otherwise tripped over:
http://www.mdgx.com/secrets.htm#FDPT
> >>Precisely the reason I ditched PM and bought
Acronis Disk Director
> >>(
www.acronis.com) as it appears to be the only
company with the foresight
> >>to
> >>realise that fact. It will allow you to make a
bootable rescue CD (it's
> >>the
> >>same with its imaging application - True Image
- too, I believe that Ghost
> >>only creates floppies).
> >
> > I've heard many good things about Acronis in this
newsgroup. I
> > downloaded the evaluation version but haven't got
around to
> > installing it -- struggling along with NTI Backup
for now. Seems
> > like I need to make Acronis a priority. Thanks for
the extra nudge!
> >
> > --
> >
> > Stan Brown, Oak Road Systems, Tompkins County, New
York, USA
> >
http://OakRoadSystems.com/
Hello, I made the same mistake of assuming that PM wouldn’t be prone
to such a stupid error as this, but I’m getting the same exact
problem.
I’ve done this to my computer before, so I know a little bit about
windows and it’s booting and recovery, but I don’t claim to be an
expert. Changing the boot.ini file won’t (though I still tried, and
it didn’t) fix anything in this case, because the computer is booting
into windows correctly. The error message I am getting is in the same
screen as a boot-time chkdsk. This means that windows has slated PM
to do some work before finishing its booting stuff, and PM simply
crashes.
As an aside, I remember thinking "hmmm, changing the drive letter
like this would cause any work PM has planned for the boot would have
incorrect path names." But then I thought that if I realized this
before starting the process, then the people at Symantec probably
thought of it too and dealt with it accordingly, like referring to
partitions instead of drive letters or something. Nope, Symantec had
a D+ high school programming student doing this for extra credit, so
such an (I would think) obvious problem is left unsolved. I would
expect this out of freeware, but not software you pay for.
Pardon my rant, but I’m frustrated
If anybody knows about the way windows slates boot-time activities
(like chkdsk) this problem could be resolved by skipping the boot-time
stuff and proceeding to windows. Or if I could poke around in the
registry I might be able to fix the incorrect references.
If you have any idea how to do the above in Linux or the windows
recovery console, please let me know.
Also, the error message speaks of a batch file it can’t find. If
anybody knows what that batch file is called and where it is I could
just move the file to suit PM’s special needs. I can’t find any
relevant-looking batch files, except for one:
C:\windows\system32\MsDtc\Trace\msdtcvtr.bat. That is the only
batch file on my entire OS partition. The partition containing PM
doesn’t have any .bat files - save two irrelevant ones - that can be
attributed to PM. There are no mystery .bat files either, strangely
enough.
P.S. FYI, my windows partition is in FAT32 format so Linux can write
to it without any problems. I think this also means that the registry
is in a file somewhere, but I’m not sure if that’s true.
