wine-devel December 2003

wine-devel@winehq.org

109 participants
267 discussions

Re: Easy IE installer script
by Ivan Leo Murray-Smith 23 Dec '03

23 Dec '03

> Why do you say that? Because of how copyright works, if a file isn't yours, you need a written permission to prove that you have the right to use it/redistribute it, or the copyright holder can claim that the use/redistribution of the file is unauthorized. > I'd like to see the legal text that says they are > not redistributable, The microsoft windows (Favourite version of 32-bit windows here) license > as they are intended to be shipped alongside > applications IIRC you need a M$ development tool to obtain a license that allows you to do that. Also, such license only allows use for applications designed for microsoft windows. AFAIK wine is not a windows app. > and can be freely downloaded from the net M$ is free to sue anybody that violates it's copyright, and claiming that other people have violated M$ copyright has never (And will never) save anybody in court. They can choose to sue you and not dll-files. > (ie the situation > is no different to the current one). It is, IE is not an app but a OS component, so there are a lot more restrictions on IE than on anything else. A solution would be to ask the user to insert his windows CD, and just get the files needed for IE installation from there. > Maybe, but they'd have to sue me. Given that there are people running > websites that ship practically every DLL on a windows system, that would > not make much sense. Those websites are online to help windows users, winehq is online to get windows users to unix+wine BTW they already CAN sue you. > They'd also have a hard time arguing that the MSVC > Runtime is not meant to be redistributed when many apps do so. No, it would be very easy for them to prove that all vendors that ship MSVCRT with there apps have a license from microsoft to do so. Ivan.

2 1

Re: Re: winemine2 winelib example
by Dimitrie O. Paun 23 Dec '03

23 Dec '03

> Doh, I meant bin2res. After making clean I need to > extract them like: > ../../tools/bin2res -o faces.bmp ./rsrc.rc > > Otherwise they aren't available when wrc runs on rc.rc. > Seems odd that wrc can't pull the data out of the src.rc > file itself though. Actually it can, but it's the other resource compilers that can't (MS' rc, and windres). So for compatibility with those, we use the current scheme. -- Dimi.

1 0

Re: Easy IE installer script
by Ivan Leo Murray-Smith 23 Dec '03

23 Dec '03

>The installer program contains a few things that may or may not be >redistributable - for instance, it contains MSVCRT40.DLL and MFC40.DLL, >both of which are available for free from dll-files.com so it seemed to >make sense to include them. You can't redistribute them, unless you have some sort of special license from m$. There is a simple trick to get round this. You can usually find m$ dlls like mfc, msvcrt and so on in microsoft trial game installers. So, to do this legally, you would have to ask the if he wants to accept the license conditions of the trial game that contains the needed dll, then download the demo from the net (You can even point to download.microsoft.com), extract and install the dll (Installing the game may be necessary if you can't get the dlls out of the installer), and then do whatever else the script does. I suppose it would be a good thing to warn the user that he must have a windows license to use IE4,5 or 6. >Do people think this should be linked to from WineHQ? Not as it is now, M$ could sue for copyright violation, it wouldn't be a nice experience. Ivan.

2 1

Re: Re: winemine2 winelib example
by Dimitrie O. Paun 23 Dec '03

23 Dec '03

> Should we modify the winelib documentation? The docs > make it sound like its an easy two step process. Yes, we should. We should also modify winemaker to: 1. Generate MinGW compatible Makefiles 2. Use winegcc to achive (1) 3. Drop the configure script altogether. With winegcc there's no need for a configure script anymore, and besides, using autoconf is project policy, not something we should force down people's throats. > Also, is there a way to get wrc to extract all of the > objects in an rc file? What do you mean by this? -- Dimi.

2 1

winemine2 winelib example
by Chris Morgan 23 Dec '03

23 Dec '03

After reading about the winamp3 source code release I've been interested in working with winelib. I've been trying to get the winemine2 example to work from the winelib documentation http://winehq.com/site/docs/winelib-user/ winelib-getting-started#WINEMAKER-TEST After doing the winemaker and configure step I run make and get: ~/wine/programs/winemine2$ make sed -e 's,@bindir\@,/usr/local/bin,g' -e 's,@winelibdir\@,.,g' ./ wineapploader.in >wineapploader || rm -f wineapploader LD_LIBRARY_PATH="/home/cmorgan/wine/libs:$LD_LIBRARY_PATH" /home/cmorgan/wine/ tools/winebuild/winebuild -o winemine2.exe.dbg.c --debug -C. dialog.c main.c gcc -c -I. -I/home/cmorgan/wine/include -g -O2 -fPIC -D_REENTRANT -o winemine2.exe.dbg.o winemine2.exe.dbg.c LD_LIBRARY_PATH="/home/cmorgan/wine/libs:$LD_LIBRARY_PATH" /home/cmorgan/wine/ tools/wrc/wrc -I. -I/home/cmorgan/wine/include -o En.res En.rc En.rc:23:22: Error: syntax error make: *** [En.res] Error 1 ~/wine/programs/winemine2$ I'm not sure what the issue is with En.rc, I've compared it against other resource files and it looks quite similar. I edited the Makefile to just use rsrc.rc as winemine2_exe_RC_SRCS and this let me get further and build the standalone app but when I remove the binary resource files like winemine.ico and the *.bmp files these aren't rebuilt. Extracting them manually from rsrc.rc with wrc works however. Are the docs out of date on this? Bug in winemaker? Chris

