Video Screencast Help

error 41 unable to bind, and unable to Ghostcast

Created: 06 Nov 2008 • Updated: 23 May 2010 | 7 comments


I'm using GSS ver. 2.0, we bought it awhile ago, but we're just getting around to implementing it now.

When I run into trouble is when I go to pull an image onto a machine (HPdc5000). I can boot to PXE, but the disk I've created (with the B57 driver from broadcom) give me an "error: 41 Unable to bind." on Netbind. I've used at least 3 interations of Protocol.ini,Autoexec.bat, and config.sys

I am also getting " Interrupt Vector For Packet Driver not specified in Protocol.ini "

but I don't where in the .ini to put it.
the driver does load, and echos back to me device info, (MAc, Model#, linespeed, INT5).

I think I'm having a similar problem when I use GhostCast from a boot CD, it loads up, starts to image, but then fails somewhere between 25-75% done (but only 10 out of 10 times), I,ve tried unicast and multicast, 2 differnt switches, one unmanaged, the other managed, neither is doing any blocking of any sort.


I *think* that  I'm runing into a network driver issue, but I've tried drivers from both HP and broadcom, B57.dos (device ID 1696). or maybe jut missing a config option in netbind or protocol.ini ??

any help would be GREATLY appreciated  ...

Discussion Filed Under:

Comments 7 CommentsJump to latest comment

Krish Jayaratne's picture


Unable to bind usually means that it tires to load an incompatible driver. 

Interrupt Victor is 0x60 for the default driver. This is specified in protocol.ini file (intvec = 0x60) in the default driver. May be this was missed when adding a new driver. 

 What happens if you use UNDI driver and UNDI(Irqcfg) Driver? The driver is same in both cases, but (irqcfg) has a special executable to check for interrupt conflicts.


Message Edited by Krish Jayaratne on 11-07-2008 07:51 PM
DannoATcorporate's picture

OK, I'll try that UNI driver (I'm assuming that I can find it in the install somewhere ?), but in what of the protocol.ini section do I put that vector?

Krish Jayaratne's picture



It is under [pktdrv] section. If you look at the protocol.ini, it usually has the following entries 



drivername = pktdrv$ 

bindings = nic 

intvec = 0x60 

chainvec = 0x66 


UNDI driver is one of the default drivers, you can select it from GBW. 






DannoATcorporate's picture


So I've tried putting in the PKTDRV section, but I'm still getting the 'interrupt vector not specified' error.

I've tried to use the GBW to create a bootable network package with the uni driver, but after completion it gives me a 28MB image, and the VF editor will not open an ISO. Should I be able to use that 28MB iso to boot across the network?  (This was after selecting "Network Boot Package" from the GBW menu)


What else can I try ... I'm about ready to scrap this project, and go back to CD's, after reading this forum, seems like that's what most end up doing ...


is the 2.5 network Ghostcast work any better ?? it would be nice if I could get this to work

(sorry for the rant, I'm on day 4 of fustration)


Krish Jayaratne's picture



Yes, it is frustrating when things don't work, but I hope the it would pay back once it is setup :-) 


In case of CD, you said it is failing when doing multicast. This is likely to be an issue we have seen some time back (there are many posts in the forum) where the same IRQ was used for network and disk. Did you try using the UNDI (IRQ CFG) driver? 


Regarding PXE image - it should not create 28MB file in 2.0, (though 2.5 create large PXE packages when WinPE is used.). Could you let me know what selections you made when creating it?


Did you add any files to the templates folder? 





DannoATcorporate's picture




I tried today using the PXE boot menu for MS drive letter mapping, which WORKED, mostly... I was able to map a drive create an image, but not to restore one. I get error:

Application Error 437 cannot read from file.

at almost 1/2 way through the restore (the image i took was from the same system, with a differnt drive installed)


I have not added templates, or files to the current template(perhaps I need to ?)

to make the 28MB iso file, I used the GBW, Network boot package, universal Packet driver v2.0 [irqcfg],PC DOS,Ghost client type,no USB or Firewire, DHCP,then (because non of te systems I need to image have floppys) I chose .iso; I'm trying USB now...

But I really wanted to boot from PXE, have a menu where I could choose which (of the 3-4) hardware I'm restoring, then it would pull the correct image. All from the network, without needing USB or CD's to boot from. That is the Goal... is that even possible ??


right now I can boot to the USB thumbdrive, but cannot find the ghostcast server...


I'm tired of going in 5 directions too, can we narrow this down to one thiong that *should* work ,and get it working ?



The Unidriver with the IRQ config I've tried too, but I'm not sure of the settings required in the config files config.sys and protocol.ini .

Still unable to get to the network at all with any of the choices I've created, or the default ones... other than the drive mapping.


On the CD ISO I've made, I chose the UNI irq driver, but still could not restore an image without error.


what should I try next??



Krish Jayaratne's picture



OK. What you are trying to do it certainly possible, but some of them are not straight forward. However, the best way to get it running soon is to use the PXE image and GhostCast server. 


1. To create the PXE image, select "TCP/IP Network Boot Image" from the Ghost Boot Wizard. I think the confusion was starting from "Network boot package" in you last attempt. That allows you to create a boot packages for different media. When you select .iso, it creates an iso image which could be burn to a CD/DVD.


2. "TCP/IP" Network boot image" creates a .sys file. You can use this with 3Com PXE server, just by adding it to the .pxe menu file. I think you are familiar with that process already.


3. When creating this PXE image, select UNDI driver. It works well with most of the machines. But you can select a specific driver too. With some machines, specific driver performs better than UNDI. But you need to have different images for different machines. However, you said that you had problems with UNDI driver when booted from CD. May be your machines does not work well with UNDI. So it is worth trying the specific driver (Driver for the perticular card) too.


4. This image includes a "Packet driver". This driver cannot be used to map network drives. It is to use with GhostCast server. Please try this process and use it with Ghostcast server.



 Once you get this process going, we can expand it to use Mapped Network drives etc. But I think it is best to start with that and get it going before trying others.