DPRO5 Installation problem

When I run the install msi for dpro5 (just downloaded), I immediately get a
dialog with title

"Dolphin Smalltalk Professional 5.0 Installer Information" and the message
"Error 1327.Invalid Drive: V:\".

When I dismiss that, the InstallShield dialog says:

"The wizard was interrupted before Dolphin Smalltalk Professional 5.0 could be
completely installed".

This was immediately after launching the msi, no install path was given yet,
and there is no V:\ on the machine. Before the MSI I tried the full install
with the same result. This is on an NT box, 4.0 sp at least 6. On another
machine running  W2000, I dont get this error.

> This was immediately after launching the msi, no install path was given
yet,
> and there is no V:\ on the machine. Before the MSI I tried the full
install
> with the same result. This is on an NT box, 4.0 sp at least 6. On another
> machine running  W2000, I dont get this error.

Are you sure the NT box has the latest installer?  There's a separate
upgrade for just the installer (be sure to install the one that applies to
NT) that _might_ help.

Have a good one,

Bill

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

Andy or Blair,

I am still unable to install dpro5 because of this error. Searching around for
1327 and installshield I didnt really find an exact hit but they seemed to
imply that it could be caused by a reference to the drive in some file in the
install script. Could there be such as reference somewhere in your build?
Otherwise, what could be wrong?

-Alan R

PS I have ensured I have the latest version of the windows installer.

On Sat, 14 Sep 2002 14:59:47 GMT, ar <[hidden email]> wrote:

Alan,

> I am still unable to install dpro5 because of this error. Searching around
for
> 1327 and installshield I didnt really find an exact hit but they seemed to
> imply that it could be caused by a reference to the drive in some file in
the
> install script. Could there be such as reference somewhere in your build?
> Otherwise, what could be wrong?

There shouldn't be any reference to drive V: in the MSI files since there
has never been such a drive on the machine where the InstallShield script
was developed and the installer deployed. As far as I can remember the
installation worked okay on NT4 when we tested it under VMware before the
Dolphin 5 release. I'm not sure what service pack that was conducted on but
I'll check later when I'm in a position to run up NT again.

Has anyone else experienced similar problems installing Dolphin 5 under NT?

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

"ar" <[hidden email]> wrote in message
news:IEyDPYw=Bcg=[hidden email]...
> When I run the install msi for dpro5 (just downloaded), I immediately get
a
> dialog with title
>
> "Dolphin Smalltalk Professional 5.0 Installer Information" and the message
> "Error 1327.Invalid Drive: V:\".
>
> When I dismiss that, the InstallShield dialog says:
>
> "The wizard was interrupted before Dolphin Smalltalk Professional 5.0
could be
> completely installed".
>
> This was immediately after launching the msi, no install path was given
yet,
> and there is no V:\ on the machine. Before the MSI I tried the full
install
> with the same result. This is on an NT box, 4.0 sp at least 6. On another
> machine running  W2000, I dont get this error.
>

This is a long shot, but if you're stuck it could allow the installation to
complete.

Before the install starts map V: to \\MyComputerName\C$ where MyComputerName
is the NetBIOS name of your computer.  Now V: points to your harddrive.

Run the MSI installer and see if the error persists.  If not, run RegEdit
and ensure that any path information related to the install points to C:\
and not V:\.

 From here, Dolphin should run.  Let me know if this works.

Kind regards,
Jeffrey D. Panici

P.S.  You could also SUBST V: to C: instead of mapping it (NET USE).

Alan R <[hidden email]> wrote in message
news:[hidden email]...
> Andy or Blair,
>
> I am still unable to install dpro5 because of this error. Searching around
for
> 1327 and installshield I didnt really find an exact hit but they seemed to
> imply that it could be caused by a reference to the drive in some file in
the
> install script. Could there be such as reference somewhere in your build?
> Otherwise, what could be wrong?

You might try running it with verbose logging turned on to learn more about
what it is trying to do, you can read about that here:
http://groups.google.com/groups?selm=6GNz2KTVBHA.302%40cppssbbsa01.microsoft
.com&output=gplain

I am not a big fan of MSI as I have had problems installing stuff on Windows
2000 with it.

Good luck,

Chris

Alan,