4 5

Easy IE installer script
by Mike Hearn 23 Dec '03

23 Dec '03

Hi everyone, I thought I'd let the list know that I wrote an easy IE installer program, for those times when only explorer will do. On a Wine CVS build, no windows install, it installs pretty much perfectly, and it does run (stability is so so :). It'll also put a nice menu entry in your menus if your desktop uses the standard mechanism. The installer program contains a few things that may or may not be redistributable - for instance, it contains MSVCRT40.DLL and MFC40.DLL, both of which are available for free from dll-files.com so it seemed to make sense to include them. It also includes the Tahoma font, which IE installs anyway, but I install it first because current Wine seems to enjoy picking BitStream Vera Mono which doesn't look too good and causes UI layout problems. You can get it from here: http://bylands.dur.ac.uk/~mh/install-ie6.run Just download and run it, like so: sh install-ie6.run It contains a Linux Winelib DSO program (for figuring out your linux windows drive path), so may or may not work on other platforms. Do people think this should be linked to from WineHQ? It's a pretty common question in #winehq. enjoy, thanks -mike

1 0

Re: newbie wine developer question
by Dimitrie O. Paun 23 Dec '03

23 Dec '03

> 1) Should I report fixme's in bugzilla? (I guess, not, > but I'm not sure). That's correct, please don't. It would polute Bugzilla, and they are much easily accessible via grep :) > 2) I would like to fix some fixme (which I can > reproduce), but I don't understand a lot of thins. The simplest way is to send patches, ask specific questions, resend patches, ... etc. We'll be glad to help. -- Dimi.

1 0

Console problem
by Peter Oberndorfer 23 Dec '03

23 Dec '03

Hello I'm trying to get the freeware version of IDA (console) working, but if i run it in wine it just hangs. If i run it with winedbg it works fine. I found out that the problem is that AllocConsole is never called for the application if it is being run from wine. But since IDA runs in the console subsystem it should get a console according to MSDN. MSDN says: The CONSOLE subsystem is for a Win32 character-mode application. Console applications are given a console by the operating system. So here is the technical side of the problem: AllocConsole should get called from process_attach() ->dlls/kernel/kernel_main.c:180 So the external variable main_create_flags tells us if we need a console. This variable is set from process_init() ->dlls/kernel/process.c:634 This function itself performs the server call init_process() which returns 0 in create_flags from server/process.c:356 So the problem is that there is no startup_info -> server call returns 0 -> no console for the first process. Setting process->create_flags = CREATE_NEW_CONSOLE from init_process() call fixes the problem BUT with this winedbg starts up in a small ugly windows console that is not resizeable :-/ Anyone knows how to fix this? Greetings Peter

2 2

Re: wine bugs in win.c
by Uwe Bonnes 23 Dec '03

23 Dec '03

>>>>> "kscho" == kscho <kscho(a)tibetsystem.com> writes: kscho> Hi~ I'm interested in wine. and find some bug... window's kscho> caption is optional, but current is not. kscho> wine/windows/win.c kscho> line 1087 /* Correct the window style - stage 2 */ Your contribution is appreciated. But better read http://www.winehq.com/site/sending_patches It make's the patch easier to integrate. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Re: ilink32
by Flameeyes 22 Dec '03

22 Dec '03

Adrian Smarzewski wrote: > I would like to run Borland Ilink32 under Wine. > where can I find _working_ patch for version 20031118? Please anyone knows? Seems like ilin32 checks for reservation of some memory areas, to be sure to be run on a Windows system. Also, these areas changes with the version of windows provided to ilink32. If anyone can help me to find where reservations are wrote, I'll try to find them out and add them. -- Flameeyes <dgp85(a)users.sourceforge.net> You can find LIRC for 2.6 kernels at http://flameeyes.web.ctonet.it/

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
27
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel December 2003