hi all, i have managed to get my application (step 7 microwin) running perfectly under wine: the real trouble was just getting past the installation, since setupapi and setupx aren't fully implemented in wine yet. anyway, this application is something of a programming environment for an S7, which is a programmable controlling unit (to operate different machines). i can hook up the S7 to my computer via serial port cable, and this works without problems straight out of wine. the S7 also has an ethernet jack so that i could connect it to my PC via ethernet cable. under windows, i simply load the program, then choose the connection method, and, if an ethernet adapter is installed, i can select it... which is my problem under wine: i have no ethernet adapter "installed" as i would have it under windows, and since this device is not present, i can't select it. ah, so the question really is: how can i "trick" the application into thinking an ethernet adapter is present? as far as i know, the app only requires the device driver to be present, and doesn't require any additional protocols (such as TCP/IP)... any ideas or suggestions? thanks for the help in advance. matthias
On Fri, 16 Apr 2004 11:03:20 +0200, you wrote:> the S7 also has an ethernet jack so that i could connect it to my PC via > ethernet cable. under windows, i simply load the program, then choose > the connection method, and, if an ethernet adapter is installed, i can > select it... which is my problem under wine: i have no ethernet adapter > "installed" as i would have it under windows, and since this device is > not present, i can't select it. > > ah, so the question really is: how can i "trick" the application into > thinking an ethernet adapter is present? as far as i know, the app only > requires the device driver to be present, and doesn't require any > additional protocols (such as TCP/IP)... > > any ideas or suggestions?I did not know, but a quick Google showed that (not unusual) Windows programmers may use at least half a dozen way of detecting that an adapter is present. Best guess is with the iphlpapi. Run with WINEDEBUG=+iphlpapi wine ... If there are iphlpapi trace's, post them. If not, it is possible it tries to get the information from the registry. Run wine with the +relay debug channel, and look at suspicious registry entries that are queried ("ethernet", "adapter", "device" etc.) Other traces that might give a clue are winsock (WINEDEBUG=+winsock), com (WINEDEBUG=+ole). If your program can be downloaded somewhere, enter an bug report in wine's bugzilla (http://bugs.winehq.org) and give the programs URL. Rein. -- Rein Klazes rklazes@xs4all.nl
Hello Matthias, Matthias Schweinoch disse:> hi all, >####stripped> ah, so the question really is: how can i "trick" the application into > thinking an ethernet adapter is present? as far as i know, the app only > requires the device driver to be present, and doesn't require any > additional protocols (such as TCP/IP)... > > any ideas or suggestions?Well, in fact i have a sugestion: the ethernet interface can exist only in kernel space - as a tun/tap interface, or even as a "dummy" interface - and in this case you can install a "dummy" device in your linux box and attrib a real ip number and netmask to it. If you have another device attached to your linux box, not an ethernet device, with a ip number already configured to it, you can route the packets from the "dummy" interface (visible to wine, i guess) to the this one. I don't know if it will work, but you can give it a try. HTH, RSalles> > thanks for the help in advance. > > matthias > _______________________________________________ > wine-users mailing list > wine-users@winehq.org > http://www.winehq.org/mailman/listinfo/wine-users >-- "A well-written program is its own heaven; a poorly-written program is its own hell." TAO of Programming - Book 4