Error Loading Device Driver .dos
activation email? 1 Hour 1 Day 1 Week 1 Month Forever Login with username, password and session length Forum only search News: Home Help Login Register Computer Hope » Microsoft » Microsoft DOS » Trouble Installing Ethernet Driver in MS-DOS 6.22 « previous next » Print Pages: [1] Go Down Author Topic: Trouble Installing Ethernet Driver in MS-DOS 6.22 (Read 10232 times) 0 Members and 2 Guests are viewing this topic. jaydubTopic StarterGreenhorn Experience: Experienced OS: Windows XP Trouble Installing Ethernet Driver in MS-DOS 6.22 « on: July 30, 2011, 04:59:53 PM » I'm having difficulty installing an ethernet driver for my NIC under MS-DOS 6.22. My goal is to get a broadband cable connection and install Arachne web browser. Network hardware is as follows: - Marvell Yukon 88E8001 Gigabit Ethernet Controller is built into ASUS motherboard and uses PCI-E bus. Connected to router.- Marvell Yukon 88E8056 Gigabit Ethernet Controller is built into ASUS motherboard and uses PCI bus. Currently not connected to router.- DLink 655 Wireless Router (using ethernet cable, not wireless)The Yukon driver is NDIS2 Marvell DOS driver v8.21.1.1 from ASUS which includes the files yuknd.dos, protocol.ini and oemsetup.inf. To install the driver, I'm using instructions found at http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Networking_FreeDOS_-_NDIS_driver_installation, which is based on DIS_PKT9.DOS. So, I've assembled a floppy with the following files:- protman.dos (extracted from MS Client 3.0)- protman.exe (extracted from MS Client 3.0)- netbind.com (extracted from MS Client 3.0)- DIS_PKT9.dos (downloaded from link at the SourceForge page cited above) - yuknd.dos (ethernet driver from ASUS)- protocol.ini (new file created by me with MS-DOS EDIT command and saved with .ini extension)It should be noted I did not include on the floppy two of the driver files from ASUS:- oemsetup.inf (packet driver converter instructions did not say to use other files when assembling the floppy)- the original protocol.ini (per packet driver converter instructions, I created and used a new protocol.ini file)All files on floppy were copied to a new C:\NET directory and no other files exist in t
the parameters 7 Installation 8 Reboot Overview Drivers based on the "Network Driver Interface Specification" (NDIS) are the default in the Windows world. The most recent version is NDIS 6 which is used in Windows Vista. Windows 98 used NDIS 5, Windows 95 came with NDIS 3.1. In DOS you have to use the real-mode driver NDIS2. Where to find them It is most likely a NDIS driver exists for your network card. Look for a directory called "NDIS2" in your cards installation files. If you can't find a driver, take a look at this site. The ending of the driver name has to be *.DOS, so for instance http://www.computerhope.com/forum/index.php?topic=121970.0 the driver of the 3com 3C574 PC-Card is called "EL3C574.DOS". How they work In the language of the NDIS architecture these drivers are called "Media Access Control" (MAC) drivers. The MAC driver is only one component of the NDIS architecture as you can see in the figure above. According to the NDIS 2.1 documentation NDIS seems to work like that: Commands in FDCONFIG.SYS (FreeDOS) or CONFIG.SYS (other DOS) load the Protocol Manager driver PROTMAN.DOS, the http://freedos.sourceforge.net/wiki/index.php/Networking_FreeDOS_-_NDIS_driver_installation MAC driver and the protocol driver. This can be done by lines for each of these drivers or by starting the "Installable File System Helper" driver, which is loaded by "DEVICEHIGH=IFSHLP.SYS" and starts the Protocol Manager, the MAC and the protocol drivers according to PROTOCOL.INI. The Protocol Manager reads the configuration from PROTOCOL.INI and makes them available to the MAC driver and protocol driver which load after him. The MAC driver and the protocol driver load and configure themselve according to that information. They identify themselves to the Protocol Manager. Before MAC driver and protocol driver can communicate, they have to be bound together, so they can access each others "entry points" (communication ports). This bind process is controlled by the Protocol Manager based on information in PROTOCOL.INI. The binding sequence can be triggered by NET.EXE or NETBIND.COM (which can be done in AUTOEXEC.BAT). The Protocol Manager (PROTMAN.DOS) then starts the memory resident (Terminate and Stay Resident - TSR) program PROTMAN.EXE to execute the bind command and to control the correct ordering of drivers. After binding has occurred, the MAC and the protocol driver communicate directly to each other. The Protocol Manager is not involved in this communication process any longer, so NETBIND.COM frees most of the memory previously reserved by the Protocol Manager. The configuration of NDIS under DOS has chang
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for https://www.experts-exchange.com/questions/24607481/PROTOCOL-INI-Issue.html Help Receive Real-Time Help Create a Freelance Project Hire for a https://support.symantec.com/en_US/article.TECH24586.html Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > PROTOCOL.INI Issue Want to Advertise Here? Solved PROTOCOL.INI Issue Posted on error loading 2009-07-28 System Utilities MS DOS PCs 1 Verified Solution 5 Comments 1,010 Views Last Modified: 2013-12-01 I'm trying to wipe and reinstall Windows XP Tablet Edition 2005 on a tablet PC which has no onboard drives other than a hard drive. I used the instructions I found at http://www.lockstockmods.net/2008/04/26/easy-way-to-pxe-boot-windows/ for booting to the network. error loading device As part of the process, I had to add a custom driver to the image (which is an image of Bart's Network Boot Disk). The NIC driver loads ok and I'm accepting all the defaults on the first boot like the instructions say, but when it tries to do a net init and load PROTMAN.DOS, I get the following error: PRO0008E: Invalid decimal digit in PROTOCOL.INI file Error loading device driver PROTMAN.DOS. Error 7306: The driver failed to initialize. When I examine the PROTOCOL.INI file, it appears that it is being dynamically generated by the MSNET.BAT file included with Bart's Network Boot Disk, so I'm not sure what I can do to avoid this problem. I'm including what's in the PROTOCOL.INI file. I had to retype by hand since there's no way to copy and paste the file. ; Protocol.ini generated by msnet.bat [network.setup] version=0x3110 netcard=nu2$nic,1,NU2$NIC,1 transport=tcpip,TCPIP lana0=nu2$nic,1,tcpip [tcpip] NBSessions=6 DriverName=TCPIP$
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' "Error 7306 : The driver failed to initialize" and "Error 7321: Network-card drivers failed to load" TECH24586 October 3rd, 2007 http://www.symantec.com/docs/TECH24586 Support / "Error 7306 : The driver failed to initialize" and "Error 7321: Network-card drivers failed to load" Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation Drivers are not loading when using PXE and, when trying to install BootWorks, a message is displayed stating that the NIC is not compatible. PXE Errors Error loading device driver B57.DOS Error 7306 : The driver failed to initialize B57.DOS was not loaded Error 7321: Network-card drivers failed to load or Error loading device driver B44.DOS Error 7306 : The driver failed to initialize B44.DOS was not loaded Error 7321: Network-card