I am running TransferPro on a Solaris 2.x machine and sometimes the drive entries for my attached Macintosh and DOS SCSI drives vanish. Why is this happening and what can I do about it?
A – Starting with Solaris 2.2, the Solaris kernel will automatically unload dynamically loadable device drivers (such as the TransferPro ff driver) when it thinks the driver is no longer being used. Unfortunately, the automatic unload is not done properly or completely, and part of the operating system thinks the drivers are still loaded. The work around is to manually unload the ff drivers, and then launch TransferPro again. Manually loading and unloading the drivers is described in Appendix B, “Software Technical Details”. Starting with R3V1.6 of TransferPro for Solaris 2.x, the TransferPro ff drivers are now loaded into /kernel/drv instead of /usr/kernel/drv, and the ff drivers are force-loaded at boot time. The kernel is less likely to unload drivers which reside in /kernel/drv and the problem occurs much less frequently. Top of page Q – Part of the main TransferPro window is cut off when displayed on my SPARC. The vertical scroll lists are cut off at the bottom and some of the tex
Related Questions
- I am running TransferPro on a Solaris 2.x machine and sometimes the drive entries for my attached Macintosh and DOS SCSI drives vanish. Why is this happening and what can I do about it?
- Whenever I telnet into my Mac running NetBSD from a machine running Mac OS, SunOS, or Solaris, I have severe terminal emulation problems. Whats wrong?
- Why are there no Macintosh or DOS drives in the TransferPro drive list, even though I have those drives attached?
