Hello, I am trying to run a program named "Prognos" (Version 5) for medical purposes by a Company named "MedPrevent" (http://www.medprevent.de/produkte-prognos_de.php). As installation crashed, I installed on Windows and then copied the installed files to Linux where I wanted to run the app via wine. The startup dialogs show up but then there is an error message that the "Borland Database Engine" (BDE) can't be found, which is needed to have the program access it's database. I know that the BDE is for Windows of course and basically just a small collection of DLL's, if I am right. So I would like to know if there is any chance in getting a connection. Could it be done by providing DLL overrides maybe? Or do you have any other ideas for bypassing this? Any help would be appreciated. Thanks Briareos
> Can you give wine output to see the missing dlls which you can add ?There is no output about missing DLL's. I don't really understand the procedure (how the program acts with the BDE) a hundred percent. Probably it does a connection like Program->BDE->ODBC->Data Source ... or something like that. The BDE-Installation created a directory with that content: http://pastebin.ca/638017 I ran the BDEADMIN.EXE as well (in windows and linux) but there is just a Datasource named ECDCMusic to be found in Windows and none in Linux/WINE. Judging by the name as the medical program has nothing to do with music, I wonder if this could be related or not ...
> Hm, but could you simply pastebin the whole output then ? > wine "program.exe" &> debug.logYou can find some output here: http://pastebin.ca/638039 But be aware that that output is only triggered when I hit Alt+F4 during the splash screen. The splash screen itself shows a progress bar indicating the loading, but it sticks to 0 % forever.
Am Sonntag, 29. Juli 2007 16:18 schrieb Warren Dumortier:> Download this dll: MSVCP60.dll > Copy it in system32 and add it as native with winecfg !Did that. With the result, that now still the splash screen hangs at 0 %. But when i hit Alt+F4 now it jumps to 16 % and hangs there. Unfortunately the program does not tell me what it is trying to do at this point ... Probably connection attempts ...
Additional info: I noticed that I can repeat that Alt+F4 thing at 16 % reaching 33 % then again to reach 41 % and then at 50 % the program windows shows up - but the fields are not filled with data and the cursor is permanently showed as the windows hourglass. I can click. I think now we are really there where the BDC-problem shows its effect. I also get the error about the program not being able to initialize the BDC ... Am Sonntag, 29. Juli 2007 16:49 schrieb Briareos:> Am Sonntag, 29. Juli 2007 16:18 schrieb Warren Dumortier: > > Download this dll: MSVCP60.dll > > Copy it in system32 and add it as native with winecfg ! > > Did that. With the result, that now still the splash screen hangs at 0 %. > But when i hit Alt+F4 now it jumps to 16 % and hangs there. Unfortunately > the program does not tell me what it is trying to do at this point ... > Probably connection attempts ... > > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users
Am Sonntag, 29. Juli 2007 16:58 schrieb Warren Dumortier:> Without any logs iit is difficult to help you :pSure. With your help I managed to have a lot running now. Thanks! There is still one error that prevents me from doing actual measurements with the device/software, but all fields are filled now. The new question that arised is as follows: I can configure the program to use a specific COM-Port (where the hardware-device is connected). The problem is, that I have a connection at ttyUSB0. I remember that in windows sometimes a special driver is used to give the USB-Port a COM-number (e.g. for software that first used Serial connections via COM and later switched to USB-cables). Anyway: Can I do something similar in Linux as well? I guess I could just remove the tty0 and link it to ttyUSB0 but I am not sure if that would work - and also I don't think thats a clean way to do it ...
Am Sonntag, 29. Juli 2007 16:58 schrieb Warren Dumortier:> Without any logs iit is difficult to help you :pHere come some logs :) I've now done a link from tty9 to ttyUSB0. For your info here is the dmesg-output from connecting the USB-cable (it's short so i provide it inline): [17205091.904000] usb 1-1: new full speed USB device using uhci_hcd and address 3 [17205092.048000] cp2101 1-1:1.0: cp2101 converter detected [17205092.160000] usb 1-1: reset full speed USB device using uhci_hcd and address 3 [17205092.296000] usb 1-1: cp2101 converter now attached to ttyUSB0 I told the program to look only at COM9 for the device, but when it tries to connect I get an error dialog: "SetCommState function failed (win error code: 21)" In the console there is this: fixme:comm:set_queue_size insize 1024 outsize 1024 unimplemented stub err:comm:set_baud_rate tcgetattr error 'Input/output error' Maybe these infos help progressing. As I said in the last message, I don't know if the handling can or can't function (seeing it from protocol-/hardwareside) if I just do a symlink to a different DEV-file (COM->USB) ...
Please write a bug report about this problem to http://bugs.winehq.org . In AppDB most bugs get lost because AppDB is not a bugzilla. If you fill the bug report then chances that this problem will be fixed will rise a lot. On Sunday July 29 2007 22:41, Briareos wrote:> > You need to create a symbolic link from COM device to TTY like this: > > > > ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com2 > > > > This will create the symbolic link from COM2 to ttyUSB0. > > Thank you. With that hint the program now runs without any error messages, > except the > "fixme:comm:wait_on EV_RXFLAG not handled" > which occurs when the program scans the COM-port for the hardware (and does > not find it). > > I was told in the #winehq that the handling of this flag is simply not > implemented yet :( So I guess chances are bad for getting that to run ... > > Anyway I made an appdb entry for the app and provided current test-data > plus little how-to. > > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users