Hi Daniel, Thanks for the reply.. I actually did improve the error handler and found that it returned net error 5 (bad MOA interface). I received this error when I tested it at yet another studio to try and rule out any network issues from the first place. Again, half the macs worked, the other half gave the error.. I'm really not sure what's causing it, any idea?
I'll buy whoever helps me solve this problem a pint, heck, make it a keg.. 12 hours till my deadline ;( cheers, James Acres > > From: Daniel Plaenitz <[EMAIL PROTECTED]> > Date: 2002/07/21 Sun PM 07:56:22 EDT > To: [EMAIL PROTECTED] > Subject: RE: <lingo-l> getNetText problem on iMacs? > > At 18:17 21.07.2002 -0400, James Acres wrote: > > >I'm working on a cross-platform projector (it's on a hybrid CD). It uses > >getNetText() to send and receive data to a PHP script. It's worked > >perfectly on every Windows PC I've tested it on, as well as a G3 and a > >powermac that we have in the office. However, I tested it on 4 G3 iMacs > >at a friend's studio today, and I received the same error from all of > >them while trying connecting to the PHP script.. > > > >Unfortunately, I didn't have great error-logging routines in this > >version, so I wasn't able to grab the getNetError() code, but I do know > >that it wasn't returning "OK" and didn't seem to be one of the common > >errors (as I have a function that returns most of the common connection > >error codes back as strings, yet this one didn't yield anything in the > >"case of" statement..) > > James, > > I guess you hope for something which might retrieve that error w/o doing > the test once again, alas, there are too many possible points of failure. > > Chances are that there is something special about those "4 G3 iMacs at a > friend's studio today" but them being iMacs is not necessarily the 'culprit'. > > Your friend may have some special habit of configuring those boxen or that > network's firewall, proxy, DNS, ... have been setup in a way your script > didn't anticipate. Too many variables. > > The case statement supports the really useful otherwise: clause. Use it > to report the netError() in case any expected error condition doesn't > apply. Examples of handlers to do this may be found at > http://www.lingo.de/wwwboard/messages/135.htm or > http://www.directoru.com/community/chartsAndTables/netLingoErrorCodes.html > > I'd recommend to build a new projector with enhanced error handling. Test > it again were it failed. Test it at some other friend's G3 iMacs. If this > poses a problem, pack a stripped-down (bare bone) version into a > mac-friendly archive, put it at some URL and post that URL here. > > Other folks asking for test/feedback got plenty of response here so I > believe it's worth the trouble of creating the bare bones example. You > might even add a link to a .zip archive to avoid the pc-users feeling > excluded ;-) > > > Good luck, > > Daniel Plaenitz > > > [To remove yourself from this list, or to change to digest mode, go to >http://www.penworks.com/lingo-l.cgi To post messages to the list, email >[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for >learning and helping with programming Lingo. Thanks!] > [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
