Jump to content

Recommended Posts

Posted

Just got a few Tosh Sat Pro A100s and I'm trying to get a ghost image of them.

XP is saying the card is an Intel Pro 100 VE. I've got the e100b.dos driver that I use with other Pro 100 and VE cards and it refuses to work.

Keeps giving me the error about NIC not found etc.

It's driving me mad.

Dos uses e100b.dos, yet windows uses e100b325.sys, just wondering if theres an e100b325.dos driver out there somewhere which its looking for?

Any help would be VERY much appreciated

Posted

the a120 we had was with a gb lan card so that was easy enough luckily, just use e1000 driver instead.

 

so this hp tool, what exactly does it do? just let you boot a usb stick and do the image to that instead of ghosting across a network?

Posted

i couldn't get a ghost cd or ghost cast server to work, and there was no floppy drive, so this basically boots into a mini linux kernel which loads the ghost program.

 

then you start the job from the server end

 

bit of an ugly workaround but it works.

Posted

not had a chance to look at this yet, but i dont get how ghost works on the usb stick. you mean you make the usb stick bootable then load the ghost program from usb?

 

we only have 2gb sticks and our images are shaping up to be about 7-8gb, so i do need network access to save it to a remote area.

Posted

we use gss 2.0 and this has the option to use a usb stick that it formats and loads the drivers onto as a replacement for either floppy or cd so you still need the correct driver which is not much of a help.

 

However there is also an the other option to load the ghost client onto the machine in windows and then set the ghost console to take the image of the pc. This boots the machine into a virtual partition and you don't need to use the driver to get there.

 

Don't know if i have explained it very well. If you check out symantecs website im sure it has more info there. http://www.symantec.com/enterprise/products/newfeatures.jsp?pcid=1025&pvid=865_1

Posted

@badboy:

 

we used the ghost client from the console, but when you tell it to create a new image, it still needs to access the network from DOS to send the image somewhere doesn't it.

 

in the end i just told it to write the image to dvd as it went. had to waste two dvds for it but at least its done

Posted
Oh sorry. Apologies. My friend posted this while i left the laptop for 5 minutes! He himself is not a geek and finds the fact that I look on these forums relatively amusing.
Posted
Hi, I am trying to create a Ghost boot disk for the A120. I have the e1000 driver, but it comes up Unable to loacte PCI LAN adaptor. Has anyone got any suggestions at all?
Posted

Thanks for the tip badboyvtec.

 

That seemed to get further, so I think the NIC part is sorted using ms-dos instead pc-dos.

 

Now the error "invalid command.comopied Enter correct name of command interpreter (eg, C:\command.com) >>_" comes up - thats exactly how it appears on the screen, Guees it meant invalid command.com copied.

 

\ isn't working on the laptop keyboard in dos so I can't type c:\command.com any way!

 

This is GSS 2.0 and the ghost.exe file is over 2 disks. The error appears after loading the second part of ghost.exe is completed.

Posted

try creating the second disk again, it might mean it didn't copy over the ms dos files properly.

i had that this morning, ghost disk 2 whinging about unable to find command.com so i created it again, worked fine.

Posted

Thank you MK-2

 

I copied command.com onto the 2nd disk and it loaded the ghost program.

 

When I chose ghost, multicast I got

 

Application error 19913

 

Unable to start tcp/ip

Cant find dhcp server

Possible network setup problem

 

Ho-hum!

Posted
You need to create a win 98 boot disk and then point gss towatrds that after pressing the get msdos button. Then we created an ISO to burn onto CD as this avoids using 2 floppies. Also you must have the correct driver for your nic.
Posted

Hi all, in the end I got a set of disks for the Intel Pro 100 NICs and manually copied over the E1000 driver, edited the config.sys and proman.ini accordingly and finally it works! My boot disk wizard must be screwed in some way.

 

Thanks for everyone's advice.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...