We always dothe sameprocedurewithGhost8.0andPXEserver, in thiscase,the computer startsand executes theinstructionsofPC-DOSbutwhenloadghost.exeocurrs the 35016 error ABORT no such file directory (ENOENT)
I thinkanymodificationcanbeintroducedintothestorage system
mpedreira, I believe I am having the same problem you did. The 35016 error you describe is symptomatic, the initial error seems to be:
ERROR: Unable to control A20 line!
XMS Driver not installed.
Googling this message gives some suggestions for modifying the way himem.sys is called, specifically by adding "/M:1" to the end of the line in config.sys that calls it. However, in my configuration, the file isn't called by config.sys at all, but by a file in C:\TFTPBOOT called "ghost.sys", which I guess is a netbootdisk image file. Attempting to edit this file directly is useless, it will just cause the connection to hang at "transferring image file".
I guess the next step is to download netbootdisk and hope it has some good tools for modifying an existing boot disk, rather than building a new one. And once you get that far, there is no guarantee that the recommended change will work for the 6320.
Does anybody have any insight into this issue? We can't be the only two people who experienced this problem.
There is a nifty little utility in GSS 2.0 called the 3Com Boot Image Editor. (C:\Program Files (x86)\3Com\Boot Services\ImgEdit.exe) Use this to open ghost.sys (or whatever you named your Ghost boot image, it most likely lives in C:\TFTPBOOT). Select Config.sys, File, Edit. On the line that says "Device=himem.sys", add "/machine:1" to the end. Clicking OK and Exit will save changes.
Congratulations, you should now be able to ghost a 6320.
mpedreira
1 Message
0
May 10th, 2011 11:00
I also I have boot problems whit e6310
We always do the same procedure with Ghost 8.0 and PXE server, in this case, the computer starts and executes the instructions of PC-DOS but when load ghost.exe ocurrs the 35016 error ABORT no such file directory (ENOENT)
I think any modification can be introduced into the storage system
Hurr Durr
2 Posts
0
June 9th, 2011 05:00
mpedreira, I believe I am having the same problem you did. The 35016 error you describe is symptomatic, the initial error seems to be:
ERROR: Unable to control A20 line!
XMS Driver not installed.
Googling this message gives some suggestions for modifying the way himem.sys is called, specifically by adding "/M:1" to the end of the line in config.sys that calls it. However, in my configuration, the file isn't called by config.sys at all, but by a file in C:\TFTPBOOT called "ghost.sys", which I guess is a netbootdisk image file. Attempting to edit this file directly is useless, it will just cause the connection to hang at "transferring image file".
I guess the next step is to download netbootdisk and hope it has some good tools for modifying an existing boot disk, rather than building a new one. And once you get that far, there is no guarantee that the recommended change will work for the 6320.
Does anybody have any insight into this issue? We can't be the only two people who experienced this problem.
Hurr Durr
2 Posts
1
June 9th, 2011 10:00
Fixed.
There is a nifty little utility in GSS 2.0 called the 3Com Boot Image Editor. (C:\Program Files (x86)\3Com\Boot Services\ImgEdit.exe) Use this to open ghost.sys (or whatever you named your Ghost boot image, it most likely lives in C:\TFTPBOOT). Select Config.sys, File, Edit. On the line that says "Device=himem.sys", add "/machine:1" to the end. Clicking OK and Exit will save changes.
Congratulations, you should now be able to ghost a 6320.