Vista: RUN Command results in "Program too big to fit in memory"

I have an ageing Clipper 5.01 application that has been running
without too many problems on every variation of Windows until Vista.

But in Vista I have a rpoblem when I try to RUN another program. On
all previous Windows versions of NT descent (NT/2000/XP) I do a RUN
("cmd /c "+<another program> ), which causes the external program to
run while the Clipper program pauses until it ends.

In Vista this results in a "Program too big to fit in memory", no
matter what I try.

Does anybody have a similar experience? Any suggestions?

Dick

PS I know that swpruncmd() instead of RUN might be a solution, but at
this stage of the lifecycle of the program I really do now want to
make a change like this

Dear tmkoster:

<tmkoster@gmail.com> wrote in message
news:f7008558-4fad-4e36-ad28-35e72c70015e@e6g2000prf.googlegroups.com...
> I have an ageing Clipper 5.01 application that has
> been running without too many problems on every
> variation of Windows until Vista.
...
> In Vista this results in a "Program too big to fit in
> memory", no matter what I try.

What have you tried?  Is the program via desktop shortcut, batch
file, or what?  What environment variables / values are present
when the application runs?  What command line parameters do you
pass (if any)?

David A. Smith

On Sun, 30 Mar 2008 09:48:39 -0700 (PDT), tmkoster@gmail.com wrote:

>I have an ageing Clipper 5.01 application that has been running
>without too many problems on every variation of Windows until Vista.
>
>But in Vista I have a rpoblem when I try to RUN another program. On
>all previous Windows versions of NT descent (NT/2000/XP) I do a RUN
>("cmd /c "+<another program> ), which causes the external program to
>run while the Clipper program pauses until it ends.
>
>In Vista this results in a "Program too big to fit in memory", no
>matter what I try.
>
>Does anybody have a similar experience? Any suggestions?
>
>Dick
>
>PS I know that swpruncmd() instead of RUN might be a solution, but at
>this stage of the lifecycle of the program I really do now want to
>make a change like this

Hi Dick,

Are you using Blinker?

Is the application linked in extended/protected mode?

Regards,

Ross McKenzie
ValuSoft
Melbourne Australia

valusoft AT optusnet DOT com DOT au

Hello Ross

No - this is not with Blinker but with the original RTLINK

Dick

On Mar 31, 4:29 am, NoJunk_valus...@optusnet.com.au (Ross McKenzie)
wrote:
> On Sun, 30 Mar 2008 09:48:39 -0700 (PDT), tmkos...@gmail.com wrote: 
> 
> 
> 
> 
> 
>
> Hi Dick,
>
> Are you using Blinker?
>
> Is the application linked in extended/protected mode?
>
> Regards,
>
> Ross McKenzie
> ValuSoft
> Melbourne Australia
>
> valusoft AT optusnet DOT com DOT au

Hello David

The propgram that is being invoked is actually included in a BAT file;
the BAT file is invoked with a number of parameters. However, ths
issue seems to be the invocation om the "cmd" command interpreter,
regardless of the actual program that is being invoked.

I have since seen that there are differences in the memory layout as
displayed with the MEM command - but I don't have access to the VISTA
system at this moment, so will post that later this w

Dick Koster

On Mar 31, 12:18 am, "N:dlzc D:aol T:com \(dlzc\)" <dl...@cox.net>
wrote:
> Dear tmkoster:
>
> <tmkos...@gmail.com> wrote in message
>
> news:f7008558-4fad-4e36-ad28-35e72c70015e@e6g2000prf.googlegroups.com...
> 
> ... 
>
> What have you tried?  Is the program via desktop shortcut, batch
> file, or what?  What environment variables / values are present
> when the application runs?  What command line parameters do you
> pass (if any)?
>
> David A. Smith

Dear tmkos...:

On Mar 31, 1:45=A0pm, tmkos...@gmail.com wrote:
> Hello David
>
> The propgram that is being invoked is actually
> included in a BAT file; the BAT file is invoked
> with a number of parameters.

=46rom command line, from desktop, from shortcut...?

> However, ths issue seems to be the invocation
> om the "cmd" command interpreter, regardless of
> the actual program that is being invoked.

Doh!  Command.com should be invoked to run a DOS program, not cmd.exe.

> I have since seen that there are differences in
> the memory layout as displayed with the MEM
> command - but I don't have access to the VISTA
> system at this moment, so will post that later
> this w

Good luck.

David A. Smith

David,

Actually, I have been using "cmd" instead of "command" for many years
now when running under W2K or XP. Can't remember any more why I
switched, but it probably had to do with better functionality than
"command"; and it has always worked fine before Vista.

If you google on "cmd versus command" you get some interesting
discussions on the merits of cmd.

Anyway, I will give it a try

Thx

Dick
On Mar 31, 11:16 pm, dlzc <dl...@cox.net> wrote:
> Dear tmkos...:
>
> On Mar 31, 1:45 pm, tmkos...@gmail.com wrote:
> 
> 
>
> From command line, from desktop, from shortcut...?
> 
>
> Doh!  Command.com should be invoked to run a DOS program, not cmd.exe.
> 
>
> Good luck.
>
> David A. Smith