Question Echo %cd% Change In Behaviour?

NeilM

New Member

• Apr 27, 2017

• #1

Good afternoon,

I am currently developing in Progress V8.3B on windows 10 (winver 1703) Post the Windows 10 creators update.

Until recently the following piece of code was working fine.

def var a as char format "x(70)".

input through "echo %cd%" no-echo.
import unformatted a.
input close.

message a. pause.

It would return the directory path.

If I run that same piece of code on a progress session on a Windows Server 2012 R2 running Progress 8.3B it would return a "J:\".

If I run OS-COMMAND("echo %cd%") on my windows 10 (winver 1703) I would get back "C:\testcode".

I am perplexed and a little bit concerned to be honest.

 

Last edited: May 9, 2017

Stefan

Well-Known Member

• Apr 27, 2017

• #2

Your issue looks very similar to OpenEdge 10.2A - INPUT THROUGH set does not work after Windows Update 1703 on Windows 10

 

NeilM

New Member

• Apr 27, 2017

• #3

Eek it does look depressingly similar.

I am not sure how embedded INPUT THROUGH is, but I have used it quite a lot. Obviously the Windows Server is fine for now, but a change like this could sneak under the radar.

Unfortunately I use my Surface Pro for development on this project. I may have to code around the problem, and reduce usage of INPUT THROUGH. Given the age of the Progress 8.3 I am not completely sure of my options.

 

TomBascom

Curmudgeon

• Apr 27, 2017

• #4

Did you say 8.3? And "currently developing"? In the same sentence?

And yet you are somehow running Windows 10... on a Surface Pro.

My head is going to explode.

 

RealHeavyDude

Well-Known Member

• Apr 27, 2017

• #5

How did you manage to install Progress V8.3B on Windows 10 ( or Windows 7+ for that matter )?

Just curious.

 

TomBascom

Curmudgeon

• Apr 28, 2017

• #6

FWIW I just happen to know that v6 runs on both. It was copied though. Not "installed".

 

TomBascom

Curmudgeon

• Apr 28, 2017

• #7

And nothing even vaguely resembling "development" is takes place - it exists solely to enable migrations and upgrades.

 

NeilM

New Member

• Apr 28, 2017

• #8

Unfortunately I don't get to pick the versions of Openedge I get to work on, 8.3 is the version that has chugged along merrily for years at this company and has worked for them. I have come in to pick up the work and I hope to upgrade them this year.

However the point in question is the issue with the creators update, and Progress have acknowledged that it has caused problems, seemingly on versions 11.* as well.

INPUT THROUGH issue on Windows 10 Winver 1703 OS Build 15063.520 Openedge 8.3B - Forum - OpenEdge Development - Progress Community

 

NeilM

New Member

• Apr 28, 2017

• #9

TomBascom said:

Did you say 8.3? And "currently developing"? In the same sentence?

And yet you are somehow running Windows 10... on a Surface Pro.

My head is going to explode.

Click to expand...

Progress just works, it is a great strength and weakness.

 

RealHeavyDude

Well-Known Member

• May 2, 2017

• #10

Yes, you are right in that Progress running almost everywhere under almost all conditions, even in extremely hostile environments, is a great strength of Progress. Nevertheless, I am just surprised that somebody is still running 8.3 on a modern operating system.

Heavy Regards, RealHeavyDude.