It is the ODBC PPC version that you should be using. If I remember
correctly, the last Butler driver was PPC only, there wasn't a 68k version
released.

This shouldn't affect Garth's issues because he is trying to connect from a
Win box and there doesn't even need to be an ODBC installed on the Butler
box.

Hope this helps,

Steve Smith

Skadt Information Solutions
Office: (519) 624-4388
GTA:    (416) 606-3885
Fax:    (519) 624-3353
Cell:   (416) 606-3885
Email:  [EMAIL PROTECTED]
Web:    http://www.skadt.com


> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:owner-witango-talk@;witango.com]On Behalf Of Bill Conlon
> Sent: October 31, 2002 2:27 PM
> To: Multiple recipients of list witango-talk
> Subject: RE: Witango-Talk: T3 tcp/ip db connection (licensing issue?)
>
>
> Garth,
>
> Thanks.  I'm working these issues right now.  Still can't get Butler to
> run reliable on the G3 Desktop/9.2.2, even with Base Extensions plus
> Butler necessities.  What's baffling is it runs fine on my similar
> desktop, and the G3 in question is the most stable in the whole shop
> (never needs a forced reboot).  I'll solve it eventually, and in the
> interim use my desktop as the database server.
>
> But, the big stumbling block is I haven't been able to find the plain old
> ODBC CP.  I only have the  PPC version -- even if I install a fresh copy
> from the Tango 3.5 CD (or Tango 2000 for that matter).  I thought it was
> in the System Software, but I can't run the OS 7.5 or 8 installers on a
> G3 desktop, and the 8.1 CD doesn't have it.  My Office 98 CD only has the
> PPC CP.
>
> Before I switch to AppleTalk and try to install onto my MacSE (It worked
> when I tried it last year), do you know where I should look for this
> control panel?
>
> Thx, bill
>
> >I have had a t3 installation running very stably on 7.6.1 for the
> >past 4  or so years and haven't upgraded OS on that machine (doidn't
> >want to upset the apple cart).
> >
> >Where did you experience problems initially when you were setting up
> >the connection - it is pretty straight forward, so maybe there's
> >something missing in your setup.
> >
> >If you are using the Visigenic ODBC drivers that come with t3
> promo CD then:
> >1. Install the TCP/IP link port in Butler
> >2. Create a tcp/ip dsn on your app server box (ie wither through the
> >ODBC Control panel - not the ODBC PPC Control Panel which doesn't
> >work with the Visigenic drivers, or using t3 editor which is the
> >method I prefer)
> >3. Create a taf and reference the appropriate dsn - it should load
> >the tables (this is where I'm getting stuck on my win2k box)
> >
> >As described in these posts I have recently tested it on 9.2.2 on a
> >G3 Powerbook (testing a Win to Mac tcp/ip connection - more on that
> >below) I didn't have any probs with Butler hanging when I was
> >accessing it though Tango 3 editor on the win box hung every time I
> >attempted this.
> >
> >I haven't recently tried a tcp/ip from one mac to another but I could
> >and will. I'll access my OS 7.6.1 server via tcp/ip from this Mac and
> >see how it goes and report to you if you'd like.
> >
> >I am still tying to figure out where my problem is with my win2k box
> >since everytime I try to load the tables to add them to a taf on the
> >win box, the request via tcp/ip goes through to the 7.6.1 box and
> >Butler begins loading the tables, but either doesn't fincish the
> >process, or can't send the data back. Either way, though, Butler
> >doesn't hang, it is still processing other (local) requests at the
> >same time.
> >
> >If you have any insight into my prob I'd appreciate it - if you have
> >a win2k box I'd love to hear from you if you could set up t3 on that
> >(from the Promo CD) and test the tcp/ip out and see if it works.
> >
> >I have a question? When a Mac or Win box sends a tcp/ip request to
> >Butler, it has nothing to do with the ODBC drivers on the Butler box
> >does it? I wouldn't have thought so but I just want to know for sure
> >so I can rule that out of my testing.
> >
> >cheers
> >Garth
> >
> >
> >>This thread got me curious, so I got out my old Tango 3.52
> promotional CD
> >>and installed Butler 2.52.  My thinking was that while we'll be staying
> >>with MacOS9 for another year, I might as well start preparing for
> >>migration from Filemaker to a RDBMS.
> >>
> >>So I got it running locally on my development machine (PowerMac G3/
> >>MacOS9.2.2) -- no problems.  But the first migration step is a separate
> >>DB server (currently Filemaker Pro 4 and Tango run on the
> samemachine, so
> >>I loaded ButlerSQL on a similar PMacG3/9.2.2 system, and after many
> >>frustrating attempts, finally got connected from my development machine,
> >>both in the Tango editor and via the Butler client.
> >>
> >>But what really perplexes me is the instability of Butler.  It hangs
> >>whenever any background process runs.  And when it hangs, it is really
> >>difficult to start (several power cycles required with Preferences
> >>trashing required).
> >>
> >>I'm hoping that if I turn off enough extensions I'll get this working.
> >>The system in question is pretty vanilla, but I could put MacOS 8.6 on a
> >>partition if that works.  Anyone remember any tricks or conflicts with
> >>Butler?
> >>
> >>Thanks.
> >>
> >>
> >>>I now know the following about this situation:
> >>>- I can setup a taf to a access db on the Win2k box so I know that
> >>>tango 3 on the win 2k server is working properly.
> >>>- I setup a new db on the Mac and a new tcp/ip dsn to connect to it
> >>>from the Win2k box and it connects to Butler on the Mac but hangs. If
> >>>I delete the file source then it gives me the appropriate error. So I
> >>>know that the control requests made via the Butler WIN32 dsn are
> >>>working correctly.
> >>>- When I request to see the tables of the tcp/ip dsn which is listed
> >>>in the tango 3 editor on the Win 2k box, I can see the user appear in
> >>>the Butler Users window  on the Mac and see the number increase from
> >>  >1 to 9 in increments (which is what a DAM dsn does from a user on the
> >>>Mac itself) so I know that the Butler WIN32 dsn is requesting the
> >>>data and finding it correctly, but it just doesn't send the data back
> >>>and tango 3.6 editor on the Win2k box hangs when that happens.
> >>>
> >>>We have run netstat to see what's happening when we make the request,
> >>>and it shows the win2k box using port 1039 and going to the mac
> >>>butler port of 8682 correctly, however maybe the data i s coming back
> >>>on a different port which is being blocked?
> >>>
> >>>So, my summation is that the problem is either
> >>>- port mapping
> >>>- MTU problem on the Mac (as the mac is running on a ADSL connection)
> >>>
> >>>what do you think it would be?
> >>>If I can get this running this will solve a major prob that we are
> >>  >having with some firewalls blocking access to the Mac from outside on
> >>  >the Internet (because it can only be accessed through port 81 for
> >>  >http and port 22 for ftp).
> >>  >
> >>  >any suggestions are received gratefully.
> >>>
> >>>Garth
> >>>
> >>>
> >>>>below...
> >>>>
> >>>>>Do you have an T3 Editor on the Windows box? If so, try
> using the SQL
> Query
> >>>>>window from the editor with the appropriate data source to make a
> >>>>>connection. If it can, you should then be able to eliminate
> the Mac side
> as
> >>>>>the source of the problem.
> >>>>
> >>>>Yep, that's what I was saying - I try a SQL query from the editor on
> >>>>this datasource (which is definitely a tcp/ip dsn) and I can see it
> >>>>access via port 8682, loads the user in the Butler Users window, and
> >>>>then hangs. When we delete the database from the Public Databases
> >>>>folder, it gives us the appropriate error. So we know that we are
> >>>>definitely taking to Butler on the Mac. But that's about all we know
> >>>>at present.
> >>>>
> >>>>>You mentioned that you can see the attempt at a connection
> in the Users
> >>>>>window of Butler. It is a TCP/IP port that is set up and not program
> >>>>>linking, right?
> >>>>
> >>>>Yep, seems to be connecting from the Tango editor Ok when I request
> >>>>the data tables to load.
> >>>>
> >>>>>   Also where was the original taf file created? I seem to
> >>>>>recall problems with taf files that were originally set up
> with Program
> >>>>>Linking rather than TCP/IP after they were moved to a Windows box.
> >>>>
> >>>>Maybe that's where the problem is - I'll create an entirely new taf
> >>>>using the Win T3 editor with a tcp/ip dsn and a new database on the
> >>>>Mac and see how that goes.
> >>>>
> >>>>>The
> >>>>>Butler version that was on that promo CD did not have any
> limitations on
> >>>>>connections to the best of my knowledge.
> >>>>
> >>>>I certainly haven't seen any readme about any limitations on the
> >>>>license apart from the number of concurrent users (which I know to
> >>>>be 10).
> >>>>
> >>>>>One other thing to look at is whether the appropriate port
> is opened to
> the
> >>>>>machine running Butler. I think it needs port 8682 and of course
> >>>>>this should
> >>>>>be set up in both the datasource, and on the port in Butler.
> Also make
> sure
> >>>>>that the port is activated on Butler.
> >>>>
> >>>>yep -using that and that seems to be working (one way anyway -
> >>>>sending control data but maybe not receiving data back to the Win box
> >>>>
> >>>>>I don't think the references to the old P.SQL drivers would
> cause this
> >>>>>problem. Since Pervasive came into the picture in 98 I have
> always had
> both
> >>>>>P.SQL and Butler drivers installed on my Win boxes.
> >>>>
> >>>>well I'll set up an access db and test it with a local datasource as
> >>>>well and get back to you.
> >>>>
> >>>>>Hope this helps,
> >>>>>
> >>>>>Steve Smith
> >>>>>
> >>>>>Skadt Information Solutions
> >>>>>Office: (519) 624-4388
> >>>>>GTA:    (416) 606-3885
> >>>>>Fax:    (519) 624-3353
> >>>>>Cell:   (416) 606-3885
> >>>>>Email:  [EMAIL PROTECTED]
> >>>>>Web:    http://www.skadt.com
> >>>>>
> >>>>>   -----Original Message-----
> >>>>>   From: [EMAIL PROTECTED]
> >>>>>   [mailto:owner-witango-talk@;witango.com]On Behalf Of Garth Penglase
> >>>>>   Sent: October 23, 2002 8:16 AM
> >>>>>   To: Multiple recipients of list witango-talk
> >>>>>   Subject: RE: Witango-Talk: T3 tcp/ip db connection
> (licensing issue?)
> >>>>>
> >>>>>
> >>>>>   I don't think so, since it includes demos using PSQL
> datasources, but
> >>>>>   I'll have a look at the info on the Tango CD and see if I can find
> >>>>>   any clues as to whether it is licensed only for access. I
> have been
> >>  >>>>  using the Mac 3.52 promo version only with Butler so I
> don't know if
> >>>>>   it has limitations otherwise.
> >>>>>
> >>>>>   The installer seems to make references to other ODBC
> sources I think.
> >>>>>
> >>>>>   When I use the Windows Tango 3.52 Editor that comes on
> the CD to open
> >>>>>   a taf with the Butler tcp/ip link as the datasource, I can see the
> >>>>>   Butler drivers making a connection with Butler on the Mac but then
> >>>>>   Butler seems to time out (something times out) because everything
> >>>>>   just sits there - whatever user account was used to open
> the taf in
> >>>>>   > the editor and make the load request is shown in the
> Butler Users
> >>>>>   > table and there are connections made, but it hangs from
> there. We did
> >>>>>   > test the connection by deleting the datasource and when
> we requested
> >>>>>   it to load the tables it gave an appropriate error (saying that it
> >>>>>   couldn't connect to the datasource) so the connection
> from the Win 2k
> >>>>>   box via Butler tcp/ip on the standard Butler port seems
> to be working
> >>>>>   > - I have a feeling that it may be a port mapping
> problem between the
> >>>>>   two machines since the mac is sitting on the internal
> network and is
> >>>>>   reached externally (form the Internet) by mapping
> incoming requests
> >>>>>   to port 81 for http and that has presented some problems
> when ftping
> >>>>>   to the machine from certains networks - any ideas on how
> we can test
> >>>>>   that?
> >>>>>
> >>>>>   I'll make a connection to a local dsn (say an access db)
> and see how
> >>>>>   it goes. We did load the PSQL demos but we were having the stanza
> >>>>>   problem at that time so we un-installed the whole tango
> installation
> >>>>>   and re-installed a few times, the last couple of times without the
> >>>>>   PSQL demos so haven;t tested it with them I don't think.
> >>>>>
> >>>>>   Another point to note is that the uninstaller did not remove the
> >>>>>   references to the PSQL drivers in the ODBC panel in Win2k
> - is this,
> >>>>>   in some way, a possible cause of the problem would you
> think? It is
> >>>>>   annoying - we'll re-install them and see if they work and
> then try to
> >>>>>   un-install them separately - any tips on that?
> >>>>>
> >>>>>   thanks Steve
> >>>>>   Garth
> >>>>>
> >>>>>
> >>>>>   >Any chance you're using a Tango for Access product? Yes there
> >>>>>   was a release
> >>>>>   >of a product that was similar to Tango for Filemaker but for
> >>>>>   Access and the
> >>>>>   >windoze platform. I can't remember if it was a 2.x product or
> >>>>>   3.x. I used to
> >>>>>   >have a list of the serial number prefixes which identified the
> >>>>>   exact version
> >>>>>   >of the product but I don't know where it is.
> >>>>>   >
> >>>>>   >Other things to check is that you've set up a system data
> >>>>>source, etc. I
> >>>>>   >know that the Win Butler driver works under Win2000
> because I've used
> >>it.
> >>>>>   >
> >>>>>   >Will that same version connect to any other data source?
> >>>>>   >
> >>>>>   >Hope this helps,
> >>>>>   >
> >>>>>   >Steve Smith
> >>>>>   >
> >>>>>   >Skadt Information Solutions
> >>>>>   >Office: (519) 624-4388
> >>>>>   >GTA:    (416) 606-3885
> >>>>>   >Fax:    (519) 624-3353
> >>>>>   >Cell:   (416) 606-3885
> >>>>>   >Email:  [EMAIL PROTECTED]
> >>>>>   >Web:    http://www.skadt.com
> >>>>>   >
> >>>>>   >
> >>>>>   >>  -----Original Message-----
> >>>>>   >>  From: [EMAIL PROTECTED]
> >>>>>   >>  [mailto:owner-witango-talk@;witango.com]On Behalf Of
> Garth Penglase
> >>>>>   >>  Sent: October 22, 2002 9:20 PM
> >>>>>   >>  To: Multiple recipients of list witango-talk
> >>>>>   >>  Subject: Witango-Talk: T3 tcp/ip db connection
> (licensing issue?)
> >>>>>   >>
> >>>>>   >>
> >>>>>   >>
> >>>>>   >>  --
> >>>>>   >>  Hi everyone,
> >>>>>   >>  this is particularly for those who have been around tango for
> >>>>>   >>  quite a while.
> >>>>>   >>
> >>>>>   >>  I recently installed Tango 3.52 promo version (10 user
> >>>>>version) under
> >>>>>   >>  Win 2k. Originally I was getting stanza probs which
> we finally were
> >>>>>   >>  able to resolve (by fluke only though the suggestions from
> >>>>>historical
> >>>>>   >>  and recent entries on this list were useful).
> >>>>>   >>
> >>>>>   >>  Now I am trying to connect from the Win2k box using
> Butler WIN 32
> >>>>>   >>  drivers to a Mac running Butler but when running the
> taf which uses
> >>>>>   >>  the tcp/ip DSN I get this message:
> >>  >>>>  >>
> >>>>>   >>  An error occurred while processing your request:
> >>>>>   >>
> >>>>>   >>  Position: Insert
> >>>>>   >>  Class: Internal
> >>>>>   >>  Main Error Number: -109
> >>>>>   >>
> >>>>>   >>  This type of data source is not supported by the
> server license.
> >>>>>   >  >
> >>>>>   >>  Position: Insert
> >>>>>   >>  Class: Internal
> >>>>>   >>  Main Error Number: -4
> >>>>>   >>
> >>>>>   >>  Unable to connect to the specified data source.
> >>>>>   >>  Verify that data source is properly configured and
> that database
> >>>>>   >>  server is online.
> >>>>>   >>
> >>>>>   >>  I'm sure I remember having connected via tcp/ip from
> one mac to
> >>>>>   >>  another using the same license (actually the Mac
> version of the
> >>>>>   >>  software off the same CD) so I think the server
> license message is
> >>>>>   >>  erroneous. But am I wrong? Is it indeed not possible
> using this
> >>>>>   >>  license?
> >>>>>   >>
> >>>>>   >>  thanks
> >>>>>   >>  Garth
> >>>>>   >>
> >>>>>
> ________________________________________________________________________
> >>>>>   >>  TO UNSUBSCRIBE: send a plain text/US ASCII email to
> >>>>>   [EMAIL PROTECTED]
> >>>>>   >  >                 with unsubscribe witango-talk in the
> message body
> >>>>>   >  >
> >>>>>   >  >
> >>>>>   >
> >>>>>
> >>>>>_____________________________________________________________
> ___________
> >>>>>   >TO UNSUBSCRIBE: send a plain text/US ASCII email to
> >>>>>[EMAIL PROTECTED]
> >>>>>   >                 with unsubscribe witango-talk in the
> message body
> >>>>>
> >>>>>
> >>>>>   --
> >>>>>
> ________________________________________________________________________
> >>>>>   > TO UNSUBSCRIBE: send a plain text/US ASCII email to
> >>>>>[EMAIL PROTECTED]
> >>>>>                   with unsubscribe witango-talk in the message body
> >>>>>
> >>>>>
> >>>>>_____________________________________________________________
> ___________
> >>>>>TO UNSUBSCRIBE: send a plain text/US ASCII email to
> [EMAIL PROTECTED]
> >>>>>                  with unsubscribe witango-talk in the message body
> >>>>
> >>>>
> >>>>--
> >>>>______________________________________________________________
> __________
> >>>>TO UNSUBSCRIBE: send a plain text/US ASCII email to
> [EMAIL PROTECTED]
> >>>>                 with unsubscribe witango-talk in the message body
> >>>
> >>>
> >>>--
> >>>_______________________________________________________________
> _________
> >>>TO UNSUBSCRIBE: send a plain text/US ASCII email to
> [EMAIL PROTECTED]
> >>>                 with unsubscribe witango-talk in the message body
> >>>
> >>
> >>
> >>Bill Conlon
> >>
> >>To the Point
> >>345 California Avenue Suite 2
> >>Palo Alto, CA 94306
> >>
> >>office: 650.327.2175
> >>fax:    650.329.8335
> >>mobile: 650.906.9929
> >>e-mail: mailto:bill@;tothept.com
> >>web:    http://www.tothept.com
> >>
> >>
> >>________________________________________________________________________
> >>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> >>                 with unsubscribe witango-talk in the message body
> >
> >
> >--
> >________________________________________________________________________
> >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> >                with unsubscribe witango-talk in the message body
> >
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>                 with unsubscribe witango-talk in the message body
>

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to