[Bug 7854] New: VB 3.0: Installation fails

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=7854

Summary: VB 3.0: Installation fails
           Product: Wine
           Version: 0.9.33.
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wine-kernel
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Installation of VB 3.0 from floppy disk fails, first with a message about the
Windows directory being on another drive then a very uninformative message
saying "Setup could not be completed due to system errors".

With the first VB 3.0 Pro floppy mounted as either /media/fd then running "wine
/media/fd/setup.exe" or mounted as .wine/drive_c/install/ then running as "wine
C:\install\Setup.exe" (as suggested by Declan Moriarty on 19th of March in the
Wine Users list installation at first proceeds normally with the suggestion of
installation in the C:\VB directory and confirmation that it should be created.
 The a dialog box is displayed saying:
> Setup needs to install some files in your
> Windows directory.  This directory is on a
> drive other than the one where you want to 
> install Visual Basic.
>
> If you choose Custom installation on the
> next screen, Setup will show you the
> space required on each of these drives.

This is strange because this is a clean Win 0.9.33 installation with only the C:
(and Z:) drives mapped.

Carrying on, the Installation Options dialog gives the choice of Complete
Installation or Custom Installation.  Choosing Complete goes via an Install ODBC
Drivers dialog to a failure, Custom goes straight to the failure.  The failure
dialog box is not very helpful:
> Setup could not complete due to system
> errors.
>
> Please clear up the cause of errors and try
> again.  To install VB properly, please run setup
> again.

I have previously run a relatively large VB 3.0 application OK under a previous
Wine installation which exhibitted this problem.

In trying to diagnose this problem I wrote a little C test program to display
the results of GetWindowsDirectory and GetSystemDirectory.  The results it
produced seemed to me like they might be related to this problem but rather than
add speculation here I've submitted them separately: Bug #7853.

I've looked at some WINEDEBUG output for running this program.  It wasn't very
informative to me but I'll take a fresh log and attach it here.