SunPCi User's Guide

Appendix A Troubleshooting

This appendix provides tips for rectifying problems you may encounter while using SunPCi software.

If you have a question or encounter a problem with SunPCi (such as a Windows NT “blue screen”), please contact your support provider. It is most helpful if you include the following information in your email:

What you observed, including any error messages that were displayed
What you were doing at the time
The application you were using (including the application version number)
Steps to recreate the problem (very important)

The following list describes the troubleshooting topics included in this appendix.

Known Problems With SunPCi

This section describes some known problems with this release of SunPCi. Additional information on this release appears in the SunPCi 1.1 Release Notes.

Updates to the information in this section and workarounds (if available) will be posted to the SunPCi home page at http://www.sun.com/desktop/products/sunpci.

Note –

The SunPCi home page contains software updates, patches, and other information about the SunPCi product. Visit the home page frequently for all the latest information.

Running Microsoft Windows 95/NT Applications

Running Windows 95 From CD-ROM

Windows 95 cannot be installed with the “Run From CD-ROM” option. Use any of the other options.

SunPCi Appears to Hang When Browsing Network Drives

If you are running Solaris 2.6 on your workstation, you may observe a very long time lag when browsing network drives. SunPCi may even appear to hang as it searches the contents of the drives. This is a feature of Solaris 2.6 and Solaris 7.

Solaris 2.6 contains a “browsing” feature that allows you to automatically view all automount points on your workstation. In Solaris 2.5.1 and earlier versions, automounted directories are not visible until they have been mounted.

This may cause Windows 95/NT applications to slow down considerably when browsing for files on your workstation (especially on your R: drive, which is /), and may cause problems when viewing very large directories with Windows Explorer or saving to a subdirectory in one of these directories.

You can turn off this problem by editing the Solaris 2.6 auto_master file. To edit this file, perform the following steps:

Use a text editor to open the file /etc/auto_master.

The file should look similar to the following:

# Master map for automounter#+auto_master/net	-hosts					-nosuid,nobrowse/home	auto_home					-nobrowse/xfn	-xfn

Move the +auto_master line in the file to the bottom of the list, after -nobrowse. If the -nosuid, nobrowse and -nobrowse keywords are not present in the file, add them.

The result should look similar to the following:
```
# Master map for automounter#/net	-hosts					-nosuid,nobrowse/home	auto_home					-nobrowse/xfn	-xfn+auto_master
```

Save the file and exit the text editor.

Reboot your system.

The “browsing” feature should be turned off.

Displaying Shortname Tails

When the DOS window reads a Windows 95/NT-style long file name, it truncates the long name into DOS format (that is, an eight-character file name followed by a three-character extension) and adds a number to the file (such as ~1); this number is called a shortname tail. When reading long file names on extended drives in the Windows 95 DOS window or the Windows NT Command window, the window can only display shortname tails ending in the number 1; it cannot display ~2, ~3, and so on.

Note –

