Ghost image

with symantec ghost you can create a network (tcp/ip) boot disk, you boot into the boot disk map a drive by useing the following
net use x: \\servername\sharename or
cmds use x: \\servername\sharename
make sure a copy of ghost.exe is in the share.

so you boot into your network floppy
type ghost.exe

create your image file and then move onto your next laptop.

obviously you don't have much knowledge of computers if you don't think you can get onto a network from
DOS.

hmmm....DOS

interesting response you have matheson.

Might have been more useful if you included it in you're first response though... (you know, so that us "uninformed users" might be able to make sense of it")

You're last remark was uncalled for!

I only asked you "for interest sake" (such that I, and maybe anoopkck, might become more informed) how you would have achieved the same result using ghost...and you respond as if I am less intelligent than you are...

Considering you're uncanny remarks, I wonder if I said that you were the less informed one what your response would be.
Then I would know for sure, what your calibur of intelligence actually is, I would consider it a smarter decision, to rather keep your remarks to yourself.

you have an interesting theory on my knowledge of DOS...

Which brings me back to  what I  said earlier. i.e "I don't think you can do this from DOS"

English lesson no.1 (read first, understand second then respond third...not read then respond and never mind understanding)

Keyword here is "think" which is something you should have done before throwing around slanderous remarks and unfounded accusations.

Now you stated that you used Ghost to create a network boot disk in order to complete your network setup. Great! You didn't use DOS though...which is what I wanted to know, so you suggested "net use"...fine.

Saying that just because I didn't have extensive knowledge on "ghost" and the "net use" topics, I don't know anything about computers, is really jumping the gun.

anoonkck, think of it this way, if I never responded the way I did, do you think matheson would have replied with a more descriptive answer? Would his original answer have helped you at all? Or would you have struggled to make sense of his explanation?

Some people need a bit of help, when the arrogant people think they know everything and make themselves heard, maybe it's their arrogance that helps others, rather than their actual knowledge on the subject.

think about it

hmmm....DOS

interesting response you have matheson.

Might have been more useful if you included it in you're first response though... (you know, so that us "uninformed users" might be able to make sense of it")

You're last remark was uncalled for!

I only asked you "for interest sake" (such that I, and maybe anoopkck, might become more informed) how you would have achieved the same result using ghost...and you respond as if I am less intelligent than you are...

Considering you're uncanny remarks, I wonder if I said that you were the less informed one what your response would be.
Then I would know for sure, what your calibur of intelligence actually is, I would consider it a smarter decision, to rather keep your remarks to yourself.

you have an interesting theory on my knowledge of DOS...

Which brings me back to  what I  said earlier. i.e "I don't think you can do this from DOS"

English lesson no.1 (read first, understand second then respond third...not read then respond and never mind understanding)

Keyword here is "think" which is something you should have done before throwing around slanderous remarks and unfounded accusations.

Now you stated that you used Ghost to create a network boot disk in order to complete your network setup. Great! You didn't use DOS though...which is what I wanted to know, so you suggested "net use"...fine.

Saying that just because I didn't have extensive knowledge on "ghost" and the "net use" topics, I don't know anything about computers, is really jumping the gun.

anoonkck, think of it this way, if I never responded the way I did, do you think matheson would have replied with a more descriptive answer? Would his original answer have helped you at all? Or would you have struggled to make sense of his explanation?

Some people need a bit of help, when the arrogant people think they know everything and make themselves heard, maybe it's their arrogance that helps others, rather than their actual knowledge on the subject.

"think" about it

you can use symantec ghost which gives you the choice to create a dos boot disk or use its another OS,

and there's no need to be so melodramatic about it, just get on with it, and as you should know dos being the simpleist of operating systems you should know that you can use the config.sys and autoexec.bat to upload a NIC's drivers thus creating the network connection, then call the protocall.ini file from the config.sys statingwether you want to set a static or dhcp address and wether you want it to be a mamber of a domain or not.

and before you get up on ur high horse, i have been commented on, similar to the one i made, and on this site, but honestly it didn't bother me, there's no point in fighting over it, tis just being immature.

so anyways, here is your config.sys example:
DEVICEHIGH=A:\HIMEM.SYS
DOS=HIGH,UMB
LASTDRIVE=Z
DEVICEHIGH=A:\NET\PROTMAN.DOS /i:A:\NET
DEVICEHIGH=A:\NET\ELNK3.DOS
DEVICEHIGH=A:\NET\NTSTS.DOS
DEVICEHIGH=A:\NET\DLSHELP.SYS

the autoexec.bat:
@ECHO OFF
SET PATH=A:\NET\;a:\;%PATH%;
SET TEMP=A:\
SET TCPHELP=A:\NET
SET ETCDIR=A:\NET
REM \MOUSE.COM
A:\NET\NET START
A:\NET\CMDS LOGON

protocol.ini:
[network.setup]
version=0x3100
netcard=NIC,1,NIC
transport=nts$ntst2,NTS$NTST2
transport=ibm$netbeui,IBM$NETBEUI
lana0=NIC,1,ibm$netbeui
lana1=NIC,1,nts$ntst2

[NTS$NTST2]
DefaultDomain=domain
BOOTPFLAG=DHCP
DriverName=ntsts$
VCs=16
VCReceiveLarge=6
VCSends=6
RcvWindow=2920
UseMemory=UMB
BINDINGS=NIC
LANABASE=1

[protman]
DriverName=PROTMAN$
PRIORITY=ibm$netbeui

[IBM$NETBEUI]
DriverName=netbeui$
SESSIONS=20
NCBS=20
BINDINGS=NIC
LANABASE=0

[nic]
drivername = ELNK3$




