IBM x345 and Ghost 7.0

[DaliRides]

I have an x345 server and am having trouble pushing down a ghost image. I have the image created, I can connect to the Multicast session, but once connected and I hit send, the image is not pushed down to the server. Eventually I get a 'connection timed out' message on the multicast server.

I have the following:
System ROM BIOS – 1.13
Raid 5i BIOS – 6.10.24 (RAID 0+1)
Diagnostics – 1.04
Hard Drive FW – 1.15 (S27P)
Integrated Systems Management Processor – 1.07

I have tried using the -fni switch as well and that did not work either.

My AutoExec.bat is:
@echo off
prompt $p$g
\net\netbind.com
MOUSE.COM
cd \ghost
echo Loading...
GHOST.EXE -fni -fdsp

My config.sys is:
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos
DEVICE=\net\e1000.dos

 

[catorze]

The Ghost boot diskette needs EMM386 to work with the x345.

 

[DaliRides]

Would the proper way to do this be adding the following to config.sys?

device=himem.sys
device=emm386.exe
dos=umb
files=100
buffers=30

so then my config.sys should look like this in total:
device=himem.sys
device=emm386.exe
dos=umb
files=100
buffers=30
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos
DEVICE=\net\e1000.dos

I supposed I would also need to copy himem.sys and emm386.exe to the root of the floppy disk?

 

[DaliRides]

OK, so I tried it like I had listed above. When my Config.sys includes the call for himem.sys the boot freezes. When it does not include it I get the emm366.exe not loaded error - No XMS Manager loaded.

Hmmmm......

 

[DaliRides]

Well, now I replaced my himem.sys from the one that is included with W2K, with one from the 6.22 DOS bootdisk that gets created from bootdisk.com. I no longer have the freeze, but I still get the error in reference to no XMS Manger loaded.

 

[DaliRides]

OK, Himem and emm386 are loaded now, but I am getting a different error.

After they load up, the Ghost portion starts to load.
I get an error stating that there is an Unsupported Memory Manger present. Unable to initialize proteced mode services. Failure Driver did not load.

So now I have no network. As of now my config.sys looks like this:
device=himem.sys
device=emm386.exe AUTO
dos=umb
files=100
buffers=30
DEVICE=\net\protman.dos /I:\net
DEVICE=\net\dis_pkt.dos
DEVICE=\net\e1000.dos

I have no idea what to do now....Anyone?

 

[catorze]

Yuo enabled emm386, but are not using the additional memory space to offload the other devices so the kernel can use more conventional memory. Change the DEVICE statements (for the network devices) to DEVICEHIGH.

 

[DaliRides]

It is still not working. My config.sys now looks like this:
device=himem.sys
device=emm386.exe AUTO
dos=umb
files=100
buffers=30
DEVICEhigh=\net\protman.dos /I:\net
DEVICEhigh=\net\dis_pkt.dos
DEVICEhigh=\net\e1000.dos

When I boot to the disk I get the following issues:
I still get the same errors as listed earlier in the thread realted to Unsupported Memory Manger. To be more specifc I also get the following:
Remove all memory Managers from the configuration
Driver did not load, NDIS Environment invalid
Error 33: Unable to bind

Again, this only happens when himem and emm386 are in use. Otherwise the disk boots fine but GHost doesn't work.

 

[catorze]

What version of BIOS are you running? EMM386 support was added in v1.05.

 

[DaliRides]

I am running the followign BIOS and FW versions:
• System ROM BIOS – 1.13
• Raid 5i BIOS – 6.10.24
• Diagnostics – 1.04
• Hard Drive FW – 1.15
• Integrated Systems Management Processor – 1.07

 

[DaliRides]

Also, if I try to pull the image of the IBM server I get the following error:

Error reading FILE_VOLUME MFT record

 

[DaliRides]

Upgraded to version 7.5 CE and still am having the same issue.

 

[catorze]

I don't see the RAID driver in your Config.sys.