[RESOLVED] VB6 Install on Workstation under Vista

[TOMBUGGY]

I have used the following to install a VB6 app on a workstation under XP:
-- Map Drive Z to \\computername\sharedfolder (UNC Path)
-- Using Setup from PDW install to Z:\
This works under Windows XP.

I have now added to the network another workstation that is running Windows Vista. I did the same drive mapping. When I attempt to install the app to Z:\ I get the following error: "Error determining allocation unit for Drive Z." Help!

[RobDog888]

Its probably a permissions issue. What is the path on the Vista system?

[TOMBUGGY]

I'm not sure what you mean by "What is the path on the Vista system?" The default path in Setup is C:\Program Files\Appname.exe. As I did under XP, I change this to Z:\ where Drive Z is mapped as originally described.

With respect to Permission Issues, do you mean permission from the Host or permission on the Vista workstation?

Thanks.

[RobDog888]

You say you map a Z drive but that relates to a path on the Vista system but what path?

Permissions to write to the Vista systems evaluated Z drive path.

[TOMBUGGY]

I likely was not complete or clear. The Host (Server) is an XP system. Its computer name is Sportsware2 and its shared folder name is GHM. One workstation is an XP system on which I was able to map a network drive (Z) using a UNC Path of \\Sportsware2\GHM. I am able to install on this workstation to Z:\ with the PDW Setup program. The new workstation is a Vista system on which I tried to do the same thing, i.e. map the drive in the same way and install to Z:\.

What I neglected to mention originally is that the first error message I get is: "The destination directory Z:\ doest not exist. Do you want it created?" If I answer 'Yes' that is when I get the message: "Error determining allocation unit for Drive Z."

[RobDog888]

But my point is that if you are mapping a drive from any system/os to this Vista system, you will need to have permissions to access the Vista systems file directories and location that you wish to map.

[TOMBUGGY]

I guess I'm confused. I am mapping a drive FROM the Vista system to the shared folder on the XP system, i.e. to \\Sportsware2\GHM.

[Hack]

Outside of the setup package, using Windows Explorer, can you map this drive manually?

[TOMBUGGY]

I am NOT mapping the drive with the Setup package. I have mapped it with Vista via Computer and Map a Network Drive.

[RobDog888]

Oh another turn on this thread

Well maybe the P&D wiz is just having troouble with mapped drives but if it says it cant eval the path then you need to look at permissions which ever way it is going to.

[TOMBUGGY]

Well, the P&D Wiz didn't have trouble with a mapped drive when I installed the app on the XP workstation with mapping to a XP host. So, it may be permissions related to Vista, something about going from a Vista worksation to a XP host, or something else network-wise. Looks like I'm going to have to get a local Vista and Network expert onsite because I'm certainly neither.

[RobDog888]

[color=navy]It it more then likely just a network issue as the firewall on Vista may be blocking the actions of the install over the drive.[color]

[TOMBUGGY]

Voila - Installation on Vista Workstation Resolved!! On a wild and desperate guess I decided to try using the UNC Path to the XP host as the installation path in PDW Setup (instead of the mapped drive letter). IT WORKED - why I don't know, but it worked.

Obviously there's something different about Vista because installing to the mapped drive (Z:\) worked from a XP workstation to the XP host and didn't work from the Vista workstation to the XP host. I think I'll try reinstalling from the XP workstation using the UNC Path - perhaps it's a "universal solution" for both XP and Vista.

Update - I did the XP install using the UNC Path and it was successful. I'm going to use that approach and marik this thread resolved.