and network.ini :
[network]
computername=computer
lanroot=A:\NET
autostart=netbeui full
username=user
domain=domain
lslogon=yes
reconnect=no
passwordcaching=no
timesync=no

this is for ibm DOS,
which is essentially MS-DOS as microsoft created it, so all the protocols and syntax will work in MS DOS

To Create a PC Image (Windows 2000)

1.      Set up the PC/Laptop from its manufacturers Rescue discs to ensure the PC has all the correct Drivers.

2.      Ensure the correct Windows Service Pack has been applied

3.      Install and Register all your Applications.

4.      If you want All Pc’s to have a default Home Page and/or Proxy Server, Open a MMC Console (Start - Run - MMC - [ENTER]) Add the group policy snap in. Configure the home page as http://yourhomepage then configure the proxy as Your Proxy IP address

5.      Ensure the machine is set to get its IP address dynamically and is connected to the network. (Unless you use Static IP addressing!)

6.      Set the administrators password.

7.      If you use Novell Install and configure the Novell Client

8.      Apply I.E. Service Packs

9.      Apply MSOffice Service Packs

10.      To display a Login message on every machine Go to the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon   and in the followink keys paste in this text...

LegalNoticeCaption

<Title of the Message>

LegalNoticeText

<Text of the Message>

11.      If you use Host Files copy them to the following locations

      Win9x c:\windows
      Win2k c:\winnt\system32\drivers\etc

12.      Download the latest Sysprep files from http://www.microsoft.com/windows2000/downloads/tools/sysprep/default.asp  Create a directory on the root of the C:\ drive called “sysprep”. Extract all the files from the Deploy cabinet on the Windows 2000 CD to this directory, Then copy any newer files into this directory that you downloaded earlier

13.      If You need to create an unattended file (So you don’t have to fill in all the prompts that windows usually gives you run setupmgr.exe from the sysprep folder and follow the onscreen prompts.

14.      Press start - run - cmd [Enter]. At the command prompt type cd:\sysprep [Enter] then type sysprep -pnp [Enter]. Sysprep will now run and close the PC down. If you restart the PC it will rebuild itself. It is now ready for Ghosting/Cloning

15.      Before cloning your Hard Drive, ensure you have another hard drive (That Big enough to hold the image fitted to the machine being ghosted. (You cannot ghost to the same Hard Drive!)

16.      Arm yourself with a bootdisk from www.bootdisk.com (Ensure it had RAMDRIVE on it and it works!) And a copy of Ghost.exe from symantec

17.      Boot with your bootdisk

18.      Type ghost then return. (This will create one big image if you want to split the image up, to fit on CDROM’s type “ghost.exe -split=600 –auto”)

19.      At the welcome screen press enter to clear the message.

20.      Using the Cursor Keys select Local, Disk, To Image then return.

21.      At the select local source press enter

22.      At the file name to copy to screen, Use the Tab Keys to navigate to the image location your second Hard Drive.

23.      Press Tab to navigate to the filename box and give the image a name (i.e. delllat1)

24.      Keep pressing the Tab Key till Save is highlighted then press return.

25.      At the Compress Image screen Tab to "High" Then press return.

26.      At the proceed screen Tab to "Yes" then press return.

27.      When it is completed it should say, "Dump completed successfully"

28.      If you’re deploying from CDROM you can now burn the image “portions” to CDROM. Ensure the first disk is bootable and has a copy of ghost on it to restore the image to a new computer.

*****Links*****
http://www.anandtech.com/guides/viewfaq.html?i=115

You say you do NOT have Ghost or similar. SO

1) Use RIS, free from MS

2) Use the IBM RapidInstall option.  You should be able to create an image, and transfer it to the other machines, and then use the F11 ket to do a restore. You will probably require the use of Sysprep,  etc to get diferent SID's and Serial #'s

Check out the IBM site for more info.

I hope this helps !

Also http://www.terabyteunlimited.com/image.html  may have a demo or free for 30 days full version

ALso see
http://www-tcsn.experts-exchange.com/Hardware/Q_20092048.html

I hope this helps !

Thank you Matheson.

I am sure your answer is much more helpful, considering your last response. I certainly learned something.

On my last note, if it didn't bother you in the first place, then why did you take the time to be "more helpful" than in your original response. So that the melodramatic, immature can realise how clever you are? Probably.

On the other hand, I agree, this is rather stupid to have to waste each other's time with this...

Sheldon

...Sheldon gets up on his high horse and gallops into the "unknown"...

oh oh oh where's the unknown...
sounds interesting! ;o)

You said you do NOT have Norton Ghost or Power Quest Drive Image?
 
Huji

not a licenced copy

no way!
use the ghost server... look at the options when you first run it
you should be able to run ghost as a LISTENING server

the bootdisk is created with a command line option -
just pop in the disk on the target machine and it will seek out the listening server, you can then remotley image the laptop

http://www.techmarketingink.com/NG6RG.PDF
heres a user manual, sorry im not infront of my pc and dont have the resources i need to give you step by step...
i do remember it only took me 30 minutes to figure it out from scratch

I had 15 client machines that I wanted to ghost windows onto (yes, I had 15 licences...)
First I used partition magic to shrink the c: partition to make room for a d: partition to hold
the ghost image. Then I took a ghost image of an installed machine writing it to a server on the network. Went to each machine in turn and copied the ghost image
to the d: drive. ran ghost to restore from the ghost image to the c: drive.
Worked great, and provided exelent disaster recovery

Yes,you can make a DOS boot floppy that will provide network support but it's
not entirarly trivial, you need to get the correct DOS drivers for your NIC (if available...)
etc.
As far as matheson's "DOS boot floppy", have you actually tried it and made it work, on a bare machine without
having win3.1 on the machine ?
Cheers, Bjorn