Error 33 Unable To Bind Marvell
mobile theme. If CTH has helped you, please consider liking and sharing us on Facebook Search Forums Show Threads Show Posts Advanced Search Go to Page... Topic Tools #1 June 26th, 2007, 06:49 PM izzzy12k New Member Join Date: Jun 2007 O/S: Windows XP Pro Location: San Diego, CA Posts: 16 DOS Networking issue I am having an issue trying to back (via image) my new computer. I have a DOS boot disk I have been using on my old computer and never had an issue. Now with my new computer, I updated the dos drivers on http://www.symantec.com/connect/forums/ghost-boot-disk-error-33-unable-bind the floppy to use the new computers Intel NIC, yet now I keep getting an error and am not sure what's causing it or how to fix. Here's the error I get: Code: "pro0004e: A parameter does not belong to any logical module" "Error loading device driver PROTMAN.DOS" The error seems to happen when the "net initialize" command is executed. Anyone know what's the cause? Thanks, -Iz izzzy12k View Public http://www.cybertechhelp.com/forums/showthread.php?t=158507 Profile Find all posts by izzzy12k #2 June 26th, 2007, 08:15 PM izzzy12k New Member Join Date: Jun 2007 O/S: Windows XP Pro Location: San Diego, CA Posts: 16 Found the issue was tied to the protocol.ini file which was missing some info... Now when the batch file executes netbind.com.. it errors out with "Error: 33 Unable to bind" Almost there izzzy12k View Public Profile Find all posts by izzzy12k #3 June 27th, 2007, 01:32 AM izzzy12k New Member Join Date: Jun 2007 O/S: Windows XP Pro Location: San Diego, CA Posts: 16 Got it fixed.. one of my [labels] had a typo in the protocol.ini izzzy12k View Public Profile Find all posts by izzzy12k #4 July 4th, 2007, 04:59 PM james.barr New Member Join Date: Jul 2007 Posts: 3 Put me out of my misery... I'm having this same problem... What was the missing info from protocol.ini? james.barr View Public Profile Find all posts by james.barr #5 July 5th, 2007, 02:28 PM izzzy12k New Member Join Date: Jun 2007 O/S: Windows XP Pro Location: San Diego, CA Posts: 16 Well initially my protocol.ini had: Code: ; Protocol.Ini section for the Intel(R) PRO/1000 Adapters DRIVERNAME
activation email? 1 Hour 1 Day 1 Week 1 Month Forever Login with username, password and http://www.computerhope.com/forum/index.php?topic=121970.0 session length Forum only search News: Home Help Login Register Computer Hope » Microsoft » Microsoft DOS » Trouble Installing Ethernet Driver in http://elinux.org/LTSI_Kernel_Porting_Information:_Yocto_Poky MS-DOS 6.22 « previous next » Print Pages: [1] Go Down Author Topic: Trouble Installing Ethernet Driver in MS-DOS 6.22 (Read 10201 times) 0 error 33 Members and 1 Guest 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 error 33 unable 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 m
Yocto Poky 1.3 Patches: 1.4 Notes: LTSI Kernel Porting Information: Yocto Poky The following shows the information of the result of porting the Yocto Poky 9.0.0 distribution with the LTSI 3.4 kernel for CuBox. Anyone is more than well come to add information here in the following format What had been done: Cherry-pick local patches for CuBox from a git repository that has been maintained by Rabeeh Khoury, who is a SolidRun Company guy, and merge them into the LTSI 3.4 kernel. Make a Yocto recipe for CuBox and the LTSI kernel. Screenshot Booting the Yocto Poky on CuBox Screenshot of the Yocto Poky on Cubox Boot log of the LTSI kernel in CuBox Boot log CuBox ** LOADER ** U-Boot 2009.08-dirty (Jan 21 2013 - 10:57:40) Marvell version: 5.4.4 NQ SR1 BootROM: Version on chip: 2.33 Status: OK Retries #: 0 Board: CuBox SoC: 88AP510 (A1) CPU: Marvell Sheeva (Rev 5) CPU @ 800Mhz, L2 @ 400Mhz DDR3 @ 400Mhz, TClock @ 166Mhz PEX 0: interface detected no Link. PEX 1: interface detected no Link. DRAM: 2 GB CS 0: base 0x00000000 size 1 GB CS 1: base 0x40000000 size 1 GB Addresses 60M - 0M are saved for the U-Boot usage. SF: Detected W25Q32 with page size 4 kB, total 4 MB Streaming disabled L2 Cache Prefetch disabled L2 Cache ECC disabled Modifying CPU/CORE/DDR power rails to 1.0(-2.5%) / 1.0(-5%) / 1.5(-5%) USB 0: Host Mode USB 1: Host Mode Setting VPU power OFF. Setting GPU power ON. MMC: MV_SDHCI: 0, MV_SDHCI: 1 Net: egiga0 [PRIME] Hit any key to stop autoboot: 0 ===> Executing ext4load usb 0:1 0x02000000 /boot.scr (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 1 USB Device(s) found Waiting for storage device(s) to settle before scanning... scanning bus for storage devices... 0 Storage Device(s) found ** Bad partition 1 ** ===> Executing ext4load usb 1:1 0x02000000 /boot.scr ** Bad partition 1 ** ===> Executing fatload usb 0:1 0x02000000 /boot.scr ** Can't read from device 0 ** ** Unable to use usb 0:1 for fatload ** ===> Executing fatload usb 1:1 0x02000000 /boot.scr ** Can't read from device 1 ** ** Unable to use usb 1:1 for fatload ** ===> Executing ext4