Ghost: Error w sreshell.exe

Archive
1

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

2

First a couple of questions about things that you may have already done or accounted for.

  

   1) How much memory is on the machine when you are booting the System Recovery Disk (SRD)?

   2) Are you using the latest drivers for your NIC?

   3) What are your machine specs?

3

   1) How much memory is on the machine when you are booting the System Recovery Disk (SRD)?

 2GB

   2) Are you using the latest drivers for your NIC?

Of course.

   3) What are your machine specs?

Athlon64 X2 4400+

Biostar N68PA-M2T

NVidia Chipset

 

Typical Symantec response - no help at all.  Because of the long delay before a response (also typical of Symantec), I've had a chance to try it on 3 other machines. Didn't get the network up and going on any of them, either automatically or manually adding NIC drivers. 

 

That's enough for me. I've seen this happen on other Symantec products, the support for which dwindled and vanished b4 Symantec dropped the app and left users in the lurch.  I'm going back to messing w/ Aconis and BartPE boot discs, if not Image for Windows.

 

You didn't want my business anyway.  I'm a bad user.  I actually expect results.

 

J_G

Message Edited by jim_geneva on 10-09-2008 04:48 PM
4

Sorry, the response has been so long for you.  I usually only get wind of things like this when they are old.  I asked questions only because the initial posts did not contain enough information to even make an intelligent suggestion.  From your answer you have eliminated one possibility that I am aware of that could cause startup problems -- you have sufficient memory.  But I am still in the dark about the NIC.  On your motherboard I'm a little better off, but the information is apocryphal.  Google did not turn up a manufacturers site for me for your motherboard.  I do know that we do not have anything like that in our team. 

 

Still I need to ask another question.  Are you using a 64-bit or 32-bit NIC driver?  Even though you OS may be 64-bit, the SRD environment is 32-bit.  Hence the drivers used in the SRD have to be 32-bit.

 

Message Edited by Johan_Jeffery on 10-09-2008 06:13 PM
5

Greetings,

 

When trying to boot into a lights out restore session, I get the following error:

Error in sreshell.exe.  The instruction at ...  The memory could not be read.

 

Any thoughts?

 

JG

Message Edited by jim_geneva on 10-04-2008 04:46 AM
6

SreShell.exe Application error when using my recovery disk.

 

Referred memory at 0x00000056 memory could not be read.   As soon as I clicked OK, system rebooted and the message came up again.
I then ignored  the message and ghosted back to the chosen date and everything is working fine.
 
Perhaps that is what's causing my "unknown system status" message in NSR??
I have 4gigs of ram running vista shows 3 however memory is not an issue. I've used this several times during beta testing and have had no problems before now.
Any help would be appreciated.
Running 32bit vista SP1 with  AMD x2 4400 
7

I just tried booting the Ghost 14 Recovery CD on a brand new Dell Inspiron 530, with 4gb memory, and got similar error in sreshell.exe:

...instruction referred to memory at 0x00000058.  The memory could not be read.

 

The "solution" I was given by online Symantec chat was to physically remove 2 gb of memory from the pc (so max is now 2gb), and try again.

 

I haven't done that yet, but am kind of flabergasted at the workaround.

 

Anyone shed any light on this?  (I plan to pull memory next week, but I don't want to have to do this anytime I need the recovery cd!)

 

8

Let me know if this is the right solution. That sounds a little phony to be. If one can’t have more than 2gigs to run a program, they should let everyone know, period!

9

Of course it wasn't the right solution.  I removed 2 sticks of memory and booted from the SRD cd and the got the very same error message.

 

I re-contacted LiveChat and they connected remotely to the pc and took some system logs etc. and said they would forward that to the Symantec analysts.  I am supposed to wait a week and then "call again" with a case number I was given.

 

I'll keep you posted in 7 days.

10

Thanks for the update. Sounds like they really don't know either. Bogus solution of removing ram!  What good is 4,6, or even 8gigs of ram if this program would limit the memory.

Not a good sign. NSW2009P is still using the old NSR so hopefully there will be new testing soon.

TIA

11

On my 5th LiveChat I was instructed to download the ...SRDandProd.iso file from their ftp site and try again.  I did that, burned a cd and this time it booted ok and worked.

 

The first LiveChat I was told to download the ...SRDonly.iso file, which is either bad or my download was corrupted.  My advice is avoid that one.

 

At least it is now working.

12

MY DAY

 

1) Bought Ghost 14 - v. expensive but the shop didn't have Acronis

2) Made a C: image on USB2 HDD - quite fast

3) Made a recovery CD

4) Downloaded an update from Symantec

5) Deleted first backup image, made another C: image in same location

6) Tried to boot using above recovery CD : "SreShell error" - USB Drive not recognised

7) Checked this forum

8) Made a second recovery CD whilst in Lotus Posture chanting OM

9) This booted fine without unintelligible error message

 

My conclusion is that the Ghost Recovery CD works fine so long as you sit in Lotus Position chanting OM

13

Hello all!

 

I had this problem after reading all this posts, I tried something else and it helped me out.

 

My recovery disk was used couple times, and it probably took some of the settings and saved in it.

 

 

So, I burned a brand new recovery disk from my saved ISO file, also a deleted all the partition from my system, and it worked  right away!!!

 

It's worth to try, let me know if helped you also.

 

Good luck!!

 

14

I may or may not have gotten farther with this.  After some research it looked like it wasn't loading my NIC driver, so I added it.  Now, however, I get the following error: Process x:\windows\system32\wpeutil reported an error executing the requested operation.  This is repeatable - all I have to do is try to turn on networking services.  What's going on?  The reason I moved away from Acronis TI WS was dwindling/no network support on boot disks / partitions.  Now it seems Ghost is having the same problems...