Dolphin installer on clean 2k machine

Blair,

I just put beta 2 on a fresh-from-the-box P4 with Win2k, and the installer
bombed out over msvcp60.dll.  Copying the file to its system32 directory and
re-running the installation fixed it.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

"Bill Schwab" <[hidden email]> wrote in message
news:[hidden email]...
> Blair,
>
> I just put beta 2 on a fresh-from-the-box P4 with Win2k, and the installer
> bombed out over msvcp60.dll.  Copying the file to its system32 directory
and
> re-running the installation fixed it.

Bill, when you say the "installer" presumably you don't mean the initial MSI
part, but the first run of Dolphin which shows the unlock dialog?

Regards

Blair

"Blair McGlashan" <[hidden email]> wrote in message
news:[hidden email]...
> "Bill Schwab" <[hidden email]> wrote in message
> news:[hidden email]...
> > Blair,
> >
> > I just put beta 2 on a fresh-from-the-box P4 with Win2k, and the
installer
> > bombed out over msvcp60.dll.  Copying the file to its system32 directory
> and
> > re-running the installation fixed it.
>
> Bill, when you say the "installer" presumably you don't mean the initial
MSI
> part, but the first run of Dolphin which shows the unlock dialog?

As far as I remember (it has been some time since) it is the installer that
starts complaining. (but of course then Dolphin is also not workinh
correctly).

Davorin Rusevljan

Hi Blair,

> > I just put beta 2 on a fresh-from-the-box P4 with Win2k, and the
installer
> > bombed out over msvcp60.dll.  Copying the file to its system32 directory
> and
> > re-running the installation fixed it.
>
> Bill, when you say the "installer" presumably you don't mean the initial
MSI
> part, but the first run of Dolphin which shows the unlock dialog?

No, the MSI file blew up w/ some kind of error number; I didn't even try to
run Dolphin at that point for fear of what it might do if it ever did get
going.  Figuring that it was dependency related, I put depends.exe on the
machine and saw the missing file.  After copying it to the machine and
re-installing (actually a "repair" IIRC), all was well.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]