The term “DOS window” refers to the DOS shell window that you access from Windows 95 (called the Command Window in Windows NT. It does not refer to DOS windows running under OpenDOS 7.01.

Reading Windows Formatted CDs

Note –

This section refers to Windows 95 only. If you are running Windows NT, skip this section.

Some versions of Solaris (Solaris 2.5.1 and 2.6) are unable to read some Windows formatted CDs, such as the RockRidge format. If SunPCi cannot read a CD you are trying to use, check the contents of the CD as described in the following procedure.

Open a Command Tool window on the Solaris desktop.

Enter the following commands:
```
% cd /cdrom/cdrom0
% ls -lR
```
If the system responds with a message similar to the following, it is unable to read the setup file from your CD:

./setup.exe: No such file or directory

total 170

-r-xr-xr-x 1 root sys 45 Aug 21 1996 autorun.inf*

dr-xr-xr-x 2 root sys 2048 Nov 26 11:46 doc/

-r-xr-xr-x 1 root sys 11171 Nov 25 10:01 readme.txt

dr-xr-xr-x 2 root sys 2048 Nov 26 11:46 setup/

If this happens, you will need to download and install a Solaris patch. Instructions for installation are included with the patch. You can find the patches at http://access1.sun.com.

Download patch 104560 for Solaris 2.5.1.

Download patch 105486 for Solaris 2.6.

The SunPCi Installation Guide contains instructions on how to install the patches, which are also included on the SunPCi software CD.

Network Neighborhood

When you open the Network Neighborhood on the Windows 95/NT desktop, the Network Neighborhood window does not show My Workstation. The workstation and the SunPCi card share the same network interface, so they do not “see” each other on the network. Both can communicate with the network, however.

For more information on networking your workstation with your SunPCi host, refer to Networking With SunPCi.

International Keyboard Support

Note –

This section refers to DOS and Windows 95. If you are running Windows NT, skip this section.

DOS uses the file C:\dos\keyb.com as its keyboard driver. However, Windows 95 uses the file C:\windows\keyb.com. This results in the loss of support for international keyboards when you use Windows 95.

The following procedure explains how to modify your autoexec.bat and config.sys files to use the DOS keyboard driver for international support.

For more information on international support, refer to Appendix B, SunPCi International Support.

To restore support for international keyboards, follow this procedure:

In the SunPCi window, click the Start button, and then select Programs and then Accessories from the pop-up menus.

Select Notepad, and then open your C:\autoexec.bat file.

Add the following line to the file:
```
C:\dos\keyb.com
```

Save the file and close it.

Open your C:\config.sys file.

The following line may appear:

rem DEVICE=C:\DOS\SETVER.EXE

If it does appear, remove the rem (remark) statement and save the file.

If it does not appear, add the line DEVICE=C:\DOS\SETVER.EXE to the file and then save it.

Exit Notepad.

Click the Start button and then select Shut Down from the pop-up menu.

The Shut Down Windows dialog box appears.

Select Restart the computer in MS-DOS mode and then click Yes to reboot SunPCi.

When SunPCi has finished rebooting, the MS-DOS prompt appears in the SunPCi window.

Enter the following commands at the DOS prompt:
```
C:\> CD DOS
C:\> SETVER keyb.com 7.01
C:\> win
```
This sets the keyboard driver to the proper version and starts Windows 95.

You will need to enter the CD DOS and SETVER commands every time you start SunPCi. You may want to configure your SunPCi system to automatically boot to the DOS prompt each time. Refer to Appendix C, SunPCi Performance Tips for instructions on how to configure your system.

SunPCi Hardware Problems

Error Messages

The following table shows some error messages that result from hardware problems, possible causes of those problems, and solutions.

Table A–1 SunPCi Error Messages


Error Message	Possible Cause	Solution
`Drive not ready. Abort/Retry/Fail?`	If you get this message when you double-click on your CD-ROM drive in Windows NT Explorer, your SunPCi installation may have one of the following problems: Your workstation's Open Boot PROM (OBP) is out of date. Your CD-ROM drive may not be a Sun-supplied drive.	Update the OBP as described in OBP (Open Boot PROM) Problems. SunPCi only supports Sun-supplied CD-ROM drives. Replace the CD-ROM drive in your system with a Sun-supplied drive.
`General Protection Failure`	If running a Windows NT application produces this failure or a `Null pointer` message, your version of Windows may require a software patch.	Download and install `speu.exe` as described in General Protection Failures in Windows NT Applications.
`Warning: /etc/devlink.tab not updated correctly` `Perhaps the system OBP needs to be updated`	Your workstation's Open Boot PROM (OBP) is out of date.	Update the OBP as described in OBP (Open Boot PROM) Problems.
`Driver not found.` `Can't attach to device.` `Devlinks not created`	Your workstation cannot identify the PCI device. This can be due to the following reasons: Your SunPCi card is not installed securely in the PCI slot. Your `/etc/devlink.tab` file was not updated correctly when you installed SunPCi. Your workstation's Open Boot PROM (OBP) is out of date.	Remove and reinstall your SunPCi card as described in the SunPCi Installation Guide. Update the OBP as described in OBP (Open Boot PROM) Problems.
`The SunPCi drivers could not be loaded. Is another session running?`	This message may have appeared for one of the following reasons: You already have a SunPCi session running. You removed the SunPCi card and then reinstalled it in a different PCI slot in your workstation. You started up SunPCi without first restarting your workstation after you installed the card.	Quit the other session before running SunPCi again. If possible, remove the card and install it into the PCI slot it first occupied Log in as superuser, type in `halt` at the # prompt to halt your system again, and restart at the `ok` prompt using `boot -r`.
`Driver couldn't be loaded. SunPCi cannot open the device.`	Your SunPCi card may not be properly seated in the PCI slot.	Make sure that the board is securely seated in the PCI slot.
`Your BIOS may be out of date.`	You need to update your BIOS.	Refer to the SunPCi Installation Guide for more information.
System could not transfer file data from buffers.	You have run out of disk space on your host file system.	Make more space on your host file system.

Mouse Problems

Table A–2 shows some common mouse problems and possible solutions.

Table A–2 Mouse Problems


Problem	Possible Cause	Solution
Two mouse cursors appear on the SunPCi desktop.	You may not yet have installed the SunPCi drivers for Windows 95.	To use the mouse before you install the drivers, choose Attach Mouse from the Options menu, or press Meta-M. After you have finished installing the drivers, the mouse will operate normally.
Mouse movements appear jerky after SunPCi installation.	You may not yet have installed the SunPCi drivers for Windows 95.	Refer to Chapter 3, Starting SunPCi Software for the First Time for information on how to install the drivers. After you have finished installing, you will notice that the mouse movement appears much more smooth.

Diskette Drive Problems

Table A–3 shows some problems that can occur with the diskette drive and SunPCi.

Table A–3 Diskette Drive Problems


Problem	Possible Cause	Solution
Cannot access the diskette in the diskette drive.	There is a conflict between SunPCi and the Solaris Volume Manager (`vold`) for control of the drive. The file `/dev/rdiskette` may not have read/write permissions.	Refer to Diskette Drive Conflicts. Check the permissions on the file and change them if necessary.
Cannot eject the diskette. The error message `eject: open failed on .dev/rdiskette. Device busy` is displayed.	Another Solaris command window may have control of the diskette drive.	Refer to Ejecting Diskettes for more information.
Cannot use low density diskettes.	The diskette is probably not formatted correctly.	Refer to Ejecting Diskettes for more information.

Diskette Drive Conflicts

SunPCi software and the Solaris Volume Manager program (vold) tend to conflict with each other for control of the diskette drive. Volume Manager provides automatic mounting services for peripheral devices attached to your system, such as diskette drives.

The conflict arises when Volume Manager support is enabled on your system and you attempt to access a diskette drive through a SunPCi window. In such instances, an error message is displayed and the diskette access fails.

By default, when SunPCi software is installed, Volume Manager support is disabled for diskette drives, and so most users will not encounter a problem. However, it is possible to re-enable Volume Manager on your system, and thus encounter the problem at a later time.

If Volume Manager support for diskette drives has been re-enabled on your system, and you encounter problems accessing diskette drives through SunPCi, try disabling Volume Manager and restarting the SunPCi window. If the problem persists, try disabling Volume Manager and rebooting your system.

To disable the Solaris Volume Manager, perform the following steps:

Make sure that SunPCi is not running. Become superuser.

Disable Volume Manager by entering the following command:
```
# /opt/SUNWspci/bin/vold_floppy_disable
```

Exit superuser.

Restart all SunPCi windows.

Keyboard Problem

Backspace Key Does Not Work in DOS (Windows 95 Only)

Do not map the Delete key to the Backspace key. If you do this, you will not have a Backspace key available when you are working with DOS applications. When you press the Backspace key, it will not backspace, but will instead delete the character at the current cursor location. If you have mapped these two keys by modifying your .xinitrc file, there will be a line in the file that reads: xmodmap -e keycode 50 = delete. You should remove this line to restore the original key assignments.

CD-ROM Drive Problems

This section describes possible problems you might encounter with Windows 95 or Windows NT and your CD-ROM drives.

Problems with Windows 95

If you are trying to access Solaris files and CD-ROM drives from Windows 95 and you are unable to use the Map Network Drive command in Windows Explorer to set up the drive, be sure to check the following:

Make sure you have the CD in the CD-ROM drive. This is the most likely reason that a drive mapping may not work.

Make sure you entered the path for the CD-ROM drive as \\cdrom\cdrom0, with two backslashes at the beginning.

Problems with Windows NT

Table A–4 describes some problems you might encounter with CD-ROM drives, possible causes, and solutions.

Table A–4 CD-ROM Drive Problems in Windows NT


Problem	Possible Cause	Solution
When you insert or eject a CD in one CD-ROM drive, the other CD-ROM drive becomes unreachable.	You have two SCSI CD-ROM drives in your system.	You will need to select which CD-ROM to use with SunPCi. Refer to Setting Up Your CD-ROM Drive.
When you double-click on the CD-ROM drive in Windows NT Explorer, you get the following error message: `Drive not ready. Abort/Retry/Fail?`	Your workstation's Open Boot PROM (OBP) is out of date. Your CD-ROM drive may not be a Sun-supplied drive.	Update the OBP as described in OBP (Open Boot PROM) Problems. SunPCi only supports Sun-supplied CD-ROM drives. Replace the CD-ROM drive in your system with a Sun-supplied drive.
Playing an audio CD in Solaris using the `workman` utility causes Windows NT to hang. Starting Windows NT while an audio CD is playing pauses the audio CD.	Your CD-ROM drive is being shared by both Solaris and Windows NT. As soon as Windows NT detects the presence of the CD, it pauses the CD.	Disable CD detection in either Solaris or Windows NT. The CD cannot be shared by both operating systems. Note that once you have disabled CD detection in one operating system, you will need to mount the CD manually in that operating system.

Setting Up Your CD-ROM Drive

If you are not using Solaris Volume Manager (vold) to control your CD-ROM drive or if you have more than one CD-ROM drive, you will have to specify which drive you want to use with SunPCi. To set up your CD-ROM drive, perform the following procedure:

Start SunPCi, if it is not already running.

The console window from which you start the application displays the following message:
```
sunpci: Your SunPCi.ini file does not specify a CD device
        assuming /vol/dev/aliases/cdrom0
```

From the Options menu, choose Attach CD-ROM.

The Specify CD-ROM Device File dialog box is displayed.

Type in the path to the CD-ROM device you want to use (for example, /vol/dev/aliases/cdrom0).

When you have finished typing in the path, click OK.

Exit Windows NT and reset SunPCi.

When SunPCi restarts, it will use the CD-ROM drive device you specified.

OBP (Open Boot PROM) Problems

If you see the following message after installing SunPCi software, your workstation's Open Boot PROM (OBP) may be out of date.

## Executing postinstall script.
Warning: /etc/devlink.tab not updated correctly
         Perhaps the system OBP needs to be updated

Another way to check if your OBP is out of date is to see if the file /dev/sunpcdrv2 exists on your workstation. If the file does not exist, you will need to update the OBP. If it does exist, your OBP is current.

If your workstation's OBP is out of date, you will need to update it to be compatible with SunPCi. To perform the update, go to the following Web site and download the appropriate instructions for your particular workstation:

http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/pub-Hardware&na

To update your OBP, you will first need to find out the current version of your OBP software, and then update the OBP using the software that corresponds to your workstation type.

To find out your OBP version, follow these steps:

Type the following command at the % prompt (do not type the %):
```
% /usr/sbin/prtconf -V
```
You should see a display similar to the following:

OBP 3.11.2 1998/04/20 15:37

In this example, the OBP version is 3.11.2.

Make note of your OBP version.

You will need this information when you update your OBP. (The README file for the hardware upgrade contains information on the latest OBP revision number for your workstation type.)

Obtain the latest OBP version for your platform.

You should get the latest OBP from your Service Provider or from the sunsolve.sun.com Web site described earlier in this section. The OBP version required by your workstation depends on the workstation model.

Open the README file for the OBP in any text editor and print it.

The README file contains detailed and specific instructions on how to update your OBP, including the necessary hardware changes (moving a jumper on your workstation's CPU). It also shows the latest OBP revision number for your workstation type. Because you will have to turn off power to your system in order to move the jumper, you will need a printed copy of the instructions in order to complete the procedure.

Note –
You may find it helpful to use a flashlight while moving the jumper.

Follow the update instructions carefully.

Video Display Problems

External Monitor Resolutions

Table A–5 shows the external VGA display resolutions that SunPCi supports. For best results, you may want to increase the amount of available video RAM from 1 Mbyte (the default) to 4Mbytes and reset the VGA memory clock to 70 MHz. For information on how to increase the video RAM, refer to .

Note –

Before you change the resolution or display depth of your monitor, be sure to shut down all running applications and save your work. You do not need to test a new setting before applying it.

Note –

Remember that increasing your video memory decreases the amount of available system memory.

Table A–5 SunPCi External Video Resolutions


Resolution (pixels)	Color Depth (number of colors)	Refresh Frequency (Hz)
640 x 480	256, 32K, 64K, 1.6M	60, 72, 75, 85
800 x 600	256, 32K, 64K, 1.6M	56, 60, 72, 75, 85
1024 x 768	256, 32K, 64K 1.6M	43 (interlaced), 60, 70, 75, 85 43 (interlaced), 60, 70, 75
1280 x 1024	256 32K	43 (interlaced), 60, 75 43 (interlaced), 60

Printer Problems

This section describes some problems you may encounter when printing from applications running under SunPCi software.

Problems Printing to a PostScript Printer

If you are having problems printing from an application to a PostScript printer, try the following:

Print to a file and print the file from a command window using lp filename. If this does not work, it may be an indication that your printer is not configured correctly. Make sure your default printer and any other printer you are trying to access is set up in your /etc/lp/printers directory.

Make sure the setting in your application matches the setting for the default printer in your Windows 95/NT Network Control Panel. The Setup Wizard will have already installed and configured the PostScript printer for you, if you performed these steps during installation.

Print to a file. View the file from a Solaris command window using od -a. If you see the letters eot anywhere in the file, it is an indication that there are ^D characters present in the file. The PostScript printer will not recognize these characters.

SunPCi Software Problems

Installation Problems

This section lists some possible problems with installing and running SunPCi software.

Table A–6 SunPCi Installation Error Messages


Error Message	Possible Cause	Solution
`Not enough disk space to install SunPCi software.`	Your workstation's hard disk or your home directory is out of space.	Delete unnecessary files, applications, or both to make more disk space available. If necessary, ask your system administrator for assistance. When you have created or obtained more disk space, start the SunPCi installation again. As an alternative, you can install SunPCi software on a different disk or system.
`You need additional swap space to install and run the SunPCi software.`	SunPCi software requires a minimum of 12 Mbytes of swap space.	Increase the amount of swap space on your system and then try installing SunPCi software again.

Software Startup Problems

When starting SunPCi software, you may encounter one of the following error messages.

Command not found: Make sure that the SunPCi program directory—by default, /opt/SUNWspci/bin—is in your environment PATH. Refer to Chapter 3, Starting SunPCi Software for the First Time for instructions.
Correct Solaris Installation Required

If you do not have the correct Solaris installation on your system, you will encounter problems when attempting to start SunPCi software. SunPCi software requires at least the End User System, Developer System, or Entire Distribution installations of Solaris versions 2.5.1 and 2.6 and Solaris 7. SunPCi will not run if you only have the Core System installed. Ask your system administrator for assistance in determining which system is installed on your workstation.

Windows 95 or Windows 95 Application Installation Problems

Whenever you install new applications on SunPCi, make sure you have your Windows 95 CD available. The installation program may require files from the Windows 95 CD.

Windows NT Problems

This section describes some problems you may encounter while using Windows NT.

General Protection Failures in Windows NT Applications

If your Windows applications show General Protection Failure or Null Pointer errors, you may need to install the Microsoft Windows Library update patch speu.exe. This patch is not included with the Windows NT software or with Service Pack 4. Information on the patch and the patch file are located on the Microsoft Web site at the following location:

http://www.microsoft.com/windows/downloads/contents/wurecommended/s_wuservicepacks/mfclibrary/default.asp?site=ntw

Problems Installing to Network Drives

If you have problems installing Windows NT applications to network drives, try installing the applications to your C: or D: drives. The applications should then install correctly.

Recovering from Windows NT Setup

After you have finished installing and configuring Windows NT, you may want to use the Windows NT CD again at another time (for example, to view the Windows NT documentation on the disk). If you insert the Windows NT CD into your CD-ROM drive, an Autorun dialog box is displayed. This dialog box includes the Windows NT Setup option. Do not use this option to reinstall Windows NT; use the Add/Remove Software option in the Autorun dialog box or the Add/Remove Software Control Panel.

If you did select the Windows NT Setup option by mistake, select a different operating system in the OS Loader screen after SunPCi reboots. For example, choose Last Operating System on C:.

Creating Windows NT Repair Disks

The boot floppies that come with the Windows NT Workstation package do not contain the SunPCi drivers. If you try to use these repair disks to recover from a Windows NT, the SunPCi drivers will not be installed and the software will not work correctly.

If you want to create a repair disk for your SunPCi installation of Windows NT, perform the following procedure:

From the Start Menu, choose Shut Down, and then choose Restart the Computer.

Click OK.

Windows NT shuts down and restarts.

At the OS Loader screen, use the down arrow key to select Previous Operating System on C:. Press Return.

SunPCi then boots into DOS. When it has finished booting, the DOS prompt (C:\>) is displayed.

Back up the following files to another area on your workstation's hard disk or to a floppy. These files are needed in order to initialize the MS-DOS environment.

C:\winnt\system32\Autoexec.nt C:\winnt\system32\Config.nt

Copy the following files to a floppy disk. If Windows NT Workstation 4.0 does not start up, you will need this floppy in order to boot Windows NT.

C:\Ntldr C:\Boot.ini C:\Ntdetect.com C:\bootsect.dos C:\Hal.dll

You might want to make more than one copy of this floppy, in case one copy is damaged or lost.

Copy these registry files to a directory on your workstation's hard disk (such as $HOME/temp). You will need these files to restore the Windows NT Registry.

C:\System32\config\Sam C:\System32\config\Sam.log C:\System32\config\Sam.sav C:\System32\config\Security C:\System32\config\Security.log C:\System32\config\Security.sav C:\System32\config\Software C:\System32\config\Software.log C:\System32\config\Software.sav C:\System32\config\System C:\System32\config\System.alt C:\System32\config\System.sav C:\System32\config\System.log C:\System32\config\Default C:\System32\config\Default.log C:\System32\config\Default.sav C:\System32\config\Userdiff C:\System32\config\Userdiff.log

Note –
You may not have .sav files in your directory. This is normal. However, if you do have .sav files, it is a good idea to back them up.

Copy these files to floppy to restore the default user profile:

C:\winnt\profiles\Default User\Ntuser.dat C:\winnt\profiles\Default User\NTuserdat.log

Note –
In DOS, the directory will appear as C:\winnt\profiles\Defaul~1\.

Using the Repair Disks

When you need to recover Windows NT, follow this procedure:

Insert the floppy with the DOS files you copied into your floppy drive and then start SunPCi.

Your SunPCi window will boot to the DOS prompt.

Note –
If you have trouble booting to the DOS prompt and you have the MS-DOS 6.22 diskette available, insert the DOS diskette into your floppy drive and restart SunPCi again.

At the DOS prompt, copy the files from the other floppies back into the directory paths specified in each of the steps.

Copy the files you stored on your workstation's hard disk into the specified directories.

When you have finished copying all of the saved files into their respective directories, choose File and Reset PC to restart SunPCi.

SunPCi boots into Windows NT.

If you have trouble booting into Windows NT, insert the floppy with the Windows NT boot files that you created in Step 1 of the previous procedure in your floppy drive and restart SunPCi again.

Windows NT should boot from the floppy; press F3 to boot to the DOS prompt. You can now recopy the Windows NT boot files from the floppy disk onto your C: drive.

Note –
If you need to restore the Windows NT system password files only, restore the following files: C:\System32\config\Sam C:\System32\config\Sam.log C:\System32\config\Sam.sav

Emulated Hard Drive Problems

Attaching Drive C:

To be sure that you will always be able to attach drive C:, you can change the permissions on the drive. Changing the permissions will keep other users from being able to attach drive C: even when you are not using the SunPCi program. To change permissions on drive C:, type the following in a command window:

% chmod 600 ~/pc/C.diskimage

This makes the drive inaccessible to other users.

Disk Error Messages

If your SunPCi window shows the message Non-system disk or disk error at startup, your C: drive may have been corrupted, or you have a non-bootable floppy disk in drive A:. If you do not have a floppy disk in drive A:, delete the default C: drive file in $HOME/pc and then restart SunPCi.

You may want to make periodic backup copies of your C: drive. Refer to Backing Up Your C: Drive for more information.

Extended Drive Problems

Cannot Mount Extended Drives With Windows Explorer

If you cannot mount extended drives, networking may not be installed on SunPCi.

Try to log in to the network first. If you can reach the network from the UNIX side, then go to the Start menu in SunPCi and select Control Panel, then double-click on Network. Set up your SunPCi installation on the network. Refer to your Windows documentation for more information.

If you still cannot connect to the network after logging in, you will need to reinstall Windows 95.

To log in to the network, follow this procedure:

Start up SunPCi and enter your user name and password when the dialog box prompts you to log in to Microsoft Networking.

To log in to the network if you are already running SunPCi, follow these steps:

Click the Start button and then select Exit.

When the dialog box asks you whether you want to shut down or restart the computer, click on Restart.

When the Microsoft Networking dialog box appears, type in your user name and password and press Return.

You will then be able to mount extended drives. Refer to Extended Hard Drives for instructions on how to use Windows Explorer to map network drives.

Networking Problems

Cannot Connect to Other Systems

Before you start to diagnose problems using SunPCi to connect to other systems on the network, make sure that you have configured SunPCi and your workstation as follows:

Your workstation and SunPCi host must have different IP addresses.

Both the SunPCi host and the workstation should be located on the same physical subnet, although they may be on different virtual subnets.

Your workstation and SunPCi must have the same netmask. The value of the netmask depends on the type of network you are using; contact your network administrator for more information.

If you are having trouble using SunPCi with TCP/IP, perform the following steps to determine the cause of the problem.

Note –

You will need to know the names and IP addresses of another system on the same subnet as your workstation, and of a system not on the same subnet. Contact your network manager if you do not have this information.

Diagnosing TCP/IP Problems

In the SunPCi window, open a DOS window. In Windows 95/NT, choose the Start button and then select Applications and MS-DOS Prompt from the pop-up menus.

The DOS Prompt window is displayed.

Enter the ping command, followed by the IP address of a system on your subnet (not your workstation). For example:
```
C:\> ping 206.4.151.254
```
If this ping command succeeds, proceed to Step 1. If it returns an error such as Host not found, your SunPCi card may be using the wrong subnet, or your netmask may be incorrect. Contact your network manager to make sure you have the correct information.

Enter the ping command, followed by the name of the system you pinged in Step 1. For example:
```
C:\> ping bobswk
```
If this ping command succeeds, proceed to Step 1. If it returns an error, your DNS (Domain Name Service) needs to be reconfigured. Contact your network manager for the host name, domain name, and IP address of each DNS server on your network.

Enter the ping command, followed by the IP address of a system not on your subnet. For example:
```
C:\> ping 199.172.10.2
```
If this ping command succeeds, proceed to Step 1. If it does not succeed, make sure that you have specified the correct network router. Contact your network manager.

Enter the ping command, followed by the name of a system not on your subnet. For example:
```
C:\> ping maryswk
```
If this ping command succeeds, then TCP/IP is set up correctly. If it returns an error, contact your network manager and double-check the information you set up for the DNS servers as described in Step 1.