I've tested the installation of D5 Pro on a fresh NT4 SP6 machine and
everything seems okay. I can only suggest that you perhaps have an "odd"
installation of NT on your machine. Have you tried the suggestions made by
Jeffrey Panici; they might at least get you up and running on this machine.

Best Regards,

Andy Bower
Dolphin Support
http://www.object-arts.com
---
Are you trying too hard?
http://www.object-arts.com/Relax.htm
---

On Thu, 10 Oct 2002 16:27:37 +0100, "Andy Bower" <[hidden email]>
wrote:

>I've tested the installation of D5 Pro on a fresh NT4 SP6 machine and
>everything seems okay. I can only suggest that you perhaps have an "odd"
>installation of NT on your machine. Have you tried the suggestions made by
>Jeffrey Panici; they might at least get you up and running on this machine.

Thanks for verifying that. I found the "oddity". V was in fact a network
mapping which for some reason doesn't appear when this machine is started
standalone (even though other network drives do). Installshield can show the
other (unconnected) drives in the install location prompt, but chokes on V
which is somehow defined but no longer mapped.

Mapping V to the local drive worked (thanks Jeff), as well as just connecting
to the network. Oddly, the problem returns if I remove the local mapping so
there must be some further definition of V somewhere in NT.

-Alan

"Alan R" <[hidden email]> wrote in message
news:[hidden email]...
> On Thu, 10 Oct 2002 16:27:37 +0100, "Andy Bower" <[hidden email]>
> wrote:
>
> >I've tested the installation of D5 Pro on a fresh NT4 SP6 machine and
> >everything seems okay. I can only suggest that you perhaps have an "odd"
> >installation of NT on your machine. Have you tried the suggestions made
by
> >Jeffrey Panici; they might at least get you up and running on this
machine.
>
> Thanks for verifying that. I found the "oddity". V was in fact a network
> mapping which for some reason doesn't appear when this machine is started
> standalone (even though other network drives do). Installshield can show
the
> other (unconnected) drives in the install location prompt, but chokes on V
> which is somehow defined but no longer mapped.
>
> Mapping V to the local drive worked (thanks Jeff), as well as just
connecting
> to the network. Oddly, the problem returns if I remove the local mapping
so
> there must be some further definition of V somewhere in NT.
>
> -Alan
>

Alan --

If you don't *see* V: in the mapped drive list then it's substituted (SUBST
command) not mapped.  Go to a DOS (cmd.exe) prompt and type SUBST with no
command-line parameters and press Enter.  If anything is listed, then you'll
need to remove it with SUBST /D V:.

It might also be possible there's an errant registry entry for network drive
mappings.  I need to dig through my documentation to find where in the
registry hierarchy these live.

Let me know what SUBST turns up and I'll dig around my docs and notes for
the registry keys.

Regards,
Jeffrey D. Panici
Worker Bee Solutions, Inc.

"Jeffrey D. Panici" <[hidden email]> wrote in message
news:oHoq9.3033$[hidden email]...
>
> "Alan R" <[hidden email]> wrote in message
> news:[hidden email]...
> > On Thu, 10 Oct 2002 16:27:37 +0100, "Andy Bower" <[hidden email]>
> > wrote:
> >
> > >I've tested the installation of D5 Pro on a fresh NT4 SP6 machine and
> > >everything seems okay. I can only suggest that you perhaps have an
"odd"
> > >installation of NT on your machine. Have you tried the suggestions made
> by
> > >Jeffrey Panici; they might at least get you up and running on this
> machine.
> >
> > Thanks for verifying that. I found the "oddity". V was in fact a network
> > mapping which for some reason doesn't appear when this machine is
started
> > standalone (even though other network drives do). Installshield can show
> the
> > other (unconnected) drives in the install location prompt, but chokes on
V (SUBST
> command) not mapped.  Go to a DOS (cmd.exe) prompt and type SUBST with no
> command-line parameters and press Enter.  If anything is listed, then
you'll
> need to remove it with SUBST /D V:.
>
> It might also be possible there's an errant registry entry for network
drive
Okay, I found the registry path:

HKEY_CURRENT_USER\Network\[DriveLetter]

Where [DriveLetter] is the name of the mapped drive.  If you see V in there,
you can just remove that key from the tree.

Hope this helps.

- Jeff Panici