I'm having problems running VB 3.0 programs under Wine and installing the VB 3.0 development environment. According to the app DB people have got VB 3.0 running before. I'm running on Ubuntu Dapper (x86). Previous tests were with earlier versions of Wine - I've had this problem hanging about for a few weeks now. This morning I uninstalled Wine with extreme prejudice (i.e., asking Synaptic to remove configuration files, etc) and deleted by ~/.wine directory then installed 0.9.33. This produced the same results I saw before. I can run my VB3 application but I have to copy the DLLs, etc, which it requires (VBRUN300.DLL, various .VBXs) into the application directory. If they're just in Windows\System (~/.wine/drive_c/windows/system) they're not found. When I come to install VB 3.0 from floppy using: wine /media/fd/setup.exe the first few windows go fine including confirmation that installation will be in C:\VB then I get one 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. Pressing OK on that gives a window with a choice of Complete Installation or Custom Installation. Choosing Complete gives a window asking about installing ODBC drivers then an error, choosing Custom goes direct to the error. The error message is not overly helpful: Setup could not be completed due to system errors. Please clear up the cause of errors and try again. To install VB properly, please run setup again. wine notepad.exe runs fine. Another 32-bit Windows program also works OK, modulo some issues with serial port handling which I may look into at some point in the future. Therefore I think the basic Wine installation is not completely borked. Any suggestions for what I should try next? Thanks, Ed Davies.
On Mon, 2007-03-19 at 13:09 +0000, Ed Davies wrote:> Any suggestions for what I should try next?I'd try mounting the setup disk on .wine/drive_c/install/ or some such directory, and running the setup from there. I'd also give the program the Dos pathname: wine C:\\install\\Setup.exe You can also run it using winedbg, or with WINEDEBUG variable set e.g. WINEDEBUG=+ to try for more information.>-- Declan Moriarty <junk_mail@iol.ie>
Ed Davies wrote:>> Any suggestions for what I should try next?Declan Moriarty replied:> I'd try mounting the setup disk on .wine/drive_c/install/ or some such > directory, and running the setup from there. I'd also give the program > the Dos pathname: > > wine C:\\install\\Setup.exe > > You can also run it using winedbg, or with WINEDEBUG variable set > > e.g. WINEDEBUG=+ > > to try for more information.Sensible suggestions, thanks. I tried both but unfortunately they didn't help (i.e., still failed with the alternate mount point and the debug output didn't make much sense to me). I wrote a little test program to see how GetWindowsDirectory and GetSystemDirectory work in 16-bit apps under Wine. The output was not ideal so I submitted a bug report: http://bugs.winehq.org/show_bug.cgi?id=7853 "GetSystemDirectory returns wrong directory to 16-bit apps" and a separate (but linked) report for VB 3.0 installation in general: http://bugs.winehq.org/show_bug.cgi?id=7854 It'll be interesting to see what response these reports get. Ed Davies.
On Sun, 2007-03-25 at 14:48 +0100, Ed Davies wrote:> Ed Davies wrote: > >> Any suggestions for what I should try next?Re Bug 7584: There is/was some tweak in wine to allow non case sensitive names. I think it was in the compile time questions asked when compiling wine. Of course I hit return and accepted the default (whatever that was). That failing, or being miles off, can you symlink c:\installdirectory to C:\INSTALLDIRECTORY (or vice versa) and go from there? Also check out bug 3723. -- Declan Moriarty <junk_mail@iol.ie>