[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ucrow::desktop_acms

Title:DECtp Desktop for ACMS
Moderator:UCROW::GIBSON
Created:Mon Sep 24 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:859
Total number of notes:3034

827.0. "mac tcp tool/pathworks/bus error?" by CSC32::J_HENSON (Don't get even, get ahead!) Fri Feb 21 1997 12:56

acmsdi v2.2, mac v7.5.5, mac tcp tool v1.1.1, ucx v3.3 

A customer is attempting to use mac tcp as his transport between
a mac and an ovms system.  He is getting a bus error when attempting
to call db_init from the mac.  He can get this error when he runs
our own examples.

One of his questions is the actual requirements.  In particular,
is pathworks required to use mac tcp?  He does NOT have pathworks
installed on his system.  If not, can anyone give me some ideas
as to how to correct or troubleshoot this problem.

I know absolutely nothing about mac tcp, and we don't have any
such expertise at the csc any more.

Thanks,

Jerry
T.RTitleUserPersonal
Name		DateLines
827.1SPD infoUCROW::KNEELANDSun Feb 23 1997 15:599
Hi Jerry,

The Desktop SPD states that MacTCP is available
with PATHWORKS for Macintosh V1.1 or MacX 1.17
from Apple Computer Inc, hence I would say yes
PATHWORKS is required to use MacTCP tool with
ACMS Desktop.

Colette
827.2PATHWORKS optionalUCROW::KNEELANDMon Feb 24 1997 09:3210
From:   UCROW::BAIRD        "John Baird - ACMS Desktop, DTN=226-6013"
To:     UCROW::KNEELAND
CC:     BAIRD
Subj:   RE: Please confirm that PATHWORKS required on MAC in order to use MacTCP
 tool  Thanks. Colette

No, PATHWORKS is not required.  Only the MacTCP Tool.  If they need the tool
we could probably just send it to them.

        John
827.3More info?EYEORE::BAIRDMon Feb 24 1997 10:254
    I just ran a quick test using the MacTCP Tool.  It worked 
    without any problems.  Has the customer definitely isolated
    the problem to the use of MacTCP?  Just saying he's getting
    a bus error on DBInit is not telling us much.
827.4what other information?CSC32::J_HENSONDon't get even, get ahead!Mon Feb 24 1997 14:469
>>                       <<< Note 827.3 by EYEORE::BAIRD >>>
>>                                -< More info? >-

What should I ask for?  Keep in mind that just about everybody knows
more about desktop on the Mac and Mac TCP tool than I.

Thanks,

Jerry
827.5Stuff to look into...EYEORE::BAIRDTue Feb 25 1997 09:5518
    Start out with the basics...
    
    1. Is the MacTCP Tool in the extensions folder?  This is where it's 
       normally installed.  If installed elsewhere, the system has to
       know where it is.  But I see no reason to install it anywhere else.
    
    2. There's a MacTCP control panel where the individual Mac's TCP
       address is defined along with routing information, TCP domains,
       whether or not it's running over ethernet or ethertalk, etc.
       Has that been done?
    
    3. There's also a MacTCP DNR file that shows up in the System Folder.
       I can't remember if that gets installed or if it gets dynamically
       created.  At any rate, knowing whether or not it's there may give
       us some clues.
    
    4. Are they running MacsBug or any other kind of debugger?  If so
       what, if any, information does that provide?
827.6ThanksCSC32::J_HENSONDon&#039;t get even, get ahead!Wed Feb 26 1997 09:138
>>                       <<< Note 827.5 by EYEORE::BAIRD >>>
>>                           -< Stuff to look into... >-


Thanks, John.  I have asked my customer to check this, but don't
have any additional information at this time.

Jerry
827.7answers to your questionsCSC32::J_HENSONDon&#039;t get even, get ahead!Mon Mar 03 1997 09:4340
>>                       <<< Note 827.5 by EYEORE::BAIRD >>>
>>                           -< Stuff to look into... >-

Here's the answers.

    
>>    1. Is the MacTCP Tool in the extensions folder?  This is where it's 
>>       normally installed.  If installed elsewhere, the system has to
>>       know where it is.  But I see no reason to install it anywhere else.
  
Yes it is.

  
>>    2. There's a MacTCP control panel where the individual Mac's TCP
>>       address is defined along with routing information, TCP domains,
>>       whether or not it's running over ethernet or ethertalk, etc.
>>       Has that been done?
  
Yes it has.

  
>>    3. There's also a MacTCP DNR file that shows up in the System Folder.
>>       I can't remember if that gets installed or if it gets dynamically
>>       created.  At any rate, knowing whether or not it's there may give
>>       us some clues.
  
The MacTCP DNR file is in the System Folder.  


>>    4. Are they running MacsBug or any other kind of debugger?  If so
>>       what, if any, information does that provide?

They are running MacsBug, but are not sure of what to look for.  Can you
elaborate on this?

Where to next?

Thanks,

Jerry