In article <87n1bmw6ec.fsf@wine.dyndns.org>, "Alexandre Julliard" <julliard@winehq.com> wrote:> This is release 20010216 of Wine, a free implementation of Windows on > Unix. This is still a developers only release. There are many bugs and > unimplemented features. Most applications still do not work correctly. >It looks like wineinstall is still somewhat broken. It sucessfully installs but dosn't find the Windows registry. ---------- Searching for an existing Windows installation... found. Created /root/.wine/config using your existing Windows installation. You probably want to review the file, though. Checking for real Windows registry... Not found, default Wine registry will be installed. Compiling regapi... rm -f regapi && ln -s ../../wine regapi Preparing to install default Wine registry entries... Installing default Wine registry entries... Warning: could not find wine config [Drive x] entry for current working directory /home/drovar/wine-20010216; starting in windows directory. Warning: /home/drovar/wine-20010216/programs/regapi/regapi not accessible from a DOS drive Warning: /home/drovar/wine-20010216/programs/regapi/regapi not accessible from a DOS drive Warning: /home/drovar/wine-20010216/programs/regapi/regapi not accessible from a DOS drive Registry entries successfully installed. Linking root's user registry hive to the global registry... Installation complete for now. Good luck (this is still alpha software). If you have problems with WINE, please read the documentation first, as many kinds of potential problems are explained there.
This is release 20010216 of Wine, a free implementation of Windows on Unix. This is still a developers only release. There are many bugs and unimplemented features. Most applications still do not work correctly. Patches should be submitted to "wine-patches@winehq.com". Please don't forget to include a ChangeLog entry. WHAT'S NEW with Wine-20010216: (see ChangeLog for details) - Several PostScript driver improvements. - Improved enhanced metafiles support. - Beginnings of PowerPC support. - Lots of bug fixes. See the README file in the distribution for installation instructions. Because of lags created by using mirror, this message may reach you before the release is available at the ftp sites. The sources will be available from the following locations: http://www.ibiblio.org/pub/Linux/ALPHA/wine/development/Wine-20010216.tar.gz ftp://ftp.infomagic.com/pub/mirrors/linux/sunsite/ALPHA/wine/development/Wine-20010216.tar.gz ftp://ftp.fu-berlin.de/unix/linux/mirrors/sunsite.unc.edu/ALPHA/wine/development/Wine-20010216.tar.gz ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/Wine-20010216.tar.gz It should also be available from any other site that mirrors ibiblio.org. For more download locations, see http://ftpsearch.lycos.com. You can also get the current source directly from the CVS tree. Check http://www.winehq.com/dev.html for details. If you submitted a patch, please check to make sure it has been included in the new release. If you want to get the new releases faster, you can subscribe to the wine-patches mailing list by sending a mail containing 'subscribe wine-patches your_address' to majordomo@tiger.informatik.hu-berlin.de. You will get a patch against the previous release when a new one is released. Wine is available thanks to the work of many people. See the file AUTHORS in the distribution for the complete list. -- Alexandre Julliard julliard@winehq.com
Alexandre Julliard <julliard@winehq.com> wrote:> This is release 20010216 of Wine, a free implementation of Windows > on Unix. This is still a developers only release. There are many > bugs and unimplemented features. Most applications still do not > work correctly. >Problem: /usr/bin/wine is not more the wine-binary, but instead a shell script which sometime launches xmessage. /usr/bin/notepad is still a softlink to /usr/bin/wine, but wine needs as $1 a program to launch, so just typing "notepad" results in an error message. I guess, this is the reason why winedbg fails, cause it is too linked to /usr/bin/wine.> - Several PostScript driver improvements. >I get actually: Invoking /usr/bin/wine.bin origin.exe ... err:psdrv:PSDRV_AFMGetCharMetrics missing ;, failed. [C 0 ; WX 600 ; N null] err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. Are these locations to the afm-files hard coded in the sources? (afm.c line 489 ff.) I guess, this is not a good idea. Many thanks, Hilmar -- Wer HTML postet oder gepostetes HTML quotet oder sich gepostetes oder gequotetes HTML beschafft, um es in Verkehr zu bringen, wird geplonkt. Dresdener LaTeX-Stammtisch: http://www.ifbus.de/~schubi/LatexDD.html http://rudi.urz.tu-dresden.de/~hille/
In article <3olo69.4sq.ln@preusse-16223.user.cis.dfn.de>, Hilmar Preusse <hille42@web.de> wrote:>> - Several PostScript driver improvements. >> >I get actually: > >Invoking /usr/bin/wine.bin origin.exe ... >err:psdrv:PSDRV_AFMGetCharMetrics missing ;, failed. [C 0 ; WX 600 ; N null] >err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. >err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. >err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. >err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found.These are more like warnings.>Are these locations to the afm-files hard coded in the sources? >(afm.c line 489 ff.) I guess, this is not a good idea.Why not, since these are standard font description files? It is better than having the user supply a list of .AFM file in his .wine/config. Ciao, Marcus
>>>>> "Marcus" == Marcus Meissner <marcus@jet.franken.de> writes:> In article <3olo69.4sq.ln@preusse-16223.user.cis.dfn.de>, > Hilmar Preusse <hille42@web.de> wrote: >>> - Several PostScript driver improvements. >>> >> I get actually: >> >> Invoking /usr/bin/wine.bin origin.exe ... >> err:psdrv:PSDRV_AFMGetCharMetrics missing ;, failed. [C 0 ; WX 600 ; N null] >> err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. >> err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. >> err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found. >> err:psdrv:PSDRV_AFMGetCharMetrics No whitespace found.> These are more like warnings.>> Are these locations to the afm-files hard coded in the sources? >> (afm.c line 489 ff.) I guess, this is not a good idea.> Why not, since these are standard font description files?> It is better than having the user supply a list of .AFM file in his > .wine/config.> Ciao, MarcusI changed afm.c to use an [afmdirs] section as well as [afmfiles]. In afmdirs I specify the directories where wine should search for afm files. I also disabled the 4 hardcoded paths and moved them to the ini file. It works great. I still need to get Word to actually write something instead of spitting out empty sheets of paper. In Word, using the menu File->Print... makes word say there is no printer installed. Clicking on the print icon in word does print, but so far only blank paper is being printed. regards, Bernhard Ege