Toshiba T2100 and PCMCIA FAX/modem
Return to The Hardware Shelf
Last update: 7th February, 1996
Symptoms
PCMCIA FAX/modem not working on Toshiba T2100
Hardware
Toshiba T2100
Problem
Installation steps not clear.
Procedure
The first step is to select the right PCMCIA support during the Warp installation process. It asks for the most compatible type from a list of 5 options (3600, 4500, 4600, 4700 & 4800). On your advice, I selected T4500. The install process puts several lines into CONFIG.SYS. It is important that these files are inserted in the correct order. The following example shows the relative ordering that the device drivers must have.
DEVICE=C:\OS2\MDOS\VAPM.SYS ... BASEDEV=PCMCIA.SYS DEVICE=C:\OS2\MDOS\VPCMCIA.SYS ... DEVICE=C:\OS2\MDOS\VMOUSE.SYS ... DEVICE=C:\OS2\BOOT\AUTODRV2.SYS C:\OS2\AUTODRV2.INI BASEDEV=IBM2TOS1.SYS /s0=1 /c0=15
The next move was 'dual boot' into native DOS (I replaced what came on the machine with PC DOS 7) and go through all the steps outlined in the Card Manager User's Guide. TSETUP and PCMSETUP need to be configured properly. I'm using a Megahertz XJ1144 card and in order to test the set up I installed and registered the FaxWorks program that came with it. Then a 'dual boot' back to OS/2 and into the System Setup screen to push the 'Plug and Play for PCMCIA' button. This program only recognized one socket, so it was very important to make sure the card was in socket '0". Up and Running!
Notes
It works! I'm using an 'easy install', 'dual boot' setup on a T2100 with 12 Mg of Ram. The correct sequence was not obvious or documented, so perhaps this information will be helpful to someone.
BTW: Part of the install process was unexpected. As mentioned, I replaced MS-Dos 6.22 with PCDOS 7. After installing Warp, the first time I used 'dual boot' into Dos, the Windows Logo appeared very briefly, then a blank screen and back to the C:\> prompt. Fortunately, I made a full backup (23 disks, not 27, as the manual claims) and was able to boot from the companion utility disk and do a full Restore. Windows re-appeared, I booted back to OS/2 and everything (well, almost everything) works. Still having to start up the comet cursor manually, and MaxTime , Fn-esse, etc. are problematical, but Hey! I'm on line. Even the Resume function works; would you believe 'on the desktop' in 10 seconds!!
Sample CONFIG.SYS
REM IFS=C:\OS2\HPFS.IFS /CACHE:64 /CRECL:4 PROTSHELL=C:\OS2\PMSHELL.EXE SET USER_INI=C:\OS2\OS2.INI SET SYSTEM_INI=C:\OS2\OS2SYS.INI SET OS2_SHELL=C:\OS2\CMD.EXE SET RESTARTOBJECTS=STARTUPFOLDERSONLY SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS,LAUNCHPAD SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE SET COMSPEC=C:\OS2\CMD.EXE LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;c:\tcpip\dll;C:\TCPIP\UMAIL; SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\WINDOWS;c:\tcpip\bin;C:\TCPIP\UMAIL; SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\OS2\APPS;C:\WINDOWS SET PROMPT=$i[$p] SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;c:\tcpip\help;C:\TCPIP\UMAIL; SET GLOSSARY=C:\OS2\HELP\GLOSS; SET IPF_KEYS=SBCS PRIORITY_DISK_IO=YES FILES=20 BASEDEV=IBMKBD.SYS DEVICE=C:\OS2\BOOT\TESTCFG.SYS DEVICE=C:\OS2\BOOT\DOS.SYS DEVICE=C:\OS2\BOOT\PMDD.SYS BUFFERS=40 IOPL=YES DISKCACHE=D,LW,AC:C MAXWAIT=3 MEMMAN=SWAP,PROTECT SWAPPATH=C:\OS2\SYSTEM 2048 10240 BREAK=OFF THREADS=256 PRINTMONBUFSIZE=134,134,134 COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON SET BOOKSHELF=C:\OS2\BOOK; SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR SET SOMDDIR=C:\OS2\ETC\DSOM REM SET DELDIR=C:\DELETE,512; BASEDEV=PRINT01.SYS BASEDEV=IBM1FLPY.ADD REM BASEDEV=IBM2FLPY.ADD BASEDEV=IBM1S506.ADD BASEDEV=XDFLOPPY.FLT BASEDEV=OS2DASD.DMD SET EPMPATH=C:\OS2\APPS; PROTECTONLY=NO SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS FCBS=16,8 RMSIZE=640 DEVICE=C:\OS2\MDOS\VEMM.SYS REM DOS=LOW,NOUMB DOS=HIGH,UMB DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB DEVICE=C:\OS2\MDOS\VDPMI.SYS DEVICE=C:\OS2\MDOS\VDPX.SYS DEVICE=C:\OS2\MDOS\VWIN.SYS DEVICE=C:\OS2\MDOS\VW32S.SYS DEVICE=C:\OS2\BOOT\APM.SYS DEVICE=C:\OS2\MDOS\VAPM.SYS BASEDEV=PCMCIA.SYS DEVICE=C:\OS2\MDOS\VPCMCIA.SYS DEVICE=C:\OS2\MDOS\VMOUSE.SYS DEVICE=C:\OS2\BOOT\POINTDD.SYS DEVICE=C:\OS2\BOOT\MOUSE.SYS CODEPAGE=437,850 DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP SET VIDEO_DEVICES=VIO_SVGA DEVICE=C:\OS2\BOOT\COM.SYS DEVICE=C:\OS2\MDOS\VCOM.SYS DEVICE=C:\OS2\BOOT\AUTODRV2.SYS C:\OS2\AUTODRV2.INI BASEDEV=IBM2TOS1.SYS /s0=1 /c0=15 DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=C:\OS2\MDOS\VSVGA.SYS SET ETC=c:\tcpip\etc SET TMP=c:\tcpip\tmp DEVICE=c:\tcpip\bin\inet.sys DEVICE=c:\tcpip\bin\ifndisnl.sys DEVICE=c:\tcpip\bin\vdostcp.vdd DEVICE=c:\tcpip\bin\vdostcp.sys RUN=c:\tcpip\bin\cntrl.exe RUN=c:\tcpip\bin\vdosctl.exe REM FaxFaxFaxFaxFax -- Please do not modify this group of lines IOPL=FxPrint DEVICE=C:\FaxWorks\Fmd.sys SET OCRNOTES=C:\FaxWorks\Calera REM FaxFaxFaxFaxFax -- FaxWorks Pro for OS/2
David Cull provided this update (6th November, 1995):
Since I sent that info a couple of things have happened. The Toshiba 2100 chips and technology video failed miserably in the 'Clear & Simple' Performance Plus Version 3 tests. It was so slow there was a tendency to re-boot while waiting for screens to re-draw. After much telephone work I managed to download the C&T OS/2 driver upgrade. It's called OS2CT.exe and is available from the Toshiba America BBS 714 837 4408 or 4409.
Installation of the new video drivers failed on about the 7th disk and I was finally able to contact someone in Toshiba technical support who confirmed that the upgrade only works with C&T 256 colour screens. I don't know how well it works.
The T2100 went back to from whence it came and I mortgaged the farm in order to get a 'bottom end' IBM ThinkPad. This is a 340CSE and has some problems of its own, but that's another story. If you are interested, I'll pass along what IBM has to say about video driver failures for that machine.
Hope this helps someone avoid the several weeks of frustration I went thru. Even better, perhaps someone at the Toshiba 1-800 can prepare a list of correct answers to questions about whether their equipment runs Warp.
By David Cull
Return to The Hardware Shelf