I recently bought a refurbished Dell Latitude LM, Pentium 166MMX. It came with nothing but a floppy and AC power supply.
Hard drive has nothing on it. So I bought a third party external pcmcia cd-rom to get it going. It will not recognize the cd-rom or any card it seems until I have the PCMCIA 2.1 Card and Socket Services installed.
I don't know where to get this. Hard drive is empty, no disks were supplied with the system, and after scouring the support pages at dell have really came up empty. Can anyone help???
Adaptec 1460 AND iomega zip PCMCIA SCSI adaptors have an enabler for this purpose. The Following lines are required in your Config.sys file for PCMCIA support in DOS or Windows 3.1x. If you have installed Cardsoft to a directory other than C: cardsoft, then change the path accordingly. DEVICE=C: DOS HIMEM.SYS DEVICE=C: EMM386.EXE NOEMS X=D000-DFFF DEVICE=C: CARDSOFT SSCIRRUS.EXE DEVICE=C: CARDSOFT CS.EXE DEVICE=C: CARDSOFT CSALLOC.EXE DEVICE=C: CARDSOFT CARDID.EXE These files will activate the PC Card socket. There will probably be additional drivers required by the PCMCIA Card itself.
In order to get more information on any additional drivers, please call the manufacturer of the card or reference the manual. This has been provided as a convenience for our customers. Technical Support does not support the MS-DOS operating system on the LM.
Some drivers of PCMCIA cards have an integrated direct enabler function. Unfortunately the drivers of many cards do not yet support modern PCI PCMCIA Controllers. Therefore the 'Legacy/Notebook' mode in the System Setup (Advanced- PCI devices- PCMCIA I/O Address) must be adjusted (compatibility with the old ISA Controller type). On the other hand there are many cards that do have a direct enabler function that has been adjusted to a PCI PCMCIA (NOT CardBus!) Controller.
Because with such drivers the PCMCIA Controller is looked for as a PCI Device, the Legacy setting in the System Setup does not have any effect - a new driver by the card manufacturer is required or an older driver which still has an ISA-Bus compatible direct enabler function. The Accton EN2216 Ethernet Card driver Ver. The possible settings, depending on the card type, are: I/O=180,240, 260.,2F0,300,320, 340.,370,3A0h and A20,A24(TokenRing) (addresses 200h, 220h, 330h and 380h collide with the standard settings of the Audio Board; for other resources used see BIOS Setup). IRQ=3,4,5,7,9,10,11,15 (IRQ4 is used by Com 1 as a standard, 7 is used by LPT1,5 is used by the Audio Board. IRQ3 is reserved for the IrDA Port, but it can be used for other purposes as long as IrDa Port is not addressed, IRQ 15 is used by the CD-ROM - if available).
Thanks a million to you guys making Absalon and keep up the good work and keep them episodes coming, us fans will do our best to back you up. These lads do not get paid to do these episodes and as a die hard fan the only way i can support is by donating towards production. I seriously urge all fellow DBZ lovers to be generous and not let this series die off. Its a more mature and gritty take on the Dragonball lore along with splendid animation.
![Dragon ball ab salon episode 3](/uploads/1/2/4/0/124004723/230805616.png)
If necessary you can reprogram all ports and the Audio Board in the Setup or you can switch them off completely. The LM uses an INTEL 365 PCIC or compatible PCMCIA controller One way around the DOS issue is to use WIN95 diskettes. Boot up and Format C: Then Copy Every SINGLE DISKETTE to the c: drive. Then install WIN9X A PARALLEL scsi DRIVE or PARALLEL ethernet ADAPTOR helps with this because you do not need cardsoft to enable the pcmcia slots as you arent yet using them.
Microsoft stopped supporting dos a long time ago which is why there are no dos drivers for new desktops or laptops. The C640 is a totaly different animal than the LM. The C640 has a CARDBUS controller not PCMCIA. And I believe that the C640 WILL NOT EVER support DOS. The LM is a PENITUM the C640 is a PENTIUM4 CLASS LAPTOP. Thanks for your reply, though not very satisfactory w.r.t.
My problem I am just a litte surprised about the many times I, and all the others who have similar questions, are confronted with the 'killer remark' (this is a literal translation of the Dutch word 'dooddoener') that DOS is no longer supported. It may not be supported by Microsoft but IT IS STILL USED AND DISTRIBUTED WIDELY, also by reknown software companies such as Symantec (ghost!!) or Power Quest (Partition Magic), to mention just a few. It is a shame, indeed, that Symantec does not provide the drivers necessary for the pertinent hardware to do just that what the software is meant for, i.e. Producing and restoring disk images. I did find a set of 'card and socket servises' drivers on the IBM website (aimed at the mentioned applications using Thinkpad models - so they seem to value there clients needs).
![Cardsoft Download Cardsoft Download](https://thumb1.shutterstock.com/display_pic_with_logo/4163113/469172300/stock-photo-blank-business-card-with-soft-shadows-469172300.jpg)
This, I believe, should be exemplary, for Dell and other laptop manufacturers. The IBM (IBMDOS based) drivers load well on my Latitude C640 but then, unfortunately, aspi2dos.sys comes with the message 'host adapter at port address 340 failed diagnostics' and the same for address 140 - thus 'aspi2dos.sys installation failed' Seems as if I have come a long way but stranded while sighting the shore (forgive me: this is also a literal translation of a Dutch expression).
Sorry for missing the point here. I wish to attach a scsi device (Quantum DLT 15/30 SCSI drive), not a usb nor firewire device and address this device under DOS (exactly as I do on my desktop with AHA-2930 SCSI controller) So, what is the use of USB or Firewire drivers in my case??? DUSE supports just USB and firewire. I use Norton Ghost 2002 (licenced) and know how to make bootdiscs.
As a matter of fact the way I have been imaging my dell disk up till now is via a network bootdisc (master/slave on laptop/desktop). Works fine, UNDER DOS, no problem. Again, what I prefer is writing the image to the DLT drive directly UNDER DOS.
![Cardsoft Download Cardsoft Download](/uploads/1/2/4/0/124004723/386302535.jpg)
Hope this clarified my needs.
PCMCIA-GPIB and Windows 3.1 - SystemSoft CardSoft The majority of name-brand and off-brand computers shipping today (other than IBM and Toshiba) are shipped with CardSoft. It is probably the most stable CS on the market. SystemSoft seems to have been recognized as the industry leader for CS as Microsoft actually hired them to write the socket services for Windows 95. In the past, CardSoft was shipped with primarily no-name brand computers simply because it was cheap. Early revisions were not great.
Toshiba Cardsoft Download
I am kurious oranj rarlab. Now it is shipped not only with some of the off brands, but also with such popular systems as Compaq and NEC. The current revision works better with our card than probably any other CS. Recognizing CardSoft CardSoft is typically installed in a /CARDSOFT directory.
On Compaq machines, however, it is usually installed in a /CPQDOS directory. Different versions on different machines will install a different number of drivers but one example is shown below: DEVICEHIGH=C: CARDSOFT SSCIRRUS.EXE DEVICEHIGH=C: CARDSOFT CS.EXE DEVICEHIGH=C: CARDSOFT CSALLOC.EXE DEVICEHIGH=C: CARDSOFT ATADRV.EXE DEVICEHIGH=C: CARDSOFT MTSRAM.EXE DEVICEHIGH=C: CARDSOFT MTDDRV.EXE DEVICEHIGH=C: CARDSOFT CARDID.EXE CardSoft usually installs at the memory space from D000-DFFF. You can also select the ranges C000-CFFF and E000-EFFF quite easily. We have not tried any other ranges but they should also work. Of the above drivers, only 4 are required for use with our cards: the socket services driver (SSxxxxxx.EXE), CS.EXE, CSALLOC.EXE, and CARDID.EXE.
The other drivers are for PCMCIA memory cards or disk drives. To reduce RAM usage with CardSoft about the only thing that you can do is REMark out these extra drivers. Using CardSoft There are a lot of things that you have to do with other card services that you do not need to worry about with CardSoft. One of the biggest problems with other card services is that if they do not recognize the card, they automatically try to give it resources. That is not true with CardSoft. If it does not recognize the card, it will leave it unconfigured.
CardSoft does come with both a Windows and DOS configuration utility. The Windows utility, CardView, offers little more than showing what card is in a particular socket. It is not worth using.
The DOS utility provides a little more power, however it is still easier to simply edit the csalloc.ini file rather than use config. SystemSoft is supposed to be releasing a newer version of CardSoft called CardWizard. It should be just as stable as previous versions, however it is supposed to have a nicer user interface and be much easier to configure. We have not seen this particular software yet nor do we know of any companies who are currently shipping it with their machines. CardSoft, like CardWare, also uses sounds to tell some things about insertion/configuration of cards. After introducing the card into the system, there is typically a short delay followed by a low-toned beep.
This is a sign that CardSoft was able to recognize card insertion and read the CIS, but that it did not actually configure the card. Whenever CardSoft actually configures the card, it will emit two beeps. It will also emit two beeps when the card is unconfigured. CardSoft will actually remove resources from the card whenever it is released by our driver. (Note: When running ibtest, you will actually get two beeps for each time that it tries to configure a card and two more beeps each time it tries to unconfigure. In other words, you can expect a total of 16 beeps!) In most cases, CardSoft should come preconfigured in the system.
In these cases, we will rarely get customer calls. Most of the problems that we will see with CardSoft will be related to base I/O or interrupt conflicts or cases where customers have an old version of the CS.
As with CardWare, you should be able to use Any for the ibconf settings. If you have problems with IRQ conflicts or base I/O address conflicts, we recommend removing them from CS use by editing csalloc.ini. You should also be able to force addresses if necessary. Changing CS Resources Although the resources for CardSoft can be modified using the DOS config.exe program, you will probably have better luck simply editing the initialization file. CardSoft stores its initialization information in a file called csalloc.ini. Newer versions of this file look like the example below which was taken from vendor release 2.06.
The file consists of a top section which CardSoft may modify at boot time and a bottom section which is only modified by the user. Any changes that you wish to make to CS resources should be made at the bottom of the file below the 'Resource modifications' line. Information below this line will override any information at the top of the file. To exclude interrupts, add an IRQEXCLUDE line. To exclude I/O space, use an IOEXCLUDE line.
![Toshiba cardsoft download Toshiba cardsoft download](/uploads/1/2/4/0/124004723/489488848.jpg)
To reserve (include) I/O space, add an RIO line. To include/exclude memory from CS use, add a MEMINCLUDE or MEMEXCLUDE line (and be sure to make appropriate changes to the memory manager). The numbers are all to be entered in hex. They may be separated by commas or hyphens, where a hyphen includes all values in between the two external numbers as well. # csalloc.ini # # # The available resources described by the 'MEM=', 'IO=', # and 'IRQ=' lines may have been altered by the 'xINCLUDE' # and/or 'xEXCLUDE' lines below! # The 'MEM=', 'IO=' and 'IRQ=' lines are provided for # Read-Only purposes. # MEM=D000-DFFF IO=108-1EF,1F8-277,280-2BF,2E0-2E7,2F0-2F7,300-37F,3A0-3BF, 3E8-3EF IRQ=7,A-C,F # #.
Resource modifications should be made below # this line. # RIO=170-177,2E8-2EF,2F8-2FF,370-377,3E8-3FF MEMEXCLUDE=C000-CFFF,E000-EFFF IRQEXCLUDE=F IOEXCLUDE=300-31F CardSoft Support and Some Common CardSoft Suppliers SystemSoft 313 Speen Street Natick, MA 01760 (508) 651-0088 (508) 851-8188 (fax) Compaq: www.compaq.com ftp.compaq.com Midwest Micro: www.mwmicro.com ftp.mwmicro.com.