Menu
▾
▴
Re: [AL] Problems in X
|
From: Marcelo T. <mar...@in...> - 2001-05-30 05:51:04
|
Thank U. I downloades the newer drivers and they work OK BYE >From <all...@ca...> Wed May 30 03:44:49 2001 Received: from oosix.icce.rug.nl [129.125.14.80] by canvaslink.com with ESMTP (SMTPD32-6.00) id A4F01CC01D4; Wed, 30 May 2001 03:44:48 -0400 Received: (from hein@localhost) by oosix.icce.rug.nl (8.9.3/8.9.3/Debian 8.9.3-21) id JAA30113 for al...@ca...; Wed, 30 May 2001 09:42:34 +0200 From: Hein Zelle <he...@ic...> Date: Wed, 30 May 2001 09:42:34 +0200 To: al...@ca... Message-ID: <200...@oo...> Mail-Followup-To: al...@ca... References: <001201c0e89d$109ce0c0$0a0...@mw...> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001201c0e89d$109ce0c0$0a0...@mw...>; from de...@me... on Tue, May 29, 2001 at 08:11:24PM -0400 Subject: Re: [AL] Which network library should I use for mmorpg? Precedence: bulk Sender: all...@ca... Reply-To: al...@ca... X-UIDL: 291336202 Status: O Content-Length: 1610 Lines: 24 The Walters wrote: > I am going to begin a online RPG project. I am wondering which network library people think I should use. I am looking for answers from people who have actually used the library they are supporting. Right now I am thinking about either Winsock or Libnet. I am sort of leaning towards Libnet because it looks slightly easier to use than Winsock. Both of them run in linux I believe? I am wondering if Libnet will give me enough control to handle everything for the online rpg which I think it will. Does anyone have any thoughts or suggestions to help guide me on my decision? I don't think winsock will work on linux, it's rather typically windows specific :> However, the standard unix sockets functions look, as far as I know, quite a bit like the windows ones. I have not actively used libnet yet, but I suppose it's the best choice for portability. Should you decide to go for basic sockets, I can advise you to use our (Martijn Versteegh & me) Fusebox and Plug C++ classes (If you don't mind using C++, that is). They form a wrapper around unix sockets. The windows version using winsock is not finished yet, however. Please send me an email if you want to use this. If you can avoid it I would advise against using bare socket code: It's quite a bit of programming to get it right, and it took us a while to get things working robustly. Hein Zelle >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-< Hein Zelle he...@ic... http://www.icce.rug.nl/~hein >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-< >From <all...@ca...> Wed May 30 06:53:29 2001 Received: from vesuri.Helsinki.FI [128.214.205.10] by canvaslink.com with ESMTP (SMTPD32-6.00) id A1281476015E; Wed, 30 May 2001 06:53:28 -0400 Received: (from valiviit@localhost) by vesuri.Helsinki.FI (8.11.4/8.11.4) id f4UApE317825 for al...@ca...; Wed, 30 May 2001 13:51:14 +0300 (EET DST) From: Mika Valiviita <val...@cc...> Message-Id: <200...@ve...> In-Reply-To: <OE2...@ho...> from =?ISO-8859-1?Q?Javier_Gonz=E1lez?= at "May 28, 2001 06:50:41 pm" To: al...@ca... Date: Wed, 30 May 2001 13:51:13 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [AL] Problems with 3.9.35/36 and mingw32 Precedence: bulk Sender: all...@ca... Reply-To: al...@ca... X-UIDL: 291336203 Status: O Content-Length: 474 Lines: 14 >> PS. Anyone know about the 'parse error before HMONITOR' problem on lines >> 148,149 of ddraw.h? > >What directx sdk and what mingw32 winapi version? I got those files mentioned in readme.mgw, dx70_min.zip and dxlibs.zip, no mention of winapi in the readme, I don't know if that is included. The parse error goes away if I comment out DECLARE_HMONITOR in the 2 .h files of allegro that have them. I just wonder if that causes problems. Mika V. -- #include ".signature" >From <all...@ca...> Wed May 30 07:00:39 2001 Received: from vesuri.Helsinki.FI [128.214.205.10] by canvaslink.com with ESMTP (SMTPD32-6.00) id A2D614CC015E; Wed, 30 May 2001 07:00:38 -0400 Received: (from valiviit@localhost) by vesuri.Helsinki.FI (8.11.4/8.11.4) id f4UAwOR15466 for al...@ca...; Wed, 30 May 2001 13:58:24 +0300 (EET DST) From: Mika Valiviita <val...@cc...> Message-Id: <200...@ve...> To: al...@ca... Date: Wed, 30 May 2001 13:58:24 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [AL] Problems with 3.9.35/36 and mingw32 Precedence: bulk Sender: all...@ca... Reply-To: al...@ca... X-UIDL: 291336204 Status: O Content-Length: 427 Lines: 11 Regarding my 'plasmaeffect' problem, it seems that it happens with examples that use 320x240 mode and DXSO,DXAC or DXSA. So it is likely my gfxcard can't handle that. They work with DXWN, GDIB and dos version. As for the 800x600x16 problem, the DXSO,DXAC and DXSA won't open that, but 640x480x8 instead. Again, the larger size works with DXWN and GDIB, and also with dos version of Allegro. Mika V. -- #include ".signature" >From <all...@ca...> Wed May 30 07:56:31 2001 Received: from hotmail.com [64.4.14.207] by canvaslink.com with ESMTP (SMTPD32-6.00) id AFEE180D015E; Wed, 30 May 2001 07:56:30 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 30 May 2001 04:54:13 -0700 X-Originating-IP: [62.83.100.28] From: =?iso-8859-1?Q?Javier_Gonz=E1lez?= <xav...@ho...> To: <al...@ca...> References: <200...@ve...> Date: Wed, 30 May 2001 13:50:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: <OE7...@ho...> X-OriginalArrivalTime: 30 May 2001 11:54:13.0720 (UTC) FILETIME=[3EF93D80:01C0E8FF] Subject: Re: [AL] Problems with 3.9.35/36 and mingw32 Precedence: bulk Sender: all...@ca... Reply-To: al...@ca... X-UIDL: 291336205 Status: O Content-Length: 584 Lines: 15 > >> PS. Anyone know about the 'parse error before HMONITOR' problem on lines > >> 148,149 of ddraw.h? > > > >What directx sdk and what mingw32 winapi version? > > I got those files mentioned in readme.mgw, dx70_min.zip and dxlibs.zip, > no mention of winapi in the readme, I don't know if that is included. > > The parse error goes away if I comment out DECLARE_HMONITOR in the > 2 .h files of allegro that have them. I just wonder if that causes > problems. try getting the latest winapi version (0.5 i think) in the files section of this site http://sourceforge.net/projects/mingw >From <all...@ca...> Wed May 30 09:07:14 2001 Received: from mail.libertysurf.net [213.36.80.91] by canvaslink.com with ESMTP (SMTPD32-6.00) id A0817401D2; Wed, 30 May 2001 09:07:13 -0400 Received: from zephyr (213.36.130.236) by mail.libertysurf.net (5.1.053) id 3B13383B0002EF35 for al...@ca...; Wed, 30 May 2001 15:04:59 +0200 Message-ID: <001601c0e909$2993bf60$ec8224d5@zephyr> From: "Eric Botcazou" <ebo...@li...> To: "Allegro mailing list" <al...@ca...> References: <200...@ve...> Date: Wed, 30 May 2001 14:55:53 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Subject: Re: [AL] Problems with 3.9.35/36 and mingw32 Precedence: bulk Sender: all...@ca... Reply-To: al...@ca... X-UIDL: 291336206 Status: O Content-Length: 906 Lines: 27 > Regarding my 'plasmaeffect' problem, it seems that it happens with > examples that use 320x240 mode and DXSO,DXAC or DXSA. So it is > likely my gfxcard can't handle that. Weird because, beginning with 3.9.35 version, Allegro queries the gfx driver for the list of supported fullscreen modes and doesn't even try to set up any mode that is reported as unavailable. > As for the 800x600x16 problem, the DXSO,DXAC and DXSA won't open that, > but 640x480x8 instead. You probably don't have enough VRAM to set up a DirectX fullscreen 800x600x16 mode: it requires 800x600x2=960000 bytes plus the overhead due to the Windows desktop. > Again, the larger size works with DXWN and GDIB, Yes, because both modes allocate no additional amount of VRAM beyond the Windows dekstop. > and also with dos version of Allegro. Yes, no desktop under DOS, hence no overhead. -- Eric Botcazou ebo...@mu... |