• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3495
  • Last Modified:

lots of toshiba tecra A3 laptops, want to image using ghost corporate 7.5 marvell yukon 88e8036 PCI-E

Hello,

Can anyone provide me with the details on how to successfully make a boot disk or rom for a Toshiba Tecra A3? The toshy has a MArvell yukon 88e8036 pci-e nic.

i have searched the web but no good, have tried using the standard ndis driver but i think i need to add some switches etc to the boot disk making process in ghost corp 7.5

please advise

thanks,
0
acetate
Asked:
acetate
2 Solutions
 
maimon22Commented:
you try this one if it helps you http://www.ntfs.com/

and i think this is what you need http://www.acronis.com/homecomputing/products/diskdirector/multibooting.html?ad=A04010358 you have check it out carefuly and you can see at the buttom


0
 
roadhog_NZCommented:
Sounds like your saying that you are unable to make a boot disk for the toshy nic is that right?
If you have added the driver in ghost and it does not work, you might have to change one of the drivername=var$ variables in protocol.ini on the floppy, if you post the contents of this file and the dir list of the floppy i could confirm.
0
 
ZoidlingCommented:
If making the boot floppy doesn't work out for you, try Ultimate Boot CD (http://ubcd.sourceforge.net/).  It's open source and has a very nice NIC autodetect feature that will have your laptop booted to DOS and connected to your LAN in  jiffy.  I use it for my ghosting needs and it works well with a variety of hardware so you don't need a library of boot floppies for every different NIC in your shop.
0
 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

 
acetateAuthor Commented:
hello,

yes, marvell yukon wrote back to me, giving me a dos driver and these instructions;

1. Autoexec.bat
2. Config.sys
3. Protocol.ini
4. Directory of Files


1. AUTOEXEC.BAT

@echo off
SET PATH=C:\GHOST
\net\netbind.com
GHOST


2. CONFIG.SYS

LASTDRIVE=Z
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos /I:\net
DEVICE=\net\yuknd.dos



3. PROTOCOL.INI

[protman]
drivername=PROTMAN$

[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

[nic]
drivername = Yuknd$



4. DIRECTORY OF FILES

08/06/2004  03:21p               5,781 DIS_PKT.DOS
08/06/2004  03:21p               8,513 NETBIND.COM
08/06/2004  03:21p              21,696 PROTMAN.DOS
08/06/2004  03:21p              13,770 PROTMAN.EXE
08/06/2004  03:21p                 138 PROTOCOL.INI
08/06/2004  03:21p              56,586 YUKND.DOS


how does this look???

0
 
roadhog_NZCommented:
looks about right to me
0
 
acetateAuthor Commented:
ok, sorry, im no good with ghost, how do i use this?? i made a new ghost disk, added the .dos driver and copied all these files to the floppy disk, ghost says unable to bind error

0
 
acetateAuthor Commented:
the error im getting at startup is: LTE0016E: Drivername missing in Protocal.inio
0
 
acetateAuthor Commented:
worked it out
0
 
roadhog_NZCommented:
had to put the drivers in the net folder?
0
 
acetateAuthor Commented:
yep
0
 
roadhog_NZCommented:
cheers
0

Featured Post

What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now