comp.os.os2.beta (Usenet) Saturday, 06-Nov-1999 to Friday, 12-Nov-1999 +----------------------------------------------------------------------------+ From: kulle@t-online.de 07-Nov-99 14:36:10 To: All 07-Nov-99 15:15:21 Subj: Too much memory allocated From: kulle@t-online.de (Klaus Kulbarsch) Hi, after installing FP11 on a German WARP 4 (the install did run smoothly without any problem), two programs show a strange behaviour. One of them doesn't start anymore but only produces such an error-message: (I'll try to translate it in English) "No more memory could be allocated. The program will be stopped. 4290787314 bytes should be allocated" and only the "OK" - Button to choose. I know: 4 GB is quite a lot, but: on Warp 4 GA it ran without any problem? Another thing happens, when opening the file-dialog in my favourite editor, MED for OS/2: if there's no CD in my CD-ROM, it claims about "drive Z: not ready" but goes on working when klicking on the apropriate button to close that window. Same as mentioned above: with WARP 4 GA no problem. Everything else seems okay - so far ... If someone out there has any hints to solve these problems I would be glad to hear it. Thank you in advance. This OS/2 WARP 4 system uptime is 1d 15h 30m 49s 539ms (en). -- ProNews/2 Klaus Kulbarsch FIDO preferred ;-) 2:2426/1205 33.6 2:2426/1206 X75 --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: T-Online (1:109/42) +----------------------------------------------------------------------------+ From: Jan.Danielsson@falun.mail.telia.com 07-Nov-99 16:17:02 To: All 07-Nov-99 15:15:21 Subj: Re: Too much memory allocated From: "Jan Danielsson" >One of them doesn't start anymore but only produces such an >error-message: >(I'll try to translate it in English) > >"No more memory could be allocated. The program will be stopped. >4290787314 bytes should be allocated" and only the "OK" - Button to >choose. > >I know: 4 GB is quite a lot, but: on Warp 4 GA it ran without any >problem? I don't think that the application did attempt to allocate that much memory before. It's more likely that some API now modifies some variable in a way it didn't before the fixpak. I don't think it's a problem you'll be able to solve yourself (unless you are skilled in kernel debugging :-). Contact the developer of the application. Odd problem, though.. Can't really see how it could happen.. >Another thing happens, when opening the file-dialog in my favourite >editor, MED for OS/2: if there's no CD in my CD-ROM, it claims about >"drive Z: not ready" but goes on working when klicking on the >apropriate button to close that window. Same as mentioned above: with >WARP 4 GA no problem. I have seen that behavior in Warp4 GA. Someone told me it was a driver problem. After installing a fixpak, I never saw the problem again. [...] >ProNews/2 Klaus Kulbarsch >FIDO preferred ;-) *Ofcourse* it is! :-) (2:205/323) /j --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Telia Internet (1:109/42) +----------------------------------------------------------------------------+ From: kulle@t-online.de 07-Nov-99 20:32:08 To: All 07-Nov-99 20:07:01 Subj: Re: Too much memory allocated From: kulle@t-online.de (Klaus Kulbarsch) Von "Jan Danielsson" am Sun, 7 Nov 1999 16:17:04: > >I know: 4 GB is quite a lot, but: on Warp 4 GA it ran without any > >problem? > > I don't think that the application did attempt to allocate that much memory > before. It's more likely that some API now modifies some variable in a way it > didn't before the fixpak. I don't think it's a problem you'll be able to > solve yourself (unless you are skilled in kernel debugging :-). Ierks - no that's not my thing ... > Contact the developer of the application. I did - it was a good advice. He knows about the problem and has a fixed version of the program on his homepage - now it's running without that error-message, but the description of some fields is not readeable ;-) It's really funny: you wanna fix your system, but then the problems are going to start .... > Odd problem, though.. Can't really see how it could happen.. Yeah ... > >Another thing happens, when opening the file-dialog in my favourite > >editor, MED for OS/2: if there's no CD in my CD-ROM, it claims about > >"drive Z: not ready" but goes on working when klicking on the > >apropriate button to close that window. Same as mentioned above: with > >WARP 4 GA no problem. > I have seen that behavior in Warp4 GA. Someone told me it was a driver > problem. After installing a fixpak, I never saw the problem again. Curious - maybe I find another IDEDASD.EXE packet solving this. > [...] > >ProNews/2 Klaus Kulbarsch > >FIDO preferred ;-) > > *Ofcourse* it is! :-) (2:205/323) Yeah! Many thanks for your response. This OS/2 WARP 4 system uptime is 1d 16h 38m 07s 820ms (en). -- ProNews/2 Klaus Kulbarsch FIDO preferred ;-) 2:2426/1205 33.6 2:2426/1206 X75 --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: T-Online (1:109/42) +----------------------------------------------------------------------------+ From: nospam@nospamnospam.com 08-Nov-99 19:23:29 To: All 08-Nov-99 20:06:28 Subj: Re: Netscape cache messing up From: nospam@nospamnospam.com (Magnus Olsson) On Fri, 5 Nov 1999 08:32:04, andy wrote: > > I'll take the opportunity to thank you and the IBM team for > > communicator 4.61. I'm not completely happy with it (drag and drop > > still works better with 2.02, which is also more stable), but it's a > > big leap forward from 4.04 and caching works *much* better than in > > 2.02!:-) > > The only stability problem I've got (up to now) is that the messenger crashes every > first time I start it I've got something that may be related. Some ten times i've had the messenger crash when selecting a warpcast message *right after* retrieving new messages. If i restart messenger and select an unread warpcast message it crashes again, and again, but if i select an already read message, i can thereafter read all messages without any crashing. BTW: I think the fact that it's always been warpcast messages is only coincidence, if there is such a thing:-) When talking about problems with communicator, the thing i find most annoying is that downloads quietly finish before they are *really* finished. > > greetings > Andreas > - all the best Magnus Olsson --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Utfors AB (1:109/42) +----------------------------------------------------------------------------+ From: stefanj@gte.net 09-Nov-99 11:13:10 To: All 09-Nov-99 10:58:10 Subj: MAMERun beta 3 From: stefanj@gte.net (Jason Stefanovich) I just uploaded beta 3 my OS/2 PM frontend MAMERun for the DOS version of MAME. You can get it at the MAMERun homepage at: http://home1.gte.net/stefanj/mamerun.htm or at Hobbes: ftp://hobbes.nmsu.edu/pub/incoming/mrunb3.zip This is the ONLY frontend for MAME under OS/2. Whats New Beta 3: * Hotlist now shows actual game names * Added extra options for vector games * Added option to play back recorded files * Added support for windowed modes * Added support for external commands * Cleaned up the interface * Removed the VPOBJ library * No longer need the prebuilt mamerun.ini and defaultmamerun.ini * Fixed misc. small bugs What is it: MAMERun is a FREEWARE OS/2 PM frontend for the DOS version of MAME (Multi. Arcade Machine Emulator). A Frontend is a program that makes it easier for the user to interface with their application, which usually has a command line interface. MAME is a very popular emulator that allows you to run thousands of classic arcade games on your PC (if you own the ROMs). You can find the MAME homepage at http://mame.retrogames.com/. The Official (and very good) OS/2 PM port of MAME was done by Marty Amodeo and is at http://emuos2.vintagegaming.com/. Requirements: OS/2 MAME for DOS (I used version .36 beta 8) DOS Support installed RexxUtil joystick device driver (for joystick support, download from hobbes or DDPAK) ROMs (DO NOT ASK ME FOR, OR WHERE TO GET ROMS!!) --- WtrGate+ v0.93.p7 sn 165 * Origin: Origin Line 1 Goes Here (1:109/42) +----------------------------------------------------------------------------+ From: Andreas.Buchholz@gmx.de 10-Nov-99 00:14:17 To: All 10-Nov-99 05:30:17 Subj: Re: Too much memory allocated From: Andreas.Buchholz@gmx.de (Andreas Buchholz) In article , kulle@t-online.de (Klaus Kulbarsch) wrote: ... >Another thing happens, when opening the file-dialog in my favourite >editor, MED for OS/2: if there's no CD in my CD-ROM, it claims about >"drive Z: not ready" but goes on working when klicking on the >apropriate button to close that window. Same as mentioned above: with >WARP 4 GA no problem. config.sys: AUTOFAIL=YES -- Ciao \\|// Andreas (o -) -----------------------------------------------------.oOOo--(_)--oOOo.---- If at first you don't succeed, work for Microsoft. --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: Completely unorganized (1:109/42) +----------------------------------------------------------------------------+ From: kulle@t-online.de 10-Nov-99 12:09:12 To: All 10-Nov-99 10:29:14 Subj: Re: Too much memory allocated From: kulle@t-online.de (Klaus Kulbarsch) Von Andreas.Buchholz@gmx.de (Andreas Buchholz) am Tue, 9 Nov 1999 23:14:35: > >Another thing happens, when opening the file-dialog in my favourite > >editor, MED for OS/2: if there's no CD in my CD-ROM, it claims about > >"drive Z: not ready" but goes on working when klicking on the > >apropriate button to close that window. Same as mentioned above: with > >WARP 4 GA no problem. > > config.sys: > > AUTOFAIL=YES Yes - thanks, would have been a possibility. But it seems the better choice was upgrading from V. 1.24 to 1.26 ;-) Nearly the same as with the other problem. This was known since FP 10 and Carsten Arnold, author of TRANSLATOR had a fix for it. Now everything's working well. Thanks to all of you! -- ProNews/2 Klaus Kulbarsch FIDO preferred ;-) 2:2426/1205 33.6 2:2426/1206 X75 --- WtrGate+ v0.93.p7 sn 165 * Origin: Usenet: T-Online (1:109/42) +----------------------------------------------------------------------------+ +============================================================================+