Assignment rejected by specialist
:strip_exif()/u/10517/cup_anim.gif?f=community)
Gewoon ff zoeken op OS/2 
Heb het niet doorgelezen, maar anders doe je het toch via NFuse? Knal je er gewoon een published app. tegenaan, en deze via het web.
Ervanuitgaande dat er een christelijke broswer voor OS/2 te vinden is uiteraard.
Suc6
Koffie
IBM OS/2 Warp Version 4.0
Overview
This document describes how to use the Citrix WinFrame Win16 and DOS Clients on an OS/2 Version 4.0 system. The following connectivity methods are supported for the WinFrame Win16 and DOS Clients:
Client
TCP/IP
IPX
SPX
NetBIOS
Async
(Direct)
Async
(Modem)
DOS
Yes
Yes
No
Yes
Yes
Yes
Win16
Yes
No
No
Yes
Yes
Yes
In addition to using the WinFrame Win16 and DOS Clients, you can configure the WinFrame Web Client (Win16 version) for use with the IBM OS/2 Web Explorer.
Software Requirements
IBM OS/2 Warp 4.0
File and Print Client Services
TCP/IP Services
NetWare Client Services
Citrix WinFrame Version 1.6
WinFrame DOS Client Version 1.6, version 94B or above
WinFrame Win16 Client Version 1.6, version 94B or above
WinFrame Win16 Web Client, latest version from www.citrix.com/demoroom/default.asp
Installation
OS/2 Installation
Install OS/2 Warp Version 4.0 following the standard install procedure. Use the default settings. Install networking support for File and Print Client Services, Novell NetWare, TCP/IP Client Services, and the NetWare client. Verify that the network adapter settings are correct. Select the workstation name, description (if desired), and domain name. Choose the protocol you want to use. For TCP/IP, specify the hostname (usually the same as the workstation name), the IP address, the subnet mask, the router address, and the domain name required by your configuration, or use DHCP if a DHCP server is present on the LAN.
IBM OS/2 Warp Version 4.0 includes network and TCP/IP protocols and software as part of the operating system. Follow the instructions for installing the additional network and TCP/IP software as part of the installation of the system. Network and TCP/IP software for WINOS2 and virtual DOS are installed as defaults during the installation.
--------------------------------------------------------------------------------
Note The Client name and password must be the same on both the IBM LAN Server and the WinFrame server.
--------------------------------------------------------------------------------
WINOS2 Setup
Before installing the WinFrame Client, the WINOS2 settings must be set to allow the WinFrame Client to operate properly with DDE and Clipboard. Establish the settings as follows:
--------------------------------------------------------------------------------
Note You may elect not to make these settings if you do not intend to use the DDE or Clipboard functions.
--------------------------------------------------------------------------------
1. Under OS/2 System Folder, select System Setup and then WIN-OS/2 Setup.
2. Under WIN-OS/2 Setup Settings. select the Data Exchange tab.
3. On the Data Exchange settings page, select Public for both selections. This is required for DDE and Clipboard operation.
4. Close all the previous selections; this portion of the settings is complete.
5. Under OS/2 System Folder, select Command Prompts.
6. Go to the Settings page of either the seamless WINOS2 or full screen WINOS2 icon. (The right mouse button brings up a menu; click on Settings.)
7. Select the Session tab, then select WIN-OS/2 settings. Make sure the All DOS and WIN-OS/2 settings radio button is highlighted and select OK.
8. Set WIN_RUN_MODE to 3.1 Enhanced Compatibility.
9. Set WIN_DDE to On.
10. Set WIN_CLIPBOARD to On.
11. Select Save and close the notebook.
12. Close all the previous selections; this portion of the settings is complete.
13. When using IBM LAN and NetBIOS, the following line must be entered in the AUTOEXEC.BAT:
x:\ibmcom\ltsvcfg n1=1
where x is the OS/2 system drive. This command enables the NAME_NUMBER_1 support required to support NetBIOS connections.
Client Installation on OS/2
Before installing the Client, decide what protocols you will use. Client installation is simple; insert the WinFrame Client diskette in drive A and run setup in a WINOS2 session.
Client Protocol
TCP/IP
If you choose TCP/IP, make sure you have the server hostname handy and that OS/2 TCP/IP and DOS TCP/IP are installed.
IBM LAN
All IBM LAN software must be installed prior to installing the Client. You must know the server name, the Client name, and the password. The following line must be in AUTOEXEC.BAT to allow NetBIOS to work:
c:\ibmcom\lstvcfg n1=1
Dial-In
When installation starts, you are asked if you wish to select the Dial-In option.
Do not select this option at this time. Once installation is complete and you are setting up the local user, you may elect to use the Dial-In option to allow a modem connection.
WinFrame Win16 Client
Before installing the WinFrame Client, decide what network protocols and hardware adapters will be used.
IPX and SPX connections are not supported at this time because OS/2 does not support VxDs. TCP/IP connections are supported without any changes. NetBIOS connections are supported if you load NAME_NUMBER_1 support. Serial Dial-In and direct connect connections are supported without any changes.
WinFrame Win16 Web Client and Web Explorer
The IBM OS/2 Web Explorer is an OS/2-based Web browser. The procedure below describes how to configure the IBM OS/2 Web Explorer for use with the Citrix WinFrame Web Client.
1. Download the WinFrame Win16 Web Client from the Citrix Demo Web page (www.citrix.com/demoroom/default.asp). Follow the directions on the page to install the Client.
2. Edit the file C:\MPTN\ETC\EXPLORE.INI. In the [advanced] section specify a MAILCAP file if one does not exist by adding C:\MPTN\ETC\MAILCAP to the end of the mailcap= statement. In the [advanced] section, specify a EXTMAP file if one does not exist by adding C:\MPTN\ETC \EXTMAP to the end of the EXTMAP= statement. Save the file and exit the editor.
3. Edit or create the file C:\MPTN\ETC\MAILCAP. Add the line:
application/x-ica; c:\ICAWIN\WFICA16.EXE %s
Save the file and exit the editor.
4. Edit or create the file C:\MPTN\ETC\EXTMAP. Add the line:
application/x-ica ica
Save the file and exit the editor.
5. Restart the Web Explorer.
WinFrame DOS Client
Change the DOS_FILES setting for the WinFrame DOS Client session to 40. The default value of 20 causes the WinFrame DOS Client to exit with an "insufficient files" error message.
DOS sessions under OS/2 Warp load NetWare support (TBMI2 and NETX) by default; IPX connections are supported without any changes. SPX is not supported.
TCP/IP support also is loaded by default. When creating a TCP/IP remote application entry, specify TCP/IP-VSL as the connection type. Include the following line in the AUTOEXEC.BAT or in a .BAT file that starts the DOS Client:
x:\wfclient\mibmtcp.exe
NetBIOS connections require you to load NAME_NUMBER_1 support before running the Client. This support is not enabled by default. Include the following line in the AUTOEXEC.BAT or in a .BAT file that starts the DOS Client:
x:\ibmcom\ltsvcfg n1=1
where x is the OS/2 system drive. This command enables the NAME_NUMBER_1 support required to support NetBIOS connections.
DOS async connections require changes to the default DOS settings for the session. The following changes support direct connect and modem connections at up to 57.6KBps:
COM_DIRECT_ACCESS
On
COM_HOLD
On
COM_RECEIVE_BUFFER_FLUSH
None
COM_SELECT
All
DOS_DEVICE
x:/OS2/MDOS/COMDD.SYS (see note below)
DOS_FILES
40
HW_ROM_TO_RAM
On
HW_TIMER
On
IDLE_SECONDS
60
IDLE_SENSITIVITY
100
--------------------------------------------------------------------------------
Note x is the OS/2 system drive. Add this device driver statement to the list of device drivers.
--------------------------------------------------------------------------------
Usage
The WinFrame Win16, DOS, and Win16 Web Clients are supported on OS/2 Warp Version 4.0. The sections below discuss the compatibility issues for each Client.
--------------------------------------------------------------------------------
Note Cut, Copy, and Paste operations only work when cutting or copying data from the WinFrame Client and pasting it to the WINOS2 or OS/2 session. Data cut or copied from the OS/2 or another WINOS2 session (not the one running the WinFrame Client) cannot be pasted to the WinFrame Client.
A hotfix is available that fixes the problem described above. Contact your Citrix Technical Support representative for details. The DOS Client does not support Cut and Paste operations between OS/2 and WinFrame sessions.
--------------------------------------------------------------------------------
Printer Setup
Local Printing
1. Verify that the WINOS2 printer drivers are installed.
2. To access your local printer, type net use LPT:x \\client\LPT:y (where x and y are printer ports) at a command prompt and press ENTER.
3. Create a printer object for the local printer using the WinFrame Client Print Manager. Once the printer object is created, the printer is accessible by the Client using WinFrame server applications.
Printing on an IBM LAN Domain/Server
1. Make sure the printer is physically attached to the IBM LAN server. The IBM LAN server must have the printer driver installed.
2. The printer must be shared and available to all members. All members must have Create Permissions (CP) print permission granted on the IBM LAN Server.
3. The printer object for the WinFrame server connection must be created using the WinFrame server Print Manager.
4. To connect the WinFrame server to the IBM LAN server, use the Print Manager Connect feature. You must type the UNC Share name in the printer box; for example, \\server47\4019. This creates a print object in Print Manager.
5. When creating the object, select the Share option during object creation.
6. Once the printer object is created, the printer is accessible by the clients. WinFrame server applications can now print on the IBM LAN server printer.
7. The client, as a member of the WinFrame server, automatically has a print object created in the Client Print Manager. The client user has to select the print object as default to configure the server printer as the default printer.
Printing On the WinFrame Server
The printer object for a WinFrame printer is created using the WinFrame Print Manager.
1. Create the printer object as a shared object.
2. Once the printer object is created, the printer is accessible by the clients. Applications running on the WinFrame server can now print on the server printer. The client, as a member of the WinFrame server, automatically has a print object created in the Client Print Manager. The client user has the option of selecting the print object as default if the server printer needs to be the default printer.
DDE and OLE
DDE and OLE are supported within the WinFrame client. There is no interoperability between the WinFrame client and WINOS2 or OS/2 sessions.
Network and CD-ROM Drives
All non-local drives are supported by executing the following command at the WinFrame client command prompt:
net use x: \\client\y
where x is the drive to be mapped to and y is the non-local drive supported by OS/2.
Heb het niet doorgelezen, maar anders doe je het toch via NFuse? Knal je er gewoon een published app. tegenaan, en deze via het web.
Ervanuitgaande dat er een christelijke broswer voor OS/2 te vinden is uiteraard.
Suc6
Koffie
IBM OS/2 Warp Version 4.0
Overview
This document describes how to use the Citrix WinFrame Win16 and DOS Clients on an OS/2 Version 4.0 system. The following connectivity methods are supported for the WinFrame Win16 and DOS Clients:
Client
TCP/IP
IPX
SPX
NetBIOS
Async
(Direct)
Async
(Modem)
DOS
Yes
Yes
No
Yes
Yes
Yes
Win16
Yes
No
No
Yes
Yes
Yes
In addition to using the WinFrame Win16 and DOS Clients, you can configure the WinFrame Web Client (Win16 version) for use with the IBM OS/2 Web Explorer.
Software Requirements
IBM OS/2 Warp 4.0
File and Print Client Services
TCP/IP Services
NetWare Client Services
Citrix WinFrame Version 1.6
WinFrame DOS Client Version 1.6, version 94B or above
WinFrame Win16 Client Version 1.6, version 94B or above
WinFrame Win16 Web Client, latest version from www.citrix.com/demoroom/default.asp
Installation
OS/2 Installation
Install OS/2 Warp Version 4.0 following the standard install procedure. Use the default settings. Install networking support for File and Print Client Services, Novell NetWare, TCP/IP Client Services, and the NetWare client. Verify that the network adapter settings are correct. Select the workstation name, description (if desired), and domain name. Choose the protocol you want to use. For TCP/IP, specify the hostname (usually the same as the workstation name), the IP address, the subnet mask, the router address, and the domain name required by your configuration, or use DHCP if a DHCP server is present on the LAN.
IBM OS/2 Warp Version 4.0 includes network and TCP/IP protocols and software as part of the operating system. Follow the instructions for installing the additional network and TCP/IP software as part of the installation of the system. Network and TCP/IP software for WINOS2 and virtual DOS are installed as defaults during the installation.
--------------------------------------------------------------------------------
Note The Client name and password must be the same on both the IBM LAN Server and the WinFrame server.
--------------------------------------------------------------------------------
WINOS2 Setup
Before installing the WinFrame Client, the WINOS2 settings must be set to allow the WinFrame Client to operate properly with DDE and Clipboard. Establish the settings as follows:
--------------------------------------------------------------------------------
Note You may elect not to make these settings if you do not intend to use the DDE or Clipboard functions.
--------------------------------------------------------------------------------
1. Under OS/2 System Folder, select System Setup and then WIN-OS/2 Setup.
2. Under WIN-OS/2 Setup Settings. select the Data Exchange tab.
3. On the Data Exchange settings page, select Public for both selections. This is required for DDE and Clipboard operation.
4. Close all the previous selections; this portion of the settings is complete.
5. Under OS/2 System Folder, select Command Prompts.
6. Go to the Settings page of either the seamless WINOS2 or full screen WINOS2 icon. (The right mouse button brings up a menu; click on Settings.)
7. Select the Session tab, then select WIN-OS/2 settings. Make sure the All DOS and WIN-OS/2 settings radio button is highlighted and select OK.
8. Set WIN_RUN_MODE to 3.1 Enhanced Compatibility.
9. Set WIN_DDE to On.
10. Set WIN_CLIPBOARD to On.
11. Select Save and close the notebook.
12. Close all the previous selections; this portion of the settings is complete.
13. When using IBM LAN and NetBIOS, the following line must be entered in the AUTOEXEC.BAT:
x:\ibmcom\ltsvcfg n1=1
where x is the OS/2 system drive. This command enables the NAME_NUMBER_1 support required to support NetBIOS connections.
Client Installation on OS/2
Before installing the Client, decide what protocols you will use. Client installation is simple; insert the WinFrame Client diskette in drive A and run setup in a WINOS2 session.
Client Protocol
TCP/IP
If you choose TCP/IP, make sure you have the server hostname handy and that OS/2 TCP/IP and DOS TCP/IP are installed.
IBM LAN
All IBM LAN software must be installed prior to installing the Client. You must know the server name, the Client name, and the password. The following line must be in AUTOEXEC.BAT to allow NetBIOS to work:
c:\ibmcom\lstvcfg n1=1
Dial-In
When installation starts, you are asked if you wish to select the Dial-In option.
Do not select this option at this time. Once installation is complete and you are setting up the local user, you may elect to use the Dial-In option to allow a modem connection.
WinFrame Win16 Client
Before installing the WinFrame Client, decide what network protocols and hardware adapters will be used.
IPX and SPX connections are not supported at this time because OS/2 does not support VxDs. TCP/IP connections are supported without any changes. NetBIOS connections are supported if you load NAME_NUMBER_1 support. Serial Dial-In and direct connect connections are supported without any changes.
WinFrame Win16 Web Client and Web Explorer
The IBM OS/2 Web Explorer is an OS/2-based Web browser. The procedure below describes how to configure the IBM OS/2 Web Explorer for use with the Citrix WinFrame Web Client.
1. Download the WinFrame Win16 Web Client from the Citrix Demo Web page (www.citrix.com/demoroom/default.asp). Follow the directions on the page to install the Client.
2. Edit the file C:\MPTN\ETC\EXPLORE.INI. In the [advanced] section specify a MAILCAP file if one does not exist by adding C:\MPTN\ETC\MAILCAP to the end of the mailcap= statement. In the [advanced] section, specify a EXTMAP file if one does not exist by adding C:\MPTN\ETC \EXTMAP to the end of the EXTMAP= statement. Save the file and exit the editor.
3. Edit or create the file C:\MPTN\ETC\MAILCAP. Add the line:
application/x-ica; c:\ICAWIN\WFICA16.EXE %s
Save the file and exit the editor.
4. Edit or create the file C:\MPTN\ETC\EXTMAP. Add the line:
application/x-ica ica
Save the file and exit the editor.
5. Restart the Web Explorer.
WinFrame DOS Client
Change the DOS_FILES setting for the WinFrame DOS Client session to 40. The default value of 20 causes the WinFrame DOS Client to exit with an "insufficient files" error message.
DOS sessions under OS/2 Warp load NetWare support (TBMI2 and NETX) by default; IPX connections are supported without any changes. SPX is not supported.
TCP/IP support also is loaded by default. When creating a TCP/IP remote application entry, specify TCP/IP-VSL as the connection type. Include the following line in the AUTOEXEC.BAT or in a .BAT file that starts the DOS Client:
x:\wfclient\mibmtcp.exe
NetBIOS connections require you to load NAME_NUMBER_1 support before running the Client. This support is not enabled by default. Include the following line in the AUTOEXEC.BAT or in a .BAT file that starts the DOS Client:
x:\ibmcom\ltsvcfg n1=1
where x is the OS/2 system drive. This command enables the NAME_NUMBER_1 support required to support NetBIOS connections.
DOS async connections require changes to the default DOS settings for the session. The following changes support direct connect and modem connections at up to 57.6KBps:
COM_DIRECT_ACCESS
On
COM_HOLD
On
COM_RECEIVE_BUFFER_FLUSH
None
COM_SELECT
All
DOS_DEVICE
x:/OS2/MDOS/COMDD.SYS (see note below)
DOS_FILES
40
HW_ROM_TO_RAM
On
HW_TIMER
On
IDLE_SECONDS
60
IDLE_SENSITIVITY
100
--------------------------------------------------------------------------------
Note x is the OS/2 system drive. Add this device driver statement to the list of device drivers.
--------------------------------------------------------------------------------
Usage
The WinFrame Win16, DOS, and Win16 Web Clients are supported on OS/2 Warp Version 4.0. The sections below discuss the compatibility issues for each Client.
--------------------------------------------------------------------------------
Note Cut, Copy, and Paste operations only work when cutting or copying data from the WinFrame Client and pasting it to the WINOS2 or OS/2 session. Data cut or copied from the OS/2 or another WINOS2 session (not the one running the WinFrame Client) cannot be pasted to the WinFrame Client.
A hotfix is available that fixes the problem described above. Contact your Citrix Technical Support representative for details. The DOS Client does not support Cut and Paste operations between OS/2 and WinFrame sessions.
--------------------------------------------------------------------------------
Printer Setup
Local Printing
1. Verify that the WINOS2 printer drivers are installed.
2. To access your local printer, type net use LPT:x \\client\LPT:y (where x and y are printer ports) at a command prompt and press ENTER.
3. Create a printer object for the local printer using the WinFrame Client Print Manager. Once the printer object is created, the printer is accessible by the Client using WinFrame server applications.
Printing on an IBM LAN Domain/Server
1. Make sure the printer is physically attached to the IBM LAN server. The IBM LAN server must have the printer driver installed.
2. The printer must be shared and available to all members. All members must have Create Permissions (CP) print permission granted on the IBM LAN Server.
3. The printer object for the WinFrame server connection must be created using the WinFrame server Print Manager.
4. To connect the WinFrame server to the IBM LAN server, use the Print Manager Connect feature. You must type the UNC Share name in the printer box; for example, \\server47\4019. This creates a print object in Print Manager.
5. When creating the object, select the Share option during object creation.
6. Once the printer object is created, the printer is accessible by the clients. WinFrame server applications can now print on the IBM LAN server printer.
7. The client, as a member of the WinFrame server, automatically has a print object created in the Client Print Manager. The client user has to select the print object as default to configure the server printer as the default printer.
Printing On the WinFrame Server
The printer object for a WinFrame printer is created using the WinFrame Print Manager.
1. Create the printer object as a shared object.
2. Once the printer object is created, the printer is accessible by the clients. Applications running on the WinFrame server can now print on the server printer. The client, as a member of the WinFrame server, automatically has a print object created in the Client Print Manager. The client user has the option of selecting the print object as default if the server printer needs to be the default printer.
DDE and OLE
DDE and OLE are supported within the WinFrame client. There is no interoperability between the WinFrame client and WINOS2 or OS/2 sessions.
Network and CD-ROM Drives
All non-local drives are supported by executing the following command at the WinFrame client command prompt:
net use x: \\client\y
where x is the drive to be mapped to and y is the non-local drive supported by OS/2.
Ergo Conclusio, de bijbel is een Java-applet
?? Heb nog nooit probs ermee gehad.
Zelfs niet via inet ipv intranet.
Desnoods zou je de MS client kunnen pakken.
Oh nee oeps ... je draait geen MS Terminal.
Pagina: 1