[Bug 10608] New: Not work export sql of Power Designer 12.1, problem with VBscript

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

Summary: Not work export sql of Power Designer 12.1, problem with
                    VBscript
           Product: Wine
           Version: 0.9.46.
          Platform: Other
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wine-binary
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=9406)
 --> (http://bugs.winehq.org/attachment.cgi?id=9406)
Message of error Power Designer 12.1

$ dpkg -l | grep wine
ii  wine                                   0.9.46-0ubuntu1                     
Microsoft Windows Compatibility Layer (Binar

Hello, I testing Power Designer 12.1, and work, minimum problem with refresh in
button, no many problem.

Now I create MER/DB, and not export SQL, problem with VBScript, I install
http://fprelease.free.fr/fpwine/ , and install VBScript. now message of error :
-(

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #1 from Cristian Aravena Romero   2007-11-30 08:17:57 ---
Created an attachment (id=9407)
 --> (http://bugs.winehq.org/attachment.cgi?id=9407)
.wine.stderr.log

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #2 from Cristian Aravena Romero   2007-11-30 08:18:23 ---
Created an attachment (id=9408)
 --> (http://bugs.winehq.org/attachment.cgi?id=9408)
.wine.stdout.log

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #3 from Cristian Aravena Romero   2007-11-30 08:23:26 ---
Created an attachment (id=9410)
 --> (http://bugs.winehq.org/attachment.cgi?id=9410)
$wine ".wine/drive_c/Archivos de programa/Sybase/PowerDesigner
12/pdshell12.exe"

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #4 from Cristian Aravena Romero   2007-11-30 08:26:22 ---
My script for install VBScript:
http://fprelease.free.fr/fpwine/v0.9.49/fpwine

My VBScript -> vbs56men.exe

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|wine-binary                 |wine-misc

--- Comment #5 from Vitaliy Margolen   2007-11-30 10:29:02 ---
First of all - install latest Wine version (currently 0.9.49).
Second - read what Wine tells your and fix it:

err:module:import_dll Library MSVCP60.dll (which is needed by L"C:\Archivos de
programa\Mozilla ActiveX Control v1.7.12\mozctl.dll") not found

(btw why are you using this old component which is no longer supported/used by
Wine?) You should remove / rename ~/.wine directory, and reinstall your
program. Only this time you should use wine_gecko (run 'wine iexplore
http://winehq.org and click "Install" when asked to install wine gecko).

Third, read FAQ about how to properly start applications:
http://wiki.winehq.org/FAQ

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

Cristian Aravena Romero  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #9406 is|0                           |1
           obsolete|                            |
Attachment #9407 is|0                           |1
           obsolete|                            |
Attachment #9408 is|0                           |1
           obsolete|                            |
Attachment #9410 is|0                           |1
           obsolete|                            |

--- Comment #6 from Cristian Aravena Romero   2007-12-02 11:49:01 ---
Created an attachment (id=9457)
 --> (http://bugs.winehq.org/attachment.cgi?id=9457)
$ wine .wine/.../pdshell12.exe

Vitaliy Margolen:

Update wine:
$ dpkg -l | grep wine
ii  wine                                   0.9.50~winehq0~ubuntu~7.10-1        
Microsoft Windows Compatibility Layer (Binar

Re-install and run Power Designer:

Message in console:
-------------------
err:ole:CoGetClassObject class {b54f3741-5b07-11cf-a4b0-00aa004a55e8} not
registered
err:ole:CoGetClassObject no class object {b54f3741-5b07-11cf-a4b0-00aa004a55e8}
could be created for context 0x1
-------------------

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #7 from Vitaliy Margolen   2007-12-02 19:24:38 ---
This command IS INVALID.
$ wine .wine/drive_c/Archivos\ de\ programa/Sybase/PowerDesigner\
12/pdshell12.exe

I'm guessing you still can not read the FAQ. Then just for you here it is:

How do I run Wine?

Wine is not something you run, you run applications with it. Simply open your
applications and Wine should be loaded to run them automatically. You can
configure your wine environment by running winecfg, and you can browse your
fake windows drive at ~/.wine/drive_c

If you would like a general overview and tutorial about using Wine, you can
read the User Guide. For the most part, however, Wine should be as
straightforward as clicking the application you'd like to run from your
Gnome/KDE/Whatever menu.

When using the terminal there are two valid methods of running applications.
The first method is to chdir into the program's folder and then run the
application directly, e.g.

cd "~/.wine/drive_c/Games/Tron" && wine tron.exe

The second method should ONLY be used if you are intending to install from
something which has multiple CDs (you need to use this method to allow you to
swap discs) as it doesn't always work. It consists in using the full Windows
path like so...

wine "C:\Games\Tron\tron.exe"

Do NOT run with the full Linux path i.e. "wine /stuff/mygame.exe" or by double
clicking icons from your file manager (sometimes this works but more often it
will fail with errors of some sort).

This is because Wine passes this path as-is to the windows program in argv[0].
This is exactly what cmd.exe does and Wine has extensive tests for that.
However some programs expect fully qualified windows path in argv[0], and break
if they don't get it. Lots of programs written with Borland tools will have
that problem because Borland mistakenly stated in the manuals that argv[0] will
always be set to fully qualified path of the executable. Which is not the case.

If you use Gnome, KDE or XFCE4, then after you have installed some applications
in Wine you should notice a Wine subfolder in your main desktop menu with menu
entries for all your installed Wine programs (as long as you told them to make
Start Menu shortcuts). If any apps seem to be missing try running "wineboot"
and looking again.

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #8 from Cristian Aravena Romero   2007-12-02 23:22:41 ---
(In reply to comment #7)
> This command IS INVALID.
> $ wine .wine/drive_c/Archivos\ de\ programa/Sybase/PowerDesigner\
> 12/pdshell12.exe

Vitaliy Margolen I'm newbabie in Linux. I'm sorry, for my work fine (New test):

~$ wine .wine/drive_c/Archivos\ de\ programa/Sybase/PowerDesigner\
12/pdshell12.exe
~$cd .wine/drive_c/Archivos\ de\ programa/Sybase/PowerDesigner\ 12/
~/.wine/drive_c/Archivos de programa/Sybase/PowerDesigner 12$wine pdshell12.exe

I use:
* wine 0.9.50 -> http://www.winehq.org/site/download-deb
* wine-doors 0.1.1 -> http://www.wine-doors.org/
* Ubuntu Gutsy (Is magic)
> I'm guessing you still can not read the FAQ. Then just for you here it is:
>
> How do I run Wine?
>
> Wine is not something you run, you run applications with it. Simply open your
> applications and Wine should be loaded to run them automatically. You can
> configure your wine environment by running winecfg, and you can browse your
> fake windows drive at ~/.wine/drive_c
>
> If you would like a general overview and tutorial about using Wine, you can
> read the User Guide. For the most part, however, Wine should be as
> straightforward as clicking the application you'd like to run from your
> Gnome/KDE/Whatever menu.

I star program with Gnome in menu (Thanks to wine-doors); and console.
> When using the terminal there are two valid methods of running applications.
> The first method is to chdir into the program's folder and then run the
> application directly, e.g.
>
> cd "~/.wine/drive_c/Games/Tron" && wine tron.exe
>
> The second method should ONLY be used if you are intending to install from
> something which has multiple CDs (you need to use this method to allow you to
> swap discs) as it doesn't always work. It consists in using the full Windows
> path like so...
>
> wine "C:\Games\Tron\tron.exe"
>
> Do NOT run with the full Linux path i.e. "wine /stuff/mygame.exe" or by double
> clicking icons from your file manager (sometimes this works but more often it
> will fail with errors of some sort).
>
> This is because Wine passes this path as-is to the windows program in argv[0].
> This is exactly what cmd.exe does and Wine has extensive tests for that.
> However some programs expect fully qualified windows path in argv[0], and break
> if they don't get it. Lots of programs written with Borland tools will have
> that problem because Borland mistakenly stated in the manuals that argv[0] will
> always be set to fully qualified path of the executable. Which is not the case.
>
> If you use Gnome, KDE or XFCE4, then after you have installed some applications
> in Wine you should notice a Wine subfolder in your main desktop menu with menu
> entries for all your installed Wine programs (as long as you told them to make
> Start Menu shortcuts). If any apps seem to be missing try running "wineboot"
> and looking again.

Ok, I new test and attach new report/info. Many thanks for you comment!  :-)

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #9 from Austin English   2008-06-09 16:20:19 ---
Is this still an issue in current (1.0-rc4) or newer wine?

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #10 from Cristian Aravena Romero   2008-06-09 17:40:45 ---
(In reply to comment #9)
> Is this still an issue in current (1.0-rc4) or newer wine?

Other user testing?

see:
http://www.sybase.com/products/modelingmetadata/powerdesigner

Power Designer user in many schools.

Many thanks!
--
Cristian

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

--- Comment #11 from Austin English   2008-12-08 04:21:41 ---
Is this still an issue in current (1.1.10 or newer) wine?

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |ABANDONED

--- Comment #12 from Austin English   2009-06-08 11:45:22 ---
Abandoned. If this is still an issue in current (1.1.23 or newer) wine, and you
can provide the needed information, feel free to reopen.

[Bug 10608] Not work export sql of Power Designer 12.1, problem with VBscript

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #13 from Austin English   2009-06-08 11:48:02 ---
Closing.