Path: dummy.bahnhof.se!newsfeed1.swip.net!swipnet!newsfeed.cwix.com!152.163.199.19!portc03.blue.aol.com!portc03.blue.cs.com!audrey01.news.cs.com!not-for-mail
From: fitzpatri8@cs.comLESSPAM (Fitzpatri8)
Newsgroups: comp.sys.atari.st
Subject: Re: Geneva/NeoDesk
Lines: 66
NNTP-Posting-Host: ladder07.news.cs.com
X-Admin: news@cs.com
Date: 31 May 1999 04:12:15 GMT
References: <3751e4008a97b40@oden.se>
Organization: CompuServe (http://www.compuserve.com/)
X-Newsreader: AOL Offline Reader
Message-ID: <19990531001215.05083.00006223@ngol03.news.cs.com>
Xref: dummy.bahnhof.se comp.sys.atari.st:17808

>This would force me to install several thousand programs in this way
>and I would have to continue doing it for each new prgram I get or make.
>That is totally ridiculous, so I won't do it.

     I understand completely.

>I definitely want that patch, so I hope you can tell me where to find it.


     A search of my archives uncovered this publicly released email on the
subject:

 >> Thanks for the reply.  Unloading was enabled by default, however
 >>when I turn off unloading and try to run an application, I get a
 >>dialog box  saying "Invalid handle!", "handle=0", with two buttons,
 >>"continue" and  "tolerate". Doesn't matter which button I choose, I
 >>get either 2 or 3  bombs depending on the application I am attempting
 >>to run.  The TT  doesn't crash,  it just dumps me back to Thing.   I
 >>can't even  figure out if the "invalid handle" message is coming from
 >>Geneva,  Thing or TOS.
 >
 >You've found a bug in Geneva :) I just checked it: Thing uses - if
 >available - an extended way to run applications, which also allows to
 >limit a program's memory usage. Unfortunately, Geneva doesn't handle
 >the special case "limit to 0 bytes", which actually means "unlimited",
 >so all applications run by Thing which do not have their memory
 >limited won't be able to allocate any memory, which also causes the
 >opening of VDI workstations to fail (the application which presented
 >you the "invalid handle" alert didn't check whether v_opnvwk() failed
 >and therefore used the handle which actually means "no handle").
 >
 >As a workaround, use Geneva on top of MiNT, then this problem will
 >disappear (and unloading Thing should also be working smoothly). If
 >using MiNT is not an option for you, use a hex editor and search for
 >the bytes $3a3c $0f01 $6004 $3a3c $0701 in thing.app and replace $0f01
 >with $0c01 and $0701 with $0401. This will disable memory limitation
 >in programs run by Thing completely (so even if you enter some value
 >in the application options, it won't be used).
 >
 >I will report this bug (together with some others) to Dan Wilga, and I
 >hope he'll fix it in the next release (if there will be one).
 >
 >> I was puzzled by the announcement that Thing 1.20 would NOW work
 >>with Geneva.  On my system, 1.09 seems more compatible with Geneva
 >>than 1.27.
 >
 >As you see, that's not Thing's fault. Btw, using Thing 1.20 will also
 >cure the problem, but of course you'll then be missing some of the new
 >features in 1.27 ...
 >
 >
 >Ciao
 >
 >Thomas
 >
 >
 >--
 >Thomas Binder (Gryf @ IRCNet)  gryf@hrzpub.tu-darmstadt.de


     Having not read the documentation for Geneva-specific programming, I shant
speculate as to what constitutes a "bug" and what may simply be a faulty
assumption.  It's sufficient to say that I did perform the patch on a demo copy
of Thing 1.27 here and the fix worked as advertised.

Tom
