Hi Laurie,

 

Just got back from seeing my new family, I didn't mention before that they
are in Russia. Mum and bub going well. Soon we will all be together under
the one roof.

 

I must admit that I have avoided using WP Shell with Windows. Where DP is
particularly well behaved in its access to the file system, I think Shell
makes some lower level calls, to do some of its more creative task
switching, and keyboard processing and perhaps some of those calls bypass
the high levels calls and that could be causing a problem.  Even WP did some
creative things with hardware, just one minor example that comes to mind was
the F5-F5 to bring up the file list of the last accessed folder, which never
worked with the 32-bit version of Windows.

 

Also from my memory, Shell needs to use quite a bit of Expanded Memory, and
perhaps you are having troubles with the default amounts of Expanded Memory
that Windows gives it, and it could be with Microsoft Networking it adds an
extra burden on it. I used to be quite a whiz at Extended and Expanded
Memory and techniques for managing it, but this was a lifetime ago. 

 

Regards

 

Brian

 

 

 

 

 

 

  _____  

From: [email protected]
[mailto:[email protected]] On Behalf Of Laurie Corvacho
Sent: Friday, 30 September 2011 4:23 AM
To: [email protected]
Subject: Re: [Dataperf] Problems with Shell and XP Pro/Windows Server 2003

 

Hi, Brian,

 

Congratulations!!! I hope all of you are doing wonderfully - I hope you all
(especially Mum) get some rest! 

 

The Netware server and the Windows server are strictly functioning as file
servers, as you guessed.  I am just wondering if the Microsoft client messes
with the DOS session somehow, such as taking more memory, etc.  (For the
Netware server, we had been using the Netware client, not the Microsoft
client for Netware.)  (I have tried using both cmd.exe and command.com, and
they both mess up equally.)

 

Also, the macro works fine for a while before it crashes, and I would think
that if it were a rights issue, it wouldn't be able to work at all.  (It
goes through a list of files on the screen, doing something to each one,
depending on several criteria.)  Depending on the length of the list, it
would eventually stop while running from the Netware server also, but this
would be after going through several pages of the list, and it never typed
garbage like it is doing now - it would just stop.  Now it crashes after
about the 3rd to 5th item in the list. I probably have a memory leak (or
even several) somewhere in my macro due to my programming ignorance, but
before it was manageable - now it is not.  Also, I am running the macro as
administrator, so I wouldn't think there should be any permissions issues.

 

Do you have any suggestions?

 

Thanks, and take care of your lovely family!!

 

Laurie

 

 

 

 

 

 

 

----- Original Message ----- 

From: Brian <mailto:[email protected]>  Hancock 

To: [email protected] 

Sent: Thursday, September 29, 2011 5:11

Subject: Re: [Dataperf] Problems with Shell and XP Pro/Windows Server 2003

 

Hi Laurie,

 

When you say running from a Netware Server or running from a Windows 2003
Server, I presume you mean that you are using these as file servers, and you
are actually running the applications on some client machine.  I really
suspect this is what you are doing, and if so I do not think it is simply a
memory issue as you are not executing any DP code in the memory space of
these servers but only in the client. If the client is exactly the same as
when you were previously using Netware then I would think it is either a
locking, file handles, permissions issue or some other vaguery of the
Windows networking

 

By the way everyone, I have just become a daddy again. Mum and baby boy
(Robert) are doing well, 3.5kgs (7lb 12oz), 53cm (almost 21 inches), lots of
dark hair (no metric-imperial conversion :-)), blue eyes. (likewise). 

 

Like 2 of my other 3 boys he was late, but this one needed a c-section. 

 

Bye

Brian

 


  _____  


From: [email protected]
[mailto:[email protected]] On Behalf Of Laurie Corvacho
Sent: Thursday, 29 September 2011 12:03 PM
To: [email protected]
Subject: Re: [Dataperf] Problems with Shell and XP Pro/Windows Server 2003

 

Hi, Tim,

 

Thanks for your response.  I am already using the /w-50K startup switch,
which had worked fine for years until now.  :-(

 

(You were probably the person who told me about that years ago - thanks!)

 

I'm not sure if it's a memory issue or not, but it just seemed to me that it
might be.  The only other time I have had a problem like this, I finally
figured out that the PC that it was happening on had a non-Intel CPU that
was apparently overheating, and that was somehow causing it to suddenly
whack out while running complicated macros.  However, this is now happening
on all the PCS on my (Windows 2003) network, not just one.

 

Do you have any other ideas of things it might be?

 

Thanks!!

 

Laurie

 

 

 

 

 

----- Original Message ----- 

From: Tim Rude <mailto:[email protected]>  

To: [email protected] 

Sent: Wednesday, September 28, 2011 13:57

Subject: Re: [Dataperf] Problems with Shell and XP Pro/Windows Server 2003

 

Laurie,

 

Have you tried using the command line option to increase the memory
available for macro execution?

 

If I'm remembering correctly, the command line was /w-xx where xx is the
number of kb to allocate for the macro processor.

 

Try starting up Shell with the following command line:  mc /w-30 shell

 

See if that makes any difference.

 

Tim Rude

----- Original Message ----- 

From: Laurie <mailto:[email protected]>  Corvacho 

To: [email protected] 

Sent: Wednesday, September 28, 2011 1:45 PM

Subject: [Dataperf] Problems with Shell and XP Pro/Windows Server 2003

 

Hello, all,

 

I have some DP apps that I have been running for years off a Netware file
server with no problems.  Now I have to make them also work on a Windows
2003 server.  (All workstations are running XP Pro.)  When I run them from
the Windows 2003 server, the shell macros for my DP program are crashing,
and I have the impression it is because they are running out of memory in
the DOS window.  What happens is that after a short time running, it starts
typing garbage on the screen instead of what is supposed to be typing, and
shortly thereafter it just freezes the screen and gives up the ghost.

 

The macros are rather large - In the past I have broken some of the macros
up into smaller sub-macro files in order to get them to work when there have
been apparent memory issues, but doing that again doesn't seem to help this
time.

 

All memory settings seem to be the same on the workstations.  The only thing
I can see that seems to be a major difference is the network client.  Does
anyone have any suggestions as to what may be the problem or, more
importantly, how it can be fixed? 

 

Thanks!!!

 

Laurie


  _____  


_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf


  _____  


_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf


  _____  


_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf

_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf

Reply via email to