Re: Program will run in Terminal Session
- From: "G" <nevermind@xxxxxxxxxx>
- Date: Wed, 11 May 2005 09:35:17 +0100
I'll have to try replacing the memory (2GB).
Is there a different memory allocation for a Terminal Session that allows
this to work, while on the console it fails with error?
(Is there a way of setting the memory allocation?)
I've got the Run in Seperate Memory Tick Box on Start>Run - no difference.
I've tried Run in Compatibility Mode (run as NT4 to see if it makes a
difference) [regsvr32 %systemroot%\apppatch\slayerui.dll] still the same
error.
Must be a hardware issue if I can't get this to work by changing some
software settings.
"richard" <richard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4D913BED-72DA-47C9-9E60-1FB928660AD2@xxxxxxxxxxxxxxxx
> set it to be run under compatible mode & windows will force it to run in a
> separate memory area.
>
> finally,while i saw this kind of message, i always scan for Taoj first
> then
> replace the memory. causes i don't know how to control the memory
> allocation
> for applications on windows.
>
> "G" wrote:
>
>> Sorry I must have confused the issue here.
>>
>> I actually WANT it to run under console.
>> It's just that it ONLY runs in Terminal Session!
>>
>> Thanks
>>
>> "richard" <richard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:41440431-C4B0-4991-9D5F-1DC88DA17A58@xxxxxxxxxxxxxxxx
>> > it's possible that some "strange" applications must be run under alive
>> > sessions, console included. how's about submit it using console then
>> > keep
>> > the console locked?
>> >
>> > "G" wrote:
>> >
>> >> Running Windows 2000 Server (SP4)
>> >>
>> >> Has anyone seen an issue where an application will only run if you're
>> >> logged
>> >> into the server in a Terminal Service (admin) session?
>> >> I used to be able to schedule this job but now it has to be run
>> >> manually
>> >> through TS as it's always failing with the same error
>> >>
>> >> cstatrpt.exe Application Error
>> >> The instruction at "0x77fcc37c" referenced memory at "0xfffffff8". The
>> >> memory could not be "read"
>> >> Click on OK to terminate the program.
>> >>
>> >> [cstatrpt is the reporting tool for Ipswitch What's Up Gold]
>> >>
>> >> I thought it had cured itself yesterday when everything worked fine on
>> >> the
>> >> server - I just forgot that I also had a Terminal Session still
>> >> connected!
>> >>
>> >> Any ideas?
>> >>
>> >> Many Thanks
>> >>
>> >>
>> >>
>>
>>
>>
.
- References:
- Program will run in Terminal Session
- From: G
- RE: Program will run in Terminal Session
- From: richard
- Re: Program will run in Terminal Session
- From: G
- Re: Program will run in Terminal Session
- From: richard
- Program will run in Terminal Session
- Prev by Date: Windows Server 2003 reboots, but no virus??
- Next by Date: Hardware RAID 5 & Dynamic Disk
- Previous by thread: Re: Program will run in Terminal Session
- Next by thread: Remote Installation Services and drivers
- Index(es):
Relevant Pages
|