Dos Error Sys0006 Trying To Load Net.exe
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=PROTMAN$PRIORITY=ibm$netbeui [IBM
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 3315 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 http://en.community.dell.com/support-forums/servers/f/956/t/17287728 create a drive mapping ghost boot floppy disk, not a network ghost boot disk (ie a separate 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 http://radified.com/cgi-bin/yabb2/YaBB.pl?num=1160583601 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 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 - O
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 Close Search Login https://www.experts-exchange.com/questions/21301567/Which-NIC-with-Ghost.html Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Which NIC with Ghost? Want to Advertise Here? Solved Which NIC with Ghost? Posted on 2005-02-03 Windows Networking 1 Verified Solution 3 Comments 1,221 Views Last Modified: 2011-09-20 Could you please suggest NICs that work nicely with Ghost 2003 and Windows Server 2003 and XP machines? I have trouble accessing network drive and would rather buy the right dos error NIC than mess with custom NIC setup. Thank you 0 Question by:howei Facebook Twitter LinkedIn Google LVL 20 Best Solution bySilvers5 Hi howei, 3 com nics work great with ghost.. Are you sure it is from the NIC? it can be permissions problem mostly Go to Solution 3 Comments LVL 20 Overall: Level 20 Windows Networking 1 Message Accepted Solution by:Silvers52005-02-03 Hi howei, 3 com nics work great with ghost.. Are you sure it is from the dos error sys0006 NIC? it can be permissions problem mostly 0 Message Author Comment by:howei2005-02-04 Thanks Silver, I get all kinds of errors when Ghost reboots, eg: 1) XP machine with built in SiS 900 PCI NIC: "DOS error SYS0006 occured trying to load C:\NET\NET.EXE" 2) Server machine with D Link DFE-530TX NIC: "FATAL - board not found in system" NET 5733 "The Requester service is not started" "Abort 40213 @Find could not find the image file XXXXX on your system....." There are also machines with Realtek RTL8029 Fast Ethernet NICs 0 Message Author Comment by:howei2005-02-05 I created Mapped Ghost Boot Disk on the client machine, restarted. Had ping replay from the server where client have mapped drive to. Was asked to login but than I got message: "You were loged on, but you have not been validated by a server. Therefore, you may not have permision to use some network resources" Would you know what this message really means? I supplied correct domain user name and password. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Featured Post Find Ransomware Secrets With All-Source Analysis Promoted by Recorded Future Ransomware has become a major concern for organizations; its prevalence has grown due