[PCTECH] Problems with VB6 DriveListbox on Win XP

[Curt@xxxxxxxxxx]

Configuration:
        Windows XP Professional,
        Network Domain Server,
        User Signon to Domain and iSeries are different
        RPGILE,
        Visual Basic 6 application,

Application:
        RPGILE launches a VB6 application.  VB6 application uses a 
DriveListBox to display all available drives.

Actual drives are:
        C:\     [Local drive]
        D:\     [CD drive]
        F:\     [Local drive]
        M:\     [Mapped drive \\iSeries_Systemname\Sharename1]
        P:\     [Mapped drive \\iSeries_Systemname\Sharename2]

Problem:
When the VB6 application is launched using Microsoft's RunAS.exe and 
supplying an iSeries ID and Password.  The DriveListBox does not see any 
of the Mapped drives.

Drives displayed in the DriveListBox:
        C:\     [Local drive]
        D:\     [CD drive]
        F:\     [Local drive]
The Mapped drives are not recognized, however if the path 
\\iSeries_Systemname\Sharename1 is used instead of M:\, the desired 
file/program is accessed. 

Using the DriveListBox and DirListBox makes it easier and more user 
friendly to select the desired files.

How can I make the Mapped iSeries drives recognized.

By the way, this all works when the OS is Windows 2000.



~~~~~~~~~~~~~~~~~~~~~~~~~~~
Curt Emge
Curt@xxxxxxxxxx
Voice (858) 530-0875  Fax (858) 530-2615

********************************************************************************************************************************************************
CONFIDENTIALITY NOTICE:
Privileged and/or confidential CPU information may be contained in this 
message and may be subject to legal privilege.  This e-mail and any 
attachments are intended only for the person or entity to which it is 
addressed.  If you are not the intended recipient any dissemination, 
distribution or copying is strictly prohibited. If an addressing or 
transmission error has misdirected this e-mail, please notify the author 
by replying to it and delete this e-mail from your system and destroy any 
hard copy printouts.  Any views or opinions presented are solely those of 
the author and do not necessarily represent those of CPU. The recipient 
should check this e-mail and any attachments for the presence of viruses. 
CPU accepts no liability for any damage caused by any virus transmitted by 
this e-mail