Unsolved
This post is more than 5 years old
10 Posts
0
17303
September 11th, 2005 11:00
Ghosting a D610 Laptop over network -- Is it possible???
I've had a D600 for a year and ghosting over network is a monthly easy task. I made a bootable CD with: NDIS2\570x\B57.dos the DOS drivers and it boots from the CD directly, loads the network drivers and can dump or load images from a ghost server on the local network.
So.. I purchased a D610, and tried using the same ghost CD.. It boots OK, but the network drivers do not get loaded.. hmm.. something about Driver not found. So.. the question is, which driver exactly do I need to make the D610 recognize it's NIC?...
I searched around this board and found some references that it was problematic based ont he BOIS version, so I tried all 3 that I could find, A02 A03 and A05. same symptom.
can someone help me create a bootable network CD/floppy that I can ghost my D610????/
Thanks in advance.
No Events found!


jmwills
2 Intern
•
12K Posts
0
September 12th, 2005 05:00
JersWork
770 Posts
0
September 12th, 2005 18:00
stormy1777
10 Posts
0
September 13th, 2005 13:00
Can anyone tell me what the correct NIC boot drivers for the D610 are???
I thought it's broadcom NIC same as the D600... please help, I can not backup/restore anything..
also you can not exchange the harddisks, they have a different fitting..
WHY is that?? why not build with some standard???
Charles A
85 Posts
0
September 21st, 2005 00:00
I'm using bootable USB floppies. It worked for me using BIOS A05; GHOST 8.2; and the B57.DOS file for the D610. Not sure if this is the same as for the D600; I don't have any D600.
c:\dell\drivers\R87461\DOS\NDIS2\v7.65\B57.dos
config.sys:
protocol.ini:
Message Edited by Charles A on 09-20-2005 08:41 PM
brnf
3 Posts
0
September 26th, 2005 15:00
Hi there,
being inspired by Charles A's contribution below, I tried the following successfully;
using Ghost 2003, a D600 as Slave and the D610 as Master.
1. included an ancient CD driver to the bootimage - oakcdrom.sys
2. made it the very first entry in my config.sys (as opposed to the last one with the D600)
that's it. I noticed, that the order of booting the two devices made a difference too, however
did not investigate this in depth.
My system files are very much alikes to Charles A's (which is no surprise I guess):
Config.sys:
DEVICE=oakcdrom.sys /D:mscd001
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos
DEVICE=\net\b57.dos
LASTDRIVE = Z
Autoexec.bat:
@echo off
SET TZ=GHO-01:00
prompt $p$g
\net\netbind.com
MOUSE.COM
MSCDEX.EXE /D:mscd001 /L:Z
Dakkon98
1 Message
0
September 28th, 2005 12:00
stormy1777
10 Posts
0
September 28th, 2005 16:00
not yet, I didn't have time to do the switch, I will dedicate a few hours next week maybe.. until then the D600 is used heavily and the D610 is idle.. my thinking was the they will be similar enough.. but i guess they are not.. I'll have to experiment with the above recommendations.. too bad there is no way to attach a file to this board with the .ISO of the CD or needed files..
thanks all for the help, i will post final outcome.
brnf
3 Posts
0
September 29th, 2005 09:00
(everything else, in particular setramd.bat is Win'98 standard)
of colon O into smilies, so be aware of the correct spelling
which is: /testmemcolonOff
menuitem=NET, Start computer with Network support.
menucolor=7,0
[NONET]
device=himem.sys /testmem:Off
device=oakcdrom.sys /D:mscd001
device=himem.sys /testmem:Off
device=oakcdrom.sys /D:mscd001
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos
DEVICE=\net\b57.dos
files=10
buffers=10
dos=high,umb
stacks=9,256
devicehigh=ramdrive.sys /E 2048
lastdrive=z
country=049,850,country.sys
install=mode.com con cp prepare=((850) ega.cpi)
install=mode.com con cp select=850
install=keyb.com gr,,keyboard.sys
autoexec.bat
@ECHO OFF
if "%CONFIG%"=="NET" \net\netbind.com
set LglDrv=27 * 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15
set LglDrv=%LglDrv% O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C
call setramd.bat %LglDrv%
set LglDrv=
prompt $p$g
MSCDEX.EXE /D:mscd001 /L:Z
set PATH=%PATH%;Z:\DOS
copy Z:\Ghost\Ghost.exe %RAMD%:\
copy Z:\Ghost\Wattcp.cfg %RAMD%:\
%RAMD%:
brnf
3 Posts
0
September 29th, 2005 09:00
Since I'm new here, I did not know, that a response to a question is not
automatically posted and visible to everybody - sorry. In fact I do not
even know exactly whether the response went out to Dakkon98 or stormy1777.
So here a few more details on the subject for everybody:
I was able to create a ghost image of a D610 on a D600 via TCP/IP peer-to-peer
connection The only change I made to my D600 backup CD for making it work with
the D610, was moving the CD driver to the top in config.sys - I've been using
oakcdrom.sys (comes with windows) successfully for all CD/DVD based ghosting I
did so far.
As previously mentioned, I noticed a strange "success-dependency" on the
physical notebook connection, for getting things up and running. However,
I did not spent a lot of time to investigate this problem in depth, I rather
came up with a setup "recipe" that worked reliably for me:
1. boot both PCs without being connected
2. start Ghost on both PCs
3. open the Masters (D610) TCP/IP dialog
4. connect the PCs now with a network cable
5. start TCP/IP on the slave (D600)
6. enter the slave's TCP/IP address at the master
done
Here's some more information that might help:
Ghost: 2003 edition
Network Diver identifies itself with: "Broadcom DOS NDIS2 Driver v.7.65 (040618)"
Boot medium: DVD+RW
Boot method: floppy emulation
So much for creating an image.
Restoring is an entirely different story though, because Ghost needs some
storage space for it's logfile, which is not necessarily available. SinceI don't know PC-DOS well enough for being able to create a RAM-drive, I switched to a Win'98 recovery floppy image - on the expense of moving Ghost out of the floppy image to a directory elsewhere on the CD/DVD. Despite of removing all bells and whistles I could not fit Ghost into this floppy image.
Since this posting is already somewhat lengthy, I'll post the pertaining config.sys and autoexec.bat separately.
fastflagsrt4
10 Posts
0
October 3rd, 2005 15:00
stormy1777
10 Posts
0
October 12th, 2005 21:00
ok, finally had time to re-test. works just fine. the only difference is to replace the driver to the newer one..
this is the one I used:
c:\dell\drivers\R87461\DOS\NDIS2\v7.65\B57.dos
thanks for that post.. now it's working!! and I think this will work for both the D600 and D610, so I am happy again..