Dos Error Sys0006 Occurred
I try to boot my PE1850 to auto run ghost Join Sign in "DOS Error Sys0006" when I try to boot my PE1850 to auto run ghost Servers Information and ideas on Dell PowerEdge rack, tower and blade server solutions. Get this RSS feed Home Forums Server Media Gallery 2 Replies 0 Subscribers Postedover 11 years ago "DOS Error Sys0006" when I try to boot my PE1850 to auto run ghost Posted by Jonathan_zhao on 26 May 2005 10:50 I want to auto recover my 10 PE1850 servers by using PXE boot and Ghost Enterprise 8.2. I installed 3Com DABS on my AD server with DHCP service, my PE1850 can boot with PXE and get ip address. Then I need a image file which can boot my server to dos and map a share folder on the AD server, the share is \\pe4600\map, I've put ghost.exe and GHO file of my PE1850 servers in this folder. So I made a floppy disk from Ghost Enterprise 8.2, I found the e1000.dos driver from Symantec can't drive up my Intel pro 1000MT NIC on PE1850, I download the latest driver from www.intel.com. the version is 10.00, released on Feb28th, 2005. After I replaced the intel driver, this floppy disk can boot my server and auto map the share folder, here is the files: Autoexec.bat: @ECHO OFFSET TZ=GHO-08:00SET PATH=A:\NET\;a:\;%PATH%;SET TEMP=A:\SET TCPHELP=A:\NETSET ETCDIR=A:\NETREM \MOUSE.COMA:\NET\NET STARTA:\NET\NET.EXE USE G: \\pe4600\mapA:\NET\NET.EXE USE G: Ghost.EXE-CLONE,MODE=PLOAD,SRC=G:\pe1850.GHO:1,DST=1:1- SURE -RB Config.sys: DEVICEHIGH=A:\HIMEM.SYSDOS=HIGH,UMBDEVICEHIGH=A:\NET\PROTMAN.DOS /i:A:\NETDEVICEHIGH=A:\NET\e1000.dosDEVICEHIGH=A:\NET\NTSTS.DOSDEVICEHIGH=A:\NET\DLSHELP.SYSLASTDRIVE = Z Protocol.ini: [network.setup]version=0x3100netcard=NIC,1,NICtransport=nts$ntst2,NTS$NTST2transport=ibm$netbeui,IBM$NETBEUIlana0=NIC,1,ibm$netbeuilana1=NIC,1,nts$ntst2 [NTS$NTST2]DefaultDomain=dpstrainingBOOTPFLAG=DHCPDriverName=ntsts$VCs=16VCReceiveLarge=6VCSends=6RcvWindow=2920UseMemory=UMBBINDINGS=NICLANABASE=1 [protman]DriverName=
2003, Ghost v8.x + Ghost Solution Suite (GSS) Discussion Board › GHOST DRIVE MAPPING GHOST BOOT DISK CONTINUED (Moderators: Rad, Christer, NightOwl, Pleonasm, MrMagoo, El_Pescador) ‹ Previous Topic | Next Topic › Pages: 1 GHOST DRIVE MAPPING GHOST BOOT DISK CONTINUED (Read 3310 times) lollipopfluff N00b Offline I love YaBB 1G - SP1! Posts: 9 Back to top GHOST DRIVE MAPPING GHOST BOOT DISK CONTINUED Oct 11th, 2006 at 11:20am Okay, I am still having real problems with this.Just to recap I am trying to create a drive mapping ghost boot floppy disk, not a network ghost boot disk (ie a separate http://en.community.dell.com/support-forums/servers/f/956/t/17287728 utility in ghost)- I imagine however the process is still the same, and then with that drive mapping ghost boot floppy I am emulating it in Easy CD Creator to make a bootable cd.From your previous notes from 'how to Create a Ghost 8.0 Network Boot CD I have done the following:1. Created a mouse.ini and copied to the floppy2. Copied the mscdex.exe and the oakcdrom.sys3. Added the http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1160583601 following to the config.sys at the top of the file so my config.sys looks like thisDEVICE=OAKCDROM.SYS /D:mscd001DEVICE=\net\protman.dos /I:\netDEVICE=\net\dis_pkt.dosDEVICE=\net\b57.dosLASTDRIVE=ZDEVICEHIGH=A:\HIMEM.SYSDOS=HIGH,UMBDEVICEHIGH=A:\NET\PROTMAN.DOS /i:A:\NETDEVICEHIGH=A:\NET\B57.dosDEVICEHIGH=A:\NET\NTSTS.DOSDEVICEHIGH=A:\NET\DLSHELP.SYSLASTDRIVE = ZEdited my autoexec.bat so it now looks like this@echo offSET TZ=GHO+08:00mscdex /L:D /d:mscd001MOUSE.COM\net\netbind.com@ECHO OFFSET TZ=GHO+00:00SET PATH=A:\NET\;a:\;%PATH%;SET TEMP=A:\SET TCPHELP=A:\NETSET ETCDIR=A:\NETREM \MOUSE.COMA:\NET\NET STARTA:\NET\NET.EXE USE Z: \\BNYLN-APPS02\GHOSTA:\NET\NET.EXE USEZ:GHOST.EXEJust as an aside I have also amended my protocol.ini so it has b57$ for my driver name in the last line of the file.After I have done all of that I then emulated the floppy with Easy CD Creator. But I am still having problems???? Are you able to enlighten me. It is now coming back with an incomplete binding on the protocol side. But it is the correct NDIS driver. IP Logged NightOwl Radministrator Offline "I tought I saw a puddy tat..." Posts: 5780 Olympia, WA--Puget Sound--USA Back to top Re: GHOST DRIVE MAPPING GHOST BOOT DISK CONTINUED Reply #1 - Oct 11th, 2006 at 11:29am lollipopfluffDid you say you were able to successfully boot using the floppy boot disk?Are you then using that successful boot floppy as the source for the creation of the bootable CD?When booting the CD, press F8 after the initial *Post* of the system and when it j
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit https://www.experts-exchange.com/questions/24665627/Error-protocol-INI-does-not-have-a-DRIVENAME-E1000-entry.html Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error: protocol.INI does not have a DRIVENAME = E1000 entry Want to Advertise Here? Solved Error: protocol.INI does not have a DRIVENAME = E1000 entry Posted on 2009-08-19 Storage Software 1 Verified Solution 6 Comments 1,928 Views Last Modified: 2013-12-02 OK, I have used the drivers from the lenovo site. I have dos error used the drivers in the Ghost application as well and I can not get this to load the drivers. I used to have a PCMCIA card I used on all of these but that seemed to grow legs (agh). I receieve the message protocol.ini does not have a drivername e1000 entry. I promise you it does. i have opened the ini file and have seen it. I have looked in the ini file and I dos error sys0006 see the name in there. I am not sure what I am doing wrong. i am and have used this Ghost server for other PC's and it has worked fine. Any help would be great. 0 Question by:djreddog Facebook Twitter LinkedIn Google Best Solution bydjreddog Not this did not. I had to use an external card. Go to Solution 6 Comments LVL 15 Overall: Level 15 Storage Software 3 Message Expert Comment by:MYCU2009-08-19 Look here and see if adding the $ and the -fni switch will help you: http://www.symantec.com/connect/forums/dell-network-card-recognition 0 Message Author Comment by:djreddog2009-08-19 Ok that seemed to work but now I have another issue. I get an error "DOS error SYS006 occurred trying to load A:\NET\NET.EXE 0 LVL 15 Overall: Level 15 Storage Software 3 Message Expert Comment by:MYCU2009-08-19 Problem: When creating a network share in DOS either via the Virtual Partition or a mapped network boot disk the following error message is displayed: DOS error SYS0006 occurred trying to load "A:\NET\NET.EXE". The REQUESTER service is not started. Is it OK to start it. Solution: You can choose Y