Developer’s Guide (Mac OS)

Table Of Contents

Distributing your bundled solution 5-5

If your end-users are using the MS IPX/SPX network with Windows 95

and Windows NT

They should use the IPX/SPX-compatible Protocol to share FileMaker

Pro files. On Windows NT, they should use the NWLink IPX/SPX

Compatible Transport. You also need to distribute the FMIPX32.NET

file inside the FileMaker System folder.

If the host machine will be hosting files to more than twelve guests,

change the Maximum Connections in the Advanced panel of the

Network control panel to at least 40. Consider increasing the SPX

connections if you cannot connect the desired number of guests.

If your end-users are using the IPX/SPX network with Windows 3.1 and

Windows for Workgroups 3.11:

They should use the Novell NetWare Client Shell version 3.26 or later to

share FileMaker Pro files. You also need to distribute the FMIPX32.NET

and FMIPX16.DLL files inside the FileMaker System folder and the

4WINSYS folder with your solution.

Important FileMaker networking will not work if the Microsoft

IPX/SPX compatible driver is installed. The driver must be removed.

Novell NetWare settings

If your end-users are using a Novell NetWare network on Windows 3.1

or Windows for Workgroups 3.11, they’ll need to change a few settings

to network your bundled solution. To share FileMaker Pro runtime files

over the network, the end-user’s machine must be a fully configured

NetWare client.

To share FileMaker Pro Runtime solution files:

1 Use the Windows Setup program to set the network to the appropriate

NetWare option (usually NetWare 3.26 and above).

1 Add the following entries to your NET.CFG (or SHELL.CFG) file:

GET LOCAL TARGET STACKS=10

SPX CONNECTIONS=40

Get local target stacks needs to be set on all guest machines. SPX

connections should be set on the host machine if it will host more than

twelve guests or on guest machines using additional SPX applications.

Consider increasing the SPX connections if you cannot connect the

desired number of guests.

If your end-users are using MS TCP/IP network with Windows for