I purchased a LinkSys EtherFast 10/100 PC card (PCMPC100 v3) so that I could “Ghost” the hard drive of my Sony PCG-F420 to a desktop machine over a LAN using Symantec’s Ghost 2002 program. As I understand it, this works by setting up a DOS LAN. When I try to do this, using the “Packet Driver” from the LinkSys installation disk, I get the following error: Packet Interrupt Number 0x62 (98) *** I/O Failure *** and consequently I am unable to make a network connection. I cannot find out what is causing this problem, either in the LinkSys manual or the Knowledge Base. I would note that on page 8 of the manual, it talks about adding NOEMS X=D000-D3FF to the line DEVICE=C:\EMM386.exe in the CONFIG.SYS file – but I do not have a CONFIG.SYS file. The boot disk that I am using is generated by Ghost, and consists of the following: Contents of Floppy Boot Disk: Folder: GHOST Folder: NET File: AUTOEXEC.BAT File: COMMAND.COM File: IO.SYS File: MOUSE.COM File: MOUSE.INI File: MSDOS.SYS The Version of DOS is that that comes with Windows 98. Listing of AUTOEXEC.BAT @echo off prompt $p$g \net\PC100PD.COM MOUSE.COM cd \ghost echo Loading... GHOSTPE.EXE Contents of folder NET: PC100PD.COM Contents of folder GHOST: File: GHOSTPE.exe File: WATTCP.CFG Listing of WATTCP.CFG: IP = 192.168.1.102 NETMASK = 255.255.255.0 GATEWAY = 192.168.1.1 I have also tried to use the “NDIS2 Driver” from the LinkSys installation disk. When I do this, I get the following error: Linksys Etherfast 10/100 PC Card (PCMPC100) v2.00 (c) Copyright 2000 All rights reserved MAC0001: Initialization failure Press any key to continue… Contents of Floppy Boot Disk: Folder: GHOST Folder: NET File: AUTOEXEC.BAT File: COMMAND.COM File: CONFIG.SYS File: IO.SYS File: MOUSE.COM File: MSDOS.SYS Listing of AUTOEXEC.BAT @echo off prompt $p$g \net\netbind.com MOUSE.COM cd \ghost echo Loading... GHOSTPE.EXE Listing of CONFIG.SYS DEVICE=\net\protman.dos /I:\net DEVICE=\net\dis_pkt.dos DEVICE=\net\PC100.DOS Contents of folder NET: DIS_PKT.DOS NETBIND.COM PC100.DOS PROTMAN.DOS PROTMAN.EXE PROTOCOL.INI Listings of DIS_PKT.DOS; PC100.DOS; PROTMAN.DOS – from LinkSys disk Listing of file PROTOCOL.INI [protman] drivername=PROTMAN$ [pktdrv] drivername=PKTDRV$ bindings=nic intvec=0x60 chainvec=0x66 [nic] drivername = PC100$ Contents of folder GHOST: File: GHOSTPE.exe File: WATTCP.CFG Listing of WATTCP.CFG: IP = 192.168.1.102 NETMASK = 255.255.255.0 GATEWAY = 192.168.1.1 Unfortunately LinkSys say that they do not support DOS! Any help would be appreciated. Oliver St Quintin

If I had to guess which I do I would say you have the wrong version of ndis driver check there site at linksys.com click on products then network adapters then lne100tx. On the right side click on drivers/download. It will show you there how to ID which version you have. I hope that helps. Sadly however there oemsetup.inf file in version 5 will not work in ghost 7.5 ce. So, if this is your case also you will have to try to add it manually.

I am receiving exactly the same error, using the PC100.DOS NDIS2 driver and PCMPC100 v3 network adapter. Has anybody found a solution to this problem? NOTE: Linksys's site has no other driver version available except v2.

Dude I happened to stumble upon this site looking for a driver for my network. I am an A+ Tech I work for Microsoft your problem is your CONFIG.SYS is hidden. You have one my friend just hard to access. In any version of windows u can hide files or folders. Goto your main drive on the computer with the card in it, then goto the top menu of the window it will say TOOLS then goto VIEW and select SHOW ALL FILES it will automatically unhide the config.sys which is hidden automatically by windows so that you cannot delete it and destroy your computer if I were you I would back the config.sys up onto a floppy so if any mistakes are made when u add a few lines to it, if it dosen't work u can put it back from the floppy. Just think of me as GOD for now. My names really................ SiRdRaXoN

I have never seen an instance where Windows hides the config.sys file, although there are things that need to be loaded in the config.sys to get this to work. In order to use a PC card at the DOS level you need some sort of card services loaded to initialize the card. Once you have that installed, you would also need a packet driver. All of this would be loaded in the config.sys file which you don't have. It is tricky getting PC cards to work at the DOS level. Read this http://appdeploy.com/faq/pcmcia.shtml One thing you could do if you have enough hard drive space is drop to DOS and create your .gho image somewhere on your hard drive then boot to windows and transfer it. SiRdRaXoN would have known some of this stuff if he was a true guru, or as he calls it, a GOD.