9533 Under Linux (To Peter's Site!) 
4 Slot PCMCIA Adapter
   PCMCIA Drivers for DOS/OS2/Win3.1x
      Testing the PCMCIA Adapter
      Switch Settings
      Lock / Unlock PCMCIA Cards
         Disabling Solenoid Locks
   PCMCIA under W95
NT3.51 on the Big E

ps2estrt.exe  9533E Starter Diskette v1.0 
ps2eutil.exe 9533E utilities disk version 1.0 

Switch Positions on PCMCIA Adapter
  I have nothing yet on what values correspond to the slot, rom, or IRQ switch settings. 

From Daniel Basterfield
   I did come across a sideways hint at the purpose of one of the DIP switches on the PCMCIA card, but it's the less exciting of the four. There would appear to be 32KB of flash ROM on the card; this is described as holding the 'socket services code' - I would interpret this as it being firmware to sit between the SS driver API and the hardware of the PCMCIA controllers. It is apparently addressed as two seperate 16KB blocks when being (re)programmed; one of the switches has BLK 0 / BLK 1 markings. 

PCMCIA Drivers for DOS/Win3.1x
   These drivers are not as good as with the ones from ISA2SLOT, but the disk does have the Lock/Unlock and Security Manager Utility for OS/2 and Win3.1x

utte131.exe PCMCIA Device Drivers for 9533 
To create a diskette from the uttps131.DSK file: 
- Insert a blank diskette into the A: drive 
- At a DOS prompt type "LOADDSKF uttps131.DSK A:" and press Enter 
- Follow the instructions on the screen 
(Loaddskf.exe is included in the UTTE131.EXE file.) 

Using ISA2SLOT
   I used the Play At Will software that came with the MCA PCMCIA Adapter. If you search the subdirectories, there is all the *.idp files. One is for the IBM 4 slot adapter. Bingo! 
   A problem using the PCMINSTW.EXE (Win 3.1x) program was that it choked trying to rename the system.ini and config.sys files. How to work around that- When it asks to make changes to config.sys (and system.ini) tell it no. Then it will save the changed files as config.pcm and system.pcm in the EZPLAY directory (or wherever you told the instal program to put it). 
  Then use File Manager to move the original config.sys and system.ini to your temp directory (safety first) move the *.pcm fles to the correct locations, rename them, dump out of Winblows, reboot, and it should work. Did for me. 

Win95 PCMCIA Support
  After I got through some conceptual difficulties, I got it to work. I chose to install it under Add New Hardware, and I didn't let Win95 autodetect it (Though it works that way, it identifies it as a PCIC or compatible, NOT Intel.) 
   The default choice of I/O 03E0-03E1, IRQ works. Windows will also instal Socket Services automatically.You do not need any DOS drivers whatsoever. 
   IF the device you are using is visible under Explorer, but comes up as not ready when you click on it, try reformatting it. This was one of my problems. I could see the PC hard drive, used it to transfer W95 setup files, but it would not respond to Exploiter. Until I reformatted it. 

The PCMCIA adapter acts as a bus from the planar to the option adapters. 

   If the computer has a problem, carefully remove and reseat the riser card, any PC Cards, and the PCMCIA adapter. If, after reseating these boards, you get an 80XX error code, replace the PCMCIA adapter.

Lock/Unlock PCMCIA Cards
    PC Cards can be locked in place for security purposes with the lock mechanism. Any of the four lock mechanisms can be unlocked manually. To unlock a locked mechanism, use a pen or screwdriver (pencil lead is made from graphite, which is a conductor. Keep it away from electrical switches) to press its lock solenoid in the direction of the arrow shown below. (Solenoids 1 and 3 are shown locked. Solenoids 2 and 4 are shown unlocked.) 

Disabling Lock/Unlock
   The Lock/Unlock software does NOT work under W95 or NT. If you don't care about leaving them unlocked, simply remove the solenoid headers from J4 (front two sockets) and J3 (rear two sockets). As this is NOT an MCA system, this does not cause any prompts for the starter disk. 

  I have disconnected both solenoid headers on my e and have no problems under Win95. 

   After some switch twiddling, I had to pull a card out without being able to use the blue buttons (card was locked). Trying to reinsert the card didn't work. I looked real close- when the solenoid is in the locked position, there is a little "finger" that sticks out to retain the PC card. It's on the guide that has the eject buttons.
   If you are curious, open the case and use a small screwdriver to work a solenoid. The finger is toggled with the solenoid. As long as the case is on, it's very hard to get a grip on a card with your fingers (pliers are another story).

I thought this was a twisted joke. 

Daniel Basterfield

Well, it was not tricky, really. Rather than attach a CD-ROM drive (couldn't figure an easy way of doing that), I simply copied the NT i386 directory to the hard drive, and installed from there - I chose to use a 105MB PCMCIA drive as a big diskette, and created a suitable DOS boot disk. I've swapped the hard drive for a 512MB one, so space is not an issue. I'm using the normal 4-port PCMCIA adapter, but haven't checked (as far as I recall) if all four ports are available. I'd suspect only two ports are recognised. 

I've just tried shoving a couple of PCMCIA devices into it, and of course the damn security clips are activated, so I can't. Arse. I haven't had any luck running the DOS or Windows lock  Programs under NT. I can't even get the DOS one to run under DOS! at the moment it's only got the PCMCIA t-r adapter in it, and I can't get the bloody ethernet card back in to prove it was working when I last used it. Argh! 

Um, NT 3.51 isn't exactly nippy, but it serves well as a network device. 

>  are you implying that you are using a pcmcia adapter under 3.51? Do tell... 

   Nothing to tell - it saw it, and installed the drivers - the PCMCIA device is started, basically. I'm not sure how to check whether it's running as two instances of a two-port driver, or one instance of a four-port driver.

> I suppose I could try 4.0 on my e. As it uses the i82365SL pcmcia chipset,  it might work. 

Yup - it will. I recall that NT 4 was using around 24MB with me logged on, and without much configured in the way of services. Thrash! I tried NT 3.51 with the Shell Update - a sort of 3.51/4.0 hybrid, but that Explorer shell ate up the RAM, and only shaved 2MB off the NT 4 memory usage. Still thrashy. 

I did have OS/2 4.0 on it for a while - got really narked trying to install LanServer 5 onto it - whatever I did, it refused to play ball unless it could see the CD. Hmm. The PCMCIA adapter support was a dream, though!