Unsolved
This post is more than 5 years old
11 Posts
0
213525
April 16th, 2003 16:00
Ghosting a D600
Was wondering if anyone came across and figured out how to fix this problem. Ghost 7.5 detects the Broadcom NIC but can't start the session. NDIS2 driver loaded correctly but Ghost refuses to start. Error message mentions this
"You may need to add the line
RECEIVE_MODE=6
to the WATTCP.CFG file"
Even after that line was added I still have the same error.
Here's my PROTOCOL.INI
[protman]
drivername=PROTMAN$
[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66
[nic]
drivername = B57$
gra-VT
"You may need to add the line
RECEIVE_MODE=6
to the WATTCP.CFG file"
Even after that line was added I still have the same error.
Here's my PROTOCOL.INI
[protman]
drivername=PROTMAN$
[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66
[nic]
drivername = B57$
gra-VT
Message Edited by gra-VT on 04-26-2003 11:03 AM
No Events found!
Marshal82
2 Posts
0
March 1st, 2004 19:00
The only thing I got the cd booting with is a Windows ME bootdisk (created in Windows XP)
I'm still having problems with multicasting. I have tried the newest broadcom drivers and also the drivers mentioned in this thread.
claxstone
5 Posts
0
March 8th, 2004 12:00
-fni switch is not just for use with SATA Drives it also gets round a problem with Intel 865-based motherboard (Optiplex 270).
Anyway, if you tried this then try forcing the ghostcast to unicast rather than multicast, this of course is not ideal as you can only do one at a time.
Also I had this problem with my switch check IGMP is configured, for a while I got round a lot of problems by using a separate hub, with the ghost server and clone workstations all on the same hub.
sumitla2000
5 Posts
0
March 18th, 2004 17:00
Our success with ghosting the D600s just came to an end. A new D600 just came in the door, and now our Ghost boot disk doesn't recognize the NIC card. We know the NIC works because it gets an IP address in Windows. It seems like something has changed with the on-board Broadcom 570 Gigabit NIC. Has anyone else experienced this?
sumitla2000
5 Posts
0
March 19th, 2004 21:00
We figured it out. The newest Latitude D600 has a Broadcom 5705M ASIC on the NIC. The earlier D600s had the 5702 ASIC.
The newest NDIS2 driver from Broadcom (version 7.11) works with both versions of this NIC.
For those of you who use a multicard template in Ghost, here's the PCI-TAG info for the two different versions...
PCI-TAG = 14E4 16A6 : Broadcom 570x Gigabit Integrated Controller
PCI-TAG = 14E4 165D : Broadcom 570x Gigabit Integrated Controller
search66
8 Posts
0
April 27th, 2004 11:00
I'm having a bit different problem with my batch of D600's and the Broadcom NIC.
I can Ghostcast fine, but it is VERY slow (about 7MB a minute).
Has anyone come across this, or have any suggestions?
search66
8 Posts
0
April 28th, 2004 13:00
By default, Ghost puts this at 100/Half... So, I went in to the protocol.ini and forced it to 100/Full.
After I did this, my speed went up to 540MB a minute.
TOO BAD
2 Posts
0
May 21st, 2004 18:00
This is indeed a driver issue. I don't know if it has been said through all the postings, but the D400 NDIS driver works just fine and with the D600 and will bind the session just fine with the multicast server. This has worked just fine for me. I got the same errors when using the D600 NDIS.
TOO BAD
2 Posts
0
May 21st, 2004 18:00
Truslow
6 Posts
0
June 23rd, 2004 12:00
Have you considered using a USB floppy drive and boot off of a floppy. I have tried the CD boot with no success. For now we use a USB floppy and it works fine.
Hope this helps.
Irving
dant98
4 Posts
0
June 23rd, 2004 12:00
-Dan
dant98
4 Posts
0
June 23rd, 2004 12:00
I've done ghosting in the past, but normally boot from a floppy and multicast or just use a USB cable or CD image to go from machine to machine. Well, we haven't been ordering floppy drives with the new Dell D600 laptops. I tried setting up the network boot files on a CD, but apparently it needs to be able to write to the disk. My second solution was to try and get PXE boot working so I could boot the machines from the network and do a ghost from the client without a boot disk.
I'm using the 3Com boot services disk that came with Ghost. Everything *seems* to be set up correctly on the server end. According to the instructions, I'm running the PXEBoot service with the proxyDHCP option. When I boot the laptop, I can see the machine connect to my server, as a line entry appears in the log, but the machine sits at the "DHCP..." portion of the boot process and eventually times out claiming that nobody provided DHCP info.
Has anyone tried this before? Given the problems I've seen on here with the Broadcom card, maybe I should try something different. I'd either like to get a bootable DHCP network CD, or get PXE working. Could I insert a 3Com XJack card in the PCMCIA slot and set the bios to boot from it? Might it handle PXEboot better?
Thanks,
-Dan Thomas
Truslow
6 Posts
0
June 23rd, 2004 13:00
Dan,
Once the laptop is running ghost you can remove the drive and use it to boot another computer. You are right, all you need is one USB floppy drive. We currently use 3. We do this so we can boot multiple computers at once.
Hope this is helpful,
Irving
claxstone
5 Posts
0
June 24th, 2004 11:00
Dan,
PXE is very easy to setup and use, i find no need to use floppy's at all.
I had no experience with ghost, and i setup my server and created images for dell optiplex 260/270 laptops: latitude C810/C840/D600.
I can send you some help documents with pxe files that i have created if you like, i don't want to post my address so you can use yahoo messenger, my username is claxstone.
dant98
4 Posts
0
June 24th, 2004 11:00
Still the best solution would probably be the PXE boot. I just know very little about how PXE works, so I odn't know where my problem lies in using it. claxstone, I don't normally run yahoo messanger, but I might have to install it and drop you a line.
-Dan
claxstone
5 Posts
0
June 24th, 2004 13:00
Dan,
If you create the ghost boot disk from the ghost console, ghost.exe will fit.
Remember, when you add a driver to a template, and you enter the driver name don't put the file extension.
Cheers