Dos Error Sys 0006
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 [
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 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 http://en.community.dell.com/support-forums/servers/f/956/t/17287728 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 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 https://www.experts-exchange.com/questions/24665627/Error-protocol-INI-does-not-have-a-DRIVENAME-E1000-entry.html 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 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
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your http://www.tek-tips.com/viewthread.cfm?qid=284805 Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting https://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-40768 in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness dos error To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. HP (Compaq) servers Forum at Tek-Tips HomeForumsServer RackServersHP (Compaq) servers Forum Symantec Ghost & Compaq Proliant DL360 G2 Help 3 thread484-284805 Forum Search FAQs Links MVPs Symantec Ghost & Compaq Proliant DL360 G2 Help Symantec Ghost dos error sys & Compaq Proliant DL360 G2 Help VictorySabre (TechnicalUser) (OP) 31 May 02 21:33 Hi All,I hope someone may have a solution to this problem. I have a Compaq ProLiant DL360 G2 1U server and I need to make a bootable DOS diskette with network access to allow me to make a Ghost image to be stored on a network share.I had no problems creating one for the previous ProLiant DL360 model, but this new G2 unit with the NC7780 10/100/1000 NIC card is bugging me.I have tried downloading Compaq's Gigabit NIC drivers SP19761 and edited the protocol.ini file with no success. I have also added in the "NODE" entry and "SLOT" entry in protocol.ini with no success. I also tried disabling the 2nd NIC and repeated the above with no success. Basically during the reading of the disk, it reports that a PCI LAN Adapter could not be found. The NIC does work as I it works in Windows 2000.Does anyone know what drivers I am supposed to use?Thanks,Ed RE: Symantec Ghost & Compaq Proliant DL360 G2 Help VictorySabre (TechnicalUser) (OP) 4 Jun 02 15:
OS/2 trap errors IBM no longer actively maintains this content. It is provided as reference and may not be accurate in light of developments since its publication. It is provided on an "AS IS" basis, with no warranties of any kind. Applicable countries and regions Operating System errors and Stop Codes (called Blue Screens in Microsoft Windows, Abends in Novell NetWare, Kernel Panics in UNIX) are often the result of application and/or file corruption that can occur as a result of poor application programming or known bugs that exist in all software. Fixes to these issues are periodically released in software patches known as Service Packs, Fix Packs, or Hot Fixes. However, there are instances when errors and Stop Codes may indicate a hardware source or problem. The following lists detail the most common hardware-related error codes and actions to take when they occur. Note: If IBM hardware has recently been added or changed or if hardware errors (during POST/Startup) are occurring with the OS errors, please refer to the appropriate IBM hardware section for troubleshooting. Trap errors under IBM OS/2 Warp: There are a maximum of 255 possible traps. Trap errors consist of interrupts and exceptions. An interrupt is an event external to the processor that can occur at random times during system operation. An exception is a special condition which is detected by the processor during the execution of instructions. Exceptions only occur when the processor is executing instructions. Traps 0 through 16, with the exclusion of Trap 2, are special exceptions that are detected by the processor. If they occur, the processor takes the appropriate action according to the instructions in the interrupt handler routine of your operating system. The exception handler can vary widely according to the software vendor. Trap 2 is a non-maskable interrupt (NMI) error indicating a catastrophic system failure. Traps 17 through 31 are exceptions reserved by Intel. Traps 32 through 255 are maskable interrupts that are user defined. A summary of the traps is shown below: Trap Number: TRAP Code (Hex): Description: Explanation: 0 0000 Divide By Zero Error An application program attempted to divide a number by zero. Contact software support. 1 0001 Debug Exception Contact software support. 2 0002 NMI Interrupt An NMI interrupt is generated by the system when a catastrophic error