| |
| META TOPICPARENT |
name="ConfiguringAPPXForWindows" |
Windows Client/Disk-Server Configurations
|
|
>
> | Note: The information in this document is generally obsolete and is only presented here for archive purposes. |
| | This document explains how to set up an APPX for Windows Client/Disk-Server configuration. This is known a "Distributed Client/Server".
"Server" in this discussion is a Disk Server, which serves up a separately-lettered shared disk drive. This drive may be shared using NT, Novell, or some other disk-sharing facility. |
| |
|
|
<
< | |
| | How do you set up the links between client and the server, if the APPX engine is on every client, yet 0SA is on the SERVER? How do you make sure you will point to the server when necessary?
First, assume that you have two machines: one named 'Client' and the other named 'Server'. Server will be where you want most of the shared files to exist and Client is probably a Windows PC networked to Server somehow. |
| |
- Your APPX engine (appx.exe),
- APPX EMs (./data/00/0*/), and
- Application Design EMs (your "Object" code, or "P-code")
|
|
<
< | |
>
> | |
| |
If you want your server to also be a client (such as in a Peer-to-Peer network) (where, as a client, APPX is located on the 'C:' drive, and there exists no 'R:' drive), you can use the DOS "subst" command to create a drive 'R:' on your Server, synonymous with 'D:' on the same server. |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.